You are not logged in.

#1 2013-08-04 23:22:28

D4ve
Member
Registered: 2012-08-02
Posts: 209

[Solved] Can't mount specific usb device after kernel upgrade

So, hi everyone smile

I've got a usb device which works on other systems (usb audio player, android tablet) but not on my archlinux htpc.

System is up to date, the usb stick worked a few days ago (here shown as /dev/sdc), relevant infos (shortened):

$ uname -a
Linux arch247 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
$ lsusb
Bus 009 Device 006: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
$ dmesg
[ 1788.621747] usb 9-4: new full-speed USB device number 8 using ohci_hcd
[ 1788.771370] usb 9-4: not running at top speed; connect to a high speed hub
[ 1788.785511] usb-storage 9-4:1.0: USB Mass Storage device detected
[ 1788.793170] scsi13 : usb-storage 9-4:1.0
[ 1789.801391] scsi 13:0:0:0: Direct-Access     General  USB Flash Disk   1.00 PQ: 0 ANSI: 2
[ 1789.814964] sd 13:0:0:0: [sdc] 15669248 512-byte logical blocks: (8.02 GB/7.47 GiB)
[ 1789.819230] sd 13:0:0:0: [sdc] Write Protect is off
[ 1789.819243] sd 13:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 1789.825267] sd 13:0:0:0: [sdc] No Caching mode page present
[ 1789.825281] sd 13:0:0:0: [sdc] Assuming drive cache: write through
$ lsmod | grep ohci
ohci_hcd               26544  0 
usbcore               176991  6 ath3k,btusb,usb_storage,ohci_hcd,usbhid,xhci_hcd
$ sudo fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x89675d3a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    50333695    25165824   83  Linux
/dev/sda2        50333696   234441647    92053976   83  Linux

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004e72c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907022847  1953510400   83  Linux

Disk /dev/sdc: 8022 MB, 8022654976 bytes, 15669248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0009ae2c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048    15669247     7833600    c  W95 FAT32 (LBA)

I can't reformat the device at the moment (lack of computers here). The usb port on the pc is working (tested with another fat32 formatted usb stick).

Any ideas? Hints? Tips?

Last edited by D4ve (2013-08-18 18:48:35)

Offline

#2 2013-08-05 05:55:15

tzomatz
Member
Registered: 2013-07-05
Posts: 30

Re: [Solved] Can't mount specific usb device after kernel upgrade

Tried rebooting? And can you mount other usb devices?

Never mind. Just read it now.

I originally thought you might just have updated your kernel. I cant mount usb sticks when I have updated, so I have to reboot before trying. But as I now see, your problem is with only one.

Last edited by tzomatz (2013-08-05 05:57:09)

Offline

#3 2013-08-05 06:16:00

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,829

Re: [Solved] Can't mount specific usb device after kernel upgrade

What is the output of pacman -Qi linux    ??
Check the version number and verify that it matches the output of uname -a


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#4 2013-08-05 09:55:06

sirocco
Member
Registered: 2008-03-10
Posts: 145

Re: [Solved] Can't mount specific usb device after kernel upgrade

I have a similar problem. No automount, but manual mount is possible after few minutes after usb stick insertion.

[ 8677.095849] usb 2-5: new high-speed USB device number 2 using ehci-pci
[ 8677.559298] usb-storage 2-5:1.0: USB Mass Storage device detected
[ 8677.563037] scsi6 : usb-storage 2-5:1.0
[ 8677.563534] usbcore: registered new interface driver usb-storage
[ 8678.567074] scsi 6:0:0:0: Direct-Access     General  USB Flash Disk   2.00 PQ: 0 ANSI: 2
[ 8678.569681] sd 6:0:0:0: [sdc] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
[ 8678.570294] sd 6:0:0:0: [sdc] Write Protect is off
[ 8678.570303] sd 6:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[ 8678.570924] sd 6:0:0:0: [sdc] No Caching mode page present
[ 8678.570933] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 8709.119170] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8740.212503] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8771.145848] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8802.185849] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8802.314813] sd 6:0:0:0: [sdc] No Caching mode page present
[ 8802.314826] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 8833.119449] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8864.159161] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8895.145842] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8926.132490] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8926.260282]  sdc:
[ 8926.264719] sd 6:0:0:0: [sdc] No Caching mode page present
[ 8926.264731] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 8957.172484] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 8988.212596] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 9019.145826] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 9050.185865] usb 2-5: reset high-speed USB device number 2 using ehci-pci
[ 9050.312309] sd 6:0:0:0: [sdc] Attached SCSI removable disk

(No problem with this usb stick on kernels before 3.10.3 -- 3.9.x, 3.10.2)

May be related bug: Panasonic DMC-ZS3 mass storage USB regression in 3.10.3
https://bugs.archlinux.org/task/36296
https://bugs.archlinux.org/task/36397

