From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [bug, 2.6.26-rc4/rc5] sporadic bootup crashes in blk_lookup_devt()/prepare_namespace()
Date: Mon, 9 Jun 2008 02:06:23 -0700 [thread overview]
Message-ID: <20080609020623.b6727f2b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080609080312.GA32458@elte.hu>
On Mon, 9 Jun 2008 10:03:12 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> -tip testing has started triggering a new type of sporadic bootup crash
> a few days ago. Find below a collection of 14 crashes i've managed to
> capture so far, which are all similar to this crash pattern:
>
> BUG: unable to handle kernel paging request at ffff81003b984fb8
> IP: [<ffffffff803fafd4>] blk_lookup_devt+0x42/0xa0
> PGD 8063 PUD 9063 PMD 3be2d163 PTE 800000003b984160
> Oops: 0000 [1] SMP DEBUG_PAGEALLOC
>
> Call Trace:
> [<ffffffff80bac17b>] ? ip_auto_config+0x0/0xd94
> [<ffffffff80209259>] name_to_dev_t+0x145/0xeec
> [<ffffffff803ff2be>] ? __next_cpu_nr+0x22/0x2b
> [<ffffffff80b7f372>] prepare_namespace+0x91/0x14c
> [<ffffffff80b7eb70>] kernel_init+0x2fe/0x314
> [<ffffffff80251f3d>] ? trace_hardirqs_on_caller+0xca/0xee
> [<ffffffff80741bbb>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> [<ffffffff80251f3d>] ? trace_hardirqs_on_caller+0xca/0xee
> [<ffffffff8020d3f8>] child_rip+0xa/0x12
> [<ffffffff8020c90c>] ? restore_args+0x0/0x30
> [<ffffffff8025068d>] ? trace_hardirqs_off+0xd/0xf
> [<ffffffff80b7e872>] ? kernel_init+0x0/0x314
> [<ffffffff8020d3ee>] ? child_rip+0x0/0x12
Did you work out where it's dying? Deref of `dev' I assume?
next prev parent reply other threads:[~2008-06-09 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 8:03 [bug, 2.6.26-rc4/rc5] sporadic bootup crashes in blk_lookup_devt()/prepare_namespace() Ingo Molnar
2008-06-09 9:06 ` Andrew Morton [this message]
2008-06-09 9:09 ` Vegard Nossum
2008-06-09 9:34 ` Ingo Molnar
2008-06-09 10:35 ` Vegard Nossum
2008-06-09 13:34 ` Adrian Bunk
2008-06-09 13:58 ` Vegard Nossum
2008-06-09 14:28 ` Vegard Nossum
2008-06-09 14:57 ` Cornelia Huck
2008-06-09 15:09 ` Vegard Nossum
2008-06-09 15:29 ` Linus Torvalds
2008-06-09 15:38 ` Ingo Molnar
2008-06-09 16:15 ` Linus Torvalds
2008-06-09 17:15 ` Cornelia Huck
2008-06-09 18:03 ` Cornelia Huck
2008-06-10 3:11 ` Greg KH
2008-06-10 7:51 ` Cornelia Huck
2008-06-10 21:52 ` Greg KH
2008-06-10 3:09 ` Greg KH
2008-06-09 15:46 ` Kay Sievers
2008-06-09 15:58 ` Linus Torvalds
2008-06-10 3:07 ` Greg KH
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=20080609020623.b6727f2b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox