From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: linux-next: Tree for July 15 (bdi warning)
Date: Wed, 15 Jul 2009 20:41:07 +0200 [thread overview]
Message-ID: <200907152041.08025.bzolnier@gmail.com> (raw)
In-Reply-To: <20090715161841.9be17451.sfr@canb.auug.org.au>
On Wednesday 15 July 2009 08:18:41 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090714:
Jens, I see the following warning sometimes during disconnect
of usb-storage device, is this anything to be worried about?
------------[ cut here ]------------
WARNING: at mm/backing-dev.c:787 bdi_destroy+0x1e/0x4d()
Hardware name: Extensa 2900
Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage radeon sco bnep l2cap bluetooth rfkill lib80211_crypt_tkip xt_state ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 acerhk binfmt_misc uinput snd_intel8x0m snd_intel8x0 snd_ac97_codec ipw2200 ac97_bus snd_pcm snd_timer libipw snd soundcore uhci_hcd ehci_hcd parport_pc snd_page_alloc lib80211 parport [last unloaded: scsi_wait_scan]
Pid: 183, comm: khubd Tainted: G M 2.6.31-rc3-next-20090715-03649-g2a49c7b #23
Call Trace:
[<c0129db9>] warn_slowpath_common+0x65/0x7c
[<c01705c7>] ? bdi_destroy+0x1e/0x4d
[<c0129ddd>] warn_slowpath_null+0xd/0x10
[<c01705c7>] bdi_destroy+0x1e/0x4d
[<c0229d3d>] blk_release_queue+0x38/0x47
[<c0233f10>] kobject_release+0x3f/0x4f
[<c0233ed1>] ? kobject_release+0x0/0x4f
[<c02349c1>] kref_put+0x39/0x42
[<c0233e4d>] kobject_put+0x37/0x3c
[<c02285cb>] blk_put_queue+0xd/0xf
[<c0228747>] blk_cleanup_queue+0x3d/0x41
[<c02b9713>] scsi_free_queue+0x8/0xa
[<c02bd0f9>] scsi_device_dev_release_usercontext+0xf6/0x12c
[<c02bd003>] ? scsi_device_dev_release_usercontext+0x0/0x12c
[<c0137c3c>] execute_in_process_context+0x1d/0x5b
[<c02bd001>] scsi_device_dev_release+0x13/0x15
[<c02ae690>] device_release+0x35/0x5a
[<c0233f10>] kobject_release+0x3f/0x4f
[<c0233ed1>] ? kobject_release+0x0/0x4f
[<c02349c1>] kref_put+0x39/0x42
[<c0233e4d>] kobject_put+0x37/0x3c
[<c02ae459>] put_device+0xf/0x11
[<c02bd3df>] __scsi_remove_device+0x61/0x65
[<c02bb3a8>] scsi_forget_host+0x35/0x51
[<c02b6544>] scsi_remove_host+0x69/0xcd
[<e0833684>] quiesce_and_remove_host+0x4c/0x7e [usb_storage]
[<e083376a>] usb_stor_disconnect+0x13/0x1d [usb_storage]
[<c02e039f>] usb_unbind_interface+0x3b/0xa0
[<c02b0c84>] __device_release_driver+0x47/0x7f
[<c02b0d59>] device_release_driver+0x18/0x23
[<c02b04bb>] bus_remove_device+0x7f/0x8c
[<c02af04a>] device_del+0xf0/0x127
[<c02de6a3>] usb_disable_device+0x61/0xbf
[<c02dab52>] usb_disconnect+0x7e/0xda
[<c02db666>] hub_thread+0x30f/0xad5
[<c013a52d>] ? autoremove_wake_function+0x0/0x2f
[<c011eca9>] ? complete+0x34/0x3e
[<c02db357>] ? hub_thread+0x0/0xad5
[<c013a2f3>] kthread+0x66/0x6b
[<c013a28d>] ? kthread+0x0/0x6b
[<c01034eb>] kernel_thread_helper+0x7/0x10
---[ end trace d1600192f6c800d2 ]---
next prev parent reply other threads:[~2009-07-15 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 6:18 linux-next: Tree for July 15 Stephen Rothwell
2009-07-15 18:41 ` Bartlomiej Zolnierkiewicz [this message]
2009-07-28 7:14 ` linux-next: Tree for July 15 (bdi warning) Jens Axboe
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=200907152041.08025.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.