From: Nick Piggin <npiggin@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@vger.kernel.org
Subject: Re: 2.6.29.4: softlockup at find_get_page() et al
Date: Mon, 6 Jul 2009 09:26:47 +0200 [thread overview]
Message-ID: <20090706072647.GI2714@wotan.suse.de> (raw)
In-Reply-To: <20090703140329.GA9546@x200.localdomain>
On Fri, Jul 03, 2009 at 06:03:29PM +0400, Alexey Dobriyan wrote:
> On Tue, Jun 16, 2009 at 03:08:33PM +0200, Nick Piggin wrote:
> > On Tue, Jun 16, 2009 at 03:00:51PM +0400, Alexey Dobriyan wrote:
> > > Happened during overnight run when box was cross-compiling kernel slowly
> > > (only -j7).
> > >
> > > Example messages:
> > >
> > > [67287.109985] BUG: soft lockup - CPU#0 stuck for 61s! [conf:3980]
> > > [67287.110001] CPU 0:
> > > [67287.110001] Pid: 3980, comm: conf Not tainted 2.6.29.4-x86_64 #1 P5E
> > > [67287.110001] RIP: 0010:[<ffffffff80264902>] [<ffffffff80264902>] find_get_page+0x52/0xb0
> > > [67287.110001] RSP: 0018:ffff8801001eddd8 EFLAGS: 00000246
> > > [67287.110001] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000034
> > > [67287.110001] RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffe200010a9f40
> > > [67287.110001] RBP: ffffffff8020c3ee R08: ffffe200010a9f48 R09: ffff8800aa798c28
> > > [67287.110001] R10: ffffe200010a9f40 R11: ffffffff802f9480 R12: ffff8800aa798c18
> > > [67287.110001] R13: ffffffff8020c3ee R14: ffffffff802f4e70 R15: 000000000000000c
> > > [67287.110001] FS: 0000000000000000(0000) GS:ffffffff8075b040(0063) knlGS:00000000557116c0
> > > [67287.110001] CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
> > > [67287.110001] CR2: 00000000556d9374 CR3: 000000012faa4000 CR4: 00000000000006e0
> > > [67287.110001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > > [67287.110001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > > [67287.110001] Call Trace:
> > > [67287.110001] [<ffffffff802648cb>] ? find_get_page+0x1b/0xb0
> > > [67287.110001] [<ffffffff80264bf3>] ? find_lock_page+0x23/0x80
> > > [67287.110001] [<ffffffff80265631>] ? find_or_create_page+0x41/0xc0
> > > [67287.110001] [<ffffffff802f4edd>] ? ext2_make_empty+0x2d/0x1f0
> > > [67287.110001] [<ffffffff802f9556>] ? ext2_mkdir+0xd6/0x170
> > > [67287.110001] [<ffffffff8029b37c>] ? sys_mkdirat+0x11c/0x130
> > > [67287.110001] [<ffffffff802a585a>] ? alloc_fd+0x4a/0x140
> > > [67287.110001] [<ffffffff8022ab14>] ? sysenter_dispatch+0x7/0x2b
>
> memtest has found quite a lot of junk.
OK that's good to know (for Linux, maybe not for you!). Thanks
anyway for reporting, it is always helpful.
Thanks,
Nick
prev parent reply other threads:[~2009-07-06 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 11:00 Alexey Dobriyan
2009-06-16 13:08 ` Nick Piggin
2009-06-16 13:14 ` Alexey Dobriyan
2009-06-16 14:22 ` Nick Piggin
2009-07-03 14:03 ` Alexey Dobriyan
2009-07-06 7:26 ` Nick Piggin [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=20090706072647.GI2714@wotan.suse.de \
--to=npiggin@suse.de \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.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
all inboxes | Powered by JetHome®