Bug 8104

Summary: kernel floods console with "connect-debounce failed"
Product: Drivers Reporter: Cristian Mammoli (sengo)
Component: USBAssignee: Greg Kroah-Hartman (greg)
Status: REJECTED INSUFFICIENT_DATA    
Severity: normal CC: akpm, j.bittner, mmdyndns, protasnb, stern
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.24 Subsystem:
Regression: --- Bisected commit-id:
Bug Depends on:    
Bug Blocks: 5089    
Attachments: .config used
dmesg booting with bluetooth switch on
dmesg booting with bluetooth switch on and usb debug enabled
lspci -vvnn
lsusb -v after switching off/on bluetooth swicth (device isn't listed otherwise)
/proc/bus/usb/devices
/proc/version
uname -a
sh scripts/ver_linux
/var/log/debug with usb debug enabled
.config of last working kernel (2.6.17-11-generic)
.config of kernel 2.6.20-11-generic (that generate the bug)
dmesg with vanilla kernel 2.6.22
dmesg of 2.6.32-21-generic ubuntu build from ubuntu source

Description Cristian Mammoli 2007-03-01 03:49:40 UTC 
Most recent kernel where this bug did *NOT* occur: 2.6.17
Distribution: ubuntu 7.04
Hardware Environment: fujitsu amilo pro v3205
Problem Description:

I recently installed ubuntu feisty (linux-2.6.20) on a Fujitsu Siemens
Amilo pro v3205. Even during installation my console was flooded with
hundreds of:

[ ???.??????] hub 5-0:1.0: connect-debounce failed, port 6 disabled

The problem didn't go away after installation and logs got flooded with
the message too:

cristian@alastor:~$ grep debounce /var/log/syslog|wc -l
1621

After some googling I discovered this is probably caused by the onboard
usb bluetooth receveir: if I disable then re-enable it with the keyboard
switch the message goes away. If I boot the laptop with BT disabled,
then I enable it the message doesn't appear at all in the kernel logs.
Everything was fine on the same hardware with 2.6.17 on edgy.
Note that the bluetooth receiver does not work until I do this trick.

e.g:
cristian@alastor:~$ hcitool scan
Device is not available: No such device

The logs attached refer to an ubuntu patched 2.6.20 but tried also
2.6.20-1 and 2.6.19-4 vanilla and the problem is still there.
I tried with an external usb dongle aswell and it worked fine.
Comment 1 Cristian Mammoli 2007-03-01 03:50:59 UTC 
Created attachment 10566 [details]
.config used
Comment 2 Cristian Mammoli 2007-03-01 03:52:24 UTC 
Created attachment 10567 [details]
dmesg booting with bluetooth switch on
Comment 3 Cristian Mammoli 2007-03-01 03:53:22 UTC 
Created attachment 10568 [details]
dmesg booting with bluetooth switch on and usb debug enabled
Comment 4 Cristian Mammoli 2007-03-01 03:54:09 UTC 
Created attachment 10569 [details]
lspci -vvnn
Comment 5 Cristian Mammoli 2007-03-01 03:55:27 UTC 
Created attachment 10570 [details]
lsusb -v after switching off/on bluetooth swicth (device isn't listed otherwise)
Comment 6 Cristian Mammoli 2007-03-01 03:56:20 UTC 
Created attachment 10571 [details]
/proc/bus/usb/devices
Comment 7 Cristian Mammoli 2007-03-01 03:56:58 UTC 
Created attachment 10572 [details]
/proc/version
Comment 8 Cristian Mammoli 2007-03-01 03:57:33 UTC 
Created attachment 10573 [details]
uname -a
Comment 9 Cristian Mammoli 2007-03-01 03:59:19 UTC 
Created attachment 10574 [details]
sh scripts/ver_linux
Comment 10 Cristian Mammoli 2007-03-01 04:00:51 UTC 
Created attachment 10575 [details]
/var/log/debug with usb debug enabled
Comment 11 Anonymous Emailer 2007-03-01 07:45:40 UTC 
Reply-To: akpm@linux-foundation.org



Begin forwarded message:

Date: Thu, 1 Mar 2007 03:49:59 -0800
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 8104] New: kernel floods console with "connect-debounce failed"


http://bugzilla.kernel.org/show_bug.cgi?id=8104

           Summary: kernel floods console with "connect-debounce failed"
    Kernel Version: 2.6.20-1
            Status: NEW
          Severity: normal
             Owner: greg@kroah.com
         Submitter: sengo@sengo.net


Most recent kernel where this bug did *NOT* occur: 2.6.17
Distribution: ubuntu 7.04
Hardware Environment: fujitsu amilo pro v3205
Problem Description:

I recently installed ubuntu feisty (linux-2.6.20) on a Fujitsu Siemens
Amilo pro v3205. Even during installation my console was flooded with
hundreds of:

[ ???.??????] hub 5-0:1.0: connect-debounce failed, port 6 disabled

The problem didn't go away after installation and logs got flooded with
the message too:

cristian@alastor:~$ grep debounce /var/log/syslog|wc -l
1621

After some googling I discovered this is probably caused by the onboard
usb bluetooth receveir: if I disable then re-enable it with the keyboard
switch the message goes away. If I boot the laptop with BT disabled,
then I enable it the message doesn't appear at all in the kernel logs.
Everything was fine on the same hardware with 2.6.17 on edgy.
Note that the bluetooth receiver does not work until I do this trick.

e.g:
cristian@alastor:~$ hcitool scan
Device is not available: No such device

The logs attached refer to an ubuntu patched 2.6.20 but tried also
2.6.20-1 and 2.6.19-4 vanilla and the problem is still there.
I tried with an external usb dongle aswell and it worked fine.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Comment 12 Anonymous Emailer 2007-03-01 13:14:32 UTC 
Reply-To: oneukum@suse.de


> Most recent kernel where this bug did *NOT* occur: 2.6.17

Very good. You are the first one to report a working kernel version.

Please post dmesg of a working and a not working kernel and
lsusb -v of your devices. If possible please use kernels with
CONFIG_USB_DEBUG.

	Regards
		Oliver
Comment 13 Cristian Mammoli 2007-03-01 17:09:03 UTC 
On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
> > Most recent kernel where this bug did *NOT* occur: 2.6.17
> 
> Very good. You are the first one to report a working kernel version.
> 
> Please post dmesg of a working and a not working kernel and
> lsusb -v of your devices. If possible please use kernels with
> CONFIG_USB_DEBUG.

2.6.18 is broken as well... I'll build 2.6.17 tomorrow.
Anyway this is what happens when I turn off/on the bluetooth switch:


[   60.144000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.176000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.208000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.240000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.272000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[   60.304000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.336000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.368000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.400000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.432000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[   60.464000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.496000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   60.528000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT

*SWITCH OFF*

[   60.552000] atkbd.c: Unknown key pressed (translated set 2, code 0xe2
on isa0060/serio0).
[   60.552000] atkbd.c: Use 'setkeycodes e062 <keycode>' to make it
known.
[   60.560000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[   60.688000] hub 5-0:1.0: debounce: port 6: total 1450ms stable 100ms
status 0x100
[   60.688000] hub 5-0:1.0: state 7 ports 8 chg 0000 evt 0040
[   60.704000] atkbd.c: Unknown key released (translated set 2, code
0xe2 on isa0060/serio0).
[   60.704000] atkbd.c: Use 'setkeycodes e062 <keycode>' to make it
known.

*SWITCH ON*

[   62.296000] atkbd.c: Unknown key pressed (translated set 2, code 0xe2
on isa0060/serio0).
[   62.296000] atkbd.c: Use 'setkeycodes e062 <keycode>' to make it
known.
[   62.492000] atkbd.c: Unknown key released (translated set 2, code
0xe2 on isa0060/serio0).
[   62.492000] atkbd.c: Use 'setkeycodes e062 <keycode>' to make it
known.
[   62.612000] hub 5-0:1.0: state 7 ports 8 chg 0000 evt 0040
[   62.612000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[   62.612000] hub 5-0:1.0: port 6, status 0501, change 0001, 480 Mb/s
[   62.740000] hub 5-0:1.0: debounce: port 6: total 100ms stable 100ms
status 0x501
[   62.796000] ehci_hcd 0000:00:1d.7: port 6 full speed --> companion
[   62.796000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 003801
POWER OWNER sig=j CONNECT
[   62.796000] usb usb3: wakeup_rh (auto-start)
[   62.796000] hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0004
[   62.796000] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[   62.796000] hub 3-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
[   62.924000] hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms
status 0x101
[   63.036000] usb 3-2: new full speed USB device using uhci_hcd and
address 2
[   63.212000] usb 3-2: new device strings: Mfr=0, Product=0,
SerialNumber=0
[   63.212000] PM: Adding info for usb:3-2
[   63.212000] usb 3-2: uevent
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep00
[   63.212000] usb 3-2: configuration #1 chosen from 1 choice
[   63.212000] usb 3-2: adding 3-2:1.0 (config #1, interface 0)
[   63.212000] PM: Adding info for usb:3-2:1.0
[   63.212000] usb 3-2:1.0: uevent
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep81
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep02
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep82
[   63.212000] usb 3-2: adding 3-2:1.1 (config #1, interface 1)
[   63.212000] PM: Adding info for usb:3-2:1.1
[   63.212000] usb 3-2:1.1: uevent
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep03
[   63.212000] PM: Adding info for No Bus:usbdev3.2_ep83
[   63.212000] drivers/usb/core/inode.c: creating file '002'
[   63.212000] hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0004
[   63.316000] Bluetooth: HCI USB driver ver 2.9
[   63.316000] hci_usb 3-2:1.0: usb_probe_interface
[   63.316000] hci_usb 3-2:1.0: usb_probe_interface - got id
[   63.316000] PM: Removing info for No Bus:usbdev3.2_ep03
[   63.316000]  usbdev3.2_ep03: ep_device_release called for
usbdev3.2_ep03
[   63.316000] PM: Removing info for No Bus:usbdev3.2_ep83
[   63.316000]  usbdev3.2_ep83: ep_device_release called for
usbdev3.2_ep83
[   63.316000] PM: Adding info for No Bus:usbdev3.2_ep03
[   63.316000] PM: Adding info for No Bus:usbdev3.2_ep83
[   63.316000] PM: Adding info for No Bus:hci0
[   63.316000] usbcore: registered new driver hci_usb
cristian@alastor:~$ dmesg > dmesg-2.6.18.log
cristian@alastor:~$ 


regards

Cristian
Comment 14 Cristian Mammoli 2007-03-03 01:07:23 UTC 
On ven, 2007-03-02 at 02:08 +0100, Cristian Mammoli wrote:
> On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
> > > Most recent kernel where this bug did *NOT* occur: 2.6.17
> > 
> > Very good. You are the first one to report a working kernel version.
> > 
> > Please post dmesg of a working and a not working kernel and
> > lsusb -v of your devices. If possible please use kernels with
> > CONFIG_USB_DEBUG.
> 
> 2.6.18 is broken as well... I'll build 2.6.17 tomorrow.
> Anyway this is what happens when I turn off/on the bluetooth switch:

Well,something weird is going on here...
2.6.17 ubuntu edgy binary: works
2.6.20 ubuntu feisty binary: broken
2.6.17 vanilla: broken O_O
2.6.17 ubuntu edgy patched sources: broken

Any chance this behaviour is environment related?
compiler, libs etc?

Cristian
Comment 15 Anonymous Emailer 2007-03-03 02:36:01 UTC 
Reply-To: oliver@neukum.org

Am Samstag, 3. März 2007 10:07 schrieb Cristian Mammoli:
> On ven, 2007-03-02 at 02:08 +0100, Cristian Mammoli wrote:
> > On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
> > > > Most recent kernel where this bug did *NOT* occur: 2.6.17
> > > 
> > > Very good. You are the first one to report a working kernel version.
> > > 
> > > Please post dmesg of a working and a not working kernel and
> > > lsusb -v of your devices. If possible please use kernels with
> > > CONFIG_USB_DEBUG.
> > 
> > 2.6.18 is broken as well... I'll build 2.6.17 tomorrow.
> > Anyway this is what happens when I turn off/on the bluetooth switch:
> 
> Well,something weird is going on here...
> 2.6.17 ubuntu edgy binary: works
> 2.6.20 ubuntu feisty binary: broken
> 2.6.17 vanilla: broken O_O
> 2.6.17 ubuntu edgy patched sources: broken
> 
> Any chance this behaviour is environment related?
> compiler, libs etc?

There's a very small chance that the compiler is to blame, but
it is far more likely that the phenomenon itself is not fully repeatable.
How often did you try?

	Regards
		Oliver
Comment 16 Anonymous Emailer 2007-03-03 04:35:52 UTC 
Reply-To: cristian@mammoli.it

Oliver Neukum ha scritto:
> There's a very small chance that the compiler is to blame, but
> it is far more likely that the phenomenon itself is not fully repeatable.
> How often did you try?
>
> 	Regards
> 		Oliver
>   
Well, it happens every single time I boot (or reboot) the notebook with 
the bluetooth switch on if this is what you mean. I tried at least 2-3 
times with every kernel I tested and the only one that seems to work is 
2.6.17 from ubuntu edgy repos.
Comment 17 Cristian Mammoli 2007-03-03 04:43:19 UTC 
Oliver Neukum ha scritto:
> There's a very small chance that the compiler is to blame, but
> it is far more likely that the phenomenon itself is not fully repeatable.
> How often did you try?
>
> 	Regards
> 		Oliver
>   
Well, it happens every single time I boot (or reboot) the notebook with
the bluetooth switch on if this is what you mean. I tried at least 2-3
times with every kernel I tested and the only one that seems to work is
2.6.17 from ubuntu edgy repos.
Comment 18 Anonymous Emailer 2007-03-03 07:17:04 UTC 
Reply-To: oliver@neukum.org

Am Samstag, 3. März 2007 13:43 schrieb Cristian Mammoli:
> Oliver Neukum ha scritto:
> > There's a very small chance that the compiler is to blame, but
> > it is far more likely that the phenomenon itself is not fully repeatable.
> > How often did you try?
> >
> > 	Regards
> > 		Oliver
> >   
> Well, it happens every single time I boot (or reboot) the notebook with
> the bluetooth switch on if this is what you mean. I tried at least 2-3
> times with every kernel I tested and the only one that seems to work is
> 2.6.17 from ubuntu edgy repos.

OK, please simply concentrate on vanilla kernel.org kernels.

	Regards
		Oliver
Comment 19 Alan Stern 2007-03-03 07:51:41 UTC 
On Sat, 3 Mar 2007, Cristian Mammoli wrote:

> Oliver Neukum ha scritto:
> > There's a very small chance that the compiler is to blame, but
> > it is far more likely that the phenomenon itself is not fully repeatable.
> > How often did you try?
> >
> > 	Regards
> > 		Oliver
> >   
> Well, it happens every single time I boot (or reboot) the notebook with
> the bluetooth switch on if this is what you mean. I tried at least 2-3
> times with every kernel I tested and the only one that seems to work is
> 2.6.17 from ubuntu edgy repos.

This could be caused by something outside the USB stack.  For instance, 
ACPI might mess up the power supply to the Bluetooth device.

Alan Stern
Comment 20 Anonymous Emailer 2007-03-03 12:45:19 UTC 
Reply-To: oliver@neukum.org

Am Samstag, 3. M
Comment 21 Cristian Mammoli 2007-03-03 12:52:00 UTC 
On sab, 2007-03-03 at 12:45 -0800, bugme-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8104

> > This could be caused by something outside the USB stack.  For instance, 
> > ACPI might mess up the power supply to the Bluetooth device.
> 
> Good point. Bisection should work nevertheless, shouldn't it?
> 

I'm downloading 2.6.15 right now, I'm really running out of ideas...
I'll also try booting with acpi=off. Any further hint is highly
appreciated.
Comment 22 Alan Stern 2007-03-03 13:46:00 UTC 
On Sat, 3 Mar 2007, Oliver Neukum wrote:

> Am Samstag, 3. M
Comment 23 Cristian Mammoli 2007-03-03 14:03:21 UTC 
Alan Stern ha scritto:
>
> It should work even better than posting a message on linus-usb-devel!  :-)
>
> It's important to stick with the same userspace components as much as
> possible during the testing, in case one of them turns out to be the
> guilty party rather than something in the kernel.
>
> Alan Stern
>
>   
It takes me at least 40 minutes to build a new kernel and the overheat 
is killing my notebook :)
Anyway I'm still looking for a vanilla kernel that does not trigger the bug.

Cristian~
Comment 24 Cristian Mammoli 2007-03-04 03:02:52 UTC 
On sab, 2007-03-03 at 23:03 +0100, Cristian Mammoli wrote:
>   
> It takes me at least 40 minutes to build a new kernel and the overheat 
> is killing my notebook :)
> Anyway I'm still looking for a vanilla kernel that does not trigger the bug.
> 
> Cristian~

Well, something new happened this morning :) While I was building 2.6.16
a small bluetooth icon popped up in my traybar: the bluetooth got
recognized without my intervention! Too bad I was using a kernel without
usb debug on :(

[  753.452000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  755.468000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  757.484000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  759.500000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  761.516000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  763.532000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  765.548000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  767.564000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  769.580000] hub 2-0:1.0: connect-debounce failed, port 6 disabled
[  770.396000] usb 4-2: new full speed USB device using uhci_hcd and
address 2
[  770.576000] usb 4-2: configuration #1 chosen from 1 choice
[  771.256000] Bluetooth: HCI USB driver ver 2.9
[  771.260000] usbcore: registered new interface driver hci_usb
Comment 25 Anonymous Emailer 2007-03-04 03:27:57 UTC 
Reply-To: oliver@neukum.org

Am Samstag, 3. März 2007 10:07 schrieb Cristian Mammoli:
> Well,something weird is going on here...
> 2.6.17 ubuntu edgy binary: works
> 2.6.20 ubuntu feisty binary: broken
> 2.6.17 vanilla: broken O_O
> 2.6.17 ubuntu edgy patched sources: broken
> 
> Any chance this behaviour is environment related?
> compiler, libs etc?

Please check your boot log for the compiler used in the working kernel
binary compared to the compiler you are using.

	Regards
		Oliver
Comment 26 Cristian Mammoli 2007-03-04 08:20:02 UTC 
On dom, 2007-03-04 at 12:27 +0100, Oliver Neukum wrote:
> > compiler, libs etc?
> 
> Please check your boot log for the compiler used in the working kernel
> binary compared to the compiler you are using.

Working:
[17179569.184000] Linux version 2.6.17-10-generic (root@terranova) (gcc
version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Tue
Dec 5 22:28:26 UTC 2006 (Ubuntu 2.6.17-10.34-generic)

Not working:
[    0.000000] Linux version 2.6.20-9-generic (root@rothera) (gcc
version 4.1.2 (Ubuntu 4.1.2-0ubuntu3)) #2 SMP Mon Feb 26 03:01:44 UTC
2007 (Ubuntu 2.6.20-9.16-generic
Comment 27 Cristian Mammoli 2007-03-04 10:09:56 UTC 
On dom, 2007-03-04 at 12:27 +0100, Oliver Neukum wrote:

> 
> Please check your boot log for the compiler used in the working kernel
> binary compared to the compiler you are using.

I noticed that the message occurs if the device is active BEFORE
uhci-hcd gets loaded. 
e.g.

boot with bluetooth on: debounce failed
switch off/on bluetooth: device recognized and working
rmmod uhci-hcd then modprobe uhci-hcd: debounce failed again

and of course
boot with bt off then switching on: device recognized and working
rmmod uhci-hcd then modprobe uhci-hcd: debounce failed

I also noticed that even if I disable bluetooth in the system bios I get
debounce failed anyway depending on the position of the switch at boot
time.

dmesg with usb debug available if needed.
Comment 28 Anonymous Emailer 2007-03-04 10:16:36 UTC 
Reply-To: oliver@neukum.org

Am Sonntag, 4. März 2007 17:19 schrieb Cristian Mammoli:
> On dom, 2007-03-04 at 12:27 +0100, Oliver Neukum wrote:
> > > compiler, libs etc?
> > 
> > Please check your boot log for the compiler used in the working kernel
> > binary compared to the compiler you are using.
> 
> Working:
> [17179569.184000] Linux version 2.6.17-10-generic (root@terranova) (gcc
> version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Tue
> Dec 5 22:28:26 UTC 2006 (Ubuntu 2.6.17-10.34-generic)

Is this compiled from a kernel.org kernel? Can you recompile that exact
kernel?

	Regards
		Oliver
Comment 29 Anonymous Emailer 2007-03-04 10:22:36 UTC 
Reply-To: oliver@neukum.org

Am Sonntag, 4. März 2007 19:09 schrieb Cristian Mammoli:
> On dom, 2007-03-04 at 12:27 +0100, Oliver Neukum wrote:
> 
> > 
> > Please check your boot log for the compiler used in the working kernel
> > binary compared to the compiler you are using.
> 
> I noticed that the message occurs if the device is active BEFORE
> uhci-hcd gets loaded. 
> e.g.
> 
> boot with bluetooth on: debounce failed
> switch off/on bluetooth: device recognized and working
> rmmod uhci-hcd then modprobe uhci-hcd: debounce failed again
> 
> and of course
> boot with bt off then switching on: device recognized and working
> rmmod uhci-hcd then modprobe uhci-hcd: debounce failed

This makes it likely that some device initialisation code is not severe
enough. It is important to find out why one kernel works and the other
does not.

I'll try to find out what ubuntu does to its kernels.

	Regards
		Oliver
Comment 30 Cristian Mammoli 2007-03-04 10:22:58 UTC 
On dom, 2007-03-04 at 19:16 +0100, Oliver Neukum wrote:

> Is this compiled from a kernel.org kernel? 

Don't think it's from vanilla sources, it probably has ton of patches
from ubuntu.

> Can you recompile that exact
> kernel?

I did and it didn't work. I starting to think this is some kind of
hardware failure happened before upgrading to feisty...
Comment 31 Anonymous Emailer 2007-03-04 11:53:34 UTC 
Reply-To: oliver@neukum.org

Am Sonntag, 4. März 2007 19:23 schrieb Cristian Mammoli:
> On dom, 2007-03-04 at 19:16 +0100, Oliver Neukum wrote:
> 
> > Is this compiled from a kernel.org kernel? 
> 
> Don't think it's from vanilla sources, it probably has ton of patches
> from ubuntu.
> 
> > Can you recompile that exact
> > kernel?
> 
> I did and it didn't work. I starting to think this is some kind of
> hardware failure happened before upgrading to feisty... 

To rule that out, can you downgrade to the previously working kernel?

	Regards
		Oliver
Comment 32 Alan Stern 2007-03-04 14:16:39 UTC 
On Sun, 4 Mar 2007, Oliver Neukum wrote:

> > I noticed that the message occurs if the device is active BEFORE
> > uhci-hcd gets loaded. 
> > e.g.
> > 
> > boot with bluetooth on: debounce failed
> > switch off/on bluetooth: device recognized and working
> > rmmod uhci-hcd then modprobe uhci-hcd: debounce failed again
> > 
> > and of course
> > boot with bt off then switching on: device recognized and working
> > rmmod uhci-hcd then modprobe uhci-hcd: debounce failed
> 
> This makes it likely that some device initialisation code is not severe
> enough. It is important to find out why one kernel works and the other
> does not.

On the contrary, this indicates the problem has nothing to do with the
kernel version at all.  Probably it's just an accident of timing that one
system ends up loading uhci-hcd before the device is active and other
systems don't.

There was a very similar report recently involving ohci-hcd.  Evidently 
some EHCI controllers won't perform a handoff if the companion controller 
isn't initialized.

Alan Stern
Comment 33 Cristian Mammoli 2007-03-04 15:01:02 UTC 
On dom, 2007-03-04 at 20:53 +0100, Oliver Neukum wrote:

> To rule that out, can you downgrade to the previously working kernel?
> 
> 	Regards
> 		Oliver
I have another amilo v3205 at work, i'll do some checks on it...  I'll
try to swap hard drives, run an edgy live cd etc. If the problem doesn't
occur with it, it's definitevely an hardware failure of some kind.
Otherwise I'll try a clean edgy install on my own notebook.
Thanks for your time.
Comment 34 Cristian Mammoli 2007-03-05 00:25:03 UTC 
On lun, 2007-03-05 at 00:01 +0100, Cristian Mammoli wrote:

> I have another amilo v3205 at work, i'll do some checks on it...  I'll
> try to swap hard drives, run an edgy live cd etc. If the problem doesn't
> occur with it, it's definitevely an hardware failure of some kind.
> Otherwise I'll try a clean edgy install on my own notebook.
> Thanks for your time.

Same error on the other notebook, it seem a common problem of all amilo
notebooks with on-board bluetooth:
http://www.google.it/search?hl=it&q=amilo+debounce&btnG=Cerca&meta=
I'll install edgy tonight.

Cristian
Comment 35 Anonymous Emailer 2007-03-05 02:29:12 UTC 
Reply-To: oliver@neukum.org

Am Sonntag, 4. M
Comment 36 Cristian Mammoli 2007-03-05 04:16:06 UTC 
On lun, 2007-03-05 at 11:28 +0100, Oliver Neukum wrote:

> please try unloading and reloading the ehci driver.
> 
> 	Regards
> 		Oliver

When the device is working:

on rmmod:
[ 5873.059133] ehci_hcd 0000:00:1d.7: remove, state 4
[ 5873.059143] ehci_hcd 0000:00:1d.7: roothub graceful disconnect
[ 5873.059151] usb usb1: USB disconnect, address 1
[ 5873.059156] usb usb1: unregistering device
[ 5873.059162] usb usb1: usb_disable_device nuking all URBs
[ 5873.059171] usb usb1: unregistering interface 1-0:1.0
[ 5873.059202] PM: Removing info for No Bus:usbdev1.1_ep81
[ 5873.061906]  usbdev1.1_ep81: ep_device_release called for
usbdev1.1_ep81
[ 5873.061965] PM: Removing info for usb:1-0:1.0
[ 5873.061984] usb 1-0:1.0: uevent
[ 5873.063834] PM: Removing info for No Bus:usbdev1.1
[ 5873.067939] PM: Removing info for No Bus:usbdev1.1_ep00
[ 5873.068500]  usbdev1.1_ep00: ep_device_release called for
usbdev1.1_ep00
[ 5873.068590] PM: Removing info for usb:usb1
[ 5873.068605] usb usb1: uevent
[ 5873.069125] ehci_hcd 0000:00:1d.7: stop
[ 5873.069137] ehci_hcd 0000:00:1d.7: reset command 010002 (park)=0
ithresh=1 period=1024 Reset HALT
[ 5873.073045] ehci_hcd 0000:00:1d.7: irq normal 0 err 0 reclaim 0 (lost
0)
[ 5873.073054] ehci_hcd 0000:00:1d.7: complete 0 unlink 0
[ 5873.073062] ehci_hcd 0000:00:1d.7: ehci_stop completed status 1000
Halt
[ 5873.073074] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
[ 5873.073676] ACPI: PCI interrupt for device 0000:00:1d.7 disabled

on modprobe:
[ 5893.958827] ehci_hcd: block sizes: qh 128 qtd 96 itd 192 sitd 96
[ 5893.959442] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level,
low) -> IRQ 19
[ 5893.959468] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[ 5893.959477] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 5893.960134] drivers/usb/core/inode.c: creating file '001'
[ 5893.960147] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 1
[ 5893.960161] ehci_hcd 0000:00:1d.7: reset hcs_params 0x104208 dbg=1
cc=4 pcc=2 ordered !ppc ports=8
[ 5893.960170] ehci_hcd 0000:00:1d.7: reset hcc_params 6871 thresh 7
uframes 1024 64 bit addr
[ 5893.960223] ehci_hcd 0000:00:1d.7: debug port 1
[ 5893.960232] PCI: cache line size of 32 is not supported by device
0000:00:1d.7
[ 5893.960238] ehci_hcd 0000:00:1d.7: supports USB remote wakeup
[ 5893.960253] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xdc444000
[ 5893.960263] ehci_hcd 0000:00:1d.7: reset command 080002 (park)=0
ithresh=8 period=1024 Reset HALT
[ 5893.964161] ehci_hcd 0000:00:1d.7: init command 010001 (park)=0
ithresh=1 period=1024 RUN
[ 5893.964172] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[ 5893.964204] usb usb1: default language 0x0409
[ 5893.964222] usb usb1: new device strings: Mfr=3, Product=2,
SerialNumber=1
[ 5893.964227] usb usb1: Product: EHCI Host Controller
[ 5893.964233] usb usb1: Manufacturer: Linux 2.6.21-rc2 ehci_hcd
[ 5893.964238] usb usb1: SerialNumber: 0000:00:1d.7
[ 5893.964255] PM: Adding info for usb:usb1
[ 5893.964277] usb usb1: uevent
[ 5893.964830] usb usb1: usb_probe_device
[ 5893.964887] PM: Adding info for No Bus:usbdev1.1_ep00
[ 5893.965140] usb usb1: configuration #1 chosen from 1 choice
[ 5893.965155] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 5893.965169] PM: Adding info for usb:1-0:1.0
[ 5893.965190] usb 1-0:1.0: uevent
[ 5893.965415] hub 1-0:1.0: usb_probe_interface
[ 5893.965421] hub 1-0:1.0: usb_probe_interface - got id
[ 5893.965427] hub 1-0:1.0: USB hub found
[ 5893.965441] hub 1-0:1.0: 8 ports detected
[ 5893.965446] hub 1-0:1.0: standalone hub
[ 5893.965450] hub 1-0:1.0: no power switching (usb 1.0)
[ 5893.965455] hub 1-0:1.0: individual port over-current protection
[ 5893.965460] hub 1-0:1.0: Single TT
[ 5893.965465] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[ 5893.965472] hub 1-0:1.0: power on to power good time: 20ms
[ 5893.965481] hub 1-0:1.0: local power source is good
[ 5893.965487] hub 1-0:1.0: trying to enable port power on
non-switchable hub
[ 5893.967323] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.967336] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.969303] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.970302] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.971301] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.971313] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.972300] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.973301] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.974295] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.975293] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.975299] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.976299] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.977299] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.978291] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.978296] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.979291] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.980290] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.981289] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.981294] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.982289] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.983287] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.984289] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.984295] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.985286] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.986286] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.987288] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.987292] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.988287] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.989286] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.990284] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.990288] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.991283] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.992283] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.993283] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.993289] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.994283] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.995282] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.996282] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.996288] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.997286] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.998280] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.999279] usb 4-2: uhci_result_common: failed with status 440000
[ 5893.999285] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.000279] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.001279] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.002277] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.002282] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.003277] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.004276] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.005276] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.005281] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.006275] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.007278] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.007886] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.007891] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.007917] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
[ 5894.007932] uhci_hcd 0000:00:1d.2: port 2 portsc 008a,00
[ 5894.007944] hub 4-0:1.0: port 2, status 0100, change 0003, 12 Mb/s
[ 5894.007947] usb 4-2: USB disconnect, address 5
[ 5894.007949] usb 4-2: unregistering device
[ 5894.007952] usb 4-2: usb_disable_device nuking all URBs
[ 5894.007960] uhci_hcd 0000:00:1d.2: shutdown urb dfb387d4 pipe
40408580 ep1in-intr
[ 5894.008275] uhci_hcd 0000:00:1d.2: release dev 5 ep81-INT, period 1,
phase 0, 23 us
[ 5894.008280] usb 4-2: uhci_result_common: failed with status 440000
[ 5894.009279] uhci_hcd 0000:00:1d.2: shutdown urb dfc57a14 pipe
00418580 ep3in-iso
[ 5894.009285] uhci_hcd 0000:00:1d.2: shutdown urb dff3d414 pipe
00418580 ep3in-iso
[ 5894.010278] uhci_hcd 0000:00:1d.2: release dev 5 ep83-ISO, period 1,
phase 0, 22 us
[ 5894.010284] usb 4-2: unregistering interface 4-2:1.0
[ 5894.010308] PM: Removing info for No Bus:usbdev4.5_ep81
[ 5894.010335]  usbdev4.5_ep81: ep_device_release called for
usbdev4.5_ep81
[ 5894.010353] PM: Removing info for No Bus:usbdev4.5_ep02
[ 5894.010368]  usbdev4.5_ep02: ep_device_release called for
usbdev4.5_ep02
[ 5894.010382] PM: Removing info for No Bus:usbdev4.5_ep82
[ 5894.010397]  usbdev4.5_ep82: ep_device_release called for
usbdev4.5_ep82
[ 5894.010447] PM: Removing info for No Bus:hci0
[ 5894.068044] PM: Adding info for No Bus:usbdev1.1_ep81
[ 5894.068086] PM: Adding info for No Bus:usbdev1.1
[ 5894.068100] drivers/usb/core/inode.c: creating file '001'
[ 5894.219935] PM: Removing info for usb:4-2:1.0
[ 5894.219973] usb 4-2:1.0: uevent
[ 5894.220005] usb 4-2: unregistering interface 4-2:1.1
[ 5894.220039] PM: Removing info for No Bus:usbdev4.5_ep03
[ 5894.220072]  usbdev4.5_ep03: ep_device_release called for
usbdev4.5_ep03
[ 5894.220100] PM: Removing info for No Bus:usbdev4.5_ep83
[ 5894.220128]  usbdev4.5_ep83: ep_device_release called for
usbdev4.5_ep83
[ 5894.220166] PM: Removing info for usb:4-2:1.1
[ 5894.220179] usb 4-2:1.1: uevent
[ 5894.220244] PM: Removing info for No Bus:usbdev4.5
[ 5894.220300] PM: Removing info for No Bus:usbdev4.5_ep00
[ 5894.220328]  usbdev4.5_ep00: ep_device_release called for
usbdev4.5_ep00
[ 5894.220401] PM: Removing info for usb:4-2
[ 5894.220413] usb 4-2: uevent
[ 5894.298676] hub 4-0:1.0: debounce: port 2: total 100ms stable 100ms
status 0x100
[ 5894.298692] hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040
[ 5894.298726] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5894.298740] hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s
[ 5894.364348] hub 1-0:1.0: debounce: port 6: total 100ms stable 100ms
status 0x501
[ 5894.388509] ehci_hcd 0000:00:1d.7: port 6 full speed --> companion
[ 5894.388524] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 003801
POWER OWNER sig=j CONNECT
[ 5894.388535] hub 1-0:1.0: port 6 not reset yet, waiting 50ms
[ 5894.408846] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 003002
POWER OWNER sig=se0 CSC
[ 5894.408896] hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040
[ 5894.450864] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
[ 5894.450887] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5894.450901] hub 4-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
[ 5894.486606] hub 4-0:1.0: debounce: port 2: total 100ms stable 100ms
status 0x101
[ 5894.518845] usb 4-2: new full speed USB device using uhci_hcd and
address 6
[ 5894.635443] usb 4-2: new device strings: Mfr=0, Product=0,
SerialNumber=0
[ 5894.635478] PM: Adding info for usb:4-2
[ 5894.635504] usb 4-2: uevent
[ 5894.635533] usb 4-2: usb_probe_device
[ 5894.635583] PM: Adding info for No Bus:usbdev4.6_ep00
[ 5894.635620] usb 4-2: configuration #1 chosen from 1 choice
[ 5894.638405] usb 4-2: adding 4-2:1.0 (config #1, interface 0)
[ 5894.638429] PM: Adding info for usb:4-2:1.0
[ 5894.638452] usb 4-2:1.0: uevent
[ 5894.638484] hci_usb 4-2:1.0: usb_probe_interface
[ 5894.638490] hci_usb 4-2:1.0: usb_probe_interface - got id
[ 5894.640420] PM: Adding info for No Bus:hci0
[ 5894.640497] PM: Adding info for No Bus:usbdev4.6_ep81
[ 5894.640546] PM: Adding info for No Bus:usbdev4.6_ep02
[ 5894.640596] PM: Adding info for No Bus:usbdev4.6_ep82
[ 5894.640631] usb 4-2: adding 4-2:1.1 (config #1, interface 1)
[ 5894.640644] PM: Adding info for usb:4-2:1.1
[ 5894.640664] usb 4-2:1.1: uevent
[ 5894.640712] PM: Adding info for No Bus:usbdev4.6_ep03
[ 5894.640765] PM: Adding info for No Bus:usbdev4.6_ep83
[ 5894.640816] PM: Adding info for No Bus:usbdev4.6
[ 5894.640842] drivers/usb/core/inode.c: creating file '006'
[ 5894.644334] uhci_hcd 0000:00:1d.2: reserve dev 6 ep81-INT, period 1,
phase 0, 23 us
[ 5894.644364] uhci_hcd 0000:00:1d.2: reserve dev 6 ep83-ISO, period 1,
phase 0, 22 us
[ 5895.409272] hub 1-0:1.0: hub_suspend
[ 5895.409291] ehci_hcd 0000:00:1d.7: suspend root hub
[ 5895.409326] usb usb1: usb auto-suspend

When the device is NOT working:
on rmmod:
[ 5956.605038] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5956.606976] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5956.611471] ehci_hcd 0000:00:1d.7: remove, state 1
[ 5956.611480] ehci_hcd 0000:00:1d.7: roothub graceful disconnect
[ 5956.612159] usb usb1: USB disconnect, address 1
[ 5956.617042] hub 1-0:1.0: hub_port_status failed (err = -19)
[ 5956.617053] hub 1-0:1.0: connect-debounce failed, port 6 disabled
[ 5956.617061] hub 1-0:1.0: cannot disable port 6 (err = -19)
[ 5956.617072] hub 1-0:1.0: state 0 ports 8 chg 0000 evt 0040
[ 5956.617207] usb usb1: unregistering device
[ 5956.617213] usb usb1: usb_disable_device nuking all URBs
[ 5956.617273] usb usb1: unregistering interface 1-0:1.0
[ 5956.617796] PM: Removing info for No Bus:usbdev1.1_ep81
[ 5956.619317]  usbdev1.1_ep81: ep_device_release called for
usbdev1.1_ep81
[ 5956.619649] PM: Removing info for usb:1-0:1.0
[ 5956.619856] usb 1-0:1.0: uevent
[ 5956.620063] PM: Removing info for No Bus:usbdev1.1
[ 5956.620323] PM: Removing info for No Bus:usbdev1.1_ep00
[ 5956.620574]  usbdev1.1_ep00: ep_device_release called for
usbdev1.1_ep00
[ 5956.629199] PM: Removing info for usb:usb1
[ 5956.630008] usb usb1: uevent
[ 5956.630312] ehci_hcd 0000:00:1d.7: stop
[ 5956.630330] ehci_hcd 0000:00:1d.7: reset command 010003 (park)=0
ithresh=1 period=1024 Reset RUN
[ 5956.630398] hub 4-0:1.0: state 8 ports 2 chg 0000 evt 0000
[ 5956.630409] usb usb4: usb auto-resume
[ 5956.630413] usb usb4: finish resume
[ 5956.630426] hub 4-0:1.0: hub_resume
[ 5956.630431] usb usb4: wakeup_rh
[ 5956.636411] ehci_hcd 0000:00:1d.7: irq normal 0 err 0 reclaim 0 (lost
0)
[ 5956.636418] ehci_hcd 0000:00:1d.7: complete 0 unlink 0
[ 5956.636427] ehci_hcd 0000:00:1d.7: ehci_stop completed status 1000
Halt
[ 5956.636439] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
[ 5956.637657] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
[ 5956.659177] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.659195] hub 4-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
[ 5956.663402] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.670761] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.674488] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.677960] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.681442] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.692156] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.696040] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.699525] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.703081] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.706515] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.709946] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.715352] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.731839] uhci_hcd 0000:00:1d.2: port 2 portsc 0083,00
[ 5956.737799] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.743301] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.761068] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.770317] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.780202] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.793564] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.799309] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.804861] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.810720] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.816027] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.825327] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.837464] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.846061] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.856714] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.870974] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.876415] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.881731] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.891037] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.900627] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.906022] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.911815] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.924553] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5956.933444] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.939226] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.948203] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.953422] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5956.975736] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5957.007689] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.039648] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.054566] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.058804] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.063961] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.072492] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.081037] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.088968] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.093994] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.099558] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.109616] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.119231] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.127036] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.132342] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.137663] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.143455] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.152273] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.168561] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.168584] hub 4-0:1.0: debounce: port 2: total 1500ms stable 0ms
status 0x101
[ 5957.168590] hub 4-0:1.0: connect-debounce failed, port 2 disabled
[ 5957.168608] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
[ 5957.193671] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
[ 5957.193693] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5957.193707] hub 4-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
[ 5957.202877] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5957.208461] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
 [many more lines]

