Control: reassign -1 src:linux 3.2.0-4-686-pae On Vi, 13 iun 14, 10:03:42, A.Verheul wrote: > Package: vmlinuz > Version: 3.2.0-4-686-pae > > Debian Version: Debian wheezy 7.4.0, i386 > > Bug summary: USB ports inaccessible after boot up > > Related bugreport: #500552 - involves exactly the same problem (year 2008) - > then solved through CPU replacement - issue archived by now > > Possibly related : #750445 - describes similar problem with different error code > > Reporter: Arie Verheul > Personal status: new to Linux > > ---------------------------------------------------------------------------------------------- > Summary of what has been found so far > ---------------------------------------------------------------------------------------------- > > a. The system may work properly and hence the hardware seems OK. > > b. The issue seems not specific for Debian but rather a general kernel issue. > > c. Puppy Linux seems less sensitive for the issue. > > d. The Intel BIOS version affects the issue. > > e. There are indications that the problem might involve a timing issue. > > ---------------------------------------------------------------------------------------------- > > Dear sir or madam, > > I do experience a persistent problem with usb port setup on boot up. > The system boots up OK but ends up with non-functioning usb-ports. > This renders the system useless. The hardware used is new and recent (see specs below). > > Initially it was attempted to install Scientific Linux, which uses the Anaconda installer. > However, Anaconda boots up OK but with non-functioning usb-ports. No solution was found. > Installation was done from an usb stick (no optical drive present). > Therefore the issue seems to be a kernel issue which is not specific for Debian. > > Next it was attempted to install Debian. Just like Anaconda the Debian installer boots up > with inaccessible usb ports. This could be solved by repeatedly hotplugging the usb mouse. > After the usb ports had become accessible Debian could be installed properly. > > However, once installed Debian normally always boots up with non functioning usb-ports. > Error message as below: > > [ 20.405006] usb 1-1: device not accepting address 2, error -110 > [ 20.516591] usb 1-1: new high-speed USB device number 3 using ehci_hcd > [ 36.040241] usb 1-1: device not accepting address 3, error -110 > [ 36.152034] usb 1-1: new high-speed USB device number 4 using ehci_hcd > [ 46.562305] usb 1-1: device not accepting address 4, error -110 > [ 46.674088] usb 1-1: new high-speed USB device number 5 using ehci_hcd > [ 57.084282] usb 1-1: device not accepting address 5, error -110 > [ 57.084425] hub 1-0:1.0: unable to enumerate USB device on port 1 > > Instead of usb 1-1 the system may complain about usb 3-1 with exactly the same result. > > To inspect the hard disk Puppy Linux 5.7.1 was installed on a usb stick. > Surprisingly Puppy always booted properly, and did not seem to suffer from the usb issue. > However, when the system BIOS was updated in an attempt to solve the issue > (see below for version), Puppy randomly failed in about half of the cases. > Returning to the previous BIOS version solved this. This was reported to Intel. > > From experiments it was found that Debian could be made to work with properly functioning > usb-ports by simply deleting some log files from the /var/log directory (using Puppy). > Deleted were kernel.log and the various dmesg files. Although the effect of this remains > unclear it gives gives a 70% chance for a working system. Strange enough the reported errors > remain exactly the same, even if the system ends up in a properly working state. > The system has been used this way for over 2 month now with consistently the same results. > > The impression is that the solution found for bug #500552 was rather a workaround than a solution. > The random behaviour of both Debian and Puppy (the latter with updated BIOS) could indicate > a timing issue. In this respect it might be relevant that the system uses an SSD which is faster > than most HDD's. The effect of deleting log files could be just a slight delay in OS loading. > > I therefore took notes of the time of the first reported usb error, both in cases that ended up > with functioning usb ports as in cases with non functioning usb ports. > > ---------------------------------------------------------------------------------------------- > Boot up ending with non-functioning usb-ports > > 20.178 > 20.178 > 20.178 > 20.184 > 20.200 > 20.405 > > Boot up ending with properly functioning usb-ports > > 20.465 > 20.477 > 20.508 > 20.544 > ---------------------------------------------------------------------------------------------- > > These data support the timing issue hypothesis. > A first error at 20.405 or earlier would result in non-functioning usb-ports, > a first error at 20.465 or later would result in a properly working system. > No idea if this could make any sense but it might be worth to look into it. > > ---------------------------------------------------------------------------------------------- > SYSTEM DATA > ---------------------------------------------------------------------------------------------- > > Board Intel barebone NUC DN2820FYK > Processor Intel Celeron 2820 (dual core) 32/64 bit > > Installed RAM 4 GB > Disk Intel SSD 530 series 120GB > > BIOS initially FYBYT10H.86A.0034.2014.0306.1727 > updated FYBYT10H.86A.0034.2014.0513.1413 > > peripherals usb #1 : 4-port usb hub with logitech usb mouse > + logitech usb wireless keyboard receiver > + 1GB usb stick with Puppy OS > > usb #2 : during this test not used > usb #3 : during this test not used > > main OS Debian 7.4.0 "wheezy" 32-bits installed on SSD > auxiliar OS Puppy Linux 5.7.1 32-bits on usb stick > > ---------------------------------------------------------------------------------------------- > > lsusb > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB > Bus 001 Device 003: ID 8087:07dc Intel Corp. > Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver > Bus 001 Device 005: ID 046d:c05a Logitech, Inc. Optical Mouse M90 > Bus 001 Device 007: ID 13fe:1e00 Kingston Technology Company Inc. Flash Drive 2 GB [ICIDU 2 GB] > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > ---------------------------------------------------------------------------------------------- -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt
Attachment:
signature.asc
Description: Digital signature