From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] __write_lock_failed() oops
Date: Thu, 5 Sep 2002 01:59:24 -0700 [thread overview]
Message-ID: <20020905085924.GE888@holomorphy.com> (raw)
In-Reply-To: <20020905084502.GD888@holomorphy.com>
On Thu, Sep 05, 2002 at 01:32:40AM -0700, William Lee Irwin III wrote:
>> (gdb) p/x $eax
>> $25 = 0xc0331ca0
>> (gdb) p &tasklist_lock
>> $27 = (rwlock_t *) 0xc0331ca0
On Thu, Sep 05, 2002 at 01:45:02AM -0700, William Lee Irwin III wrote:
> The NMI oopser is going here as well (nmi_watchdog=2 for extra safety)
> so I suspect the tasklist_lock semantics are behaving badly. But it's
> not easily reproducible enough to test a quick attempt at a fix if it
> can't be recognized a priori.
> This is literally so difficult to reproduce it hasn't been seen in 2
> releases. kgdb is still going and dhowells is helping me fish stuff
> off the stack.
According to dhowells' analysis, the NMI oopser fired while do_fork()
spun on the tasklist_lock. The contention on the bloody thing is so bad
the kernel cannot survive the NMI oopser. Something is majorly FITH here.
GRRRR!!!
Cheers,
Bill
next prev parent reply other threads:[~2002-09-05 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 8:03 [BUG] __write_lock_failed() oops William Lee Irwin III
2002-09-05 8:42 ` Andrew Morton
2002-09-05 8:32 ` William Lee Irwin III
2002-09-05 8:45 ` William Lee Irwin III
2002-09-05 8:59 ` William Lee Irwin III [this message]
2002-09-05 9:08 ` William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020905085924.GE888@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.