Tested with meta-intel: db84acfc8d9ed8dccd4a79de39fee337bc729662 poky daisy: a0958261265049904fd78a2ba0198d46e5e65ea9 Using core-image-sato-sdk-crownbay-noemgd. Steps to reproduce: 1. boot system 2. plug usb stick 3. unplug usb Notice error in dmesg log: [ 5265.914557] sdb: [ 5265.917608] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 5266.139948] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 5269.870892] usb 1-2: USB disconnect, device number 4 [ 5270.129310] ------------[ cut here ]------------ [ 5270.129334] WARNING: CPU: 1 PID: 21375 at /home/pokybuild/yocto-autobuilder/yocto-slave/crownbay-noemgd/build/build/tmp/work/crownbay_noemgd-poky-linux/linux-yocto/3.14.0+gitAUTOINC+fc8c30398d_0143c6ebb4-r0/linux/fs/sysfs/group.c:216 sysfs_remove_group+0x8f/0xa0() [ 5270.129339] sysfs group c1989dc8 not found for kobject 'target3:0:0' [ 5270.129342] Modules linked in: [last unloaded: hellomod] [ 5270.129356] CPU: 1 PID: 21375 Comm: umount Tainted: G W O 3.14.0-yocto-standard #1 [ 5270.129360] Hardware name: To be filled by O.E.M. To be filled by O.E.M./To be filled by O.E.M., BIOS 4.6.3 12/29/2011 [ 5270.129364] 00000000 00000000 f57f1d68 c16a6b5d f57f1da8 f57f1d98 c103f7bf c18886bc [ 5270.129380] f57f1dc4 0000537f c18885c4 000000d8 c119190f c119190f 00000000 c1989dc8 [ 5270.129395] f4848c1c f57f1db0 c103f814 00000009 f57f1da8 c18886bc f57f1dc4 f57f1dd8 [ 5270.129411] Call Trace: [ 5270.129426] [<c16a6b5d>] dump_stack+0x4b/0x75 [ 5270.129434] [<c103f7bf>] warn_slowpath_common+0x7f/0xa0 [ 5270.129443] [<c119190f>] ? sysfs_remove_group+0x8f/0xa0 [ 5270.129451] [<c119190f>] ? sysfs_remove_group+0x8f/0xa0 [ 5270.129459] [<c103f814>] warn_slowpath_fmt+0x34/0x40 [ 5270.129467] [<c119190f>] sysfs_remove_group+0x8f/0xa0 [ 5270.129478] [<c14168e7>] dpm_sysfs_remove+0x37/0x40 [ 5270.129488] [<c140e455>] device_del+0x35/0x180 [ 5270.129498] [<c142cd54>] scsi_target_reap_usercontext+0x24/0x30 [ 5270.129507] [<c105655c>] execute_in_process_context+0x4c/0x60 [ 5270.129515] [<c142dda0>] scsi_target_reap+0xa0/0xc0 [ 5270.129524] [<c142fac3>] scsi_device_dev_release_usercontext+0x123/0x150 [ 5270.129532] [<c105655c>] execute_in_process_context+0x4c/0x60 [ 5270.129540] [<c142f998>] scsi_device_dev_release+0x18/0x20 [ 5270.129548] [<c140db6e>] device_release+0x2e/0x90 [ 5270.129557] [<c112b26e>] ? kfree+0x8e/0x180 [ 5270.129564] [<c140db75>] ? device_release+0x35/0x90 [ 5270.129573] [<c1358fcd>] kobject_cleanup+0x2d/0x70 [ 5270.129581] [<c1358ed5>] kobject_put+0x25/0x60 [ 5270.129588] [<c1358ed5>] ? kobject_put+0x25/0x60 [ 5270.129596] [<c140dea4>] put_device+0x14/0x20 [ 5270.129603] [<c142492d>] scsi_device_put+0x2d/0x50 [ 5270.129611] [<c143328a>] scsi_disk_put+0x2a/0x40 [ 5270.129619] [<c143413c>] sd_release+0x2c/0x50 [ 5270.129627] [<c116b178>] __blkdev_put+0x138/0x170 [ 5270.129635] [<c116b926>] blkdev_put+0x46/0x110 [ 5270.129644] [<c113a90d>] kill_block_super+0x3d/0x70 [ 5270.129652] [<c113ab8b>] deactivate_locked_super+0x2b/0x50 [ 5270.129660] [<c113b09e>] deactivate_super+0x3e/0x60 [ 5270.129668] [<c115351f>] mntput_no_expire+0xbf/0x140 [ 5270.129676] [<c11544cc>] SyS_umount+0x9c/0x350 [ 5270.129684] [<c115479f>] SyS_oldumount+0x1f/0x30 [ 5270.129693] [<c16ac308>] syscall_call+0x7/0xb [ 5270.129699] ---[ end trace 0f821676223a2e2b ]---
This looks to be BSP-independent to me and more about FS or USB. Assigning to Bruce as a generic kernel issue - but he need not be the only one to look at it! The kernel should of course not crash, even if the stick was not properly unmounted.
We are removing M5 from the 1.7 release so I'm moving this to M4.
Created attachment 1979 [details] call trace in dmesg Similar behavior found for Jasperforest using core-image-lsb-sdk on daisy: meta-intel 03c1dd5ca66fac19e681d52dd398591fd414a518 meta-qt3 da313317d10c0e34f9a3f1a271c5cd23c3ca3850 poky 3c66ad23bec2e69c2a69c8a66c20277c0a0deeb0
I've never seen this on any of my boards, but then again, I don't have many of the intel boards available for test. Can we confirm that this is still happening with the latest meta-intel ?
I just tried doing this on the sugarbay system with the v3.17.1 kernel, and there was no kernel call trace in the dmesg. Which kernel was the BSP using?
In the comment 5, I was using core-image-sato.
I am moving this out of NEEDINFO since it appears the question by Bruce was answered by Nitin. If not, please move this back into NEEDINFO and clarify the question.
It's actually the opposite. Nitin couldn't reproduce this, so I'm marking it as closed, not accepted.