From: Andrew Morton <akpm@osdl.org>
To: Rui Saraiva <rmps@joel.ist.utl.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-rc1-mm2: 3 dumps at __make_request, system freeze
Date: Thu, 4 Mar 2004 14:26:38 -0800 [thread overview]
Message-ID: <20040304142638.47b00812.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403042127580.28900@joel.ist.utl.pt>
Rui Saraiva <rmps@joel.ist.utl.pt> wrote:
>
> On Thu, 4 Mar 2004, Andrew Morton wrote:
>
> > Rui Saraiva <rmps@joel.ist.utl.pt> wrote:
> > >
> > > Yesterday I got these 3 dumps (on dmesg) while compiling (on ext3 fs) the
> > > kernel and some other userland utilities.
> >
> > Could you please add this?
> >
> > --- 25/drivers/block/ll_rw_blk.c~blk-unplug-when-max-request-queued-fix Wed Mar 3 16:03:01 2004
> > +++ 25-akpm/drivers/block/ll_rw_blk.c Wed Mar 3 16:03:32 2004
>
> [CUT]
>
> I'm still experiencing some problems with that patch applied. I was again
> compiling the kernel (no tvtime this time) and got this:
>
> Unable to handle kernel paging request at virtual address c1810f70 printing eip:
> c02783ae
> *pde = 00006063
> *pte = 01810000
> Oops: 0000 [#1]
> PREEMPT DEBUG_PAGEALLOC
> CPU: 0
> EIP: 0060:[<c02783ae>] Not tainted VLI
> EFLAGS: 00010086
> EIP is at __make_request+0x3ae/0x6a0
OK, I screwed up. If we ended up finding a merge in the elevator, local
variable `req' in __make_request() can end up pointing at the now-freed-up
request.
Thanks. I suggest that you disable CONFIG_DEBUG_PAGEALLOC for now - the
bug is otherwise harmless.
prev parent reply other threads:[~2004-03-04 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 18:49 Rui Saraiva
2004-03-04 19:12 ` Andrew Morton
2004-03-04 21:33 ` Rui Saraiva
2004-03-04 22:26 ` Andrew Morton [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=20040304142638.47b00812.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmps@joel.ist.utl.pt \
/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®