Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
On Mon, 17 Feb 2014, James Bottomley wrote: 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-scsim=139031645920152w=2 http://marc.info/?l=linux-scsim=139031650720168w=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, these two patches appear still not to be merged in any of your branches on git.kernel.org. Will they get there in time for the next merge window? Alan Stern -- 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
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
On Tue, 18 Feb 2014, [windows-1252] Michal �mucr wrote: On 17.2.2014 20:48, Alan Stern wrote: This isn't a USB problem. Hello, I'm experiencing very similar messages after every disconnection of USB soundcard (snd-usb-audio module). During searching for other similar occurrences of message, i've found few patches. One kind basically prevents sysfs from popping those messages at sysfs group attribute removal - https://lkml.org/lkml/2013/11/23/102 and isn't included in 3.14-rc2, other kind of patches, if i got that correctly, fixes removal ordering or its visibility at underlying subsystem (eg. SCSI, PCI for Thunderbolt hotplugging) to make sysfs happy. Do you know, that there was some general decision, to intentionally don't modify sysfs and fix that for every subsystem, which triggers that messages? Yes, there was indeed such a decision. Just asking, because then it would be probably nice to modify something also at USB audio.. my dmesg with WARNING: http://vpub.smucr.cz/pub/bbb/debug/dmesg-reconnections.log and i probably not alone: http://forums.funtoo.org/viewtopic.php?pid=10327 If you want to pursue this, you should contact the alsa-devel mailing list and the maintainers of the Sound subsystem. Alan Stern -- 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
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
On 18. 2. 2014 21:51, Alan Stern wrote: On Tue, 18 Feb 2014, [windows-1252] Michal �mucr wrote: On 17.2.2014 20:48, Alan Stern wrote: This isn't a USB problem. Hello, I'm experiencing very similar messages after every disconnection of USB soundcard (snd-usb-audio module). During searching for other similar occurrences of message, i've found few patches. One kind basically prevents sysfs from popping those messages at sysfs group attribute removal - https://lkml.org/lkml/2013/11/23/102 and isn't included in 3.14-rc2, other kind of patches, if i got that correctly, fixes removal ordering or its visibility at underlying subsystem (eg. SCSI, PCI for Thunderbolt hotplugging) to make sysfs happy. Do you know, that there was some general decision, to intentionally don't modify sysfs and fix that for every subsystem, which triggers that messages? Yes, there was indeed such a decision. Just asking, because then it would be probably nice to modify something also at USB audio.. my dmesg with WARNING: http://vpub.smucr.cz/pub/bbb/debug/dmesg-reconnections.log and i probably not alone: http://forums.funtoo.org/viewtopic.php?pid=10327 If you want to pursue this, you should contact the alsa-devel mailing list and the maintainers of the Sound subsystem. Alan Stern Hello Alan, thank you for information. Best regards, Michal Smucr -- 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
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
On 17.2.2014 9:41, 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. Sorry for third time, now without HTML, I've played with latest kernels yesterday and found the same messages after disconnection of one my USB soundcard. After some seeking at lists and testing, i believe this is inconvenient (i originally thought it is related to other problem, which i debugged), but harmless message. According to other threads, where was report, that this popped after Thuderbolt device removal. Error is printed during removal of device sysfs entries, which don't exist at that moment, because its parent sysfs folder is already deleted, if i got that correctly. relevant threads: https://bugzilla.kernel.org/show_bug.cgi?id=65281 http://www.spinics.net/lists/linux-scsi/msg70154.html http://forums.funtoo.org/viewtopic.php?pid=10327 https://lkml.org/lkml/2013/11/23/102 There was patch in latest mentioned thread by Mika Westerberg, but it is not possible to apply to 3.14 as there was some additional rework done at sysfs. Best regards, Michal -- 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
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
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 81a74bc0 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] 0009 88003170fb70 8165eb64 88003170fba8 [17828.436278] 8102c0c6 81a74bc0 880070bb7038 [17828.436298] 880033f4f168 880048aa4000 88003170fc08 8102c167 [17828.436309] Call Trace: [17828.436321] [8165eb64] dump_stack+0x19/0x1b [17828.436330] [8102c0c6] warn_slowpath_common+0x76/0xa0 [17828.436337] [8102c167] warn_slowpath_fmt+0x47/0x50 [17828.436345] [8111dae8] ? kernfs_find_and_get_ns+0x48/0x60 [17828.436353] [8111c003] sysfs_remove_group+0xa3/0xb0 [17828.436362] [813fabee] dpm_sysfs_remove+0x3e/0x50 [17828.436370] [813f281d] device_del+0x3d/0x1b0 [17828.436380] [8140ae8b] scsi_target_reap_usercontext+0x2b/0x40 [17828.436444] [81040520] execute_in_process_context+0x60/0x70 [17828.436452] [8140c027] scsi_target_reap+0x77/0xa0 [17828.436458] [8140df10] scsi_device_dev_release_usercontext+0x160/0x190 [17828.436463] [81040520] execute_in_process_context+0x60/0x70 [17828.436467] [8140dda7] scsi_device_dev_release+0x17/0x20 [17828.436472] [813f1598] device_release+0x38/0xb0 [17828.436478] [8128c7b3] kobject_cleanup+0x43/0x80 [17828.436651] [8128be98] kobject_put+0x28/0x60 [17828.436656] [813f27d2] put_device+0x12/0x20 [17828.436661] [81402d70] scsi_device_put+0x10/0x20 [17828.43] [814106c4] scsi_disk_put+0x34/0x50 [17828.436670] [81410973] sd_release+0x33/0x70 [17828.436675] [810f36e4] __blkdev_put+0x144/0x180 [17828.436679] [810f368d] __blkdev_put+0xed/0x180 [17828.436683] [810f4757] blkdev_put+0x97/0x110 [17828.436687] [810f47f0] blkdev_close+0x20/0x30 [17828.436693] [810c47b2] __fput+0xe2/0x200 [17828.436698] [810c4909] fput+0x9/0x10 [17828.436703] [81042c0f] task_work_run+0x7f/0xc0 [17828.436708] [810024e6] do_notify_resume+0x66/0x70 [17828.436829] [810c23e1] ? filp_close+0x51/0x80 [17828.436835] [81663f64] 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-scsim=139031645920152w=2 http://marc.info/?l=linux-scsim=139031650720168w=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
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
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 81a74bc0 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] 0009 88003170fb70 8165eb64 88003170fba8 [17828.436278] 8102c0c6 81a74bc0 880070bb7038 [17828.436298] 880033f4f168 880048aa4000 88003170fc08 8102c167 [17828.436309] Call Trace: [17828.436321] [8165eb64] dump_stack+0x19/0x1b [17828.436330] [8102c0c6] warn_slowpath_common+0x76/0xa0 [17828.436337] [8102c167] warn_slowpath_fmt+0x47/0x50 [17828.436345] [8111dae8] ? kernfs_find_and_get_ns+0x48/0x60 [17828.436353] [8111c003] sysfs_remove_group+0xa3/0xb0 [17828.436362] [813fabee] dpm_sysfs_remove+0x3e/0x50 [17828.436370] [813f281d] device_del+0x3d/0x1b0 [17828.436380] [8140ae8b] scsi_target_reap_usercontext+0x2b/0x40 [17828.436444] [81040520] execute_in_process_context+0x60/0x70 [17828.436452] [8140c027] scsi_target_reap+0x77/0xa0 [17828.436458] [8140df10] scsi_device_dev_release_usercontext+0x160/0x190 [17828.436463] [81040520] execute_in_process_context+0x60/0x70 [17828.436467] [8140dda7] scsi_device_dev_release+0x17/0x20 [17828.436472] [813f1598] device_release+0x38/0xb0 [17828.436478] [8128c7b3] kobject_cleanup+0x43/0x80 [17828.436651] [8128be98] kobject_put+0x28/0x60 [17828.436656] [813f27d2] put_device+0x12/0x20 [17828.436661] [81402d70] scsi_device_put+0x10/0x20 [17828.43] [814106c4] scsi_disk_put+0x34/0x50 [17828.436670] [81410973] sd_release+0x33/0x70 [17828.436675] [810f36e4] __blkdev_put+0x144/0x180 [17828.436679] [810f368d] __blkdev_put+0xed/0x180 [17828.436683] [810f4757] blkdev_put+0x97/0x110 [17828.436687] [810f47f0] blkdev_close+0x20/0x30 [17828.436693] [810c47b2] __fput+0xe2/0x200 [17828.436698] [810c4909] fput+0x9/0x10 [17828.436703] [81042c0f] task_work_run+0x7f/0xc0 [17828.436708] [810024e6] do_notify_resume+0x66/0x70 [17828.436829] [810c23e1] ? filp_close+0x51/0x80 [17828.436835] [81663f64] 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-scsim=139031645920152w=2 http://marc.info/?l=linux-scsim=139031650720168w=2 If these patches have appeared in any git repositories yet, I don't know where. James, what happened to
Re: v3.14-rc2+ WARNING: CPU: 0 PID: 24108 at fs/sysfs/group.c:216 sysfs_remove_group+0xa3/0xb0()
On 17.2.2014 20:48, Alan Stern wrote: This isn't a USB problem. Hello, I'm experiencing very similar messages after every disconnection of USB soundcard (snd-usb-audio module). During searching for other similar occurrences of message, i've found few patches. One kind basically prevents sysfs from popping those messages at sysfs group attribute removal - https://lkml.org/lkml/2013/11/23/102 and isn't included in 3.14-rc2, other kind of patches, if i got that correctly, fixes removal ordering or its visibility at underlying subsystem (eg. SCSI, PCI for Thunderbolt hotplugging) to make sysfs happy. Do you know, that there was some general decision, to intentionally don't modify sysfs and fix that for every subsystem, which triggers that messages? Just asking, because then it would be probably nice to modify something also at USB audio.. my dmesg with WARNING: http://vpub.smucr.cz/pub/bbb/debug/dmesg-reconnections.log and i probably not alone: http://forums.funtoo.org/viewtopic.php?pid=10327 Best regards, Michal Smucr -- 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
