Hide Forgot
libreport version: 2.0.8 abrt_version: 2.0.7 cmdline: BOOT_IMAGE=/vmlinuz-3.1.8-2.fc16.x86_64 root=/dev/mapper/luks-4dd234ea-76db-46aa-a9ec-7c1981194197 ro rd.md=0 rd.lvm=0 rd.dm=0 quiet KEYTABLE=ie SYSFONT=latarcyrheb-sun16 rhgb rd.luks.uuid=luks-4dd234ea-76db-46aa-a9ec-7c1981194197 LANG=en_US.UTF-8 comment: This is an oops from the drive being removed. It seems to be the same error. I think I've narrowed it down slightly to the usb cable being physically being inserted/removed, rather than the mounting/dismounting (although you've probably already determined that much!). kernel: 3.1.8-2.fc16.x86_64 reason: WARNING: at lib/kobject_uevent.c:359 add_uevent_var+0xf2/0x100() time: Sun 15 Jan 2012 03:20:46 PM GMT backtrace: :WARNING: at lib/kobject_uevent.c:359 add_uevent_var+0xf2/0x100() :Hardware name: XPS M1530 :add_uevent_var: buffer size too small :Modules linked in: binfmt_misc ses enclosure usb_storage tcp_lp joydev hidp ppdev parport_pc lp parport fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle tun 8021q garp fcoe bridge stp llc lockd libfcoe libfc scsi_transport_fc scsi_tgt rfcomm bnep ip6t_REJECT nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ip6table_filter ip6_tables snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm arc4 uvcvideo videodev media v4l2_compat_ioctl32 virtio_net iwl4965 iwl_legacy mac80211 snd_timer cfg80211 kvm_intel r852 snd r592 sky2 soundcore btusb sm_common nand nand_ids nand_ecc mtd kvm iTCO_wdt iTCO_vendor_support memstick i2c_i801 snd_page_alloc dell_wmi dell_laptop bluetooth uinput sparse_keymap rfkill dcdbas sunrpc xts gf128mul btrfs zlib_deflate libcrc32c dm_crypt sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc :_itu_t nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core mxm_wmi wmi video [last unloaded: scsi_wait_scan] :Pid: 22, comm: khubd Tainted: G W 3.1.8-2.fc16.x86_64 #1 :Call Trace: : [<ffffffff8106b7ef>] warn_slowpath_common+0x7f/0xc0 : [<ffffffff8106b8e6>] warn_slowpath_fmt+0x46/0x50 : [<ffffffff812aafa2>] add_uevent_var+0xf2/0x100 : [<ffffffff813897f4>] ? dev_uevent+0xd4/0x260 : [<ffffffff812ab416>] kobject_uevent_env+0x346/0x600 : [<ffffffff812ab6db>] kobject_uevent+0xb/0x10 : [<ffffffff81388067>] device_del+0x157/0x1b0 : [<ffffffff813880e2>] device_unregister+0x22/0x60 : [<ffffffff81439e6a>] input_unregister_device+0x13a/0x160 : [<ffffffff8148dce5>] hidinput_disconnect+0x45/0x70 : [<ffffffff8148b398>] hid_disconnect+0x68/0x70 : [<ffffffff8148b3f5>] hid_device_remove+0x55/0x70 : [<ffffffff8138ba0c>] __device_release_driver+0x7c/0xe0 : [<ffffffff8138ba9c>] device_release_driver+0x2c/0x40 : [<ffffffff8138b4bd>] bus_remove_device+0x7d/0xe0 : [<ffffffff8138803d>] device_del+0x12d/0x1b0 : [<ffffffff8148b0e0>] hid_destroy_device+0x30/0x60 : [<ffffffff8149753b>] usbhid_disconnect+0x2b/0x50 : [<ffffffff814004e2>] usb_unbind_interface+0x52/0x180 : [<ffffffff8138ba0c>] __device_release_driver+0x7c/0xe0 : [<ffffffff8138ba9c>] device_release_driver+0x2c/0x40 : [<ffffffff8138b4bd>] bus_remove_device+0x7d/0xe0 : [<ffffffff8138803d>] device_del+0x12d/0x1b0 : [<ffffffff813fe0e0>] usb_disable_device+0xb0/0x250 : [<ffffffff813f51ed>] usb_disconnect+0xad/0x190 : [<ffffffff813f7af6>] hub_thread+0xb26/0x1730 : [<ffffffff8108e760>] ? remove_wait_queue+0x50/0x50 : [<ffffffff813f6fd0>] ? usb_remote_wakeup+0x70/0x70 : [<ffffffff8108debc>] kthread+0x8c/0xa0 : [<ffffffff815df2b4>] kernel_thread_helper+0x4/0x10 : [<ffffffff8108de30>] ? kthread_worker_fn+0x190/0x190 : [<ffffffff815df2b0>] ? gs_change+0x13/0x13
*** Bug 781773 has been marked as a duplicate of this bug. ***
Have you seen this with 3.2.7 or newer?
Hi Josh, Yeah, I'm currently using 3.2.7-1.fc16.x86_64 and I've just tried with the same result. I should add that the drive still gets mounted/dismounted properly, and is perfectly usable, I thought I'd report this anyway, since it throws this oops everytime I plug/unplug the cable.
Out of curiosity, have you tried a different cable?
Yeah, I've tried it with different cables, which all work fine with other external devices. I've even just tried it now with a new cable that just came with a new drive I got last week. The oops gets thrown every time. I'm guessing it's some quirk with the controller that interfaces with the drives in the RAID array or something? This is the device, if that helps: http://support.wdc.com/product/install.asp?groupid=115&lang=en It's configured to use RAID 1.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Retested with 3.3.0-4.fc16.x86_64, same results except the file seems to have been updated, so the warning is from a different line: WARNING: at lib/kobject_uevent.c:362 add_uevent_var+0xf2/0x100()
I no longer experience this with the 3.4.x kernels. I'll close this bug. Thanks for your help!