http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c1 --- Comment #1 from Tony Mechelynck --- oops... an openSUSE *42.2* system with... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c5 --- Comment #5 from Tony Mechelynck --- Output of "journalctl -xn" is rather short, as follows: -- Logs begin at Thu 2016-01-07 17:15:28 CET, end at Mon 2017-01-23 10:34:05 CET. -- Jan 23 10:31:38 linux-2iyu org.kde.gwenview.desktop[1228]: Guess plugin: "textthumbnail" Jan 23 10:32:03 linux-2iyu org.kde.gwenview.desktop[1228]: Wanting MIME Type: "text/x-log" Jan 23 10:32:03 linux-2iyu org.kde.gwenview.desktop[1228]: Guess plugin: "textthumbnail" Jan 23 10:32:13 linux-2iyu org.kde.gwenview.desktop[1228]: Wanting MIME Type: "text/x-log" Jan 23 10:32:13 linux-2iyu org.kde.gwenview.desktop[1228]: Guess plugin: "textthumbnail" Jan 23 10:32:21 linux-2iyu netconfig[3181]: Executing 'batch' for pid 3179 Jan 23 10:32:32 linux-2iyu org.kde.gwenview.desktop[1228]: Wanting MIME Type: "text/x-log" Jan 23 10:32:32 linux-2iyu org.kde.gwenview.desktop[1228]: Guess plugin: "textthumbnail" Jan 23 10:34:05 linux-2iyu org.kde.gwenview.desktop[1228]: Wanting MIME Type: "text/x-log" Jan 23 10:34:05 linux-2iyu org.kde.gwenview.desktop[1228]: Guess plugin: "textthumbnail" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c7 --- Comment #7 from Tony Mechelynck --- Output of lsusb: Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 005: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard Bus 005 Device 007: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c9 --- Comment #9 from Tony Mechelynck --- (In reply to Tony Mechelynck from comment #7)

Output of lsusb:

Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 005: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard Bus 005 Device 007: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

... and yet my 2 USB disks are still plugged in. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c13 Tony Mechelynck changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(antoine.mechelync | |k@gmail.com) | --- Comment #13 from Tony Mechelynck --- During boot, I see "A start job is running" for both USB disks, displaying in alternation. After the X11 logon screen appears, I went back to try to login on /dev/tty2 and saw error messages interspersed with what I normally see when logging in. Since they are on a text (non-X11) console, I cannot copy-paste them, I'll try copying them by eyeball (omitting the timestamps; the integer part of their timestamps, which I'm omitting, ranges from 168 to 189). usb 6-2: device descriptor read/64, error -110 usb 6-2: new full speed USB device number 8 using uhci_hcd usb 6-2: device descriptor read/8, error -110 usb 6-2: device descriptor read/8, error -110 usb 6-2: new full speed USB device number 9 using uhci_hcd usb 6-2: device descriptor read/8, error -110 usb 6-2: device descriptor read/8, error -110 usb usb6-port2: unable to enumerate USB device Now let's get that scsi log. Not very long: New scsi logging level: /proc/sys/dev/scsi/logging_level = 939524607 SCSI_LOG_ERROR=7 SCSI_LOG_TIMEOUT=7 SCSI_LOG_SCAN=7 SCSI_LOG_MLQUEUE=0 SCSI_LOG_MLCOMPLETE=0 SCSI_LOG_LLQUEUE=0 SCSI_LOG_LLCOMPLETE=0 SCSI_LOG_HLQUEUE=0 SCSI_LOG_HLCOMPLETE=0 SCSI_LOG_IOCTL=7 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c17 --- Comment #17 from Tony Mechelynck --- Created attachment 711222 --> http://bugzilla.opensuse.org/attachment.cgi?id=711222&action=edit dmesg output after setting the scsi log level according to comment #12 (In reply to Oliver Neukum from comment #15)

Something is fishy. Are your disks USB 2.0?

How can I tell? I have used them before, including to run "zypper dup" to install opensUSE 4.2, and also after that. I think that I've used them since the latest kernel online update but I wouldn't (as we say in French) put my hand into the fire about that.

And the log is different from comment#10

Please clarify

See comment #11. These messages happened after the reboot mentioned at the end of that comment. Oh, and (don't know if relevant) after requesting a "restart" in the drop-down at top right of all virtual desktops, there was apparently a hang in the Hewlett-Packard startup screen; Ctr-Alt-Del produced the usual "Executing POST delay", then the messages about which F keys to hit to get to the setup menu or the boot-device menu appeared on that same HP screen, which was finally replaced by the GRUB startup screen (In reply to Oliver Neukum from comment #16)

Yes, the log itself goes to dmesg.

