Bug 1053631 - USB disk not visible in fdisk [NEEDINFO]
Summary: USB disk not visible in fdisk
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-15 14:26 UTC by Peter H. Jones
Modified: 2015-11-23 17:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-23 17:25:37 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
dmesg output (62.34 KB, text/plain)
2014-01-15 14:26 UTC, Peter H. Jones
no flags Details
lsusb -v output (12.62 KB, text/plain)
2014-01-15 14:27 UTC, Peter H. Jones
no flags Details
/var/log/messages (104.04 KB, text/plain)
2014-01-15 14:28 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2014-01-15 14:26:01 UTC
Created attachment 850535 [details]
dmesg output

Description of problem:
USB disk that was plugged in was not visible in fdisk after boot. Disk worked OK when I uplugged and plugged it in again.

Version-Release number of selected component (if applicable):
kernel-3.13.0-0.rc8.git1.1.fc21.x86_64

How reproducible:
Only tried once

Steps to Reproduce:
1. Booted Fedora-Live-Security-x86_64-rawhide-20140114.iso
2. Selected Troubleshooting, then moved cursor to "Test Media and start"
3. Used TAB key to remove "rhgb" and "quiet"
4. Hit return to boot

Actual results:
USB error messages on screen

"grep -n -- -110 dmesg lsusbv messages

gives:
"dmesg:793:[   18.914405] usb 2-3: device descriptor read/64, error -110
dmesg:794:[   34.122346] usb 2-3: device descriptor read/64, error -110
dmesg:798:[   49.432332] usb 2-3: device descriptor read/64, error -110
dmesg:799:[   64.643275] usb 2-3: device descriptor read/64, error -110
dmesg:801:[   75.257628] usb 2-3: device not accepting address 4, error -110
dmesg:803:[   85.771045] usb 2-3: device not accepting address 5, error -110
dmesg:806:[  101.149112] usb 5-3: device descriptor read/64, error -110
dmesg:807:[  116.383062] usb 5-3: device descriptor read/64, error -110
dmesg:809:[  131.743006] usb 5-3: device descriptor read/64, error -110
dmesg:810:[  146.977006] usb 5-3: device descriptor read/64, error -110
dmesg:812:[  157.613385] usb 5-3: device not accepting address 4, error -110
dmesg:814:[  168.149755] usb 5-3: device not accepting address 5, error -110
messages:545:Jan 15 08:16:43 localhost kernel: [   18.914405] usb 2-3: device descriptor read/64, error -110
messages:546:Jan 15 08:16:43 localhost kernel: [   34.122346] usb 2-3: device descriptor read/64, error -110
messages:550:Jan 15 08:16:43 localhost kernel: [   49.432332] usb 2-3: device descriptor read/64, error -110
messages:551:Jan 15 08:16:43 localhost kernel: [   64.643275] usb 2-3: device descriptor read/64, error -110
messages:553:Jan 15 08:16:43 localhost kernel: [   75.257628] usb 2-3: device not accepting address 4, error -110
messages:555:Jan 15 08:16:43 localhost kernel: [   85.771045] usb 2-3: device not accepting address 5, error -110
messages:558:Jan 15 08:16:43 localhost kernel: [  101.149112] usb 5-3: device descriptor read/64, error -110
messages:559:Jan 15 08:16:43 localhost kernel: [  116.383062] usb 5-3: device descriptor read/64, error -110
messages:561:Jan 15 08:16:43 localhost kernel: [  131.743006] usb 5-3: device descriptor read/64, error -110
messages:562:Jan 15 08:16:43 localhost kernel: [  146.977006] usb 5-3: device descriptor read/64, error -110
messages:564:Jan 15 08:16:43 localhost kernel: [  157.613385] usb 5-3: device not accepting address 4, error -110
messages:566:Jan 15 08:16:43 localhost kernel: [  168.149755] usb 5-3: device not accepting address 5, error -110"

Expected results:
No USB errors
Disk should be visible with fdisk command

Additional info:
dmesg output
lsusb -v output (in lsusbv)
/var/log/messages

Comment 1 Peter H. Jones 2014-01-15 14:27:15 UTC
Created attachment 850536 [details]
lsusb -v output

Comment 2 Peter H. Jones 2014-01-15 14:28:06 UTC
Created attachment 850537 [details]
/var/log/messages

Comment 3 Peter H. Jones 2014-01-15 15:07:42 UTC
In step 2 of my Description, I said I selected "Test Media". Actually, I selected the topmost choice, "Basic graphics".

I tried to repeat this test on a Toshiba NB555D with 1G RAM and a swap partition on the HD. I ended up with a white bar across the top of a black screen, and then the whole screen went dark, while the DVD drive showed constant activity for 10-15 min. Hitting keys on the keyborard produced no visible changes. I prpose to try a boot in single mode and perhaps mode 3, in order to get the messages for this machine.

Comment 4 Jaroslav Reznik 2015-03-03 15:23:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 5 Justin M. Forbes 2015-10-20 19:43:45 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 6 Fedora Kernel Team 2015-11-23 17:25:37 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.