Flash drive removal glitches

89c51 · 2014-02-22 16:23:11

This is what happens after i plug in a flash drive. It doesn't unmount (right click and unmount in E18) and if you remove it by hand it gives me:

Feb 22 18:18:56 mainland kernel: usb 3-1: new high-speed USB device number 9 using xhci_hcd
Feb 22 18:18:56 mainland kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Feb 22 18:18:56 mainland kernel: scsi15 : usb-storage 3-1:1.0
Feb 22 18:18:57 mainland kernel: scsi 15:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: Attached scsi generic sg2 type 0
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: [sdb] Write Protect is off
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: [sdb] Mode Sense: 43 00 00 00
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 22 18:18:57 mainland kernel:  sdb: sdb1
Feb 22 18:18:57 mainland kernel: sd 15:0:0:0: [sdb] Attached SCSI removable disk
Feb 22 18:19:00 mainland kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 22 18:19:00 mainland udisksd[467]: Mounted /dev/sdb1 at /run/media/toliz/ARCH_201211 on behalf of uid 1000
Feb 22 18:19:08 mainland udisksd[467]: Cleaning up mount point /run/media/toliz/ARCH_201211 (device 8:17 is not mounted)
Feb 22 18:19:08 mainland udisksd[467]: Unmounted /dev/sdb1 on behalf of uid 1000
Feb 22 18:19:09 mainland kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 22 18:19:09 mainland udisksd[467]: Mounted /dev/sdb1 at /run/media/toliz/ARCH_201211 on behalf of uid 1000
Feb 22 18:19:27 mainland kernel: usb 3-1: USB disconnect, device number 9
Feb 22 18:19:27 mainland udisksd[467]: Cleaning up mount point /run/media/toliz/ARCH_201211 (device 8:17 no longer exist)
Feb 22 18:19:28 mainland kernel: ------------[ cut here ]------------
Feb 22 18:19:28 mainland kernel: WARNING: CPU: 4 PID: 437 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
Feb 22 18:19:28 mainland kernel: sysfs group ffffffff81895c40 not found for kobject 'target15:0:0'
Feb 22 18:19:28 mainland kernel: Modules linked in: fuse usb_storage w83627ehf hwmon_vid mousedev hid_generic hid_logitech_dj usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support nls_cp...pclmul crct10dif_cFeb 22 18:19:28 mainland kernel:  drm_kms_helper ttm drm i2c_core [last unloaded: vboxdrv]
Feb 22 18:19:28 mainland kernel: CPU: 4 PID: 437 Comm: enlightenment Tainted: G        W  O 3.13.4-1-ARCH #1
Feb 22 18:19:28 mainland kernel: Hardware name:                  /DZ77BH-55K, BIOS BHZ7710H.86A.0094.2012.1101.1115 11/01/2012
Feb 22 18:19:28 mainland kernel:  0000000000000009 ffff88030a87dad0 ffffffff81512f54 ffff88030a87db18
Feb 22 18:19:28 mainland kernel:  ffff88030a87db08 ffffffff81061a3d 0000000000000000 ffffffff81895c40
Feb 22 18:19:28 mainland kernel:  ffff8800dd2ae438 ffff880306a7f190 ffff8802bacef000 ffff88030a87db68
Feb 22 18:19:28 mainland kernel: Call Trace:
Feb 22 18:19:28 mainland kernel:  [<ffffffff81512f54>] dump_stack+0x4d/0x6f
Feb 22 18:19:28 mainland kernel:  [<ffffffff81061a3d>] warn_slowpath_common+0x7d/0xa0
Feb 22 18:19:28 mainland kernel:  [<ffffffff81061aac>] warn_slowpath_fmt+0x4c/0x50
Feb 22 18:19:28 mainland kernel:  [<ffffffff8151811e>] ? mutex_unlock+0xe/0x10
Feb 22 18:19:28 mainland kernel:  [<ffffffff812191ee>] ? sysfs_get_dirent_ns+0x4e/0x70
Feb 22 18:19:28 mainland kernel:  [<ffffffff8121a376>] sysfs_remove_group+0xc6/0xd0
Feb 22 18:19:28 mainland kernel:  [<ffffffff813b6e93>] dpm_sysfs_remove+0x43/0x50
Feb 22 18:19:28 mainland kernel:  [<ffffffff813acd15>] device_del+0x45/0x1c0
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02112b7>] scsi_target_reap_usercontext+0x27/0x40 [scsi_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffff8107b867>] execute_in_process_context+0x67/0x70
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02125d4>] scsi_target_reap+0xc4/0xf0 [scsi_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffffa0214558>] scsi_device_dev_release_usercontext+0x188/0x1c0 [scsi_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffff8107b867>] execute_in_process_context+0x67/0x70
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02143cc>] scsi_device_dev_release+0x1c/0x20 [scsi_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffff813ac252>] device_release+0x32/0xa0
Feb 22 18:19:28 mainland kernel:  [<ffffffff812b6a57>] kobject_cleanup+0x77/0x1b0
Feb 22 18:19:28 mainland kernel:  [<ffffffff812b68d8>] kobject_put+0x28/0x60
Feb 22 18:19:28 mainland kernel:  [<ffffffff813ac657>] put_device+0x17/0x20
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02085eb>] scsi_device_put+0x3b/0x50 [scsi_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02967e0>] scsi_disk_put+0x30/0x50 [sd_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffffa02976a1>] sd_release+0x31/0x70 [sd_mod]
Feb 22 18:19:28 mainland kernel:  [<ffffffff811dc70c>] __blkdev_put+0x17c/0x1b0
Feb 22 18:19:28 mainland kernel:  [<ffffffff811dc6a7>] __blkdev_put+0x117/0x1b0
Feb 22 18:19:28 mainland kernel:  [<ffffffff811dd06e>] blkdev_put+0x4e/0x140
Feb 22 18:19:28 mainland kernel:  [<ffffffff811a5e94>] kill_block_super+0x44/0x70
Feb 22 18:19:28 mainland kernel:  [<ffffffff811a615d>] deactivate_locked_super+0x3d/0x60
Feb 22 18:19:28 mainland kernel:  [<ffffffff811a6716>] deactivate_super+0x46/0x60
Feb 22 18:19:28 mainland kernel:  [<ffffffff811c2455>] mntput_no_expire+0xe5/0x170
Feb 22 18:19:28 mainland kernel:  [<ffffffff811c2504>] mntput+0x24/0x40
Feb 22 18:19:28 mainland kernel:  [<ffffffff811a54f7>] __fput+0x127/0x220
Feb 22 18:19:28 mainland kernel:  [<ffffffff811a563e>] ____fput+0xe/0x10
Feb 22 18:19:28 mainland kernel:  [<ffffffff810805cf>] task_work_run+0x9f/0xe0
Feb 22 18:19:28 mainland kernel:  [<ffffffff81014e2c>] do_notify_resume+0x8c/0xa0
Feb 22 18:19:28 mainland kernel:  [<ffffffff8152166a>] int_signal+0x12/0x17
Feb 22 18:19:28 mainland kernel: ---[ end trace c848c59dda28fc2f ]---

The system works fine. No crash not anything else weird.

Rexilion · 2014-02-22 17:21:31

Known fallout from the kernfs seperation: http://www.spinics.net/lists/linux-usb/msg102568.html

Arch Linux

#1 2014-02-22 16:23:11

Flash drive removal glitches

#2 2014-02-22 17:21:31

Re: Flash drive removal glitches

Board footer