From: Kasper Sandberg <lkml@metanurb.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops on -rc2-git1, possibly md_raid1 or xfs related. (Was: Re: Linux 2.6.26-rc2)
Date: Tue, 13 May 2008 03:55:34 +0200 [thread overview]
Message-ID: <1210643734.1093.21.camel@localhost> (raw)
In-Reply-To: <1210643358.1093.14.camel@localhost>
On Tue, 2008-05-13 at 03:49 +0200, Kasper Sandberg wrote:
> Just booted -rc2-git1, and got an oops(entier dmesg):
<snip>
> max_pfn_mapped = 1245184
> x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> init_memory_mapping
<snip>
> ------------[ cut here ]------------
> WARNING: at include/linux/blkdev.h:443 blk_remove_plug+0x71/0xa0()
> Modules linked in:
> Pid: 460, comm: md1_raid1 Not tainted 2.6.26-rc2-git1 #1
>
> Call Trace:
> [<ffffffff80232b04>] warn_on_slowpath+0x64/0xc0
> [<ffffffff803609a9>] __next_cpu+0x19/0x30
> [<ffffffff8022ac8c>] find_busiest_group+0x22c/0x8d0
> [<ffffffff803551a1>] blk_remove_plug+0x71/0xa0
> [<ffffffff804219fb>] flush_pending_writes+0x3b/0x90
> [<ffffffff80421b4c>] raid1d+0x4c/0xf60
> [<ffffffff8022f2fb>] hrtick_set+0x7b/0x160
> [<ffffffff804acb50>] thread_return+0x5e/0x57e
> [<ffffffff804ad32d>] schedule_timeout+0xad/0xf0
> [<ffffffff804299e7>] md_thread+0x47/0x120
> [<ffffffff80248df0>] autoremove_wake_function+0x0/0x30
> [<ffffffff804299a0>] md_thread+0x0/0x120
> [<ffffffff80248a47>] kthread+0x47/0x90
> [<ffffffff8022fe87>] schedule_tail+0x27/0x60
> [<ffffffff8020c598>] child_rip+0xa/0x12
> [<ffffffff80248a00>] kthread+0x0/0x90
> [<ffffffff8020c58e>] child_rip+0x0/0x12
>
> ---[ end trace a97097b29774f236 ]---
<snip>
> The system appeared to work, for the few minutes i had it running,
> before i went back to .25.
Just a thought, could it be the x86 PAT? the reason i dont just test it,
is because i dont want to unnessecarily risk the data on my disks, if
you may easily be able to rule that out or something, given the call
trace :)
>
> On Mon, 2008-05-12 at 07:55 -0700, Linus Torvalds wrote:
> <snip>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2008-05-13 1:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 14:55 Linux 2.6.26-rc2 Linus Torvalds
2008-05-12 19:32 ` Bart Van Assche
2008-05-12 19:55 ` Linus Torvalds
2008-05-12 23:22 ` Kasper Sandberg
[not found] ` <200805121726.15576.alistair@devzero.co.uk>
[not found] ` <alpine.LFD.1.10.0805120933310.3019@woody.linux-foundation.org>
[not found] ` <20080512164920.GE16217@kernel.dk>
2008-05-13 1:05 ` [PATCH] Remove blkdev warning triggered by using md Neil Brown
2008-05-17 18:22 ` XFS/md/blkdev warning (was Re: Linux 2.6.26-rc2) Alistair John Strachan
2008-05-17 18:37 ` Linus Torvalds
2008-05-17 18:41 ` Linus Torvalds
2008-05-17 20:09 ` Alistair John Strachan
2008-05-17 21:17 ` Linus Torvalds
2008-05-17 23:12 ` Alistair John Strachan
2008-05-17 23:39 ` Christoph Hellwig
2008-05-18 14:12 ` Alistair John Strachan
2008-05-13 1:49 ` Oops on -rc2-git1, possibly md_raid1 or xfs related. (Was: " Kasper Sandberg
2008-05-13 1:55 ` Kasper Sandberg [this message]
2008-05-13 2:19 ` Neil Brown
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=1210643734.1093.21.camel@localhost \
--to=lkml@metanurb.dk \
--cc=linux-kernel@vger.kernel.org \
--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