On Mon, 2014-02-17 at 14:48 -0500, Alan Stern wrote: > On Mon, 17 Feb 2014, Ronald wrote: > > > I caught this by coincidence since I had netconsole attached to debug > > a nouveau MSI problem (deadlock). It happenned when I disconnected my > > external hardrive in thunar. I have attached my full dmesg. > > This isn't a USB problem. > > > [17764.280135] usb 1-2: new high-speed USB device number 13 using ehci-pci > > [17764.453094] usb-storage 1-2:1.0: USB Mass Storage device detected > > [17764.461737] scsi14 : usb-storage 1-2:1.0 > > [17772.722083] scsi 14:0:0:0: Direct-Access Maxtor 3200 > > 0341 PQ: 0 ANSI: 4 > > [17772.914430] sd 14:0:0:0: [sdb] 586114704 512-byte logical blocks: > > (300 GB/279 GiB) > > [17772.917232] sd 14:0:0:0: [sdb] Write Protect is off > > [17772.917246] sd 14:0:0:0: [sdb] Mode Sense: 17 00 00 00 > > [17772.919206] sd 14:0:0:0: [sdb] No Caching mode page found > > [17772.919222] sd 14:0:0:0: [sdb] Assuming drive cache: write through > > [17772.925185] sd 14:0:0:0: [sdb] No Caching mode page found > > [17772.925199] sd 14:0:0:0: [sdb] Assuming drive cache: write through > > [17773.020601] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 > > > [17773.027194] sd 14:0:0:0: [sdb] No Caching mode page found > > [17773.027211] sd 14:0:0:0: [sdb] Assuming drive cache: write through > > [17773.027219] sd 14:0:0:0: [sdb] Attached SCSI disk > > [17828.434461] Buffer I/O error on device sdb1, logical block 32 > > [17828.434930] Buffer I/O error on device sdb1, logical block 786432 > > [17828.434962] Buffer I/O error on device sdb1, logical block 16384 > > [17828.434971] Buffer I/O error on device sdb1, logical block 512 > > [17828.434984] Buffer I/O error on device sdb1, logical block 48496383 > > [17828.435024] Buffer I/O error on device sdb1, logical block 3 > > [17828.435032] Buffer I/O error on device sdb1, logical block 7 > > [17828.436022] ------------[ cut here ]------------ > > [17828.436053] WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 > > sysfs_remove_group+0xa3/0xb0() > > [17828.436064] sysfs group ffffffff81a74bc0 not found for kobject > > 'target14:0:0' > > [17828.436069] CPU: 0 PID: 24108 Comm: systemd-udevd Not tainted > > 3.14.0-rc2-00750-g946dd68-dirty #3 > > [17828.436141] Hardware name: Hewlett-Packard HP Pavilion dv6000 > > (RS551EA#ABH) /30B7, BIOS F.40 08/01/2008 > > [17828.436145] 0000000000000009 ffff88003170fb70 ffffffff8165eb64 > > ffff88003170fba8 > > [17828.436278] ffffffff8102c0c6 0000000000000000 ffffffff81a74bc0 > > ffff880070bb7038 > > [17828.436298] ffff880033f4f168 ffff880048aa4000 ffff88003170fc08 > > ffffffff8102c167 > > [17828.436309] Call Trace: > > [17828.436321] [<ffffffff8165eb64>] dump_stack+0x19/0x1b > > [17828.436330] [<ffffffff8102c0c6>] warn_slowpath_common+0x76/0xa0 > > [17828.436337] [<ffffffff8102c167>] warn_slowpath_fmt+0x47/0x50 > > [17828.436345] [<ffffffff8111dae8>] ? kernfs_find_and_get_ns+0x48/0x60 > > [17828.436353] [<ffffffff8111c003>] sysfs_remove_group+0xa3/0xb0 > > [17828.436362] [<ffffffff813fabee>] dpm_sysfs_remove+0x3e/0x50 > > [17828.436370] [<ffffffff813f281d>] device_del+0x3d/0x1b0 > > [17828.436380] [<ffffffff8140ae8b>] scsi_target_reap_usercontext+0x2b/0x40 > > [17828.436444] [<ffffffff81040520>] execute_in_process_context+0x60/0x70 > > [17828.436452] [<ffffffff8140c027>] scsi_target_reap+0x77/0xa0 > > [17828.436458] [<ffffffff8140df10>] > > scsi_device_dev_release_usercontext+0x160/0x190 > > [17828.436463] [<ffffffff81040520>] execute_in_process_context+0x60/0x70 > > [17828.436467] [<ffffffff8140dda7>] scsi_device_dev_release+0x17/0x20 > > [17828.436472] [<ffffffff813f1598>] device_release+0x38/0xb0 > > [17828.436478] [<ffffffff8128c7b3>] kobject_cleanup+0x43/0x80 > > [17828.436651] [<ffffffff8128be98>] kobject_put+0x28/0x60 > > [17828.436656] [<ffffffff813f27d2>] put_device+0x12/0x20 > > [17828.436661] [<ffffffff81402d70>] scsi_device_put+0x10/0x20 > > [17828.436666] [<ffffffff814106c4>] scsi_disk_put+0x34/0x50 > > [17828.436670] [<ffffffff81410973>] sd_release+0x33/0x70 > > [17828.436675] [<ffffffff810f36e4>] __blkdev_put+0x144/0x180 > > [17828.436679] [<ffffffff810f368d>] __blkdev_put+0xed/0x180 > > [17828.436683] [<ffffffff810f4757>] blkdev_put+0x97/0x110 > > [17828.436687] [<ffffffff810f47f0>] blkdev_close+0x20/0x30 > > [17828.436693] [<ffffffff810c47b2>] __fput+0xe2/0x200 > > [17828.436698] [<ffffffff810c4909>] ____fput+0x9/0x10 > > [17828.436703] [<ffffffff81042c0f>] task_work_run+0x7f/0xc0 > > [17828.436708] [<ffffffff810024e6>] do_notify_resume+0x66/0x70 > > [17828.436829] [<ffffffff810c23e1>] ? filp_close+0x51/0x80 > > [17828.436835] [<ffffffff81663f64>] int_signal+0x12/0x17 > > [17828.436839] ---[ end trace b057fe2fdcfc8458 ]--- > > [17828.441765] usb 1-2: USB disconnect, device number 13 > > You can tell by the way the stack trace doesn't mention USB at all. In > fact, this is a known SCSI problem. It has been fixed by these two > patches: > > http://marc.info/?l=linux-scsi&m=139031645920152&w=2 > http://marc.info/?l=linux-scsi&m=139031650720168&w=2 > > If these patches have appeared in any git repositories yet, I don't > know where. > > James, what happened to those two target-reap-infrastructure patches? > They don't seem to have reached linux-next yet, and I can't find them > in your SCSI repository on git.kernel.org.
Yes, I'm just about to build it. I usually start at -rc1, but got a little behind because of pressure of work. I need them to go through a full regression cycle just to make sure there aren't any new bugs, but then they'll get backported to the stable kernels. James -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