on modprobe:

[ 5999.188205] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5999.197761] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
[ 5999.212286] ehci_hcd: block sizes: qh 128 qtd 96 itd 192 sitd 96
[ 5999.213921] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level,
low) -> IRQ 19
[ 5999.214448] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[ 5999.214457] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 5999.215277] drivers/usb/core/inode.c: creating file '001'
[ 5999.215667] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 1
[ 5999.216144] ehci_hcd 0000:00:1d.7: reset hcs_params 0x104208 dbg=1
cc=4 pcc=2 ordered !ppc ports=8
[ 5999.216156] ehci_hcd 0000:00:1d.7: reset hcc_params 6871 thresh 7
uframes 1024 64 bit addr
[ 5999.217785] ehci_hcd 0000:00:1d.7: debug port 1
[ 5999.217799] PCI: cache line size of 32 is not supported by device
0000:00:1d.7
[ 5999.217806] ehci_hcd 0000:00:1d.7: supports USB remote wakeup
[ 5999.217821] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xdc444000
[ 5999.217832] ehci_hcd 0000:00:1d.7: reset command 080002 (park)=0
ithresh=8 period=1024 Reset HALT
[ 5999.221711] ehci_hcd 0000:00:1d.7: init command 010001 (park)=0
ithresh=1 period=1024 RUN
[ 5999.221728] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[ 5999.221763] usb usb1: default language 0x0409
[ 5999.221781] usb usb1: new device strings: Mfr=3, Product=2,
SerialNumber=1
[ 5999.221787] usb usb1: Product: EHCI Host Controller
[ 5999.221792] usb usb1: Manufacturer: Linux 2.6.21-rc2 ehci_hcd
[ 5999.221798] usb usb1: SerialNumber: 0000:00:1d.7
[ 5999.221816] PM: Adding info for usb:usb1
[ 5999.221839] usb usb1: uevent
[ 5999.223305] usb usb1: usb_probe_device
[ 5999.223362] PM: Adding info for No Bus:usbdev1.1_ep00
[ 5999.223908] usb usb1: configuration #1 chosen from 1 choice
[ 5999.223925] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 5999.223938] PM: Adding info for usb:1-0:1.0
[ 5999.223957] usb 1-0:1.0: uevent
[ 5999.224507] hub 1-0:1.0: usb_probe_interface
[ 5999.224513] hub 1-0:1.0: usb_probe_interface - got id
[ 5999.224520] hub 1-0:1.0: USB hub found
[ 5999.224534] hub 1-0:1.0: 8 ports detected
[ 5999.224538] hub 1-0:1.0: standalone hub
[ 5999.224544] hub 1-0:1.0: no power switching (usb 1.0)
[ 5999.224549] hub 1-0:1.0: individual port over-current protection
[ 5999.224555] hub 1-0:1.0: Single TT
[ 5999.224561] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[ 5999.224567] hub 1-0:1.0: power on to power good time: 20ms
[ 5999.224582] hub 1-0:1.0: local power source is good
[ 5999.224588] hub 1-0:1.0: trying to enable port power on
non-switchable hub
[ 5999.229739] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
[ 5999.325205] PM: Adding info for No Bus:usbdev1.1_ep81
[ 5999.325904] PM: Adding info for No Bus:usbdev1.1
[ 5999.326055] drivers/usb/core/inode.c: creating file '001'
[ 5999.357054] hub 4-0:1.0: debounce: port 2: total 1250ms stable 100ms
status 0x100
[ 5999.357064] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
[ 5999.357076] hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040
[ 5999.357098] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.357107] hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s
[ 5999.369962] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.376666] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.380818] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.399452] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.403801] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.408386] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.414546] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.420914] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.427753] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.434617] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.441911] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.454517] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.461407] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.473717] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.489035] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.496186] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.502728] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.509232] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.515620] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.522366] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.529590] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.538937] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.545027] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.551644] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.562029] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.568345] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.574443] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.605860] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.629855] usb usb4: suspend_rh (auto-stop)
[ 5999.637854] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.669810] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.677466] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.683446] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.686641] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.694235] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.698202] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
POWER sig=se0 CSC
[ 5999.708509] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.727479] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.735054] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.742765] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.751978] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.759329] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.770328] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.787838] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.796368] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.800848] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.808632] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.823582] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.830804] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.835923] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.841296] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.845015] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
[ 5999.852711] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
POWER sig=j CSC CONNECT
Comment 37 Alan Stern 2007-03-05 11:56:59 UTC 
On Mon, 5 Mar 2007, Cristian Mammoli wrote:

