Auto-mount failing with segfault on FAT drives

silverbucket · 2014-03-16 16:04:11

I've been running Arch on ThinkPads for years, just got an x240 and installed Arch on it. Everything seems to work fine except for external drives of any sort.

I'm running Gnome 3.

With my USB stick, every time I insert it, Nautilus detects it and when I attempt to view the drive it fails. Here's the dmesg output:

[32426.659595] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[32426.675126] usb-storage 2-1:1.0: USB Mass Storage device detected
[32426.675173] scsi5 : usb-storage 2-1:1.0
[32427.676716] scsi 5:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
[32427.677167] sd 5:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.8 GiB)
[32427.677442] sd 5:0:0:0: [sdb] Write Protect is off
[32427.677458] sd 5:0:0:0: [sdb] Mode Sense: 45 00 00 00
[32427.677775] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[32427.831483]  sdb: sdb1
[32427.832493] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[32439.190500] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[32439.328724] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[32444.339799] usb 2-1: device descriptor read/8, error -110
[32444.443060] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[32449.454646] usb 2-1: device descriptor read/8, error -110
[32449.611683] sd 5:0:0:0: [sdb] Unhandled error code
[32449.611686] sd 5:0:0:0: [sdb]  
[32449.611687] Result: hostbyte=0x07 driverbyte=0x00
[32449.611688] sd 5:0:0:0: [sdb] CDB: 
[32449.611690] usb 2-1: USB disconnect, device number 4
[32449.611689] cdb[0]=0x28: 28 00 00 00 0d 9b 00 00 0f 00
[32449.611695] end_request: I/O error, dev sdb, sector 3483
[32449.617844] sd 5:0:0:0: [sdb] Unhandled error code
[32449.617846] sd 5:0:0:0: [sdb]  
[32449.617847] Result: hostbyte=0x01 driverbyte=0x00
[32449.617848] sd 5:0:0:0: [sdb] CDB: 
[32449.617849] cdb[0]=0x28: 28 00 00 00 0d 9c 00 00 0e 00
[32449.617852] end_request: I/O error, dev sdb, sector 3484
[32449.617876] sd 5:0:0:0: [sdb] Unhandled error code
[32449.617877] sd 5:0:0:0: [sdb]  
[32449.617878] Result: hostbyte=0x01 driverbyte=0x00
[32449.617878] sd 5:0:0:0: [sdb] CDB: 
[32449.617879] cdb[0]=0x28: 28 00 00 00 0c ab 00 00 f0 00
[32449.617882] end_request: I/O error, dev sdb, sector 3243
[32449.617952] FAT-fs (sdb1): FAT read failed (blocknr 3211)
[32449.618677] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801574ef380
[32449.618680] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801574ef3c0
[32449.621107] FAT-fs (sdb1): Directory bread(block 32768) failed
[32449.621111] FAT-fs (sdb1): Directory bread(block 32769) failed
[32449.621113] FAT-fs (sdb1): Directory bread(block 32770) failed
[32449.621115] FAT-fs (sdb1): Directory bread(block 32771) failed
[32449.621117] FAT-fs (sdb1): Directory bread(block 32772) failed
[32449.621119] FAT-fs (sdb1): Directory bread(block 32773) failed
[32449.621120] FAT-fs (sdb1): Directory bread(block 32774) failed
[32449.621122] FAT-fs (sdb1): Directory bread(block 32775) failed
[32449.621124] FAT-fs (sdb1): Directory bread(block 32776) failed
[32449.621126] FAT-fs (sdb1): Directory bread(block 32777) failed
[31813.104727] ------------[ cut here ]------------
[31813.104734] WARNING: CPU: 3 PID: 7798 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
[31813.104736] sysfs group ffffffff81895c40 not found for kobject 'target3:0:0'
[31813.104737] Modules linked in: nls_cp437 vfat fat twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts loop usb_storage usbhid hid fuse ctr ccm snd_hda_codec_hdmi joydev mousedev arc4 snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iTCO_wdt iTCO_vendor_support cdc_mbim microcode evdev cdc_ncm psmouse uvcvideo pcspkr serio_raw iwlmvm usbnet videobuf2_vmalloc mii videobuf2_memops mac80211 cdc_acm videobuf2_core cdc_wdm videodev media btusb iwlwifi bluetooth cfg80211 rtsx_pci_ms memstick wmi tpm_tis thinkpad_acpi i915 snd_hda_intel nvram tpm rfkill ac battery snd_hda_codec video intel_agp intel_gtt drm_kms_helper drm e1000e snd_hwdep snd_pcm snd_page_alloc thermal
[31813.104776]  snd_timer mei_me lpc_ich mei i2c_algo_bit snd button shpchp i2c_i801 ptp soundcore pps_core i2c_core processor ext4 crc16 mbcache jbd2 dm_crypt dm_mod sd_mod rtsx_pci_sdmmc mmc_core atkbd libps2 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci ehci_pci libahci ehci_hcd libata scsi_mod rtsx_pci xhci_hcd usbcore usb_common i8042 serio
[31813.104801] CPU: 3 PID: 7798 Comm: umount Not tainted 3.13.6-1-ARCH #1
[31813.104802] Hardware name: LENOVO 20AL009NMC/20AL009NMC, BIOS GIET66WW (2.16 ) 12/02/2013
[31813.104804]  0000000000000009 ffff88013ecb5b40 ffffffff81513274 ffff88013ecb5b88
[31813.104806]  ffff88013ecb5b78 ffffffff81061a3d 0000000000000000 ffffffff81895c40
[31813.104809]  ffff8800c72a5c38 ffff8802114d4190 ffff8801728fb000 ffff88013ecb5bd8
[31813.104812] Call Trace:
[31813.104818]  [<ffffffff81513274>] dump_stack+0x4d/0x6f
[31813.104824]  [<ffffffff81061a3d>] warn_slowpath_common+0x7d/0xa0
[31813.104827]  [<ffffffff81061aac>] warn_slowpath_fmt+0x4c/0x50
[31813.104831]  [<ffffffff8151843e>] ? mutex_unlock+0xe/0x10
[31813.104834]  [<ffffffff8121925e>] ? sysfs_get_dirent_ns+0x4e/0x70
[31813.104837]  [<ffffffff8121a3e6>] sysfs_remove_group+0xc6/0xd0
[31813.104843]  [<ffffffff813b7033>] dpm_sysfs_remove+0x43/0x50
[31813.104846]  [<ffffffff813aceb5>] device_del+0x45/0x1c0
[31813.104857]  [<ffffffffa00a52b7>] scsi_target_reap_usercontext+0x27/0x40 [scsi_mod]
[31813.104862]  [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[31813.104870]  [<ffffffffa00a65d4>] scsi_target_reap+0xc4/0xf0 [scsi_mod]
[31813.104879]  [<ffffffffa00a8558>] scsi_device_dev_release_usercontext+0x188/0x1c0 [scsi_mod]
[31813.104882]  [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[31813.104890]  [<ffffffffa00a83cc>] scsi_device_dev_release+0x1c/0x20 [scsi_mod]
[31813.104894]  [<ffffffff813ac3f2>] device_release+0x32/0xa0
[31813.104899]  [<ffffffff812b6b47>] kobject_cleanup+0x77/0x1b0
[31813.104902]  [<ffffffff812b69c8>] kobject_put+0x28/0x60
[31813.104906]  [<ffffffff813ac7f7>] put_device+0x17/0x20
[31813.104913]  [<ffffffffa009c5eb>] scsi_device_put+0x3b/0x50 [scsi_mod]
[31813.104920]  [<ffffffffa025e7e0>] scsi_disk_put+0x30/0x50 [sd_mod]
[31813.104926]  [<ffffffffa025f6a1>] sd_release+0x31/0x70 [sd_mod]
[31813.104931]  [<ffffffff811dc75c>] __blkdev_put+0x17c/0x1b0
[31813.104936]  [<ffffffff811dc6f7>] __blkdev_put+0x117/0x1b0
[31813.104940]  [<ffffffff811dd0be>] blkdev_put+0x4e/0x140
[31813.104944]  [<ffffffff811a5f64>] kill_block_super+0x44/0x70
[31813.104947]  [<ffffffff811a622d>] deactivate_locked_super+0x3d/0x60
[31813.104950]  [<ffffffff811a67e6>] deactivate_super+0x46/0x60
[31813.104954]  [<ffffffff811c24d5>] mntput_no_expire+0xe5/0x170
[31813.104958]  [<ffffffff811c3730>] SyS_umount+0x90/0x3c0
[31813.104962]  [<ffffffff8151d8be>] ? do_page_fault+0xe/0x10
[31813.104966]  [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
[31813.104968] ---[ end trace 9c2068df074620da ]---

I never had any trouble this this before on my previous laptop (Lenovo ThinkPad E330).

Likewise, when I use TrueCrypt to mount a volume, although I don't get the stack trace, It does never shows up in Nautilus, and dmesg has the following to say about it:

[31234.534922] loop: module loaded
[31234.610930] FAT-fs (dm-5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

I can view the drive, however, so it's not as bad as the USB stick, but still not the correct behavior. There is no automount and Nautilus does not show it in the device list.

I've tried formatting the USB stick a few different times (it needs to be FAT for compatibility) and always Arch ends up corrupting the drive and making it useless.

Anyone have any idea as to what's going on here?

Thanks
-Nick

Last edited by silverbucket (2014-03-16 23:59:56)

anatolik · 2014-03-16 19:44:27

silverbucket wrote:

[31234.610930] FAT-fs (dm-5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Well, it literally says that the partition is not in a correct state and you need fsck to repair it. After you repair it, do you see the problem again?

Note that before physically unplugging your USB stick you need to unmount it. It will guarantee that the data is written back correctly.

If you repaired the USB (or formatted in anew), then ran "umount" and if you still see this message - this points to a real issue.

silverbucket · 2014-03-16 19:56:27

anatolik wrote:

silverbucket wrote:
[31234.610930] FAT-fs (dm-5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Well, it literally says that the partition is not in a correct state and you need fsck to repair it. After you repair it, do you see the problem again?
Note that before physically unplugging your USB stick you need to unmount it. It will guarantee that the data is written back correctly.
If you repaired the USB (or formatted in anew), then ran "umount" and if you still see this message - this points to a real issue.

Correct, I should have clarified, this is continually happening after fsck / reformatting the drive or any number of attempts to "start fresh" this always happens and I'm careful to unmount the drive before pulling it out.

Running just fsck on the drive doesn't seem to effect the error at all, it will say the same thing next time.

When I freshly format the drive and re-insert it, it works the first time, but fails in the same manner on subsequent inserts, event after making sure I unmounted before pulling it out.

I should add that, even with a corrupt partition, I've never seen this core dump happen before. Unless I'm mistaken this is not normal behavior and indicates something more profound is going on here, right?

Last edited by silverbucket (2014-03-16 19:57:41)

silverbucket · 2014-03-16 22:55:44

Also, when I plug this USB stick into my other Arch Linux laptop (the E330) it automounts fine, without any errors or core dumps. This is definitely something with my new system. I'm not sure if this is a hardware or OS issue though. I am leaning toward something with the OS as I installed the system from this same USB stick without issue.

Last edited by silverbucket (2014-03-16 22:57:00)

silverbucket · 2014-03-16 23:18:31

Trying again, to manually mount the USB stick, when I insert it, dmesg shows:

[22021.214586] usb-storage 2-1:1.0: USB Mass Storage device detected
[22021.214633] scsi5 : usb-storage 2-1:1.0
[22022.215965] scsi 5:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
[22022.216251] sd 5:0:0:0: Attached scsi generic sg1 type 0
[22022.216440] sd 5:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.8 GiB)
[22022.216733] sd 5:0:0:0: [sdb] Write Protect is off
[22022.216736] sd 5:0:0:0: [sdb] Mode Sense: 45 00 00 00
[22022.217088] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[22022.373041]  sdb: sdb1
[22022.374051] sd 5:0:0:0: [sdb] Attached SCSI removable disk

I then try to mount it with:

# mount /dev/sdb1 /mnt/usbstick

And although the command appears to be successful, I get the following in dmesg:

[22182.804311] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[22186.212884] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[22191.224027] usb 2-1: device descriptor read/8, error -110
[22191.327268] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[22196.338854] usb 2-1: device descriptor read/8, error -110
[22196.495462] sd 5:0:0:0: [sdb] Unhandled error code
[22196.495465] sd 5:0:0:0: [sdb]  
[22196.495466] Result: hostbyte=0x07 driverbyte=0x00
[22196.495468] sd 5:0:0:0: [sdb] CDB: 
[22196.495470] usb 2-1: USB disconnect, device number 4
[22196.495468] cdb[0]=0x28: 28 00 00 00 0c ad 00 00 f0 00
[22196.495477] end_request: I/O error, dev sdb, sector 3245
[22196.502037] sd 5:0:0:0: [sdb] Unhandled error code
[22196.502041] sd 5:0:0:0: [sdb]  
[22196.502043] Result: hostbyte=0x01 driverbyte=0x00
[22196.502045] sd 5:0:0:0: [sdb] CDB: 
[22196.502046] cdb[0]=0x28: 28 00 00 00 0c ae 00 00 ef 00
[22196.502056] end_request: I/O error, dev sdb, sector 3246
[22196.502138] FAT-fs (sdb1): FAT read failed (blocknr 3213)
[22196.502139] sd 5:0:0:0: [sdb] Unhandled error code
[22196.502141] sd 5:0:0:0: [sdb]  
[22196.502142] Result: hostbyte=0x01 driverbyte=0x00
[22196.502143] sd 5:0:0:0: [sdb] CDB: 
[22196.502144] cdb[0]=0x28: 28 00 00 00 0d 9d 00 00 0d 00
[22196.502152] end_request: I/O error, dev sdb, sector 3485
[22196.504146] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800785c7980
[22196.504149] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800785c79c0

A `df` does not show the mounted location, neither does Nautilus, however `mount` does.

/dev/sdb1 on /mnt/ZELENACEK type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

When I attempt to unmount it:

# umount /dev/sdb1

I get the following dmesg output:

[22410.233289] FAT-fs (sdb1): FAT read failed (blocknr 3210)
[22415.819947] FAT-fs (sdb1): Directory bread(block 32768) failed
[22415.819951] FAT-fs (sdb1): Directory bread(block 32769) failed
[22415.819953] FAT-fs (sdb1): Directory bread(block 32770) failed
[22415.819955] FAT-fs (sdb1): Directory bread(block 32771) failed
[22415.819956] FAT-fs (sdb1): Directory bread(block 32772) failed
[22415.819958] FAT-fs (sdb1): Directory bread(block 32773) failed
[22415.819960] FAT-fs (sdb1): Directory bread(block 32774) failed
[22415.819961] FAT-fs (sdb1): Directory bread(block 32775) failed
[22415.819963] FAT-fs (sdb1): Directory bread(block 32776) failed
[22415.819964] FAT-fs (sdb1): Directory bread(block 32777) failed
[22556.688959] ------------[ cut here ]------------
[22556.688967] WARNING: CPU: 2 PID: 27239 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
[22556.688968] sysfs group ffffffff81895c40 not found for kobject 'target5:0:0'
[22556.688970] Modules linked in: sg nls_cp437 vfat fat usb_storage fuse ctr ccm snd_hda_codec_hdmi joydev mousedev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iTCO_wdt iTCO_vendor_support microcode iwlmvm evdev cdc_mbim pcspkr uvcvideo psmouse serio_raw mac80211 videobuf2_vmalloc videobuf2_memops btusb videobuf2_core videodev cdc_ncm usbnet bluetooth mii cdc_acm cdc_wdm media iwlwifi rtsx_pci_ms cfg80211 memstick thermal snd_hda_codec_realtek wmi e1000e i915 ac thinkpad_acpi nvram rfkill battery tpm_tis snd_hda_intel tpm snd_hda_codec intel_agp intel_gtt snd_hwdep drm_kms_helper mei_me snd_pcm i2c_i801 ptp drm snd_page_alloc video snd_timer mei i2c_algo_bit snd button shpchp soundcore pps_core i2c_core lpc_ich processor ext4 crc16 mbcache jbd2 dm_crypt dm_mod sd_mod rtsx_pci_sdmmc
[22556.689016]  mmc_core atkbd libps2 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci libata ehci_pci ehci_hcd xhci_hcd rtsx_pci scsi_mod usbcore usb_common i8042 serio
[22556.689032] CPU: 2 PID: 27239 Comm: umount Tainted: G        W    3.13.6-1-ARCH #1
[22556.689034] Hardware name: LENOVO 20AL009NMC/20AL009NMC, BIOS GIET66WW (2.16 ) 12/02/2013
[22556.689035]  0000000000000009 ffff880066217b40 ffffffff81513274 ffff880066217b88
[22556.689038]  ffff880066217b78 ffffffff81061a3d 0000000000000000 ffffffff81895c40
[22556.689040]  ffff88020af40438 ffff880089e30190 ffff880211ce7800 ffff880066217bd8
[22556.689043] Call Trace:
[22556.689048]  [<ffffffff81513274>] dump_stack+0x4d/0x6f
[22556.689052]  [<ffffffff81061a3d>] warn_slowpath_common+0x7d/0xa0
[22556.689055]  [<ffffffff81061aac>] warn_slowpath_fmt+0x4c/0x50
[22556.689058]  [<ffffffff8151843e>] ? mutex_unlock+0xe/0x10
[22556.689060]  [<ffffffff8121925e>] ? sysfs_get_dirent_ns+0x4e/0x70
[22556.689063]  [<ffffffff8121a3e6>] sysfs_remove_group+0xc6/0xd0
[22556.689067]  [<ffffffff813b7033>] dpm_sysfs_remove+0x43/0x50
[22556.689070]  [<ffffffff813aceb5>] device_del+0x45/0x1c0
[22556.689079]  [<ffffffffa00c02b7>] scsi_target_reap_usercontext+0x27/0x40 [scsi_mod]
[22556.689082]  [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[22556.689089]  [<ffffffffa00c15d4>] scsi_target_reap+0xc4/0xf0 [scsi_mod]
[22556.689096]  [<ffffffffa00c3558>] scsi_device_dev_release_usercontext+0x188/0x1c0 [scsi_mod]
[22556.689098]  [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[22556.689105]  [<ffffffffa00c33cc>] scsi_device_dev_release+0x1c/0x20 [scsi_mod]
[22556.689107]  [<ffffffff813ac3f2>] device_release+0x32/0xa0
[22556.689111]  [<ffffffff812b6b47>] kobject_cleanup+0x77/0x1b0
[22556.689114]  [<ffffffff812b69c8>] kobject_put+0x28/0x60
[22556.689117]  [<ffffffff813ac7f7>] put_device+0x17/0x20
[22556.689123]  [<ffffffffa00b75eb>] scsi_device_put+0x3b/0x50 [scsi_mod]
[22556.689128]  [<ffffffffa029a7e0>] scsi_disk_put+0x30/0x50 [sd_mod]
[22556.689133]  [<ffffffffa029b6a1>] sd_release+0x31/0x70 [sd_mod]
[22556.689136]  [<ffffffff811dc75c>] __blkdev_put+0x17c/0x1b0
[22556.689140]  [<ffffffff811dc6f7>] __blkdev_put+0x117/0x1b0
[22556.689143]  [<ffffffff811dd0be>] blkdev_put+0x4e/0x140
[22556.689145]  [<ffffffff811a5f64>] kill_block_super+0x44/0x70
[22556.689148]  [<ffffffff811a622d>] deactivate_locked_super+0x3d/0x60
[22556.689150]  [<ffffffff811a67e6>] deactivate_super+0x46/0x60
[22556.689153]  [<ffffffff811c24d5>] mntput_no_expire+0xe5/0x170
[22556.689156]  [<ffffffff811c3730>] SyS_umount+0x90/0x3c0
[22556.689158]  [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
[22556.689160] ---[ end trace 615f2c14f65f6abb ]---

If I take the USB stick out and plug it in to my other Arch Linux laptop, the drive mounts fine (and complains about fsck only because of the problems incurred on my main laptop). I know the USB stick is good, it's new and I've used it many times between my other machines. I'm assuming the hardware is good as it's a new laptop, I installed Arch Linux from this same USB stick without an issue. I've also used other types of USB devices, like wireless headphones, without issues.

It must be some system configuration error. Perhaps something with the kernel or system libraries that are / are not installed? lib32 issues? (it's an x86_64 install)? I don't know, I'm grasping at straws. I have read through the USB_Storage_Devices and Udisks Arch Wiki pages without any luck.

Any help is greatly appreciated as I currently can't get any large amounts data on or off this laptop easily.

Last edited by silverbucket (2014-03-16 23:42:56)

silverbucket · 2014-03-17 00:12:42

I've just formatted the USB stick as ext4 and it seems to work fine. So this is definitely an system issue with FAT drives.

Any advice on how I can debug/fix this issue?

fdisk previously reported the partition as

/dev/sdb1 *       32  60566015 30282992   c W95 FAT32 (LBA)

silverbucket · 2014-03-18 09:48:57

No one has any ideas about this?

dreieinhalb · 2014-03-18 14:15:44

I have exactly the same problem here with my new system (Gigabyte GA-Z87X-UD3H, i5-4570) and seems that the mainline-kernel (3.14.0-1-mainline, build from AUR) fixes it.

WonderWoofy · 2014-03-18 17:24:15

silverbucket wrote:

No one has any ideas about this?

silverbucket, please use the edit button rather than posting over and over again. If someone has an idea about what might be happening here, they will reply.

R00KIE · 2014-03-19 18:49:36

I remember seeing someone report a similar problem before, it happened with fat32 on usb3, I did test it and I can confirm that at least that combination has problems.

anatolik · 2014-03-20 12:44:50

There is somewhat similar topic. https://bbs.archlinux.org/viewtopic.php?id=178774 The user posted a kernel warning the same you have. I googled it and found that 3.13 kernel has issues with USB stack.

Also @dreieinhalb says he had the same issue but 3.14 fixed it, so the problem sounds like a kernel bug. To double-check, R00KIE could you please downgrade to kernel 3.12 and see if it fixes your problem?

brain0 · 2014-03-20 14:34:11

USB 3.0 (xhci) is horribly broken right now, and the USB maintainers keep failing to submit the correct patches to the stable kernel guys. They "fixed" the problem two or three times since 3.13 came out, and broke something else. I don't have the full picture of the situation, other than that it is a complete mess. I also can't seem to find out which patches to backport in order to fix this.

R00KIE · 2014-03-20 14:37:46

@anatolik
Yes, with the last of linux 3.12 it seems to work just fine.

silverbucket · 2014-03-20 14:39:24

Hey @ROOKIE how did you downgrade your kernel? I tried with the AUR downgrader package, but it did not allow me to choose 3.12, just a previous 3.13.x version.

R00KIE · 2014-03-20 15:27:11

silverbucket wrote:

Hey @ROOKIE how did you downgrade your kernel? I tried with the AUR downgrader package, but it did not allow me to choose 3.12, just a previous 3.13.x version.

Manually.

You need to get the kernel and anything that directly depends on a specific version of the kernel and install them manually. You can get older versions of packages in the Arch Rollback Machine [1].

It should be ok to cherry pick the kernel and a few other packages and downgrade them _but_ you should be comfortable with using rescue media to fix things just in case something goes wrong.

[1] https://wiki.archlinux.org/index.php/Ar … ck_Machine

Arch Linux

#1 2014-03-16 16:04:11

Auto-mount failing with segfault on FAT drives

#2 2014-03-16 19:44:27

Re: Auto-mount failing with segfault on FAT drives

#3 2014-03-16 19:56:27

Re: Auto-mount failing with segfault on FAT drives

#4 2014-03-16 22:55:44

Re: Auto-mount failing with segfault on FAT drives

#5 2014-03-16 23:18:31

Re: Auto-mount failing with segfault on FAT drives

#6 2014-03-17 00:12:42

Re: Auto-mount failing with segfault on FAT drives

#7 2014-03-18 09:48:57

Re: Auto-mount failing with segfault on FAT drives

#8 2014-03-18 14:15:44

Re: Auto-mount failing with segfault on FAT drives

#9 2014-03-18 17:24:15

Re: Auto-mount failing with segfault on FAT drives

#10 2014-03-19 18:49:36

Re: Auto-mount failing with segfault on FAT drives

#11 2014-03-20 12:44:50

Re: Auto-mount failing with segfault on FAT drives

#12 2014-03-20 14:34:11

Re: Auto-mount failing with segfault on FAT drives

#13 2014-03-20 14:37:46

Re: Auto-mount failing with segfault on FAT drives

#14 2014-03-20 14:39:24

Re: Auto-mount failing with segfault on FAT drives

#15 2014-03-20 15:27:11

Re: Auto-mount failing with segfault on FAT drives

Board footer