On Mon, 23 May 2011, Paulo Edgar Castro wrote: > On 23/05/11 15:24, Alan Stern wrote: > > On Mon, 23 May 2011, Paulo Edgar Castro wrote: > > > >> Hello. > >> > >> I'm looking for some help trying to understand an issue. > >> My computer has an internal Bluetooth USB dongle based in the BCM2046 chip. > >> > >> It seems that since kernel v2.6.38 I seem to have lost the capacity of > >> listing the device with lsusb. e.g. everything else shows up but the > >> device which used to show up in prior to v2.6.38 > >> I've grepped and looked for potential occurrences of bcm2046 in the > >> kernel codebase with no success. > >> > >> It seems that the kernel can no longer list/understand this device... is > >> this a correct assumption ? > >> > >> Am I missing enabling some obscure config option to enable this? > >> Where would you suggest I try to look to understand hat's going on? > >> > >> I'm attaching the output of "lsusb -s 003:002 -v" from when my kernel > >> could see the device.. > > For better debugging, you should build a 2.6.38 kernel with > > CONFIG_USB_DEBUG enabled and then post the dmesg log showing what > > happens during bootup. > Yes I already have that enabled all the other DEBUG switches where they > might apply > > You might also try using 2.6.39 to see if that makes any difference. > I failed to mention this but I already did that and the issue is still > present. > > Alan Stern > Later tonight I'll try booting both the working kernel and the bad one > with extra acpi debug options ( acpi.debug_layer=0x2 > acpi.debug_level=0xffffffff ) following a tip from Oliver Neukum. > > It's very possible that given my level of ignorance I might be missing > something obvious here... > Any other debugging suggestions ? > > I'm attaching the boot log against a 2.6.39 . There aren't any obvious problems. Can you post an equivalent log from 2.6.37 where the Bluetooth device does show up, so that we can compare the differences? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