> On lun, 2007-03-05 at 11:28 +0100, Oliver Neukum wrote:
> 
> > please try unloading and reloading the ehci driver.
> > 
> > 	Regards
> > 		Oliver

> When the device is NOT working:
> on rmmod:
...
> [ 5956.663402] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.670761] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.674488] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.677960] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.681442] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.692156] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.696040] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.699525] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
> [ 5956.703081] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
...
> [ 5957.168584] hub 4-0:1.0: debounce: port 2: total 1500ms stable 0ms
> status 0x101
> [ 5957.168590] hub 4-0:1.0: connect-debounce failed, port 2 disabled
> [ 5957.168608] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
> [ 5957.193671] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
> [ 5957.193693] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
> [ 5957.193707] hub 4-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
> [ 5957.202877] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5957.208461] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
>  [many more lines]
> 
> on modprobe:
...
> [ 5999.369962] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.376666] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
> POWER sig=se0 CSC
> [ 5999.380818] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.399452] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.403801] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.408386] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.414546] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
> POWER sig=se0 CSC
> [ 5999.420914] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT

This is different from what I thought before.  It's clear there's 
something wrong with the Bluetooth hardware, or the hardware the connects 
the Bluetooth device to the USB bus.  It constantly connects and then 
disconnects, over and over again.

