From: Janet Morgan <janetmor@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <piggin@cyberone.com.au>
Subject: Re: 2.5.63 BUG in deadline-iosched.c
Date: Thu, 27 Feb 2003 19:02:20 -0800 [thread overview]
Message-ID: <3E5ED13B.3E92E287@us.ibm.com> (raw)
In-Reply-To: 20030227144749.48e8e0f1.akpm@digeo.com
Andrew Morton wrote:
> Janet Morgan <janetmor@us.ibm.com> wrote:
> >
> > I got this on 2.5.63 while running the "find" command:
> >
> > kernel BUG at drivers/block/deadline-iosched.c:145!
> > invalid operand: 0000
> > CPU: 3
> > EIP: 0060:[<c026f8a1>] Not tainted
> > EFLAGS: 00010046
> > EIP is at deadline_find_drq_hash+0x41/0xb0
> > eax: f76fe060 ebx: f76fe058 ecx: f76fe060 edx: 00000000
> > esi: f76fe060 edi: f76fe044 ebp: f76fe050 esp: f7e27c88
> > ds: 007b es: 007b ss: 0068
> > Process pdflush (pid: 16, threadinfo=f7e26000 task=c3b39300)
> > Stack: 010d7ce6 00000000 f7fd2ae0 f7fd2ae0 f7fd2ae0 f7747f80 c026fbc9
> > f7747f80
> > 010d7ce6 00000000 f7747f80 00000000 f7759000 f7759000 00000008
> > c026a438
> > f7759000 f7e27cf8 f7fd2ae0 c026cc58 f7759000 f7e27cf8 f7fd2ae0
> > 010d7ce6
> > Call Trace:
> > [<c026fbc9>] deadline_merge+0x49/0x120
> > [<c026a438>] elv_merge+0x18/0x30
> > [<c026cc58>] __make_request+0xb8/0x440
>
> Nick, could this be caused by a stale next_drq[] entry?
>
> If so,
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.63/2.5.63-mm1/broken-out/deadline-dispatching-fix.patch
>
> is designed to fix it.
Thanks Andrew. 2.5.63-mm1 fixes the problem.
next prev parent reply other threads:[~2003-02-28 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 20:11 2.5.63 BUG in deadline-iosched.c Janet Morgan
2003-02-27 22:47 ` Andrew Morton
2003-02-28 3:02 ` Janet Morgan [this message]
2003-02-28 15:38 ` Nick Piggin
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=3E5ED13B.3E92E287@us.ibm.com \
--to=janetmor@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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