Ah, ok; let's run that again then. Feel free to mark the previous dmesg log as an "obsolete attachment" if appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c19 --- Comment #19 from Tony Mechelynck --- Created attachment 711229 --> http://bugzilla.opensuse.org/attachment.cgi?id=711229&action=edit applied patches from other than Update-Test (In reply to Tony Mechelynck from comment #17) Oops, sorry. Actually I ran zypper dup with the "USB live stick" enabled (containing the install DVD), but the online repos were also enabled. But I definitely used them until recently on openSUSE 42.2, IIRC until I had to reboot because there was a patch for some software package used by (among others) systemd. I think it was one of those from Update-Test (attachment 711227) but just in case I'm attaching also the list of applied 42.2 patches from other repos. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c21 --- Comment #21 from Tony Mechelynck --- When I came back home tonight, there was a kernel update waiting for me (to 4.4.46-11.1) so I did a few experiments, switching the USB connectors around, with success but not immediately. I'll detail them below. All changes were made while the GRUB bootup menu (to select one of several possible kernels) was displayed, but after moving the selection bar to defeat the timeout, and leaving it to the kernel I intended to boot (the new kernel-default; if it hadn't worked at all I would have tried booting the kernel-vanilla instead, and then looked for something else to try). There are 4 USB slots on the front face of my computer, and some more on the back face. Only the front ones are relevant here, I'll call them A, B, C, D from right to left. IIUC A and B are on one hub and C and D on a different hub. Originally they were plugged as follows: A: mouse B: keyboard C: my drive, with a swap partition (for emergencies) and a data partition D: a bootable 42.2 DVD-image on USB Experiment 1: Boot the new kernel-default with no change. Result 1: No joy. Both USB drives still end up disconnected, "parted -l" sees only the hard disk inside the computer box, as /dev/hda. Experiment 2: swap B and C. I now have A=mouse, B=mine, C=KB, D=DVD Result 2: my drive (on slot B) is now recognised as /dev/sdb. DVD (unmoved on D) is still disconnected. Experiment 3: put them A=mine, B=DVD, C=KB, D=mouse Result 3: Now the DVD (on B) is recognised as /dev/sdb but my disk (on A) is disconnected. Experiment 4: A=KB, B=mine, C=DVD, D=mouse Result 4: Success! Now the "DVD" (on C) is seen as /dev/sdb and my disk (on B) as /dev/sdc. Next time I boot I'll try swapping both USB disks and see if slot C ends up on /dev/sdb. Not urgent because my /etc/fstab mounts "my" drive by id and by label and doesn't mount the other by default, but my sense of elegance will be more satisfied if the partition mounted on /mnt/sdb1 happens to sit on drive sdb rather than sdc. The kernel I had until a day or two before comment #0 has been uninstalled as part of this upgrade-and-reboot, and I don't intend to fetch it back (unless you tell me to). The kernels now installed on my system are kernel-default, kernel-debug and kernel-vanilla for versions 4.4.46-11.1 and 4.4.36-8.1. IIUC the last kernel where I didn't have the problem before opening this bug was a 4.4.36-5.1 kernel-default. My policy is to always set the newest kernel-default as boot default in the "Advanced" submenu of the GRUB bootloader. Oliver: I'm not setting this bug to WORKSFORME because I have treated only symptoms, not the underlying problem; you may want either to investigate some more by telling me what to test (and in due course make the bug ASSIGNED) or decide that the game is not worth the candle and RESOLVE WORKSFORME yourself (in which case I won't fight it). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c23 --- Comment #23 from Tony Mechelynck --- (In reply to Oliver Neukum from comment #22)

It is possible that your power supply is overwhelmed. Can you confirm the storage devices work separately on the same ports?

They used to work together on what I called slots C and D in comment #21, but I'll try. Stay tuned to this station.

And please provide lsusb -v and lsusb -t for the working state.

linux-2iyu:~ # lsusb -t /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 4: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 5: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M linux-2iyu:~ # lsusb -v is a lot more verbose, I'll add it as an attachment. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c25 Tony Mechelynck changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(antoine.mechelync | |k@gmail.com) | --- Comment #25 from Tony Mechelynck --- A:mouse B:keyboard C:nothing D:DVD --> Works, the disk is seen as /dev/sdb A:mouse B:keyboard C:mine D:nothing --> Works, the disk is seen as /dev/sdb A:mouse B:keyboard C:mine D:DVD --> ?!? Works, DVD=/dev/sdb, mine=/dev/sdc --- This is the original configuration (which was failing in comment #0 to #20, but the USB disks are seen in the opposite sequence to what they used to. A:mouse B:DVD C:mine D:keyboard --> Works, DVD=/dev/sdb, mine=/dev/sdc --- this is the opposite sequence (sdb vs. sdc) to that of attachment 713354; I also switched the keyboard and mouse --- but I had to unplug and replug the keyboard to use it So what? A bad contact or something? It seems that plugging the drives out then in in comment #21 was what was required (but note that in comment #21, one disk worked after moving, then didn't after moving again). Also, the sequence (sdb, sdc) of USB disks seems to be unstable when more than one is plugged in at boot time. If you don't mind, I'll leave them plugged this way. It looks like it /was/ a hardware problem after all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021325 http://bugzilla.opensuse.org/show_bug.cgi?id=1021325#c27 --- Comment #27 from Tony Mechelynck --- At the moment (and with no further disk unplugging since comment #25) I even see the HD (mounted on /) as /dev/sdc and my USB drive as /dev/sdb, which is weird, but not harmful because /etc/fstab references all disks as /dev/disk/by-id/something, which doesn't depend on the order in which they were identified. -- You are receiving this mail because: You are on the CC list for the bug.