There's no way for the EHCI controller to ignore this kind of activity.  I 
don't know what can be done about it.

Alan Stern
Comment 38 Anonymous Emailer 2007-03-06 05:16:36 UTC 
Reply-To: oliver@neukum.org

Am Samstag, 3. März 2007 10:07 schrieb Cristian Mammoli:
> On ven, 2007-03-02 at 02:08 +0100, Cristian Mammoli wrote:
> > On gio, 2007-03-01 at 22:14 +0100, Oliver Neukum wrote:
> > > > Most recent kernel where this bug did *NOT* occur: 2.6.17
> > > 
> > > Very good. You are the first one to report a working kernel version.
> > > 
> > > Please post dmesg of a working and a not working kernel and
> > > lsusb -v of your devices. If possible please use kernels with
> > > CONFIG_USB_DEBUG.
> > 
> > 2.6.18 is broken as well... I'll build 2.6.17 tomorrow.
> > Anyway this is what happens when I turn off/on the bluetooth switch:
> 
> Well,something weird is going on here...
> 2.6.17 ubuntu edgy binary: works
> 2.6.20 ubuntu feisty binary: broken
> 2.6.17 vanilla: broken O_O
> 2.6.17 ubuntu edgy patched sources: broken

Can you confirm that you built the kernel from the same sources as
the working binary was built from? Are you using an initrd? Did you
include a custom DSDT for your notebook? Which modules are
included in the initrd?

	Regards
		Oliver
