From: Andrew Morton <akpm@linux-foundation.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org, axboe@kernel.dk,
linux-scsi@vger.kernel.org
Subject: Re: [Bug 18252] spinlock lockup in __make_request <- submit_bio <- ondemand_readahead
Date: Mon, 13 Sep 2010 14:41:39 -0700 [thread overview]
Message-ID: <20100913144139.b9e18133.akpm@linux-foundation.org> (raw)
In-Reply-To: <4C8B50F1.4020502@s5r6.in-berlin.de>
On Sat, 11 Sep 2010 11:50:41 +0200
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Full quote for lkml:
>
> bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=18252
> >
> > Summary: spinlock lockup in __make_request <- submit_bio <-
> > ondemand_readahead
> > Product: IO/Storage
> > Version: 2.5
> > Kernel Version: 2.6.36-rc3
> > Platform: All
> > OS/Version: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: Block Layer
> > AssignedTo: axboe@kernel.dk
> > ReportedBy: stefanr@s5r6.in-berlin.de
> > Regression: No
> >
> >
> > Created an attachment (id=29562)
> > --> (https://bugzilla.kernel.org/attachment.cgi?id=29562)
> > BUG screenshot
> >
> > After a week uptime of 2.6.36-rc3 (I ran 2.6.35 before that),
>
> Almost two weeks uptime actually.
>
> > I was greeted by a black screen of death today in the morning:
> >
> > (see screenshot in attachment; partial transcript:)
> >
> > sending NMI to all CPUs:
> > BUG: soinlock lockup on CPU#0, ktorrent/4313, ffff8802...
> > PID: 4313, comm: ktorrent Tainted: G M D W 2.6.36-rc3 #3
> > Call Trace:
> > [...] do_raw_spin_lock+0x118/0x147
> > [...] _raw_spin_lock_irq+0x44/0x49
> > [...] ? __make_request+0x5c/0x400
> > [...] __make_request+0x5c/0x400
> > [...] generic_make_request+0x23a/0x2a9
> > [...] submit_bio+0xad/b6
> > [...] mpage_bio_submit...
> > [...] do_mpage_readpage...
> > [...] ? get_parent_ip...
> > [...] ? sub_preempt_count...
> > [...] ? __lru_cache_add...
> > [...] mpage_readpages...
> > [...] ? ext4_get_block...
> > [...] ? __alloc_pages_nodemask...
> > [...] ? ext4_get_block...
> > [...] ext4_readpages...
> > [...] __do_page_cache_readahead...
> > [...] ? __do_page_cache_readahead...
> > [...] ra_submit...
> > [...] ondemand_readahead...
> >
> > This is a system with Phenom II x4 and Radeon graphics. Since kernel mode
> > setting is fairly new for radeon, it is possible that the lockup happened with
> > earlier kernels too but simply ended in a lockup without trace dump to the
> > screen. IOW, it is not clear to me whether this is a regression or not.
> >
> > The bug happened while kaffeine wrote an MPEG 2 TS to the same filesystem from
> > which ktorrent was reading. Of course this kind of commonplace workload
> > happened without problem two or three times before during the week in which I
> > ran 2.6.36-rc3.
> >
>
> (The screenshot is a bit large, hence I reported in bugzilla instead of the list.)
>
What you've quoted above appears to be just the aftermath.
https://bugzilla.kernel.org/attachment.cgi?id=29562 indicates that the
kernel earlier crashed in scsi code, perhaps under
scsi_setup_fs_cmnd().
The question is: was that actually the first crash, or did an even
earlier one scroll off?
next prev parent reply other threads:[~2010-09-13 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18252-4803@https.bugzilla.kernel.org/>
2010-09-11 9:50 ` [Bug 18252] spinlock lockup in __make_request <- submit_bio <- ondemand_readahead Stefan Richter
2010-09-13 21:41 ` Andrew Morton [this message]
2010-09-14 6:56 ` Stefan Richter
2010-09-14 6:58 ` Jens Axboe
2010-09-14 11:18 ` Stefan Richter
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=20100913144139.b9e18133.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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