From: Anthony Campbell <ac@acampbell.org.uk>
To: linux-kernel@vger.kernel.org
Cc: sct@redhat.com
Subject: Re: Total lockups using ext3
Date: Thu, 7 Feb 2002 09:07:17 +0000 [thread overview]
Message-ID: <20020207090717.GB3899@debian.local> (raw)
In-Reply-To: <20020201181048.GA3104@debian.local> <20020201184123.A16610@redhat.com> <3C5AFCCA.362C4F3E@zip.com.au>
In-Reply-To: <3C5AFCCA.362C4F3E@zip.com.au>
On 01 Feb 2002, Andrew Morton wrote:
> "Stephen C. Tweedie" wrote:
> >
> > The fact that it always happens when the modem is on also suggests that
> > this is not a filesystem problem.
>
> mm.. There are known scheduling-inside-spinlock bugs in the PPP
> driver. Paul is working on these at present. This will cause
> deadlocks on SMP. Anthony seems to be running uniprocessor, but
> bad things could still happen.
>
> It'd be interesting to enable the local-apic-on-uniprocessor
> and io-apic-on-uniprocessor options, then boot with the
> `nmi_watchdog=1' LILO option, see if you can get an NMI oops
> backtrace.
>
>
I discovered recently that, at least in 2.4.17, I had included SMP in
the configuration by mistake (in fact, I think it happens by default).
Eliminating it seems to have solved the lockups, or at least made them
much less frequent.
Please cc any replies to me as I'm not on the list at present.
Anthony
--
Anthony Campbell - running Linux GNU/Debian (Windows-free zone)
For an electronic book (The Assassins of Alamut), skeptical
essays, and over 150 book reviews, go to: http://www.acampbell.org.uk/
Our planet is a lonely speck in the great enveloping cosmic dark. In our
obscurity, in all this vastness, there is no hint that help will come
from elsewhere to save us from ourselves. [Carl Sagan]
prev parent reply other threads:[~2002-02-07 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020201181048.GA3104@debian.local>
[not found] ` <20020201184123.A16610@redhat.com>
2002-02-02 19:22 ` Total lockups using ext3 Anthony Campbell
[not found] ` <3C5AFCCA.362C4F3E@zip.com.au>
2002-02-07 9:07 ` Anthony Campbell [this message]
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=20020207090717.GB3899@debian.local \
--to=ac@acampbell.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox