Kernel Bug Tracker – Bug 9414
Not work light of button-led with module b43 in chipset broadcom 4318
Last modified: 2007-12-20 15:49:32 UTC
Most recent kernel where this bug did not occur: 184.108.40.206
Distribution: Ubuntu Gutsy
Hardware Environment: Compaq Presario V2000
Software Environment: Default + update of kernel
Problem Description: In kernel 220.127.116.11 work with module bcm43xx and work light of led, I update to kernel 2.6.24-rc3 and WiFi work. And light of led not work.
Created attachment 13638 [details]
Created attachment 13639 [details]
Created attachment 13640 [details]
Created attachment 13641 [details]
Created attachment 13642 [details]
Created attachment 13643 [details]
Bunk, the driver work. not-light is detail. Not regression +1.
Of course a non-working driver would be a much more serious regression than a non-working LED, but still a no longer working LED is a regression.
Did someone actually try to hook this led up from userspace?
It's all doable through sysfs led triggers.
I mean, I can not magically fix this bug, as I don't own such a device. Some help is required.
@Michael: How to I help?
Cristian, if 2.6.24-rc4 is still not working for you (most likely), and if you have time to track this down, you could try to figure out the exact commit that causes this regression for you. This is a clear regression, 18.104.22.168 had a working led, 2.6.24-rc does not. So one of the commits inbetween caused this problem for you.
git-bisection can take quite some time though. Here's an link that explains it:
here's a quickstart:
git-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6.git
git-bisect good v2.6.23
git-bisect bad HEAD
then build the kernel that is suggested and boot into it - checking whether the led works fine or not. If the led works then do this:
if the led does not work then do this:
repeat this, then after 10-15 rebuilds and reboots [ ouch! :-/ ] you'll finally arrive to a point where git-bisect outputs a "bad commit" message to you. Paste that result into this bugzilla. (also paste the contents of "git-bisect log" so that we can see your bisection results)
you can then quit bisection via:
and can track the latest upstream kernel by doing "git-pull" in the linux-2.6.git directory.
> git-bisection can take quite some time though. Here's an link that explains it:
here's another link with git-bisect info:
Cristian, any progress?
Created attachment 13947 [details]
The attached patch should fix the radio LED issue. There is still a locking problem to be solved; however, the patch is suitable for testing.
Patch is available: http://marc.info/?l=linux-wireless&m=119763729709783&w=2
Patch (for b43legacy) is available: http://marc.info/?l=linux-wireless&m=119767190601835&w=2
Author: Larry Finger <Larry.Finger@lwfinger.net>
Date: Fri Dec 14 13:59:11 2007 +0100
b43: Fix rfkill radio LED