* btusb not working in 2.6.38.4
@ 2011-04-27 23:22 Andrej Podzimek
2011-04-28 5:11 ` Gustavo F. Padovan
0 siblings, 1 reply; 4+ messages in thread
From: Andrej Podzimek @ 2011-04-27 23:22 UTC (permalink / raw)
To: linux-bluetooth
[-- Attachment #1.1: Type: text/plain, Size: 2298 bytes --]
Hello,
after a recent kernel update on Arch Linux (2.6.38.4), I can see the following problem in dmesg:
------------[ cut here ]------------
WARNING: at lib/kobject.c:595 kobject_put+0x40/0x50()
Hardware name: To Be Filled By O.E.M.
kobject: '(null)' (ffff88023f60d5a0): is not initialized, yet kobject_put() is being called.
Modules linked in: btusb(+) bluetooth rfkill usbhid hid button i2c_i801 i2c_core r8169 mii iTCO_wdt iTCO_vendor_support psmouse sg serio_raw evdev pcspkr ip_tables ip6_tables x_tables tpm_tis tpm tpm_bios w83627ehf hwmon_vid coretemp ext4 mbcache jbd2 crc16 dm_mod usb_storage raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx md_mod uhci_hcd xhci_hcd ehci_hcd usbcore sd_mod crc_t10dif ahci libahci libata scsi_mod cpufreq_ondemand acpi_cpufreq freq_table processor mperf i7core_edac edac_core
Pid: 1820, comm: modprobe Not tainted 2.6.38-ARCH #1
Call Trace:
[<ffffffff8103a86b>] ? warn_slowpath_common+0x7b/0xc0
[<ffffffff8103a965>] ? warn_slowpath_fmt+0x45/0x50
[<ffffffff81248d3f>] ? skb_dequeue+0x5f/0x80
[<ffffffff8116b6f0>] ? kobject_put+0x40/0x50
[<ffffffffa025f85c>] ? btusb_probe+0x57c/0x5e0 [btusb]
[<ffffffffa00b85d5>] ? usb_probe_interface+0xe5/0x1e0 [usbcore]
[<ffffffff81215aaf>] ? driver_probe_device+0x6f/0x190
[<ffffffff81215c63>] ? __driver_attach+0x93/0xa0
[<ffffffff81215bd0>] ? __driver_attach+0x0/0xa0
[<ffffffff81214b23>] ? bus_for_each_dev+0x53/0x80
[<ffffffff812153f8>] ? bus_add_driver+0x188/0x260
[<ffffffff81215e3a>] ? driver_register+0x6a/0x130
[<ffffffffa00b748a>] ? usb_register_driver+0x8a/0x180 [usbcore]
[<ffffffffa011c000>] ? btusb_init+0x0/0x1000 [btusb]
[<ffffffff810001dc>] ? do_one_initcall+0x3c/0x170
[<ffffffff8106db3a>] ? sys_init_module+0xda/0x230
[<ffffffff8100243b>] ? system_call_fastpath+0x16/0x1b
---[ end trace 9c4648061ddb0b67 ]---
Presumably, Bluetooth does not seem to work at all (i.e., hciconfig -a does not output anything).
The output from lsusb -v relevant to the specific device is attached.
The device worked 100% flawlessly with 2.6.38.3. I had an a2dp headset and a mouse paired with it, both of which worked perfectly fine in parallel.
If you need further debugging info, please let me know.
Andrej
[-- Attachment #1.2: lsusb-v --]
[-- Type: text/plain, Size: 10978 bytes --]
Bus 003 Device 006: ID 0a5c:2198 Broadcom Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x2198
bcdDevice 3.91
iManufacturer 1 Broadcom Corp
iProduct 2 Broadcom Bluetooth 3.0 Device
iSerial 3 000272AE4653
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 216
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 7
bDescriptorType 33
bmAttributes 7
Will Not Detach
Manifestation Tolerant
Upload Supported
Download Supported
wDetachTimeout 5000 milliseconds
wTransferSize 64 bytes
Device Status: 0x0000
(Bus Powered)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: btusb not working in 2.6.38.4
2011-04-27 23:22 btusb not working in 2.6.38.4 Andrej Podzimek
@ 2011-04-28 5:11 ` Gustavo F. Padovan
2011-04-28 13:21 ` Greg KH
2011-05-07 16:50 ` Andrej Podzimek
0 siblings, 2 replies; 4+ messages in thread
From: Gustavo F. Padovan @ 2011-04-28 5:11 UTC (permalink / raw)
To: Andrej Podzimek; +Cc: linux-bluetooth, stable, greg
Hi Andrej,
* Andrej Podzimek <andrej@podzimek.org> [2011-04-28 01:22:02 +0200]:
> Hello,
>
> after a recent kernel update on Arch Linux (2.6.38.4), I can see the following problem in dmesg:
>
> ------------[ cut here ]------------
> WARNING: at lib/kobject.c:595 kobject_put+0x40/0x50()
> Hardware name: To Be Filled By O.E.M.
> kobject: '(null)' (ffff88023f60d5a0): is not initialized, yet kobject_put() is being called.
> Modules linked in: btusb(+) bluetooth rfkill usbhid hid button i2c_i801 i2c_core r8169 mii iTCO_wdt iTCO_vendor_support psmouse sg serio_raw evdev pcspkr ip_tables ip6_tables x_tables tpm_tis tpm tpm_bios w83627ehf hwmon_vid coretemp ext4 mbcache jbd2 crc16 dm_mod usb_storage raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx md_mod uhci_hcd xhci_hcd ehci_hcd usbcore sd_mod crc_t10dif ahci libahci libata scsi_mod cpufreq_ondemand acpi_cpufreq freq_table processor mperf i7core_edac edac_core
> Pid: 1820, comm: modprobe Not tainted 2.6.38-ARCH #1
> Call Trace:
> [<ffffffff8103a86b>] ? warn_slowpath_common+0x7b/0xc0
> [<ffffffff8103a965>] ? warn_slowpath_fmt+0x45/0x50
> [<ffffffff81248d3f>] ? skb_dequeue+0x5f/0x80
> [<ffffffff8116b6f0>] ? kobject_put+0x40/0x50
> [<ffffffffa025f85c>] ? btusb_probe+0x57c/0x5e0 [btusb]
> [<ffffffffa00b85d5>] ? usb_probe_interface+0xe5/0x1e0 [usbcore]
> [<ffffffff81215aaf>] ? driver_probe_device+0x6f/0x190
> [<ffffffff81215c63>] ? __driver_attach+0x93/0xa0
> [<ffffffff81215bd0>] ? __driver_attach+0x0/0xa0
> [<ffffffff81214b23>] ? bus_for_each_dev+0x53/0x80
> [<ffffffff812153f8>] ? bus_add_driver+0x188/0x260
> [<ffffffff81215e3a>] ? driver_register+0x6a/0x130
> [<ffffffffa00b748a>] ? usb_register_driver+0x8a/0x180 [usbcore]
> [<ffffffffa011c000>] ? btusb_init+0x0/0x1000 [btusb]
> [<ffffffff810001dc>] ? do_one_initcall+0x3c/0x170
> [<ffffffff8106db3a>] ? sys_init_module+0xda/0x230
> [<ffffffff8100243b>] ? system_call_fastpath+0x16/0x1b
> ---[ end trace 9c4648061ddb0b67 ]---
>
> Presumably, Bluetooth does not seem to work at all (i.e., hciconfig -a does not output anything).
>
> The output from lsusb -v relevant to the specific device is attached.
>
> The device worked 100% flawlessly with 2.6.38.3. I had an a2dp headset and a mouse paired with it, both of which worked perfectly fine in parallel.
The only Bluetooth change in 2.6.38.4 is: https://lkml.org/lkml/2011/4/19/406
However I don't think this patch is causing this issue. Do you care to patch -R it
and test?
If the problem is somewhere else we have to go with a bisect, there are only
70 patches, so it shouldn't take to long.
Greg, any idea on that? Are there similar reports of warnings for 2.6.38.4?
--
Gustavo F. Padovan
http://profusion.mobi
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: btusb not working in 2.6.38.4
2011-04-28 5:11 ` Gustavo F. Padovan
@ 2011-04-28 13:21 ` Greg KH
2011-05-07 16:50 ` Andrej Podzimek
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2011-04-28 13:21 UTC (permalink / raw)
To: Andrej Podzimek, linux-bluetooth, stable
On Thu, Apr 28, 2011 at 02:11:24AM -0300, Gustavo F. Padovan wrote:
> Hi Andrej,
>
> * Andrej Podzimek <andrej@podzimek.org> [2011-04-28 01:22:02 +0200]:
>
> > Hello,
> >
> > after a recent kernel update on Arch Linux (2.6.38.4), I can see the following problem in dmesg:
> >
> > ------------[ cut here ]------------
> > WARNING: at lib/kobject.c:595 kobject_put+0x40/0x50()
> > Hardware name: To Be Filled By O.E.M.
> > kobject: '(null)' (ffff88023f60d5a0): is not initialized, yet kobject_put() is being called.
> > Modules linked in: btusb(+) bluetooth rfkill usbhid hid button i2c_i801 i2c_core r8169 mii iTCO_wdt iTCO_vendor_support psmouse sg serio_raw evdev pcspkr ip_tables ip6_tables x_tables tpm_tis tpm tpm_bios w83627ehf hwmon_vid coretemp ext4 mbcache jbd2 crc16 dm_mod usb_storage raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx md_mod uhci_hcd xhci_hcd ehci_hcd usbcore sd_mod crc_t10dif ahci libahci libata scsi_mod cpufreq_ondemand acpi_cpufreq freq_table processor mperf i7core_edac edac_core
> > Pid: 1820, comm: modprobe Not tainted 2.6.38-ARCH #1
> > Call Trace:
> > [<ffffffff8103a86b>] ? warn_slowpath_common+0x7b/0xc0
> > [<ffffffff8103a965>] ? warn_slowpath_fmt+0x45/0x50
> > [<ffffffff81248d3f>] ? skb_dequeue+0x5f/0x80
> > [<ffffffff8116b6f0>] ? kobject_put+0x40/0x50
> > [<ffffffffa025f85c>] ? btusb_probe+0x57c/0x5e0 [btusb]
> > [<ffffffffa00b85d5>] ? usb_probe_interface+0xe5/0x1e0 [usbcore]
> > [<ffffffff81215aaf>] ? driver_probe_device+0x6f/0x190
> > [<ffffffff81215c63>] ? __driver_attach+0x93/0xa0
> > [<ffffffff81215bd0>] ? __driver_attach+0x0/0xa0
> > [<ffffffff81214b23>] ? bus_for_each_dev+0x53/0x80
> > [<ffffffff812153f8>] ? bus_add_driver+0x188/0x260
> > [<ffffffff81215e3a>] ? driver_register+0x6a/0x130
> > [<ffffffffa00b748a>] ? usb_register_driver+0x8a/0x180 [usbcore]
> > [<ffffffffa011c000>] ? btusb_init+0x0/0x1000 [btusb]
> > [<ffffffff810001dc>] ? do_one_initcall+0x3c/0x170
> > [<ffffffff8106db3a>] ? sys_init_module+0xda/0x230
> > [<ffffffff8100243b>] ? system_call_fastpath+0x16/0x1b
> > ---[ end trace 9c4648061ddb0b67 ]---
> >
> > Presumably, Bluetooth does not seem to work at all (i.e., hciconfig -a does not output anything).
> >
> > The output from lsusb -v relevant to the specific device is attached.
> >
> > The device worked 100% flawlessly with 2.6.38.3. I had an a2dp headset and a mouse paired with it, both of which worked perfectly fine in parallel.
>
> The only Bluetooth change in 2.6.38.4 is: https://lkml.org/lkml/2011/4/19/406
> However I don't think this patch is causing this issue. Do you care to patch -R it
> and test?
> If the problem is somewhere else we have to go with a bisect, there are only
> 70 patches, so it shouldn't take to long.
>
> Greg, any idea on that? Are there similar reports of warnings for 2.6.38.4?
No, I have not seen any reported warnings like this. A 'git bisect'
should be quick to do to find the offending patch.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: btusb not working in 2.6.38.4
2011-04-28 5:11 ` Gustavo F. Padovan
2011-04-28 13:21 ` Greg KH
@ 2011-05-07 16:50 ` Andrej Podzimek
1 sibling, 0 replies; 4+ messages in thread
From: Andrej Podzimek @ 2011-05-07 16:50 UTC (permalink / raw)
To: linux-bluetooth, stable, greg
[-- Attachment #1: Type: text/plain, Size: 3379 bytes --]
> Hi Andrej,
>
> * Andrej Podzimek<andrej@podzimek.org> [2011-04-28 01:22:02 +0200]:
>
>> Hello,
>>
>> after a recent kernel update on Arch Linux (2.6.38.4), I can see the following problem in dmesg:
>>
>> ------------[ cut here ]------------
>> WARNING: at lib/kobject.c:595 kobject_put+0x40/0x50()
>> Hardware name: To Be Filled By O.E.M.
>> kobject: '(null)' (ffff88023f60d5a0): is not initialized, yet kobject_put() is being called.
>> Modules linked in: btusb(+) bluetooth rfkill usbhid hid button i2c_i801 i2c_core r8169 mii iTCO_wdt iTCO_vendor_support psmouse sg serio_raw evdev pcspkr ip_tables ip6_tables x_tables tpm_tis tpm tpm_bios w83627ehf hwmon_vid coretemp ext4 mbcache jbd2 crc16 dm_mod usb_storage raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx md_mod uhci_hcd xhci_hcd ehci_hcd usbcore sd_mod crc_t10dif ahci libahci libata scsi_mod cpufreq_ondemand acpi_cpufreq freq_table processor mperf i7core_edac edac_core
>> Pid: 1820, comm: modprobe Not tainted 2.6.38-ARCH #1
>> Call Trace:
>> [<ffffffff8103a86b>] ? warn_slowpath_common+0x7b/0xc0
>> [<ffffffff8103a965>] ? warn_slowpath_fmt+0x45/0x50
>> [<ffffffff81248d3f>] ? skb_dequeue+0x5f/0x80
>> [<ffffffff8116b6f0>] ? kobject_put+0x40/0x50
>> [<ffffffffa025f85c>] ? btusb_probe+0x57c/0x5e0 [btusb]
>> [<ffffffffa00b85d5>] ? usb_probe_interface+0xe5/0x1e0 [usbcore]
>> [<ffffffff81215aaf>] ? driver_probe_device+0x6f/0x190
>> [<ffffffff81215c63>] ? __driver_attach+0x93/0xa0
>> [<ffffffff81215bd0>] ? __driver_attach+0x0/0xa0
>> [<ffffffff81214b23>] ? bus_for_each_dev+0x53/0x80
>> [<ffffffff812153f8>] ? bus_add_driver+0x188/0x260
>> [<ffffffff81215e3a>] ? driver_register+0x6a/0x130
>> [<ffffffffa00b748a>] ? usb_register_driver+0x8a/0x180 [usbcore]
>> [<ffffffffa011c000>] ? btusb_init+0x0/0x1000 [btusb]
>> [<ffffffff810001dc>] ? do_one_initcall+0x3c/0x170
>> [<ffffffff8106db3a>] ? sys_init_module+0xda/0x230
>> [<ffffffff8100243b>] ? system_call_fastpath+0x16/0x1b
>> ---[ end trace 9c4648061ddb0b67 ]---
>>
>> Presumably, Bluetooth does not seem to work at all (i.e., hciconfig -a does not output anything).
>>
>> The output from lsusb -v relevant to the specific device is attached.
>>
>> The device worked 100% flawlessly with 2.6.38.3. I had an a2dp headset and a mouse paired with it, both of which worked perfectly fine in parallel.
>
> The only Bluetooth change in 2.6.38.4 is: https://lkml.org/lkml/2011/4/19/406
> However I don't think this patch is causing this issue. Do you care to patch -R it
> and test?
> If the problem is somewhere else we have to go with a bisect, there are only
> 70 patches, so it shouldn't take to long.
>
> Greg, any idea on that? Are there similar reports of warnings for 2.6.38.4?
Hello,
I'm sorry for this false positive. It was just a typical PEBKAC. The machine runs a WiFi access point and requires ath9k from compat-wireless (since the mainline ath9k can do no better than 2 Mb/s in AP mode). I installed compat-wireless as usual, but forgot to run scripts/driver-select. Consequently, all drivers (including Bluetooth, namely btusb) got replaced. So the backtrace was caused by using btusb from compat-wireless (April 26 2011) with kernel 2.6.38.4. The problem does *not* occur in a standard vanilla kernel.
Andrej
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-05-07 16:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-27 23:22 btusb not working in 2.6.38.4 Andrej Podzimek
2011-04-28 5:11 ` Gustavo F. Padovan
2011-04-28 13:21 ` Greg KH
2011-05-07 16:50 ` Andrej Podzimek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).