[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#741079: linux-image-3.13-1-686-pae: Stack trace when unplugging usb devices



Control: tag -1 confirmed

On Sat, 2014-03-08 at 16:05 +0100, nb wrote:
[...]
> > I would like to see see the *complete* warning message for removal of
> > the USB disk ('warn_slowpath_common' is just part of the warning
> 
> > mechanism).
> 
> Here it is:
> 
> [14185.008296] usb 5-3: USB disconnect, device number 9
> [14185.048462] ------------[ cut here ]------------
> [14185.048476] WARNING: CPU: 0 PID: 8962 at /build/linux-ncyRvS/linux-3.13.5/fs/sysfs/group.c:214 sysfs_remove_group+0xae/0xb0()
> [14185.048480] sysfs group c159fb48 not found for kobject 'target2:0:0'
> [14185.048482] Modules linked in: usb_storage pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) snd_hrtimer cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative rfcomm bnep binfmt_misc vboxdrv(O) synaptics_i2c firewire_sbp2 loop fuse parport_pc ppdev lp parport 8812au(O) gspca_m5602 gspca_main btusb bluetooth videodev media cfg80211 joydev evdev pcspkr psmouse pcmcia serio_raw r852 sm_common yenta_socket nand pcmcia_rsrc nand_ecc pcmcia_core nand_ids r592 mtd memstick snd_hda_codec_realtek lpc_ich mfd_core rng_core ac battery i915 snd_hda_intel snd_hda_codec snd_hwdep asus_laptop snd_pcm acpi_cpufreq snd_page_alloc sparse_keymap rfkill video input_polldev processor button drm_kms_helper drm i2c_algo_bit i2c_core snd_seq snd_seq_device snd_timer snd soundcore hid_generic usbhid hid ext4 crc16 mbcache jbd2 sg sd_mod sr_mod crc_t10dif crct10dif_common cdrom ata_generic firewire_ohci sdhci_pci sdhci ata_piix 8139too 8139cp mii firewire_core crc_itu_t mmc_core libata thermal scsi_mod ehci_pci fan uhci_hcd ehci_hcd thermal_sys usbcore usb_common
> [14185.048581] CPU: 0 PID: 8962 Comm: umount Tainted: G           O 3.13-1-686-pae #1 Debian 3.13.5-1
> [14185.048584] Hardware name: ASUSTeK Computer Inc.         W5A       /W5A       , BIOS 0209                                11/17/2005
> [14185.048586]  00000009 c140b038 ec4dfeb0 c104d41e c14eb738 ec4dfec8 00002302 c14eb6c8
> [14185.048593]  000000d6 c119f52e c119f52e 00000000 c159fb48 f331141c f52b00f8 c104d473
> [14185.048599]  00000009 ec4dfeb0 c14eb738 ec4dfec8 c119f52e c14eb6c8 000000d6 c14eb738
> [14185.048606] Call Trace:
> [14185.048613]  [<c140b038>] ? dump_stack+0x3e/0x4e
> [14185.048619]  [<c104d41e>] ? warn_slowpath_common+0x7e/0xa0
> [14185.048623]  [<c119f52e>] ? sysfs_remove_group+0xae/0xb0
> [14185.048626]  [<c119f52e>] ? sysfs_remove_group+0xae/0xb0
> [14185.048630]  [<c104d473>] ? warn_slowpath_fmt+0x33/0x40
> [14185.048633]  [<c119f52e>] ? sysfs_remove_group+0xae/0xb0
> [14185.048639]  [<c12eea3a>] ? device_del+0x2a/0x170
> [14185.048655]  [<f823be5c>] ? scsi_target_reap_usercontext+0x1c/0x30 [scsi_mod]
> [14185.048661]  [<c1061e84>] ? execute_in_process_context+0x44/0x50
> [14185.048671]  [<f823ec5c>] ? scsi_device_dev_release_usercontext+0x11c/0x150 [scsi_mod]
> [14185.048675]  [<c1061e84>] ? execute_in_process_context+0x44/0x50
> [14185.048679]  [<c12ee2c3>] ? device_release+0x23/0x80
> [14185.048684]  [<c10aa59f>] ? module_refcount+0x6f/0x80
> [14185.048690]  [<c121919a>] ? kobject_cleanup+0x2a/0x70
> [14185.048699]  [<f84268d0>] ? scsi_disk_put+0x20/0x30 [sd_mod]
> [14185.048705]  [<c11715d1>] ? __blkdev_put+0x111/0x150
> [14185.048711]  [<c114389b>] ? deactivate_locked_super+0x1b/0x40
> [14185.048716]  [<c115b5e2>] ? mntput_no_expire+0xa2/0x120
> [14185.048720]  [<c115c733>] ? SyS_oldumount+0x73/0xb0
> [14185.048726]  [<c141628d>] ? sysenter_do_call+0x12/0x28
> [14185.048729] ---[ end trace 718a47ebe91fca5c ]---
> 
> I can reproduce it at any time.
> It's the same with a usb memory key

OK.  I can reproduce it here, too.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: