Re: 2.6.1-mm4

From: Prakash K. Cheemplavam (PrakashKC_at_gmx.de)
Date: 02/12/04

  • Next message: RANDAZZO_at_ddc-web.com: "Semaphore with timeout...." 
    Date:	Thu, 12 Feb 2004 14:15:43 +0100
To: Valdis.Kletnieks@vt.edu

    Valdis.Kletnieks@vt.edu wrote:
    > On Thu, 12 Feb 2004 08:30:54 +0100, "Prakash K. Cheemplavam" said:
    >
    >
    >>Well, I don't know whether my system actually locks up, it is like it
    >>seems the log gets flooded (when I wait long enough) but I cannot do
    >>anything with the system at that point, ie it seems like frozen.
    >
    >
    > I don't think anybody's going to be able to shoot that bug report without more
    > info. "seems like frozen" doesn't give us much to go on. Does the machine
    > still ping/ssh/etc on the net? Is it totally locked up? Any disk activity
    > lights left on/flickering, indicating life? Can you get a serial console or
    > kgdb-ethernet or something to see if there's an oops/panic?

    Hmm, I'll test those bk-snapshots and when it locks up, I'll try to
    access the pc form another machine. As I said it seems (when I wait long
    enough, within the first minute nothing in the log survives the reboot,
    probably due to reiserfs journalling) the log writes the oops I posted
    in the first message infinite times.

    > Well, the 53.36 drivers are rock-solid on my Dell laptop with a GeForce4 440Go
    > and the 2.6.3-rc1-mm1 kernel. There very well may be bugs in there, but
    > they're not ones I can replicate or diagnose...

    Maybe it is a nforce2 issue then. I think it is ACPI specific. I'll also
    try compiling latest kernel without ACPI and report back.

    Thanx,

    Prakash

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: RANDAZZO_at_ddc-web.com: "Semaphore with timeout...."

    Relevant Pages

    • Re: panic: sorele
      ... > Sleep locks: ... > ACPI global lock ... > securelevel mutex lock ... > vm map sleep mutex ...
      (freebsd-current)
    • [patch] ACPI: reduce code size, clean up, fix validator message
      ... that is because the lock validator turns itself off after the first ... But the ACPI obfuscation layers use the same spin_lock_initsite to ... initialise two not-the-same locks, so lockdep decides those two locks ... * Allocate the memory for a spinlock and initialize it. ...
      (Linux-Kernel)
    • diagnosing hard-locks [was memtest+ wont load]
      ... crunching job running overnight. ... These locks are particularly frustrating as they leave no trace in the ... the logs just stop until they come up from the reboot. ... related to that acpi stuff as it seems to happen a lot when I'm NOT ...
      (Debian-User)
    • Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel
      ... >> User space locking can only guarantee atomic operations in user space. ... > Sorry but I completely fail to see this argument., locks it, then hangs. ... Process A opens an attribute and writes to it. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: robust futex deadlock detection patch
      ... locks across the check for deadlocks and into __down_interruptible. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)