Comment 39 Marco 2007-03-16 10:18:47 UTC 
I have the same notebook & same bug.
Last version of kernel that worked normally is: 2.6.17-11-generic (via
linux-image of Ubuntu).
Last kernel sended as Feisty update (2.6.20-10-generic, 2.6.20-11-generic) don't
work.
So I tried in these days to compile a stable vanilla kernel 2.6.20.3, adding the
obsolete option CONFIG_USB_SUSPEND=y (present in previous versions), and
removing the new APM/ACPI support; but I report same flood.
Comment 40 Marco 2007-03-16 10:26:41 UTC 
Created attachment 10799 [details]
.config of last working kernel (2.6.17-11-generic)
Comment 41 Marco 2007-03-16 10:29:19 UTC 
Created attachment 10800 [details]
.config of kernel 2.6.20-11-generic (that generate the bug)
Comment 42 Cosmin Saveanu 2007-04-20 14:34:33 UTC 
I can confirm the same behaviour that appeared when I upgraded my Fujitsu
Siemens Amilo Si 1520 from Edgy Eft to Feisty (kernel 2.6.20-15). It would be
great if someone could find a solution. Thank you. Cosmin
Comment 43 Natalie Protasevich 2007-06-13 23:49:31 UTC 
Is this still broken with 2.6.22-rc4?
If so, will it be possible to check if vanilla 2.6.17 (not the Ubuntu built) is working? Then if it does, do some bisect searching between this one and next non-working vanilla (which sounds like 2.6.18)
If 2.6.17 doesn't work, then the key is probably in difference between vanilla and Ubuntu build whatever it is (some extra patches, config, compiler, compiler flags, etc.etc.)
Thanks.
Comment 44 Marco 2007-07-10 03:47:18 UTC 
I confirm that it's still broken in kernel 2.6.22-6 and 2.6.22-7 (binaries from Ubuntu Gutsy). Now i'ii try to compile last .22 stable.
Also same problem affects Fedora 7.0
Marco
Comment 45 Marco 2007-07-10 06:08:16 UTC 
The problem affects vanilla kernel 2.6.22 just compiled (no patched). I append dmesg.log for help you.
Comment 46 Marco 2007-07-10 06:08:56 UTC 
Created attachment 11991 [details]
dmesg with vanilla kernel 2.6.22
Comment 47 Anonymous Emailer 2007-07-24 14:26:34 UTC 
Reply-To: akpm@linux-foundation.org

