[05:53] <mase_work> hey guys, was wondering if I could get some clarification on a bug report  (i'm not even sure i'm asking in the right channel ) .https://bugs.launchpad.net/ubuntu/+source/linux/+bug/245779 . It says the kernel team has been unsubscribed from this report, which is cool but it doesn't really have a resolution. Does this mean that there will be no fix in 8.04 or does it mean this has been sent off to some other place where it goes in
[05:53] <mase_work> with the rest of the reports ?
[05:53] <ubot3> Malone bug 245779 in linux "Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0" [High,Confirmed] 
[21:57] <pwnguin> so here's an odd report
[21:57] <pwnguin> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/156133
[21:58] <ubot3> Malone bug 156133 in linux-firmware "bluez suite lacks bluez-firmware package" [Undecided,Incomplete] 
[21:58] <pwnguin> a user is reporting that 
[21:58] <pwnguin> # ln -s bcm2033-fw.bin BCM2033-FW.bin
[21:58] <pwnguin> # ln -s bcm2033-fw.bin BCM2033-FW.bin
[21:58] <pwnguin> err
[21:59] <pwnguin> a user is reporting that that symlink fixes a bluetooth bug
[21:59] <crimsun> the capitalisation is causing the bug? mmkay.
[21:59] <pwnguin> well
[21:59] <pwnguin> entirely plausible
[22:00] <pwnguin> the driver looks for a given file
[22:00] <pwnguin> loads the file into wherever
[22:01] <pwnguin> ext3 is case sensetive; windows generally is not
[22:02] <crimsun> it's certainly a candidate for silliest source bug ever
[22:02] <pwnguin> na
[22:02] <pwnguin> when i was working with TinyOS, there were a lot of bugs like this
[22:02] <pwnguin> that caused fail to build
[22:02] <crimsun> doesn't make the bugs any less silly
[22:03] <pwnguin> #include "dbg.h"
[22:03] <pwnguin> in absolute terms, but silliest is a relative statement
[22:08] <crimsun> seriously, though, the friggin case is hard-coded into the source :/
[22:10] <pwnguin> heh
[22:10] <pwnguin> i haven't found the code yet
[22:10] <crimsun> line 222, http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=blob;f=drivers/bluetooth/bcm203x.c;h=ee40201c7278ad94aadf43ac220c1cedfd67c49e;hb=HEAD
[22:12] <pwnguin> so, patch the kernel or change the file's case?
[22:15] <crimsun> doesn't really make a difference
[22:16] <pwnguin> well, where does the firmware bin files come from?
[22:16] <crimsun> linux-firmware
[22:16] <pwnguin> thats not what i meant
[22:16] <pwnguin> linux-firmware came from somewhere else
[22:17] <crimsun> i suppose you could contact bluetooth_help@broadcom.com
[22:17] <crimsun> that's what linux-firmware's firmware/broadcom/BCM-LEGAL.txt contains, at least
[22:18] <crimsun> in any case, i have no idea if renaming the files is permitted, though i don't see why not [as the source package is in main, not restricted]
[22:19] <crimsun> it would probably be simpler to perform the renaming in linux-firmware's debian/rules