|
Additonal bug report - Arie
Verheul
------------------------------------------------------------------------------------------------- After further experiments the
previous bug report needs a slight correction.
To make my Debian system boot up with working usb ports
all that appears
to be needed is to first start Puppy Linux, and once Puppy is ready then reboot the system and start Debian. This results (so far) always in a system with working usb ports. Unlike it was thought initially there is no need to delete any files. Deleting files appears to be irrelevant, running Puppy is what is relevant. It is essential that the system is indeed rebooted
through a software command.
If the system is turned off and later turned on again,
the trick does not work
and the system boots up with non functioning usb
ports.
The timing observations remain valid: if the system ends
up with working usb ports
the first usb error (-110) is usually reported around 20.5, if the system ends up with inaccessible usb ports the first usb error (-110) is reported around 20.2. It remains a mystery how it is possible that exactly the same error messages may result both in a system with functioning or with non functioning usb ports. Further in about a quarter of the cases a different
error message is shown now,
albeit with the same error code: [ 6.305892] ehci_hcd 0000:00:1d.0:
port 1 reset error -110
[ 7.120182] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 7.934492] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 8.542821] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? [ 8.601109] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 9.471282] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 10.285615] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 11.099945] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 11.914181] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 12.522512] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? [ 12.580794] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 13.450977] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 14.265286] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 15.079574] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 15.893876] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 16.502202] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? [ 16.560498] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 17.430662] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 18.244957] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 19.059251] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 19.873566] ehci_hcd 0000:00:1d.0: port 1 reset error -110 [ 20.481891] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? [ 20.482039] hub 1-0:1.0: unable to enumerate USB device on port 1 As was mentioned in the initial bugreport the Anaconda installer as used by Scientific Linux also shows the problem of booting up with non functioning usb ports. It was therefore tested if the trick described above also works for the SL Anaconda installer. It does not, which indicates that the issue involves more than has been found so far. It may be added here that Puppy and Debian live in
separate worlds and share only the hardware.
Puppy boots from an usb stick using ldlinux. Debian boots from the internal disk using grub. Debian and Puppy do not share a common boot mechanism. It seems therefore that (on the given system) a reboot
does not involve a complete reset,
and that if Debian detects that some other OS was running before it does some extra work, which takes on average .3 sec. Therefore it could be that, as was supposed before, this
delay of .3 sec solves the issue,
or it could be that the extra work that was done solves the issue. Therefore it might be useful to know what this extra work involves. ------------------------------------------------------------------------------------------------- |