guys, there have been updates to this bug via the bugzilla UI,
at http://bugzilla.kernel.org/show_bug.cgi?id=8104
Comment 48 Anonymous Emailer 2007-07-24 14:34:55 UTC 
Reply-To: oliver@neukum.org

Am Dienstag 24 Juli 2007 schrieb Andrew Morton:
> guys, there have been updates to this bug via the bugzilla UI,
> at http://bugzilla.kernel.org/show_bug.cgi?id=8104
> 

Hi,

we need to know the oldest kernel that does not work.
Please try 2.6.18 and 2.6.19

	Regards
		Oliver
Comment 49 Marco 2007-07-25 07:47:14 UTC 
For my configuration, oldest kernel that doesn't work is 2.6.19 (same situation for vanilla w/o patches, Ubuntu binaries, Fedora binaries).
Comment 50 Alan Stern 2007-07-25 14:12:40 UTC 
Actually we also need to know the latest vanilla kernel that does work.  So far all the working kernels seem to be customized in one way or another.
Comment 51 Alan Stern 2007-07-25 15:17:08 UTC 
Some other experiments to try with a "working" kernel and Bluetooth enabled:  rmmod uhci-hcd and modprobe it back.  Do the same with ehci-hcd.  Unload both of them and then modprobe them back in one order or the other.  Maybe it will turn out that the so-called "working" kernel doesn't always work.
Comment 52 Natalie Protasevich 2007-08-11 10:21:07 UTC 
Marco, Cosmin, Christian, did you get chance to try #51 to help with the analysis?
Thanks.
Comment 53 Marco 2007-09-04 16:30:25 UTC 
I changed the my distro. Now I work with Mandriva 2007.1 (binary kernel 2.6.17-13mdvlegacy) that presents same debounce connect problem. Unfortunately I haven't more time to spend for a kernel customization; anyway I have tried your trick.
Unloading both modules -> no more error displayed
Loading uhci-hcd -> error
Loading ehci-hcd -> error
Loading uhci-hcd & ehci-hcd -> error
Comment 54 Marco 2007-09-17 04:45:42 UTC 
Nothing to do. Every updated live distro that I've tried (OpenSuse, Fedora, Mandriva, Gentoo, Ubuntu) presents this problem with usb modules. Now I can say that this problem is indipendent from binaries of distros. To help you to fix this bug, please read this report: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/88530

Thank You!
Comment 55 Marco 2007-09-22 07:14:52 UTC 
This bug affects Fedora 8 Test 2 (Kernel 2.6.23 RC)
Comment 56 Alan Stern 2007-09-22 07:44:33 UTC 
Is anyone able to build a kernel (any version later than 2.6.0) that doesn't have this problem?  What happens if you build 2.6.17 with the config in Comment #40?

Note that it's entirely possible that the problem is triggered not by the kernel but by some other part of your distribution (like an initramfs image).  Or it could be caused by the BIOS, or by the Bluetooth hardware.
Comment 57 Cendo 2007-10-16 12:54:29 UTC 
I have the same problem with Ubuntu 7.04 & 7.10 (Release Candidate),
but Opensuse 10.3 with kernel 2.6.22 works fine.
My Notebook: fujitsu amilo pro v3205 with Bios 1.10
Comment 58 Alan Stern 2007-10-17 09:03:06 UTC 
What happens if you use the .config file from the Ubuntu kernels with the vanilla 2.6.22 kernel source?  What happens if you use the .config file from OpenSuSE 10.3 with the vanilla 2.6.22 source?
Comment 59 Ajith 2008-05-09 15:36:43 UTC 
Hi Guys,
This bug (all the symptoms including the console flooding) appeared in my HP dc7700 desktop after upgrading to Hardy (Kernel 2.6.24). It wasn't there on Gutsy nor Feisty. I've recompiled the kernel with all bluetooth off (Not sure whether there was a bluetooth device but some reports indicated that it is the blutooth that may be causing it) but still the bug remains!

