From: Prakash Punnoor <prakash@punnoor.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Jacek Luczak <difrost.kernel@gmail.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
neilb@suse.de
Subject: Re: WARNING in 2.6.25-07422-gb66e1f1
Date: Mon, 5 May 2008 19:31:06 +0100 [thread overview]
Message-ID: <200805051931.14116.prakash@punnoor.de> (raw)
In-Reply-To: <20080504183839.GN12774@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
On the day of Sunday 04 May 2008 Jens Axboe hast written:
> On Sun, May 04 2008, Jacek Luczak wrote:
> > Hi,
> >
> > I've CC:-ed few guys which may help.
> >
> > Prakash Punnoor pisze:
> > > Hi, I got this on boot:
> > >
> > > usb 2-1.3: new full speed USB device using ehci_hcd and address 3
> > > usb 2-1.3: configuration #1 chosen from 1 choice
> > > Clocksource tsc unstable (delta = -117343945 ns)
> > > ------------[ cut here ]------------
> > > WARNING: at include/linux/blkdev.h:443 blk_remove_plug+0x7d/0x90()
> > > Modules linked in: kvm_amd kvm powernow_k8 ehci_hcd ohci_hcd usbcore
> > > forcedeth Pid: 1681, comm: fsck.ext3 Not tainted
> > > 2.6.25-07422-gb66e1f1-dirty #74
> > >
> > > Call Trace:
> > > [<ffffffff80236354>] warn_on_slowpath+0x64/0xa0
> > > [<ffffffff803b6a04>] generic_make_request+0x194/0x250
> > > [<ffffffff803b82e7>] submit_bio+0x97/0x140
> > > [<ffffffff803b756d>] blk_remove_plug+0x7d/0x90
> > > [<ffffffff8049d4d4>] raid5_unplug_device+0x44/0x110
> > > [<ffffffff802666ce>] sync_page+0x2e/0x50
> > > [<ffffffff805a0985>] __wait_on_bit+0x65/0x90
> > > [<ffffffff802669c8>] wait_on_page_bit+0x78/0x80
> > > [<ffffffff8024bb70>] wake_bit_function+0x0/0x40
> > > [<ffffffff8026f1ba>] pagevec_lookup_tag+0x1a/0x30
> > > [<ffffffff80266fbd>] wait_on_page_writeback_range+0xbd/0x130
> > > [<ffffffff8026d5e0>] do_writepages+0x20/0x40
> > > [<ffffffff802670a2>] __filemap_fdatawrite_range+0x52/0x60
> > > [<ffffffff80267334>] filemap_write_and_wait+0x44/0x50
> > > [<ffffffff802bd968>] __blkdev_put+0x148/0x1b0
> > > [<ffffffff80293441>] __fput+0xb1/0x1c0
> > > [<ffffffff80290178>] filp_close+0x48/0x80
> > > [<ffffffff80291a1f>] sys_close+0x9f/0x110
> > > [<ffffffff8020c42b>] system_call_after_swapgs+0x7b/0x80
> > >
> > > ---[ end trace 94c0787a2e4d19eb ]---
[...]
>
> Looks like it caught a real bug there - unfortunately we have to check
> for ->queue_lock here as well, if this is another stacked devices and
> not the bottom device. Does this make the warning go away for you?
Nope it does not. But I see some other comments have already been posted about
this issue...
--
(°= =°)
//\ Prakash Punnoor /\\
V_/ \_V
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-05 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 9:51 Prakash Punnoor
2008-05-04 13:02 ` Jacek Luczak
2008-05-04 18:38 ` Jens Axboe
2008-05-05 7:24 ` Neil Brown
2008-05-05 18:03 ` Dan Williams
2008-05-05 19:02 ` Jens Axboe
2008-05-08 18:39 ` Rafael J. Wysocki
2008-05-08 18:46 ` Dan Williams
2008-05-08 23:18 ` Dan Williams
2008-05-09 2:15 ` Neil Brown
2008-05-09 4:59 ` Dan Williams
2008-05-09 5:38 ` Neil Brown
2008-05-12 17:46 ` Dan Williams
2008-05-13 1:08 ` Neil Brown
2008-05-05 18:31 ` Prakash Punnoor [this message]
2008-05-05 23:08 ` Gabriel C
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=200805051931.14116.prakash@punnoor.de \
--to=prakash@punnoor.de \
--cc=difrost.kernel@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.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
all inboxes | Powered by JetHome®