On Monday 13 Feb 2012 19:39:49 Peter Maffter wrote:

But both initialization methods show an error: "<3>[ 4.722529] hub 1-1:1.0: connect-debounce failed, port 1 disabled" This was not shown when booting SuSE 11.3 so I wonder why SuSE 12.1 fills up the logfile with that message: "... Feb 10 10:07:53 linux-wc9i kernel: [ 246.401407] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:55 linux-wc9i kernel: [ 248.441347] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:57 linux-wc9i kernel: [ 250.489279] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:59 linux-wc9i kernel: [ 252.537238] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:01 linux-wc9i kernel: [ 254.585179] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:03 linux-wc9i kernel: [ 256.633113] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:05 linux-wc9i kernel: [ 258.677047] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:07 linux-wc9i kernel: [ 260.724980] hub 1-1:1.0: connect-debounce failed, port 1 disabled ..."

I had something very similar to this on my laptop on the last kernel update for 11.3. After some research it appears that the kernel is now reporting these errors which before they didnt. I just lived with it I'm afraid (hardware issue as your internal USB hubs arent responding correctly). The interesting thing is when I did a zypper dup to 12.1 the lines disappeared. A -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Update to the newest 12.1 Kernel did not help, connect-debounce still appears. Also the new kernel made a failure when shutting down putting the fake RAID1 into "Verify" state which ended up in another 4-5hrs verify. :-( Once I had a boot of the 12.1 system without connect-debounce messages. I am just checking the differences. Yast2 HW Info shows some: Without debounce:               sd: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0               sd: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:1               sd: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/host10/target10:0:0/10:0:0:0 and              usb: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1              usb: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2      usb-storage: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0      usb-storage: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 whereas the same information is missing when the  connect-debounce occurs. I also disconnected all USB stuff except the built in cardreader and the connect-debounce remains so mouse and keyboard or cables are not the culprit. The built in cardreader cannot be the culprit because otherwise I would not have been able to boot without connect-debounce once. It looks like a timing issue when the USB hubs are discovered when booting. Any pointers? ----- Ursprüngliche Message ----- Von: Peter Maffter An: "opensuse@opensuse.org" Cc: Gesendet: 20:46 Dienstag, 14.Februar 2012 Betreff: Re: [opensuse] OpenSuSE 12.1: connect-debounce error That gives hope that updating the 12.1 kernel may help. Bugzilla says that Bug 547195 was marked as RESOLVED in 2010-02 https://bugzilla.novell.com/show_bug.cgi?id=547195 (funny if we both still get/got this bug) and Bug 23677 is a WONTFIX with "This is unsolvavble." from year 2007(!) https://bugzilla.novell.com/show_bug.cgi?id=236774 Nobody seems to care about this. That is also the result from reading Ubuntu forums. Since OpenSuSE 11.3 did not make debounce-problems with the same hardware I do not think that it is some hardware problem. Recently after some reboot to Windows 7 and back to OpenSuSE 12.1 I also had the case that this log message is missing and the whole 12.1 seemed to work without debounce messages. I will have to examine the corresponding boot logs. ----- Ursprüngliche Message ----- Von: Andrew Colvin An: opensuse@opensuse.org Cc: Gesendet: 9:29 Dienstag, 14.Februar 2012 Betreff: Re: [opensuse] OpenSuSE 12.1: connect-debounce error On Monday 13 Feb 2012 19:39:49 Peter Maffter wrote:

But both initialization methods show an error: "<3>[    4.722529] hub 1-1:1.0: connect-debounce failed, port 1 disabled" This was not shown when booting SuSE 11.3 so I wonder why SuSE 12.1 fills up the logfile with that message: "... Feb 10 10:07:53 linux-wc9i kernel: [  246.401407] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:55 linux-wc9i kernel: [  248.441347] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:57 linux-wc9i kernel: [  250.489279] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:07:59 linux-wc9i kernel: [  252.537238] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:01 linux-wc9i kernel: [  254.585179] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:03 linux-wc9i kernel: [  256.633113] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:05 linux-wc9i kernel: [  258.677047] hub 1-1:1.0: connect-debounce failed, port 1 disabled Feb 10 10:08:07 linux-wc9i kernel: [  260.724980] hub 1-1:1.0: connect-debounce failed, port 1 disabled ..."

I had something very similar to this on my laptop on the last kernel update for 11.3.  After some research it appears that the kernel is now reporting these errors which before they didnt.  I just lived with it I'm afraid (hardware issue as your internal USB hubs arent responding correctly).  The interesting thing is when I did a zypper dup to 12.1 the lines disappeared. A -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org