linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0()
Date: Tue, 05 Apr 2011 03:51:00 +0200	[thread overview]
Message-ID: <4D9A7584.9040903@kernel.dk> (raw)
In-Reply-To: <20110404211604.GB6133@sucs.org>

On 2011-04-04 23:16, Sitsofe Wheeler wrote:
> I'm seeing the following warning on 2.6.39-rc1-00220-g148086b when I was
> inserting an SD card (which is attached to the USB port) and USB stick
> with loads of kernel debug options on:
> 
> [    7.526172] ------------[ cut here ]------------
> [    7.526191] WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0()
> [    7.526197] Hardware name: 900
> [    7.526205] Pid: 1112, comm: udisks-part-id Not tainted 2.6.39-rc1-00227-gd7c764c-dirty #352
> [    7.526211] Call Trace:
> [    7.526224]  [<b0127208>] warn_slowpath_common+0x68/0xa0
> [    7.526232]  [<b0254e8c>] ? disk_clear_events+0xdc/0xf0
> [    7.526240]  [<b0254e8c>] ? disk_clear_events+0xdc/0xf0
> [    7.526248]  [<b012725b>] warn_slowpath_null+0x1b/0x20
> [    7.526255]  [<b0254e8c>] disk_clear_events+0xdc/0xf0
> [    7.526265]  [<b01c29c5>] check_disk_change+0x25/0x70
> [    7.526274]  [<b0345647>] sd_open+0x97/0x180
> [    7.526282]  [<b01c38ac>] __blkdev_get+0x7c/0x310
> [    7.526289]  [<b01c3b86>] blkdev_get+0x46/0x2c0
> [    7.526298]  [<b051206d>] ? _raw_spin_unlock+0x1d/0x20
> [    7.526306]  [<b01c3e55>] blkdev_open+0x55/0x70
> [    7.526316]  [<b0193262>] __dentry_open+0x112/0x290
> [    7.526323]  [<b0193446>] nameidata_to_filp+0x66/0x70
> [    7.526331]  [<b01c3e00>] ? blkdev_get+0x2c0/0x2c0
> [    7.526340]  [<b01a04fd>] do_last+0x19d/0x770
> [    7.526348]  [<b01a1730>] path_openat+0x90/0x310
> [    7.526356]  [<b01a1abd>] do_filp_open+0x5d/0x80
> [    7.526364]  [<b051206d>] ? _raw_spin_unlock+0x1d/0x20
> [    7.526373]  [<b01aec54>] ? alloc_fd+0x164/0x1b0
> [    7.526381]  [<b0194581>] do_sys_open+0xf1/0x1c0
> [    7.526389]  [<b01952ac>] ? vfs_write+0xfc/0x140
> [    7.526397]  [<b01946b9>] sys_open+0x29/0x40
> [    7.526404]  [<b0512817>] sysenter_do_call+0x12/0x36
> [    7.526410] ---[ end trace 1aec3f97d06611cd ]---
> 
> A quick Google also turns up the same report in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/748166 .

CC Tejun.

-- 
Jens Axboe


  reply	other threads:[~2011-04-05  1:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 21:16 WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0() Sitsofe Wheeler
2011-04-05  1:51 ` Jens Axboe [this message]
2011-04-06 13:04 ` Tejun Heo
2011-04-06 21:26   ` Sitsofe Wheeler
2011-04-06 21:37     ` Tejun Heo
2011-04-09  9:34       ` Sitsofe Wheeler
2011-04-10 14:59         ` Sitsofe Wheeler
2011-04-13 20:00           ` Tejun Heo
2011-04-15  9:01             ` Tejun Heo
2011-04-15 18:20               ` Tejun Heo
2011-04-15 21:41                 ` Sitsofe Wheeler
2011-04-21 17:38                   ` Tejun Heo
2011-04-21 18:43                     ` Tejun Heo
2011-05-10 16:48                       ` Tejun Heo

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=4D9A7584.9040903@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@yahoo.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).