[Bug 236774] New: Message "connect-debounce failed" keeps coming up and severely degrades performance
https://bugzilla.novell.com/show_bug.cgi?id=236774
Summary: Message "connect-debounce failed" keeps coming up and
severely degrades performance
Product: openSUSE 10.2
Version: Final
Platform: i686
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@forge.provo.novell.com
ReportedBy: casualprogrammer@yahoo.com
QAContact: qa@suse.de
On my FSC Amilo Si1520 Notebook on power up the following message is showing up
in dmesg: "hub 5-0:1.0: connect-debounce failed, port 6 disabled"
(
:~> uname -a
Linux WORKSTATION6L 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
i686 i686 i386 GNU/Linux
)
This message keeps recurring ad infinitum.
After some more investigation, I could control the appearance of the messgae by
enabling / disabling bluetooth on my notebook.
If booted with bluetooth enabled the message occurs and can be turned off by
disabling bluetooh. On reenabling bluetooth it does not recur.
If booted with bluetooth disabled, the message does not appear, even after
bluetooth is enabled.
The bluetooth device functions perfectly well with both MS Windows XP and
openSUSE 10.2, so it is very unlikely that a hardware malfunction is causing
this phenomenon.
Also googling for "connect-debounce failed" shows lots of occurences with
various distributions and hardware configurations. Probably an upstream Kernel
problem.
I am attaching two files generated with dmesg > output.txt
dmesg20070117BTON.txt is the output after booting with bluetooth enabled,
dmesg20070117BTOFF.txt is the output after booting with bluetooth disabled.
---------------------dmesg20070117BTON.txt-----------------------------------
Linux version 2.6.18.2-34-default (geeko@buildhost) (gcc version 4.1.2 20061115
(prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003f690000 (usable)
BIOS-e820: 000000003f690000 - 000000003f698000 (ACPI data)
BIOS-e820: 000000003f698000 - 000000003f700000 (ACPI NVS)
BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
118MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f76d0
On node 0 totalpages: 259728
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 225280 pages, LIFO batch:31
HighMem zone: 30352 pages, LIFO batch:7
DMI present.
Using APIC driver default
IO/L-APIC allowed because system is MP or new enough
ACPI: RSDP (v000 PTLTD ) @ 0x000f7590
ACPI: RSDT (v001 FUJ___ DW1_____ 0x20060721 LTP 0x00000000) @ 0x3f691e9c
ACPI: FADT (v001 FUJ___ DW1_____ 0x20060721 LOHR 0x0000005a) @ 0x3f697e20
ACPI: MADT (v001 FUJ___ DW1_____ 0x20060721 LOHR 0x0000005a) @ 0x3f697e94
ACPI: BOOT (v001 FUJ___ DW1_____ 0x20060721 LTP 0x00000001) @ 0x3f697fd8
ACPI: MCFG (v001 FUJ___ DW1_____ 0x20060721 LOHR 0x0000005a) @ 0x3f697f34
ACPI: MADT (v001 FUJ___ DW1_____ 0x20060721 LTP 0x00000000) @ 0x3f697f70
ACPI: SSDT (v001 PmRef CpuPm 0x00003000 INTL 0x20050228) @ 0x3f691ed8
ACPI: DSDT (v001 FUJ___ DW1_____ 0x20060721 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: 2 duplicate APIC table ignored.
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:14 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 6:14 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Detected 1995.901 MHz processor.
Built 1 zonelists. Total pages: 259728
Kernel command line: root=/dev/sda6 vga=0x314 resume=/dev/sda5 splash=silent
bootsplash: silent mode.
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1022684k/1038912k available (1697k kernel code, 15508k reserved, 968k
data, 196k init, 121408k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3995.95 BogoMIPS (lpj=7991919)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9
00000000 00000000
CPU: After vendor identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9
00000000 00000000
monitor/mwait feature present.
using mwait in idle threads.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
checking if image is initramfs... it is
Freeing initrd memory: 3218k freed
ACPI: Core revision 20060707
CPU0: Intel Genuine Intel(R) CPU T2500 @ 2.00GHz stepping 08
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3991.77 BogoMIPS (lpj=7983547)
CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9
00000000 00000000
CPU: After vendor identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9
00000000 00000000
monitor/mwait feature present.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Genuine Intel(R) CPU T2500 @ 2.00GHz stepping 08
Total of 2 processors activated (7987.73 BogoMIPS).
ENABLING IO-APIC IRQs
.TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=69
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:02.0
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Firmware left 0000:07:08.0 e100 interrupts enabled, disabling
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 *7 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 *10 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 23) interrupt mode.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 8 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:1c.0
IO window: 2000-2fff
MEM window: da000000-dbffffff
PREFETCH window: d4000000-d5ffffff
PCI: Bridge: 0000:00:1c.1
IO window: 3000-3fff
MEM window: d6000000-d7ffffff
PREFETCH window: d0000000-d1ffffff
PCI: Bridge: 0000:00:1c.2
IO window: 4000-4fff
MEM window: d8000000-d9ffffff
PREFETCH window: d2000000-d3ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 5000-5fff
MEM window: dc000000-dc0fffff
PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1c.1 to 64
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1c.2 to 64
PCI: Enabling device 0000:00:1e.0 (0004 -> 0007)
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag value 0x82 read from CMOS RAM was invalid
Simple Boot Flag at 0x36 set to 0x1
Machine check exception polling timer started.
apm: BIOS not found.
audit: initializing netlink socket (disabled)
audit(1169225982.864:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
Allocate Port Service[0000:00:1c.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
Allocate Port Service[0000:00:1c.1:pcie03]
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.2:pcie00]
Allocate Port Service[0000:00:1c.2:pcie02]
Allocate Port Service[0000:00:1c.2:pcie03]
vesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 3750k, total
7872k
vesafb: mode is 800x600x16, linelength=1600, pages=7
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 82985
bytes,<6>...found (800x600, 49016 bytes, v3).
Console: switching to colour frame buffer device 96x33
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2F] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
input: AT Translated Set 2 keyboard as /class/input/input1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
Using IPI No-Shortcut mode
ACPI: (supports S0 S3 S4 S5)
Time: tsc clocksource has been installed.
Freeing unused kernel memory: 196k freed
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI subsystem initialized
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Ist]
[20060707]
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Cst]
[20060707]
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Ist]
[20060707]
ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Cst]
[20060707]
ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI: Thermal Zone [TZ00] (49 C)
Time: acpi_pm clocksource has been installed.
ICH7: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 185
ICH7: chipset revision 2
ICH7: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1810-0x1817, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
Synaptics Touchpad, model: 1, fw: 5.10, id: 0x258eb1, caps: 0xa04713/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input2
hda: _NEC DVD_RW ND-6750A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
libata version 2.00 loaded.
ahci 0000:00:1f.2: version 2.0
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x5 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part
ata1: SATA max UDMA/133 cmd 0xF8D1C500 ctl 0x0 bmdma 0x0 irq 233
ata2: SATA max UDMA/133 cmd 0xF8D1C580 ctl 0x0 bmdma 0x0 irq 233
ata3: SATA max UDMA/133 cmd 0xF8D1C600 ctl 0x0 bmdma 0x0 irq 233
ata4: SATA max UDMA/133 cmd 0xF8D1C680 ctl 0x0 bmdma 0x0 irq 233
scsi0 : ahci
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/100, 156301488 sectors: LBA48 NCQ (depth 31/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : ahci
ata2: SATA link down (SStatus 0 SControl 0)
scsi2 : ahci
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : ahci
ata4: SATA link down (SStatus 0 SControl 0)
Vendor: ATA Model: FUJITSU MHV2080B Rev: 0000
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
sd 0:0:0:0: Attached scsi disk sda
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
sd 0:0:0:0: Attached scsi generic sg0 type 0
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
PCI: Setting latency timer of device 0000:00:1b.0 to 64
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
intel_rng: FWH not detected
Linux agpgart interface v0.101 (c) Dave Jones
ieee1394: Initialized config rom entry `ip1394'
sdhci: Secure Digital Host Controller Interface driver, 0.12
sdhci: Copyright(c) Pierre Ossman
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 58
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 58, io base 0x00001820
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.18.2-34-default uhci_hcd
usb usb1: SerialNumber: 0000:00:1d.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 225, io base 0x00001840
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.18.2-34-default uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.1
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hda: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #2 from oneukum@novell.com 2007-01-22 07:47 MST ------- You said, the device has work with Linux before. Could you give the kernel version it worked with? Also, how do disable/enable bluetooth? Do you have a physical switch? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |casualprogrammer@yahoo.com Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | ------- Comment #3 from casualprogrammer@yahoo.com 2007-01-22 18:27 MST ------- It is working with: Linux WORKSTATION6L 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 i686 i386 GNU/Linux There are two switches for wireless support: 1. A separate key with an antenna symbol above the regular keyboard, this switches off/on both, WLAN and bluetooth. 2. The key combination FN+ESC switches on/off bluetooth alone The malfunction is not the device nor the bluetooth software, bluetooth works perfectly well. This must be a problem of the USB driver, even if the bluetooth device was issuing sporadic signals, they should be suppressed by the USB driver. Obviously the bluetooth device behaves correctly, otherwise it wouldn't work. As I mentioned, googling for the symptom shows various reports of the same symptom with other distros and devices. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #4 from oneukum@novell.com 2007-01-23 03:18 MST ------- Sorry, I was unclear. Does it matter which way you disable bluetooth? Do both switches have the same effect? Could you try "rmmod ehci-hcd"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #5 from casualprogrammer@yahoo.com 2007-01-23 04:09 MST ------- OK, 1. no, it does not matter. usually I have the "wireless switch" set to on, because I'm using WLAN to connect to the internet. I control bluetooth by pressing FN+ESC repeatedly. 2. On issuing: #rmmod ehci-hcd dmesg reports: hub 2-0:1.0: connect-debounce failed, port 6 disabled hub 2-0:1.0: connect-debounce failed, port 6 disabled hub 2-0:1.0: connect-debounce failed, port 6 disabled hub 2-0:1.0: connect-debounce failed, port 6 disabled ehci_hcd 0000:00:1d.7: remove, state 1 usb usb2: USB disconnect, address 1 hub 2-0:1.0: hub_port_status failed (err = -19) hub 2-0:1.0: connect-debounce failed, port 6 disabled hub 2-0:1.0: cannot disable port 6 (err = -19) ehci_hcd 0000:00:1d.7: USB bus 2 deregistered ACPI: PCI interrupt for device 0000:00:1d.7 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled hub 4-0:1.0: connect-debounce failed, port 2 disabled after pressing FN+ESC twice ( disable & reenable bluetooth ) dmesg reports: hub 4-0:1.0: connect-debounce failed, port 2 disabled usb 4-2: new full speed USB device using uhci_hcd and address 2 usb 4-2: new device found, idVendor=0a12, idProduct=0001 usb 4-2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 4-2: configuration #1 chosen from 1 choice Bluetooth: HCI USB driver ver 2.9 usbcore: registered new driver hci_usb The connect-debounce is gone from here on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #6 from oneukum@novell.com 2007-01-23 07:06 MST ------- OK, this makes it very unlikely that a bug in a hcd driver is responsible. It seems that your hardware needs a workaround. Can you deal with a kernel patch if I send you a patch to increase debounce timeouts? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #7 from casualprogrammer@yahoo.com 2007-01-23 08:04 MST ------- Not really done it, if you tell me step by step what needs to be done, I will give it a try. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #8 from oneukum@novell.com 2007-01-31 00:45 MST ------- Hi, I've made a kernel rpm with increased timeouts. This should help determine the cause of the problem. Could you provide the dmesg with that kernel? It is available under: http://beta.suse.com/private/gregkh/10.2-oneukum/kernel-bigsmp-2.6.18.5-2.i5... Regards Oliver -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #9 from casualprogrammer@yahoo.com 2007-01-31 01:11 MST ------- Created an attachment (id=116450) --> (https://bugzilla.novell.com/attachment.cgi?id=116450&action=view) dmesg of test kernel 200701310911 That was easy :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #10 from oneukum@novell.com 2007-01-31 02:08 MST ------- OK, the problem persists. Just for the record, switching the bluetooth device off and on still fixes it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #11 from casualprogrammer@yahoo.com 2007-01-31 03:02 MST ------- Created an attachment (id=116468) --> (https://bugzilla.novell.com/attachment.cgi?id=116468&action=view) Boot with BT OFF, then switch on and, after a while, off again This is the dmesg after booting into the test kernel with bluetooth disabled. After logging in bluetooth is switched on, then off again. The problem does not show up at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #12 from casualprogrammer@yahoo.com 2007-01-31 03:08 MST ------- Created an attachment (id=116470) --> (https://bugzilla.novell.com/attachment.cgi?id=116470&action=view) Boot with BT ON, then switched OFF and ON again This is the dmesg after booting into the test kernel with bluetooth enabled. After logging in bluetooth is disabled and reenabled. The problem appears and, after BT is recognized once disappers for good. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #13 from oneukum@novell.com 2007-01-31 07:25 MST ------- Hi, could you try this kernel and provide the dmesg: http://beta.suse.com/private/oneukum/kernel-bigsmp-2.6.18.5-2.i586.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #14 from casualprogrammer@yahoo.com 2007-01-31 07:49 MST ------- Can you actuall apply your change to kernel-bigsmp-2.6.20_rc6-2 ? I just did a system update to 10.3 factory for other reasons. The system will not let me install an older kernel :-( If not, I will test your kernel when I'm through with checking out factory. WORKSTATION6L:/home/cjp/Downloads/kernel # rpm -ivh kernel-bigsmp-2.6.18.5-2.i586.rpm Preparing... ########################################### [100%] package kernel-bigsmp-2.6.20_rc6-2 (which is newer than kernel-bigsmp-2.6.18.5-2) is already installed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #15 from casualprogrammer@yahoo.com 2007-01-31 18:38 MST ------- Created an attachment (id=116723) --> (https://bugzilla.novell.com/attachment.cgi?id=116723&action=view) dmesg of test kernel boot with BT ON, then OFF and ON Booting to test kernel with BT off, after log in BT on, then off again. Wait for ca 3 min before dmesg. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #16 from casualprogrammer@yahoo.com 2007-01-31 18:40 MST ------- Created an attachment (id=116724) --> (https://bugzilla.novell.com/attachment.cgi?id=116724&action=view) dmesg of test kernel boot with BT OFF, then ON and OFF again Boot to test kernel with BT off, after login switched BT on, then off again. Wait for 3 min before dmesg. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #17 from casualprogrammer@yahoo.com 2007-01-31 18:43 MST ------- Done -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #18 from oneukum@novell.com 2007-02-02 01:56 MST ------- Could you please boot with acpi=off and provide the logs? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #19 from casualprogrammer@yahoo.com 2007-02-02 03:41 MST ------- Created an attachment (id=117022) --> (https://bugzilla.novell.com/attachment.cgi?id=117022&action=view) boot to test kernel with acpi=off, BT=on, then off and on again Booting to test kernel with acpi=off, BT switched on, after log in switched BT off, then on again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #20 from casualprogrammer@yahoo.com 2007-02-02 03:43 MST ------- Created an attachment (id=117023) --> (https://bugzilla.novell.com/attachment.cgi?id=117023&action=view) boot to test kernel with acpi=off, Wireless off, then on and BT off After switching BT off, the kernel would not reboot, but hang at udev. Therefore switched wireless off completely, after log in switched wireless on, then BT off and on again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #21 from casualprogrammer@yahoo.com 2007-02-02 03:45 MST ------- Created an attachment (id=117025) --> (https://bugzilla.novell.com/attachment.cgi?id=117025&action=view) boot to test kernel with acpi=off, BT=off, then on and off again After several attempts kernel would finally boot with wireless on, BT off. After login switched BT on, then off again -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #22 from oneukum@novell.com 2007-02-02 05:31 MST ------- Without disabling ACPI can you boot in these configuration without problems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #23 from casualprogrammer@yahoo.com 2007-02-02 08:33 MST ------- Yes, I can. With acpi=off only for the BT=OFF situation there seemed to be a huge delay / hang at udev. With BT=ON or Wireless=OFF altogether there did not seem to be a delay. I have saved the dmesg output, but they don't really look different. If you think they are useful, I can still upload. They are the same as the two before acpi=off. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #24 from oneukum@novell.com 2007-02-08 09:39 MST ------- Could you try this kernel? http://beta.suse.com/private/oneukum/kernel-bigsmp-2.6.18.5-0.17.i586.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #25 from casualprogrammer@yahoo.com 2007-02-08 16:49 MST ------- Of course I could, only I switched to factory 10.3 for good now, as I am told that this issue "https://bugzilla.novell.com/show_bug.cgi?id=239707" is not going to be solved in 10.2. As 2.6.20-rc7-2-default shows the same symptoms, I would ask you to apply your modifications to that, if it's not putting undue load on you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #26 from oneukum@novell.com 2007-02-09 06:21 MST ------- Very well: http://beta.suse.com/private/oneukum/236774/kernel-bigsmp-2.6.20-0.19.i586.r... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | ------- Comment #27 from casualprogrammer@yahoo.com 2007-02-09 15:15 MST ------- Created an attachment (id=118435) --> (https://bugzilla.novell.com/attachment.cgi?id=118435&action=view) screenshot of bootscreen :-( Booting stops 2 lines after ACPI, see attached screenshot. No matter whether BT is ON or OFF -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #28 from oneukum@novell.com 2007-02-12 01:12 MST ------- This looks like 'init' is hanging. Can you try adding init=/bin/sh to your kernel command line? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #29 from casualprogrammer@yahoo.com 2007-02-12 04:16 MST ------- Created an attachment (id=118568) --> (https://bugzilla.novell.com/attachment.cgi?id=118568&action=view) Screenshot of bootscreen after booting with init=/bin/sh There is not much change, only one line concerning time service is left out :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #30 from oneukum@novell.com 2007-02-19 04:31 MST ------- I am afraid I cannot help you with bugs in the HEAD branch unless you cannot reproduce the hang without the patch I sent you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #31 from casualprogrammer@yahoo.com 2007-02-19 08:00 MST ------- "I am afraid I cannot help you with bugs in the HEAD branch unless you cannot reproduce the hang without the patch I sent you." Now how do I interpret this ? First of all I am helping you getting bugs fixed, second I can not make any sense of "unless you cannot reproduce the hang without the patch I sent you", third I was not addressing a "hang" but the fact that openSuSE, as well as other distro's ( google fo "connect-debounce failed" ) is not capable of suppressing excessive error handling that blocks the system. I think it should be possible, to determine in the sources where and how this message is generated and just to disable it if it is repeated excessively without apparent cause. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #32 from oneukum@novell.com 2007-02-20 01:45 MST ------- I am perfectly willing to fix this bug, if I can get enough debugging output, as I cannot reproduce it myself. The problem is that we, the kernel developers, cannot fix every issue with the head branch of the kernel, which is under active development. I can send you rpms against a supported product. I can send you rpms against an unsupported product. However, if the latter don't boot, there's not much I can do. If you want to I can send you an rpm and a patch that will surpress the error message without fixing the cause. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #33 from casualprogrammer@yahoo.com 2007-02-20 05:34 MST ------- Well thanks fo the offer, Oliver, I think that won't be really helpful for me, as it will be removed by the next update again. Also I personally know now how to handle it ( just switch BT OFF and ON again ) to get around it. If you or anybody upstream needs a hand with this you are welcome to have me do further testing of the situation and supply you with the resulting information. Casual -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #34 from oneukum@novell.com 2007-02-26 03:27 MST ------- (Sorry for the late answer, flu) No, you are right that such a patch would be an improvement to the current situation. Only a slight improvement, but an improvement. I'd push it for mainline. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #35 from casualprogrammer@yahoo.com 2007-02-26 08:47 MST ------- "I'd push it for mainline." You will or you would ? Do I need to do anything so far ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #36 from oneukum@novell.com 2007-02-27 02:26 MST ------- Created an attachment (id=121228) --> (https://bugzilla.novell.com/attachment.cgi?id=121228&action=view) limit the rate of debounce error messages -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #37 from oneukum@novell.com 2007-02-27 02:28 MST ------- I have pushed it to mainline. I am not sure how to test this though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #38 from casualprogrammer@yahoo.com 2007-03-15 11:56 MST ------- I can always assist, as I can reproduce the problem at will. Also: Since I now know how to integrate patches into kernel, you may as well publish your suggested patch here and I can give it another shot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #39 from oneukum@novell.com 2007-03-16 01:52 MST ------- I did. Comment #36 has the patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #40 from casualprogrammer@yahoo.com 2007-03-16 03:29 MST ------- OK, I see, that just escaped my attention, as it does not expressly say I am your patch. Sorry. I will give it a try, but without priority, so this could take a few days. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #41 from casualprogrammer@yahoo.com 2007-03-16 10:05 MST ------- Created an attachment (id=125073) --> (https://bugzilla.novell.com/attachment.cgi?id=125073&action=view) tail -f /var/log/messges | tee messages.tail.txt from kernel 2.6.20.2-2-usb_debug_debounce I couldn't resist. So here is a tail of dmesg from booting to pressing BT=OFF then ON again after login. In addition to your patch, I doubled the values for #define HUB_DEBOUNCE_TIMEOUT 3000 /* was 1500 */ #define HUB_DEBOUNCE_STEP 50 /* was 25 */ #define HUB_DEBOUNCE_STABLE 500 /* was 100 */ out of curiosity -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #42 from casualprogrammer@yahoo.com 2007-03-17 05:08 MST ------- Created an attachment (id=125150) --> (https://bugzilla.novell.com/attachment.cgi?id=125150&action=view) dmesg after booting with BT=ON , Kernel 2.6.20.2-2-usb_debug_debounce_oldmethod -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #43 from casualprogrammer@yahoo.com 2007-03-17 05:29 MST ------- Created an attachment (id=125151) --> (https://bugzilla.novell.com/attachment.cgi?id=125151&action=view) dmesg after booting with BT=OFF , Kernel 2.6.20.2-2-usb_debug_debounce_oldmethod Created another kernel with static int old_scheme_first = 1; /* was 0 */ and the prolonged timing, your patch removed. Attachment 125150 is a dmesg after booting to that kernel with BT=ON, logging in, switching BT=OFF then ON again, then dmesg. This attachment is booting to the new kernel with BT=OFF, logging in, switching BT=ON, then dmesg. The second dmesg shows the line ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803 POWER sig=j CSC CONNECT just once, while it keeps recurring in the first one. I don't think it's a power on issue, as power is not touched on a reboot. It's neither ACPI, as I booted with noacpi without any change. My guess is, that there is some timing issue in the boot process, where to many things happen at once. Then, when the polling starts it could be causing the instability of the BT device by the high polling rate, thus prohibiting debounce to take place. ) Probably delaying the start of the USB detection a little, would cure this. ( It would be the same effect as booting with BT=OFF, then switch it to ON after login. ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #44 from oneukum@novell.com 2007-03-19 06:36 MST ------- Created an attachment (id=125257) --> (https://bugzilla.novell.com/attachment.cgi?id=125257&action=view) introduce a 4 second delay into usb startup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |casualprogrammer@yahoo.com ------- Comment #45 from oneukum@novell.com 2007-03-19 06:37 MST -------
My guess is, that there is some timing issue in the boot process, where to many things happen at once. Then, when the polling starts it could be causing the instability of the BT device by the high polling rate, thus prohibiting debounce to take place. )
It might be. The patch in #44 introduces a delay. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #46 from casualprogrammer@yahoo.com 2007-03-20 04:06 MST ------- Alas this was not it :-( Even raising the delay to 30 secs doesn't help any. But while watching the USB registration unfold, it occurred to me, that it might not be the BT device at all playing tricks on me: dmesg shows: hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x501 hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0100, change 0001, 12 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x100 hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x501 hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x501 hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0100, change 0001, 12 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x100 hub 1-0:1.0: connect-debounce failed, port 6 disabled hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 1500ms stable 0ms status 0x100 hub 1-0:1.0: connect-debounce failed, port 6 disabled For whatever reason different speeds are signaled ( 480Mb/s and 12Mb/s ), and finally when disabling and reenabling BT: atkbd.c: Unknown key pressed (translated set 2, code 0xe2 on isa0060/serio0). atkbd.c: Use 'setkeycodes e062 <keycode>' to make it known. hub 1-0:1.0: debounce: port 6: total 775ms stable 100ms status 0x100 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s atkbd.c: Unknown key released (translated set 2, code 0xe2 on isa0060/serio0). atkbd.c: Use 'setkeycodes e062 <keycode>' to make it known. atkbd.c: Unknown key pressed (translated set 2, code 0xe2 on isa0060/serio0). atkbd.c: Use 'setkeycodes e062 <keycode>' to make it known. atkbd.c: Unknown key released (translated set 2, code 0xe2 on isa0060/serio0). atkbd.c: Use 'setkeycodes e062 <keycode>' to make it known. Then USB signals: hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 100ms stable 100ms status 0x501 hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004 hub 4-0:1.0: port 2, status 0101, change 0001, 12 Mb/s hub 4-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 usb 4-2: new full speed USB device using uhci_hcd and address 2 usb 4-2: new device found, idVendor=0a12, idProduct=0001 usb 4-2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 4-2: uevent usb 4-2: usb_probe_device usb 4-2: configuration #1 chosen from 1 choice usb 4-2: adding 4-2:1.0 (config #1, interface 0) usb 4-2:1.0: uevent usbserial_generic 4-2:1.0: usb_probe_interface usbserial_generic 4-2:1.0: usb_probe_interface - got id usb 4-2: adding 4-2:1.1 (config #1, interface 1) usb 4-2:1.1: uevent usbserial_generic 4-2:1.1: usb_probe_interface usbserial_generic 4-2:1.1: usb_probe_interface - got id drivers/usb/core/inode.c: creating file '002' hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004 Bluetooth: HCI USB driver ver 2.9 hci_usb 4-2:1.0: usb_probe_interface hci_usb 4-2:1.0: usb_probe_interface - got id usbdev4.2_ep03: ep_device_release called for usbdev4.2_ep03 usbdev4.2_ep83: ep_device_release called for usbdev4.2_ep83 usbcore: registered new interface driver hci_usb What I overlooked so far was the part: hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0040 hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 6: total 100ms stable 100ms status 0x501 hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004 hub 4-0:1.0: port 2, status 0101, change 0001, 12 Mb/s hub 4-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 The BT device is shown as being registered on port 2, so what is on port 6 ? Puzzled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #47 from oneukum@novell.com 2007-03-20 04:38 MST ------- You are seeing the handover to the low speed controller. Or is your BT 480MB/s? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #48 from casualprogrammer@yahoo.com 2007-03-21 08:00 MST ------- "Or is your BT 480MB/s?" How could I know ? These days all devices seem to come as usb2.0, there is nothing in the documentation. Would "handover" also explain the change from port6 to port 2 ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #49 from oneukum@novell.com 2007-03-22 03:15 MST -------
"Or is your BT 480MB/s?" How could I know ? "lsusb -t" can show you which controller it is attached to
These days all devices seem to come as usb2.0, The lower speeds are part of USB2.0, too. It should have a "HI-SPEED" logo.
Would "handover" also explain the change from port6 to port 2 ? OHCI/UHCI and EHCI have independant root hubs. Usually a computer has several lower speed controllers and one high speed controller. The port numbers cannot match.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 ------- Comment #50 from casualprogrammer@yahoo.com 2007-03-22 03:29 MST ------- lsusb -t shows: :~> lsusb -t Bus# 5 `-Dev# 1 Vendor 0x0000 Product 0x0000 Bus# 4 `-Dev# 1 Vendor 0x0000 Product 0x0000 Bus# 3 `-Dev# 1 Vendor 0x0000 Product 0x0000 `-Dev# 2 Vendor 0x0a12 Product 0x0001 Bus# 2 `-Dev# 1 Vendor 0x0000 Product 0x0000 |-Dev# 4 Vendor 0x045e Product 0x007d `-Dev# 5 Vendor 0x03eb Product 0x3301 |-Dev# 6 Vendor 0x04a9 Product 0x1093 `-Dev# 7 Vendor 0x067b Product 0x2303 Bus# 1 `-Dev# 1 Vendor 0x0000 Product 0x0000 This does not give me any clue, though, all I know is that this: `-Dev# 2 Vendor 0x0a12 Product 0x0001 must be the BT device. What I still fail to see, is, if the BT device is on port 2 ( see https://bugzilla.novell.com/show_bug.cgi?id=236774#c46 bottom ), why has port 6 the need to be debounced ? If there's nothing there, no wonder the debounce fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=236774 oneukum@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #51 from oneukum@novell.com 2007-04-23 01:44 MST ------- This is unsolvavble. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com