For now I unloaded both the ehci and uhci modules (I'm not using any crtical USB devices at the moment) - Do let me know if you guys want to see the logs

Ajith
Comment 60 Alan Stern 2008-05-10 07:48:37 UTC 
To stop the problem you have to disable the bluetooth device in the BIOS.  Changing the kernel won't have any effect.

What version of the kernel were you using before upgrading to 2.6.24?

Please do attach (don't paste!) your logs to the bug report.  If you can collect a usbmon trace as well (see Documentation/usb/usbmon.txt in the kernel source) it would help.
Comment 61 Alan 2009-03-23 10:02:06 UTC 
Closing out stale bug
Comment 62 Jakub Bittner 2011-01-11 11:51:51 UTC 
I have the same problem, but my computer doesnt have bluetooth. Iam using Ubuntu kernel 2.6.37-9-generic (but it occured on any version in Lucid release)
Comment 63 Alan Stern 2011-01-11 15:42:49 UTC 
Jakub:

Can you build your own kernel, using vanilla 2.6.37 from kernel.org?  Enable the CONFIG_USB_DEBUG option and attach a copy of the dmesg log showing the problem.
Comment 64 Jakub Bittner 2011-01-13 08:36:42 UTC 
Created attachment 43402 [details]
dmesg of 2.6.32-21-generic ubuntu build from ubuntu source

I build kernel 2.6.32-21-generic from ubuntu sources. I know, you wanted newer kernel from vanila, but Iam not so good in kernel building. I hope it will help, anyway. :-)
Comment 65 Alan Stern 2011-01-13 14:53:38 UTC 
This looks like a hardware problem in your computer.  You can work around it by unloading ehci-hcd or unbinding it from the 0000:00:1d.7 device, but then you would lose USB-2.0 capability on those ports.
Comment 66 Jakub Bittner 2011-01-13 15:18:51 UTC 
Ok, we have 3 computers doing this. We replaced one and installed windows XP and USB worked. I will try it again with USB_DEBUG set and I will post the result here.