You are not logged in.
After upgrading the kernel from 3.10.2 to 3.10.3 I can't seem to be able to mount anymore an external USB drive. When I plug it it seems to stay forever trying and I don't get the alert on KDE to mount any of its 3 partitions.
This is what I get on dmesg:
[ 47.185544] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 47.202936] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 47.223060] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 47.223235] scsi6 : usb-storage 2-2:1.0
[ 47.223402] usbcore: registered new interface driver usb-storage
[ 51.784607] scsi 6:0:0:0: Direct-Access TOSHIBA MK5075GSX GT00 PQ: 0 ANSI: 2
[ 51.788528] sd 6:0:0:0: [sdb] 976773165 512-byte logical blocks: (500 GB/465 GiB)
[ 51.788990] sd 6:0:0:0: [sdb] Write Protect is off
[ 51.788994] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 51.789454] sd 6:0:0:0: [sdb] No Caching mode page present
[ 51.789458] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 82.614525] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 82.631376] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 82.633138] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 82.633148] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
[ 114.687694] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 114.704531] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 114.706408] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 114.706417] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
[ 146.707275] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 146.724128] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 146.726009] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 146.726018] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
[ 178.727129] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 178.743879] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 178.745869] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 178.745877] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
[ 179.651249] sd 6:0:0:0: [sdb] No Caching mode page present
[ 179.651260] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 210.746738] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 210.763599] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 210.765475] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 210.765484] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
[ 242.766504] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 242.783326] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 242.785190] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a180
[ 242.785198] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014c85a1c0
For reference, this is from 3.10.2, which works fine:
[ 39.086382] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 39.103695] usb 2-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 39.122972] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 39.123150] scsi6 : usb-storage 2-2:1.0
[ 39.123328] usbcore: registered new interface driver usb-storage
[ 43.643798] scsi 6:0:0:0: Direct-Access TOSHIBA MK5075GSX GT00 PQ: 0 ANSI: 2
[ 43.647529] sd 6:0:0:0: [sdb] 976773165 512-byte logical blocks: (500 GB/465 GiB)
[ 43.648023] sd 6:0:0:0: [sdb] Write Protect is off
[ 43.648027] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 43.648480] sd 6:0:0:0: [sdb] No Caching mode page present
[ 43.648484] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 43.653716] sd 6:0:0:0: [sdb] No Caching mode page present
[ 43.653724] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 43.679542] sdb: sdb1 sdb2 sdb3
[ 44.693759] sd 6:0:0:0: [sdb] No Caching mode page present
[ 44.693767] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 44.693772] sd 6:0:0:0: [sdb] Attached SCSI disk
Anyone has a clue as to what can be the problem?
TIA.
Offline
Offline
Yes, that's the same bug, thanks.
Offline
Hey guys, having exactly the same issue. For me it doesn't affect all USB3 devices, but does affect the same USB3 devices on a different machine with only USB2.
Is apparently an upstream problem. So for anyone else experiencing this you can use "linux-3.10.2-1-x86_64.pkg.tar.xz" & "linux-3.10.2-1-x86_64.pkg.tar.xz" packages available from http://arm.konnichi.com/2013/07/26/core/os/x86_64/
then its just
sudo pacman -U linux-3.10.2-1-x86_64.pkg.tar.xz linux-3.10.2-1-x86_64.pkg.tar.xz
Offline
@Hutchism
The bug report already says that downgrading works. Archers are expected to know what they're doing and too much hand-holding is frowned upon.
Why do you list the same package twice? Did you mean the 64-bit and the 32-bit one?
Edit: Or the second package should be linux-headers?
Last edited by karol (2013-07-31 21:23:12)
Offline
Aah, meant the headers (linux-headers-3.10.2-1-x86_64.pkg.tar.xz), but just copied the same filename twice by mistake. Was mostly just giving a link to the latest build without the bug. Yeah, maybe 'archers' are supposed to know what their doing, I don't, but I get by. I do however try and research/fix stuff before posting, which is why I rarely post.
Some of us haven't got forever to figure out where and how to fix stuff, as we have lives outside Arch, are unschooled in some of the subtle nuances of Arch and just want a quick and dirty fix to unbaulk our systems, often bugged out through no fault of our owns (^^^CASE IN POINT^^^). So if this post saves a couple of people 10 mins, that's 10 mins they could be out playing in the Sun, snow, or maybe accessing the important data on their USB3 drive that suddenly became inaccessible.
But thanks for noticing the file name is wrong...
sudo pacman -U linux-3.10.2-1-x86_64.pkg.tar.xz linux-headers-3.10.2-1-x86_64.pkg.tar.xz
Offline
Some of us haven't got forever to figure out where and how to fix stuff, as we have lives outside Arch, are unschooled in some of the subtle nuances of Arch and just want a quick and dirty fix to unbaulk our systems, often bugged out through no fault of our owns (^^^CASE IN POINT^^^). So if this post saves a couple of people 10 mins, that's 10 mins they could be out playing in the Sun, snow, or maybe accessing the important data on their USB3 drive that suddenly became inaccessible.
The point is yu are unnecessarily repeating information that is readily available in the wiki. The community puts a lot of effort into maintaining the wiki, so referring people there is probably the right way to go about it.
Offline
Fair enough, I'll take that into consideration next time I bother posting anything. Just trying to be helpful. It's late where I am. Have had a very long few days camping and racing my bike in the pouring rain. Got home fired up my system and thought I'd listen to a bit of Pink Floyd while I soaked in the bath for half an hour. You can imagine my frustration when I had to resort to BBC 6 Music as I couldn't access my hard drive, only to get bitched at for adding a few additional comments on the forum. The kind of comment which would probably be helpful to someone who doesn't realise how easy it is to downgrade. ie:
" Comment by Max (homernl82) - Tuesday, 30 July 2013, 09:38 GMT
Same here. Though I did not update quite some time before, so downgrading would be a huge effort. Please fix this soon "
Offline
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
Genius ^ Thanks
Offline
Genius ^ Thanks
Did you read the wiki on downgrading at all?
Offline
What's the matter now?
....I read enough to fix my issue and get Pink Floyd playing.
Last edited by Hutchism (2013-08-01 12:28:09)
Offline
The wiki mentions downgrader and more.
Oh well, maybe I'm just reading into your posts too much.
Sorry for derailing the thread.
Offline
Just read that bit about the tool in the AUR, as I say, read enough to fix my problem (no more, no less). Over and out from me on this thread as this is getting silly.
Offline