Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Thu, May 24, 2012 at 05:44:23PM +0300, Touko Korpela wrote: > I don't know if it's regression or not but when I rebooted 3.2.18-1, kernel > oopsed during shutdown (it wasn't logged). I don't remember that happened > before. False alarm, it wasn't kernel oops, it was X server segfault at shutdown bug #671812, fixed by xorg-server 2:1.12.1.902-1 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526105221.GA27110@tiikeri.vuoristo.local
Bug#664767: Brcmsmac driver woes, possible regression?
El 2012-05-22 a las 16:18 -0500, Jonathan Nieder escribió: > Thanks again for your patience. Could you try the attached patch > series against a 3.2.18-based kernel (like the one from kernel.org or > from sid)? (...) Downloaded the sid kernel sources, applied the 23 patches, compiled the whole kernel, generated a deb file and installed but brcmsmac module seems to be missing and whatever I add at the .config file does not resurrect the module. And I don't remember what I did the last time nor if something has changed (again) in this regard O:-) Any hint? What's the magic line to get brcmsmac back in this kernel version? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526142532.ga5...@stt008.linux.site
Bug#664767: Brcmsmac driver woes, possible regression?
On Sat, 2012-05-26 at 16:25 +0200, Camaleón wrote: > El 2012-05-22 a las 16:18 -0500, Jonathan Nieder escribió: > > > Thanks again for your patience. Could you try the attached patch > > series against a 3.2.18-based kernel (like the one from kernel.org or > > from sid)? > > (...) > > Downloaded the sid kernel sources, applied the 23 patches, compiled the > whole kernel, generated a deb file and installed but brcmsmac module > seems to be missing and whatever I add at the .config file does not > resurrect the module. And I don't remember what I did the last time nor > if something has changed (again) in this regard O:-) > > Any hint? What's the magic line to get brcmsmac back in this kernel > version? I wonder whether you really built from the Debian-patched sources (by running debian/bin/test-patches or debian/rules build or similar) or the upstream source. In Linux 3.2 you can enable either CONFIG_BCMA (bcma bus driver, supporting the b43 driver) or CONFIG_BRCMSMAC (brcmsmac driver) but not both. Debian has a patch that resolves this conflict, and they are both enabled. However, if you don't apply that patch then you need to make sure CONFIG_BCMA is disabled before you can enable CONFIG_BRCMSMAC. Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Bug#664767: Brcmsmac driver woes, possible regression?
El 2012-05-26 a las 16:07 +0100, Ben Hutchings escribió: > > Any hint? What's the magic line to get brcmsmac back in this kernel > > version? > > I wonder whether you really built from the Debian-patched sources (by > running debian/bin/test-patches or debian/rules build or similar) or the > upstream source. A mix of that. I got the sources (manually) from Debian repos and proceeded as usual (make menuconfig...). > In Linux 3.2 you can enable either CONFIG_BCMA (bcma bus driver, > supporting the b43 driver) or CONFIG_BRCMSMAC (brcmsmac driver) but not > both. Debian has a patch that resolves this conflict, and they are both > enabled. However, if you don't apply that patch then you need to make > sure CONFIG_BCMA is disabled before you can enable CONFIG_BRCMSMAC. That was it! Disabling bcma showed brcmsmac and now the module is built. Thanks a bunch, I was going nuts with this. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526154227.ga5...@stt008.linux.site
Bug#664767: Brcmsmac driver woes, possible regression?
2012/5/26 Camaleón : > El 2012-05-26 a las 16:07 +0100, Ben Hutchings escribió: >> In Linux 3.2 you can enable either CONFIG_BCMA (bcma bus driver, >> supporting the b43 driver) or CONFIG_BRCMSMAC (brcmsmac driver) but not >> both. Debian has a patch that resolves this conflict, and they are both >> enabled. However, if you don't apply that patch then you need to make >> sure CONFIG_BCMA is disabled before you can enable CONFIG_BRCMSMAC. > > That was it! Disabling bcma showed brcmsmac and now the module is > built. Thanks a bunch, I was going nuts with this. Thanks to Ben's tip now the testing is in place. The patches have been applied and brcmsmac module is loaded. Mmm... I'm attaching a kernel oops I got after having the module loaded, curious is that despite the oops, the wireless link is up and running, no reconnects (which reminds me the first reports...). Will report back for any other update or change in the wireless activity. Greetings, -- Camaleón [18798.704992] brcmsmac :02:00.0: bus 2 slot 0 func 0 irq 10 [18798.705022] brcmsmac :02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [18798.705037] brcmsmac :02:00.0: setting latency timer to 64 [18798.772188] Found chip type AI (0x13814313) [18798.780894] Applying 4313 WARs [18798.782015] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule: [18798.782026] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782036] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule: [18798.782045] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782054] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule: [18798.782063] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782072] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule: [18798.782082] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782090] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule: [18798.782101] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782110] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule: [18798.782120] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782128] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule: [18798.782138] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782146] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule: [18798.782157] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782165] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule: [18798.782175] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782183] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule: [18798.782193] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782202] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule: [18798.782212] cfg80211: 2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [18798.782221] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule: [18798.782231] cfg80211: 2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [18798.782240] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule: [18798.782250] cfg80211: 2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [18798.782259] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule: [18798.782268] cfg80211: 2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [18798.837102] cfg80211: Calling CRDA for country: ES [18798.852520] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule: [18798.852530] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 mBm) [18798.852536] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule: [18798.852543] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 mBm) [18798.852549] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule: [18798.852556] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 mBm) [18798.852562] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule: [18798.852569] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 mBm) [
Bug#674565: Bluetooth activation failed (btusb module)
Hi Jonathan, First, thanks for the reply. On Fri, May 25, 2012 at 11:20 PM, Jonathan Nieder wrote: > # hardware support > severity 674565 important > tags 674565 + upstream patch moreinfo > quit > > Hi Arief, > > Arief M Utama wrote: > > > This is a minor but annoying bug, > > btusb on my HP Envy 15 laptop failed to activate bluetooth, > > since it lacks the appropriate usb_device_id entry. > > > > I would propose adding the entry for more convinience and usability. > > Currently I have to use some commands to activate the bluetooth module > > by adding the ID entry on related sysfs file. > > > > Err, upon examining the code I found that the entry already existed in > > current 3.2 kernel source file (drivers/bluetooth/btusb.c) but looks > > like it is a typo error. > > Thanks. Please attach "lsusb" output. > > If you have time to test the attached patch series following > instructions from [1], that would also be very useful. > > This is the output from lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp. Bus 004 Device 004: ID 064e:e258 Suyin Corp. More details from lsusb output on the bluetooth device attached. I can confirm that patch number 4 [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on my laptop. Haven't tested other patches, although I can report that only patches 1, 4, 6 and 8 that applied successfully. All the best. -arief Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x0a5c Broadcom Corp. idProduct 0x21e1 bcdDevice1.12 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 218 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType
Bug#674565: Bluetooth activation failed (btusb module)
Arief M Utama wrote: > This is the output from lsusb: > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp. > Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp. > Bus 004 Device 004: ID 064e:e258 Suyin Corp. > > More details from lsusb output on the bluetooth device attached. Thanks. > I can confirm that patch number 4 > [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on > my laptop. Haven't tested other patches, although I can report that only > patches 1, 4, 6 and 8 that applied successfully. Ok. What kernel are you applying these to? Could you attach "dmesg" output from the patched kernel? I was hoping to get a quick sanity check that the other patches at least didn't cause the kernel to explode :), but answers to more important questions about them would indeed require info from people with the matching hardware. Will look around and then submit these for inclusion in 3.2.y from kernel.org if they seem to be well tested. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526183526.GA17335@burratino
Processed: Re: Bluetooth activation failed (btusb module)
Processing commands for cont...@bugs.debian.org: > tags 674565 - moreinfo Bug #674565 [linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Removed tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 674565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133805735910992.transcr...@bugs.debian.org
Bug#626427: Horrible Time Skew, Eventual Near-zero Responsiveness
Sabahattin Gucukoglu wrote: > OK. Please understand that I'm a bit busy at the moment, so I can't devote > as much time as I'd like. Thanks and no problem. I don't think there's any need to try the experimental kernel. [...] > I've included all logs since the last report for Linux and ntpd. Hopefully > this is absolutely everything you guys need to work out what/if something's > changed. Sounds like it's still broken. I had missed before that this was a 1999-era board. Lots of those have trouble with ACPI so in that light the symptoms seem less surprising. I suspect the best Linux could do to address this is to automatically disable acpi when appropriate. Thanks again for the logs! I'm keeping this closed because I think you've provided enough information for the interested and the workaround is discoverable enough. Thanks for indulging my curiosity --- I'll see if there's anything for upstream to learn from this. Cheers, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526215440.GC17335@burratino
Processed: Re: Horrible Time Skew, Eventual Near-zero Responsiveness
Processing commands for cont...@bugs.debian.org:
> tags 626427 - moreinfo
Bug #626427 {Done: Jonathan Nieder } [linux-2.6]
linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness
Removed tag(s) moreinfo.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
626427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.13380693076520.transcr...@bugs.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
Hi Camaleón, Camaleón wrote: > Mmm... I'm attaching a kernel oops I got after having the module > loaded, curious is that despite the oops, the wireless link is up and > running, no reconnects (which reminds me the first reports...). Will > report back for any other update or change in the wireless activity. Thanks. I assume you mean the brcms_c_wait_... warning when you refer to an oops. Separating the symptoms: brcms_c_wait_for_tx_completion warning: bug#672891 connection resets, segfaults, general instability: bug#664767 (this bug) "AMPDU status: BA Timeout": bug#674430 Seth wrote[1]: | The trace is related to handling a disconnection, which will also | trigger a reprocessing of the regulatory rules. The warning and the | regulatory message share a common cause, but I don't think there's a | direct relationship between them. I don't think his regulatory series[2] is likely to affect your symptoms, but maybe it will be easier to get help once that has been reviewed and applied upstream. In the meantime, thanks for your updates --- this helps a lot. Regards, Jonathan [1] http://thread.gmane.org/gmane.linux.kernel.wireless.general/87873/focus=87922 [2] http://thread.gmane.org/gmane.linux.kernel.wireless.general/89097 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526225458.GE17335@burratino
Bug#673391: Revised patches for be2net
On Fri, 2012-05-25 at 09:30 -0700, sarveshwar.ba...@emulex.com wrote: > Ben, > I am attaching the revised patches as per your comments. I was not > sure how to handle patches (4 of them) which involved changes to other > drivers too. I intend to open separate bugs for each of them and send > them. Hope that is ok. No, there's no need to open more bugs. > I have also taken care of your comment to not change the return value > in ndo_vlan_rx_[add/kill]_vid > (8e586137e6b63af1e881b328466ab5ffbe562510). The patches also contain > the upstream commit id thanks to your git-format-patch-for-backport > script. Thanks. So the remaining 4 changes are: 68aad78 sweep the floors and convert some .get_drvinfo routines to strlcpy e5686ad netdev: make net_device_ops const It's absolutely fine to apply just the parts of these that affect your driver, as in your original series. 8e58613 net: make vlan ndo_vlan_rx_[add/kill]_vid return error value This should not be applied at all, as we don't want to change the kernel API. 786f528 ethtool: Null-terminate filename passed to ethtool_ops::flash_device I think this is an important bug fix (well I would do :-) so I'll apply it and also propose to David Miller that it goes into stable updates. Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Processed: tagging 673391
Processing commands for cont...@bugs.debian.org: > tags 673391 + pending Bug #673391 [src:linux-2.6] Bug to update be2net driver in Debian 7.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 673391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133807810518691.transcr...@bugs.debian.org
