From: Patrick Mansfield <patmans@us.ibm.com>
To: Christian Staudenmayer <the_sithlord@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic (2.5.67-ac1)
Date: Mon, 14 Apr 2003 14:47:02 -0700 [thread overview]
Message-ID: <20030414144702.A18565@beaverton.ibm.com> (raw)
In-Reply-To: <20030414192548.48370.qmail@web12108.mail.yahoo.com>; from the_sithlord@yahoo.com on Mon, Apr 14, 2003 at 12:25:48PM -0700
On Mon, Apr 14, 2003 at 12:25:48PM -0700, Christian Staudenmayer wrote:
> hello,
>
> (i've posted a similar message before but i've been told to add the whole error
> message, so here it is. sorry about that, but typing screenfulls of hex numbers
> makes me feel like a geek but it also makes my head hurt ;)
>
> the 2.5.67 kernel boots fine here, but the -ac1 patch to it ends up in
> a kernel panic.
> here are the last 25 lines of the error, i don't know if there is more above of it,
> scrolling up didn't work... (btw there can be typos in it ;)
This stack looks very much like the problem with scsi queue plugging
behaviour and the removal of blk_empty_queue. It is not always hit, there
could easily be something in ac that changed the timing.
[If so] this is not a problem in the ac kernel, even though you only hit
it after adding the ac patch.
James B sent in a fix, it's included in the current bk tree, the changelog
says:
fix scsi queue plugging behaviour
Following recent changes removing blk_queue_empty(), we were
incorrectly plugging the queue some times (most often as part of
the SCSI scan process). This was causing a non-deterministic panic
in the scan code because a destroyed queue was sometimes being
unplugged and run.
Or see this for log and patch:
http://linux.bkbits.net:8080/linux-2.5/cset@1.971.103.27?nav=index.html|ChangeSet@-2d
The patch won't apply cleanly on top of 2.5.67.
-- Patrick Mansfield
prev parent reply other threads:[~2003-04-14 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:25 Christian Staudenmayer
2003-04-14 21:47 ` Patrick Mansfield [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=20030414144702.A18565@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=the_sithlord@yahoo.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
all inboxes | Powered by JetHome®