Last edited by sirocco (2013-08-05 10:15:01)

Offline

#5 2013-08-05 10:27:22

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: [Solved] Can't mount specific usb device after kernel upgrade

ewaller wrote:

What is the output of pacman -Qi linux    ??
Check the version number and verify that it matches the output of uname -a

Ups, forgot to mention that of course they match:

$ uname -a
Linux arch247 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux

$ pacman -Qi linux | grep Version
Version              : 3.10.3-1

Reboot was required too after the latest kernel upgrade.

sirocco wrote:

I have a similar problem. No automount, but manual mount is possible after few minutes after usb stick insertion.

Hm, I'll try to wait a few minutes, maybe i can mount it via commandline.

Ah, thanks. Seems the bug could be fixed in one of the next kernel updates.

For now, maybe I/we should just use the arch rollback machine until the new kernel is in the repos.

EDIT: After ~6 minutes i can mount the stick via commandline

Last edited by D4ve (2013-08-05 10:29:50)

Offline

#6 2013-08-06 00:07:25

gmesalazar
Member
From: Brazil
Registered: 2011-07-27
Posts: 14

Re: [Solved] Can't mount specific usb device after kernel upgrade

Same problem here (3.10.5). Compiling 3.9.11 with my custom config file to check it out.

Edit: as sirocco pointed out, it's possible to mount after some minutes.

Last edited by gmesalazar (2013-08-06 00:25:58)


Guilherme Salazar

Offline

#7 2013-08-06 00:20:46

gmesalazar
Member
From: Brazil
Registered: 2011-07-27
Posts: 14

Re: [Solved] Can't mount specific usb device after kernel upgrade

It works on 3.9.11.

dmesg on 3.9.11:

[   74.391651] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[   74.410514] usb 3-4: New USB device found, idVendor=0951, idProduct=1607
[   74.410529] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   74.410532] usb 3-4: Product: DataTraveler 2.0
[   74.410534] usb 3-4: Manufacturer: Kingston
[   74.410536] usb 3-4: SerialNumber: 00137299803FA931262A00CD
[   74.465400] Initializing USB Mass Storage driver...
[   74.465654] scsi7 : usb-storage 3-4:1.0
[   74.465726] usbcore: registered new interface driver usb-storage
[   74.465728] USB Mass Storage support registered.
[   75.465448] scsi 7:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[   75.465839] sd 7:0:0:0: Attached scsi generic sg4 type 0
[   75.466277] sd 7:0:0:0: [sdd] 3973120 512-byte logical blocks: (2.03 GB/1.89 GiB)
[   75.466620] sd 7:0:0:0: [sdd] Write Protect is off
[   75.466625] sd 7:0:0:0: [sdd] Mode Sense: 23 00 00 00
[   75.466955] sd 7:0:0:0: [sdd] No Caching mode page present
[   75.466960] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[   75.469081] sd 7:0:0:0: [sdd] No Caching mode page present
[   75.469087] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[   75.681901]  sdd: sdd1 sdd2
[   75.683219] sd 7:0:0:0: [sdd] No Caching mode page present
[   75.683224] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[   75.683227] sd 7:0:0:0: [sdd] Attached SCSI removable disk

dmesg on 3.10.5:

[ 1370.659092] usb 3-4: new high-speed USB device number 8 using xhci_hcd
[ 1370.677899] usb 3-4: New USB device found, idVendor=0951, idProduct=1607
[ 1370.677906] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1370.677910] usb 3-4: Product: DataTraveler 2.0
[ 1370.677913] usb 3-4: Manufacturer: Kingston
[ 1370.677916] usb 3-4: SerialNumber: 00137299803FA931262A00CD
[ 1370.678442] usb-storage 3-4:1.0: USB Mass Storage device detected
[ 1370.678711] scsi12 : usb-storage 3-4:1.0
[ 1371.674797] scsi 12:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[ 1371.675283] sd 12:0:0:0: Attached scsi generic sg4 type 0
[ 1371.675809] sd 12:0:0:0: [sdd] 3973120 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 1371.676184] sd 12:0:0:0: [sdd] Write Protect is off
[ 1371.676192] sd 12:0:0:0: [sdd] Mode Sense: 23 00 00 00
[ 1371.676560] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1371.676567] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1402.372357] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1402.389648] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1402.389655] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1433.410334] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1433.427691] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1433.427698] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1464.352379] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1464.369587] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1464.369592] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1495.294439] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1495.311616] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1495.311623] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1495.314661] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1495.314677] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1526.236340] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1526.253657] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1526.253665] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1557.306368] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1557.323619] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1557.323627] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1588.248358] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1588.265745] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1588.265752] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1619.190405] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1619.207780] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1619.207788] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1619.421206]  sdd: sdd1 sdd2
[ 1619.422735] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1619.422741] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1650.132306] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1650.149607] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1650.149614] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1681.202196] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1681.219363] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1681.219370] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1712.144197] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1712.161474] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1712.161482] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1743.086261] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1743.103565] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1743.103572] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1743.104256] sd 12:0:0:0: [sdd] Attached SCSI removable disk

EDIT: Doesn't work on 3.11-rc4 either.

Last edited by gmesalazar (2013-08-06 01:30:00)


Guilherme Salazar

Offline

#8 2013-08-06 03:52:02

gmesalazar
Member
From: Brazil
Registered: 2011-07-27
Posts: 14

Re: [Solved] Can't mount specific usb device after kernel upgrade

The patch at [1] solves the problem.

[1] http://marc.info/?l=linux-usb&m=137523956310060&w=2


Guilherme Salazar

Offline

#9 2013-08-08 05:15:16

bhrgunatha
Member
Registered: 2009-12-16
Posts: 75

Re: [Solved] Can't mount specific usb device after kernel upgrade

I'm having the same problem but with a USB2 memory stick.
It won't automount (although other USB1 and USB2 devices will.)
I can mount it manually after several minutes delay.
Previously it did automount.

$ uname -a
Linux starch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux

$ pacman -Qi linux | grep Version
Version        : 3.10.3-1

Last edited by bhrgunatha (2013-08-08 05:15:30)

Offline

#10 2013-08-13 09:51:28

Gunslinger
Member
From: Germany
Registered: 2013-01-05
Posts: 6

Re: [Solved] Can't mount specific usb device after kernel upgrade

I also have this issue after updating my two machines (now on kernel 3.10.5-1).

After the update on one of the machines I had the chance to double check the USB Memory Drive (USB 2.0) on the not-updated machine. It worked.
After updating the second machine it does not work anymore. I have a USB 3.0 Memory Drive which still works after the update (even though I have no USB 3.0 HW support on my machines yet...)

I can also confirm the timedelay of about 5 minutes after which the USB-Drive finally shows up in lsblk

...waiting for the next kernel...

/Gunslinger


The man in black fled across the desert, and the gunslinger followed.

Offline

#11 2013-08-13 11:05:49

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: [Solved] Can't mount specific usb device after kernel upgrade

As per FS#36296, linked above, the patch will not be merged in 3.10.6 either.

Offline

#12 2013-08-13 11:38:17

Gunslinger
Member
From: Germany
Registered: 2013-01-05
Posts: 6

Re: [Solved] Can't mount specific usb device after kernel upgrade

tomk wrote:

As per FS#36296, linked above, the patch will not be merged in 3.10.6 either.

Oh...well thanks, tomk! I just read the entire bugreport...

...then...maybe ≥ 3.10.7...some day...


The man in black fled across the desert, and the gunslinger followed.

Offline

#13 2013-08-13 11:53:40

sirocco
Member
Registered: 2008-03-10
Posts: 145

Re: [Solved] Can't mount specific usb device after kernel upgrade

upgpkg: linux 3.10.6-2

fixed #35991, #36296

Offline

#14 2013-08-13 12:19:47

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: [Solved] Can't mount specific usb device after kernel upgrade

Yeah! Arch devs >> kernel devs !

tongue

Offline

#15 2013-08-13 15:39:19

Lekensteyn
Member
From: Netherlands
Registered: 2012-06-19
Posts: 192
Website

Re: [Solved] Can't mount specific usb device after kernel upgrade

@tomk 3.11 has this fix for ages, you are already in the past ;-)

Offline

#16 2013-08-13 17:20:46

Gunslinger
Member
From: Germany
Registered: 2013-01-05
Posts: 6

Re: [Solved] Can't mount specific usb device after kernel upgrade

Holy Smoke...

fast solution, it's working again, thanks!


The man in black fled across the desert, and the gunslinger followed.

Offline

#17 2013-08-13 20:30:19

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: [Solved] Can't mount specific usb device after kernel upgrade

Lekensteyn wrote:

@tomk 3.11 has this fix for ages, you are already in the past ;-)

I'd have to disagree - 3.11 is not released yet, so you are in the future. smile

Offline

#18 2013-08-13 20:53:12

Lekensteyn
Member
From: Netherlands
Registered: 2012-06-19
Posts: 192
Website

Re: [Solved] Can't mount specific usb device after kernel upgrade

tomk wrote:
Lekensteyn wrote:

@tomk 3.11 has this fix for ages, you are already in the past ;-)

I'd have to disagree - 3.11 is not released yet, so you are in the future. smile

We are at -rc5 already, doesn't that count? smile Uh oh, I am outdated, I am running -rc4.

Offline

#19 2013-08-18 18:48:23

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: [Solved] Can't mount specific usb device after kernel upgrade

Ups, forgot to mention: 3-10-6-2 fixes the problem. Solved!

Last edited by D4ve (2013-08-18 18:49:19)

Offline

Board footer

Powered by FluxBB