[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
In order to get wireless stack bug fixes you are going to have to upgrade to a more recent release. ** Changed in: linux-restricted-modules-2.6.15 (Ubuntu Dapper) Status: Confirmed = Won't Fix ** Changed in: linux-restricted-modules-2.6.15 (Ubuntu) Status: Confirmed = Won't Fix -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I'm having a similar problem in Feisty with the Madwifi-ng driver on a TrendNet TEW-443PI Already ran memtest - no problems there. Here's what the kern.log outputs before I have to reboot: Kern.log: Apr 13 22:09:40 Sparta kernel: [ 8413.883195] BUG: soft lockup detected on CPU#1! Apr 13 22:09:40 Sparta kernel: [ 8413.883223] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0 Apr 13 22:09:40 Sparta kernel: [ 8413.883241] [update_process_times+51/128] update_process_times+0x33/0x80 Apr 13 22:09:40 Sparta kernel: [ 8413.883250] [smp_apic_timer_interrupt+112/128] smp_apic_timer_interrupt+0x70/0x80 Apr 13 22:09:40 Sparta kernel: [ 8413.883258] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30 Apr 13 22:09:40 Sparta kernel: [ 8413.883271] [_spin_lock_irqsave+47/80] _spin_lock_irqsave+0x2f/0x50 Apr 13 22:09:40 Sparta kernel: [ 8413.883280] [f89e28f4] ieee80211_free_node+0x24/0x80 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883308] [f89dd6d7] ieee80211_input_all+0x57/0x90 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.88] [f8b21fe1] ath_rx_tasklet+0x751/0x7e0 [ath_pci] Apr 13 22:09:40 Sparta kernel: [ 8413.883353] [tasklet_action+99/224] tasklet_action+0x63/0xe0 Apr 13 22:09:40 Sparta kernel: [ 8413.883362] [__do_softirq+130/256] __do_softirq+0x82/0x100 Apr 13 22:09:40 Sparta kernel: [ 8413.883372] [do_softirq+85/96] do_softirq+0x55/0x60 Apr 13 22:09:40 Sparta kernel: [ 8413.883379] [do_IRQ+69/128] do_IRQ+0x45/0x80 Apr 13 22:09:40 Sparta kernel: [ 8413.883387] [common_interrupt+35/48] common_interrupt+0x23/0x30 Apr 13 22:09:40 Sparta kernel: [ 8413.883399] [f8a2bff0] zz033ebfbf+0xc0/0x148 [ath_hal] Apr 13 22:09:40 Sparta kernel: [ 8413.883414] [f8a3f3b8] zz0b709eff+0x38/0x48 [ath_hal] Apr 13 22:09:40 Sparta kernel: [ 8413.883430] [f8b16b77] ath_txq_update+0x87/0xe0 [ath_pci] Apr 13 22:09:40 Sparta kernel: [ 8413.883449] [f8a2ba46] zz0067d221+0x1a/0x34 [ath_hal] Apr 13 22:09:40 Sparta kernel: [ 8413.883463] [f8b16bef] ath_wme_update+0x1f/0x90 [ath_pci] Apr 13 22:09:40 Sparta kernel: [ 8413.883474] [f89e9ac3] ieee80211_wme_updateparams_locked+0x123/0x210 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883499] [f89ea141] ieee80211_wme_initparams_locked+0x41/0x170 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883524] [f89eb521] ieee80211_wme_initparams+0x21/0x40 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883546] [f89e3a00] ieee80211_sta_join1+0xa0/0x200 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883567] [f89ee1d0] mlmelookup+0x0/0x60 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883589] [f89ee1d0] mlmelookup+0x0/0x60 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883614] [f89eee2f] ieee80211_ioctl_setmlme+0xbf/0x250 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883641] [wireless_process_ioctl+701/992] wireless_process_ioctl+0x2bd/0x3e0 Apr 13 22:09:40 Sparta kernel: [ 8413.883650] [f89eed70] ieee80211_ioctl_setmlme+0x0/0x250 [wlan] Apr 13 22:09:40 Sparta kernel: [ 8413.883673] [sock_ioctl+0/528] sock_ioctl+0x0/0x210 Apr 13 22:09:40 Sparta kernel: [ 8413.883681] [dev_ioctl+531/896] dev_ioctl+0x213/0x380 Apr 13 22:09:40 Sparta kernel: [ 8413.883697] [sock_ioctl+0/528] sock_ioctl+0x0/0x210 Apr 13 22:09:40 Sparta kernel: [ 8413.883704] [do_ioctl+43/144] do_ioctl+0x2b/0x90 Apr 13 22:09:40 Sparta kernel: [ 8413.883712] [vfs_ioctl+92/672] vfs_ioctl+0x5c/0x2a0 Apr 13 22:09:40 Sparta kernel: [ 8413.883719] [sys_ioctl+114/144] sys_ioctl+0x72/0x90 Apr 13 22:09:40 Sparta kernel: [ 8413.883725] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9 Apr 13 22:09:40 Sparta kernel: [ 8413.883741] === Apr 13 22:35:43 Sparta kernel: Inspecting /boot/System.map-2.6.20-16-generic Any ideas? Thanks, -Matt -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
** Changed in: linux-restricted-modules-2.6.15 (Ubuntu Dapper) Importance: Undecided = Critical Status: New = Confirmed ** Changed in: linux-restricted-modules-2.6.17 (Ubuntu Dapper) Status: New = Fix Released -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Hello! First of all let me say I am truly regretting doing this. This is a spam message sent to all critical bug message lists. It's purpose: making this (https://bugs.launchpad.net/ubuntu/+source/acpi- support/+bug/59695) bug critical too. This is a long standing bug and has a very serious impact on laptop type of hardware. It's priority is set to wishlist and I just cannot take this anymore. I DO NOT CARE if my account gets suspended. I am doing what's right for all my friends using Ubuntu on their laptops. -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Hi Mircea Deaconu wrote: making this (https://bugs.launchpad.net/ubuntu/+source/acpi- support/+bug/59695) bug critical too. This is a long standing bug and has a very serious impact on laptop type of hardware. It's priority is This is simply incorrect. I have just commented on the bug to explain why. Please do not spam legitimate bugs. There are proper processes for raising technical issues within Ubuntu. Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
As of Gutsy Gibbon, this bug seems to be fixed for me too. -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
me too, no problems related to madwifi. -- E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) Luca Lorenzetto, http://www.dancetj.net , [EMAIL PROTECTED] -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Is this still an issue in gutsy? Please try with a live cd of the latest (tribe 5) release: http://cdimage.ubuntu.com/releases/gutsy/tribe-5/ -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Erik: this is purely an issue in dapper. It was fixed in edgy because it was fixed in madwifi-ng and not in madwifi. -- [madwifi] Semi-random system lockups in Dapper https://bugs.launchpad.net/bugs/37773 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Mar 27, 2007 at 05:47:22PM -, Ramin Nakisa wrote: It is still broken in Feisty. I did a clean install from the latest ISO, did all the updates. Then it crashed with this error in /var/log/messages: wifi0: hardware error; resetting wifi0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3) Again: This is not the same issue. Could you please open another bug, so we can track them separately? https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+filebug For a start, please attach a complete dmesg and an lspci -vv to the new bug report. Thanks! -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
It is still broken in Feisty. I did a clean install from the latest ISO, did all the updates. Then it crashed with this error in /var/log/messages: wifi0: hardware error; resetting wifi0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3) -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Sun, Mar 25, 2007 at 09:43:04PM -, Ramin Nakisa wrote: Could you please test if it's fixed in Feisty? How do I upgrade to Feisty before the official release? I don't suppose it could be more unstable than my current Ubuntu install! https://help.ubuntu.com/community/FeistyUpgrades This sounds very similar to the previous problem (X40, exactly the same network card) so how do you know it's a different issue? Because the issue in this bug report has to do with broken locking in the madwifi-old driver. Since Edgy (and Feisty) use madwifi-ng, where this particular bug is fixed, and you're running edgy, it must be a different issue. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
This is still broken in 2.6.17. I get random lockups in Edgy. I've got an atheros card, so lspci -n gives 168c:0013. When I boot I get an error: ERROR Resource Conflict - PCI Network Controller in slot 01 Bus:02, Device:02, Function:00 Before it hangs /var/log/messages contains this error: Mar 25 17:51:37 localhost kernel: [17184040.904000] wifi0: hardware error; reseting Mar 25 17:51:38 localhost kernel: [17184041.564000] wifi0: ath_chan_set: unable to reset channel 7 (2442Mhz) flags 0xc0 'Hardware didn't respond as expected' (HAL status 3) The kernel version is 2.6.17-11-386 (version #2). My laptop is almost unusable. It works for a while then randomly hangs. Perhaps you can fix this before we get Feisty? This has been dragging on for so long without a fix. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Sun, Mar 25, 2007 at 08:48:20PM -, Ramin Nakisa wrote: This is still broken in 2.6.17. I get random lockups in Edgy. I've got an atheros card, so lspci -n gives 168c:0013. When I boot I get an error: I'm afraid you're experiencing a different issue. This lockup is fixed in madwifi-ng which is the default in Edgy. The bug is still open in Dapper, though. My laptop is almost unusable. It works for a while then randomly hangs. Perhaps you can fix this before we get Feisty? This has been dragging on for so long without a fix. Could you please test if it's fixed in Feisty? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Sunday 25 March 2007 20:58, Soren Hansen wrote: On Sun, Mar 25, 2007 at 08:48:20PM -, Ramin Nakisa wrote: This is still broken in 2.6.17. I get random lockups in Edgy. I've got an atheros card, so lspci -n gives 168c:0013. When I boot I get an error: I'm afraid you're experiencing a different issue. This lockup is fixed in madwifi-ng which is the default in Edgy. The bug is still open in Dapper, though. My laptop is almost unusable. It works for a while then randomly hangs. Perhaps you can fix this before we get Feisty? This has been dragging on for so long without a fix. Could you please test if it's fixed in Feisty? Hi Soren, How do I upgrade to Feisty before the official release? I don't suppose it could be more unstable than my current Ubuntu install! This sounds very similar to the previous problem (X40, exactly the same network card) so how do you know it's a different issue? Thanks, Ramin. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
--- Soren Hansen [EMAIL PROTECTED] wrote: Odd, that's the exact same card I have. Oh, did you still have my madwifi-ng-default package installed? That might break stuff because the modules were renamed. Thanks for this info, Soren! Indeed that's very odd, as I tested the same wifi card (I have two of them, PCI versions) on another computer, doing a fresh install of Edgy. Neither with the Life CD, nor the installed version of Edgy could I get this Wifi card to work at all. The restricted package was installed and the kernel modules were loaded fine, I could even see my router when using network-manager, but I could not connect to it. By the way, on this computer was previously installed Warty and there the Wifi card worked fine. I did the same test also on the other computer, where I originally installed your madwif-ng packages, using the Edgy Live CD (so your madwifi package cannot be the culprit), but I could neither get a connection to my router. After upgrading this machine from dapper to edgy, it still did not work (I made sure to deinstall your packages and reinstall the original packages beforehand). Thanks, Beat Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
** Changed in: linux-restricted-modules-2.6.17 (Ubuntu) Status: Unconfirmed = Fix Released As this bug was never fixed in Dapper (LTS anyone?), I freshly installed Edgy. However, with the madwifi-ng driver present there, my Wifi card with following ID did not even work: $ lspci -n | grep $(lspci | grep -i atheros | cut -f1 -d' ') | cut -f3 -d' ' 168c:0013 I have three computers using the same Wifi card. Not expecting this bug ever getting fixed, I bought three new wireless cards with a Ralink chip that feature an open source driver. My wireless woes are gone now, however, I am very unhappy about the state of how critical bugs are (not) handled in Ubuntu. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Mon, Nov 27, 2006 at 09:41:36AM -, tuxo wrote: As this bug was never fixed in Dapper (LTS anyone?), I freshly installed Edgy. However, with the madwifi-ng driver present there, my Wifi card with following ID did not even work: $ lspci -n | grep $(lspci | grep -i atheros | cut -f1 -d' ') | cut -f3 -d' ' 168c:0013 Odd, that's the exact same card I have. Oh, did you still have my madwifi-ng-default package installed? That might break stuff because the modules were renamed. Cheers. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I've experienced the same bug only after last software update. About three times in a row computer worked for 10-15 min and hanged. At first time I haven't even done anything, I wasn't even logged in, because I left computer for a while. On the other day this bug occurred only once. And It hasn't occurred during last two days. I was connected to the Net, but my connection is not wireless. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
This bug does not exist in 2.6.17 (Edgy kernel) since it's a madwifi-old issue and Edgy uses madwifi-ng. ** Changed in: linux-restricted-modules-2.6.17 (Ubuntu) Status: Unconfirmed = Fix Released -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
GlebV: This is not the bug you are looking for, this is specific to the mad-wifi wireless card drivers, so if you are having system lockups, it is a separate bug -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Also have this problem on my PentiumIII 866 + GA-60XE(815EP) But i don't have any wireless card on this machine. just a 3com ethernet adapter. just simply Dapper Server 6.06.1 + Kernel 2.6.15 server running amule+azureus. randomly shows BUG: soft lockup detected on CPU#0 and than hanged up. sysrg function isn't that useful except reboot... This machine running Memtest+ and have lots of errors, but i don't think that is the problem, before this softlockup state comes , this machine had been tested for few days , and turned all right. bring this softlockup just recent days. Don't know why... -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Nov 14, 2006 at 02:58:46PM -, CNBorn wrote: Also have this problem on my PentiumIII 866 + GA-60XE(815EP) But i don't have any wireless card on this machine. just a 3com ethernet adapter. Then you're experiencing a different bug. This machine running Memtest+ and have lots of errors, but i don't think that is the problem, before this softlockup state comes , this machine had been tested for few days , and turned all right. If Memtest gives you errors, you most certainly have a problem and it might very well be the cause of this. You should identify your faulty RAM and throw it far away. :-) -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
** Also affects: linux-restricted-modules-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I see someone just added this as also affecting l-r-m-2.6.17, ie edgy. I would like to refute this as my atheros based thinkpad has been solidly stable since I switched to madwifi-ng (first in dapper, then by upgrading to edgy). Juanje - what leads you to add 2.6.17? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I solved some random wifi-related lockups by uninstalling network- manager and directly configuring wpa_supplicant. I added a bit to the ubuntu wiki https://help.ubuntu.com/community/WifiDocs/WPAHowTo. Basically I just start wpa_supplicant with a pre-up stanza in /etc/network/interfaces rather than using network-manager. This would make sense if KDE doesn't suffer lockups if nm-applet and/or gnome- keyring-daemon etc are at fault. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
My laptop hangs up randomly with Ubuntu 6.06. I tried everythings for months, but no result. I installed Kubuntu 6.06 and interestingly it has been working fine. No hang up any longer. I do not see any differences in the configuration. It was rock solid with Ubuntu 5.10 too. Compaq Evo160, Ati Mobility card. I use two wired ethernet interfaces for routing. KD -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Dapper is out now for almost 4 months. And I can still not use my wireless, as it freezes up my computer randomly. This bug is labeled critical, but no offical fix has been released yet. As I got tired of the Ethernet cable crossing our whole appartment and like Chris Jones not keen on installing Edgy on my main production machine (stability is also my number one criteria), I tried to install the packages generously provided by the original bug reporter Soren Hansen. These packages allow you to use the madwifi-ng kernel drivers combined with a patched network-manger. I added following line to my apt sources list: deb http://www.linux2go.dk/ubuntu dapper main Did and apt-get update apt-get upgrade which installled me following packages madwifi-ng-default wpasupplicant network-manager libnm-util0 network-manager-gnome So far so good. However, after rebooting the machine, it hanged at the hardware detection point. After a long time it went past this point and booted into X. However, I was not able to get the wireless network running. The new atheros kernel modules were loaded: [~]lsmod | grep ath new_ath_pci98980 0 new_ath_rate_sample14048 1 new_ath_pci new_wlan 205276 4 new_wlan_scan_sta,new_ath_pci,new_ath_rate_sample new_ath_hal 191344 3 new_ath_pci,new_ath_rate_sample and the ath0 device showed up with ifconfig. As mentioned by Ankur Kotwal earlier in this thread, I tried to comment out the contents of the file /etc/udev/rules.d/25-iftab.rules. The machine did not hang anymore during the hardware detection point, but the wirless network didn't work anyway. Grepping the kern.log file for ath leads to following entries during booting: - snip Sep 26 17:41:57 localhost kernel: [17179594.548000] ath_hal: module license 'Proprietary' taints kernel. Sep 26 17:41:57 localhost kernel: [17179594.736000] ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) Sep 26 17:41:57 localhost kernel: [17179594.832000] ath_rate_sample: 1.2 Sep 26 17:41:57 localhost kernel: [17179594.848000] ath_pci: 0.9.6.0 (EXPERIMENTAL) Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: turboG rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: H/W encryption support: WEP AES AES_CCM TKIP Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: mac 5.9 phy 4.3 radio 4.6 Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 1 for WME_AC_BE traffic Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 0 for WME_AC_BK traffic Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 2 for WME_AC_VI traffic Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 3 for WME_AC_VO traffic Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 8 for CAB traffic Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Use hw queue 9 for beacons Sep 26 17:41:57 localhost kernel: [17179595.348000] ath0: Atheros 5212: mem=0xde80, irq=177 Sep 26 17:41:57 localhost kernel: [17179597.004000] ath_pci: driver unloaded Sep 26 17:41:57 localhost kernel: [17179597.012000] ath_rate_sample: unloaded Sep 26 17:41:57 localhost kernel: [17179597.016000] ath_hal: driver unloaded Sep 26 17:41:57 localhost kernel: [17179597.032000] new_ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Sep 26 17:41:57 localhost kernel: [17179597.068000] new_ath_rate_sample: 1.2 (svn 2006-09-18) Sep 26 17:41:57 localhost kernel: [17179597.084000] ath_pci: 0.9.4.5 (svn 2006-09-18) Sep 26 17:42:16 localhost kernel: [17179902.972000] ath0: no IPv6 routers present - snap --- Greppig kern.log file for wifi lead to this: - snip Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: H/W encryption support: WEP AES AES_CCM TKIP Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: mac 5.9 phy 4.3 radio 4.6 Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: Use hw queue 1 for WME_AC_BE traffic Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: Use hw queue 0 for WME_AC_BK traffic Sep 26 17:41:57 localhost kernel: [17179597.50] wifi0: Use hw queue 2 for WME_AC_VI traffic
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I've just started using my X40 fulltime for work and I've had 4 lockups so far today. I have just installed Soren's madwifi-ng (and related) packages as described above because I have to have this working, but it still would be really nice if the bug could be fixed in the version that dapper uses. I'm not terribly keen on upgrading the laptop to Edgy, even when released because I want this to be rock solid. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Has anyone experiencing this bug tried 2.6.17 in edgy? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Wed, Aug 23, 2006 at 10:40:30AM -, Matt Zimmerman wrote: Has anyone experiencing this bug tried 2.6.17 in edgy? We've switched to madwifi-ng in Edgy, so the problem is gone there. It only happens with madwifi-old. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
** Tags added: dapper freeze -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Just to add some more notes, I've had the crash happen a few more times and investigated more closely what's going on. I enabled the wireless LED a few days ago and I've noticed that when the machine hangs, the LED is on and stays on, so I am tempted to guess that it's hanging inside a wireless send/receive type function. In terms of SysRq commands, there's not much that seems to work - I tried to kill X, dump some stats and do a safe sync,unmount,reboot, but the only one that works is the reboot one. I would hazard a guess that this is because the kernel is busy waiting for the wireless driver to finish doign whatever its doing. However, all of this makes it extraordinarily difficult to track down what's really going on, especially with no serial port. Can anyone think of some other way(s) we can collect information about what failed? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Jul 25, 2006 at 11:10:11AM -, Chris Jones wrote: However, all of this makes it extraordinarily difficult to track down what's really going on, especially with no serial port. Can anyone think of some other way(s) we can collect information about what failed? There's always netconsole.. Via the wired interface, of course. :-) Cheers. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Very similar problem. My Compaq EVO 110 laptop was rock solid with Breesy. With Dapper it locks up randomly when I use Firefox. No mouse, no keyboard, no any massage. I use ATI Radeon Mobility and the ATI prop. driver. I use the latest upgrade, but this bug persists from the beginning. I have tried both 386 and 686 kernel, open and propr. drivers. No change. I have no idea what to try yet. Denes -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I have a desktop system (AMD64 on an ABit AV8) which has an atheros chipset (pci id 168c:0013) and it works completely reliably, the machine simply never crashes. However, I have just also acquited a Thinkpad x40 with the atheros chipset and I have seen a few crashes where the whole system hung. I'm running network-manager on it and I don't notice any particular link between anything and the crashes, but SysRq does still work. Next time I will try and get a dump out of it, but usually it crashes while I'm in X and all I can do is alt-sysrq-b -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Soren, Thanks it now works. But it is subject to an annoying behavior that others have observed. NetworkManager continuously disconnect and reconnects. Apparently the way to get it fixed is stop NetworkManager from continuously scanning... How does one do that? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Wed, Jul 19, 2006 at 02:22:36PM -, Michel Lesoinne wrote: Apparently the way to get it fixed is stop NetworkManager from continuously scanning... How does one do that? I don't know. I have not experienced this behaviour. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Tue, Jul 18, 2006 at 02:28:44AM -, Michel Lesoinne wrote: Still as soon as NetworkManager starts it gets the wifi in a weird state and never connects. I have to kill NetworkManager, unload the modules and reload them to be able to connect manually. Soren, do you have a package of what you did that I can install? Yes. It can be found here: http://www.linux2go.dk/ubuntu/pool/main/m/madwifi-ng-default/madwifi-ng-default_1.0_all.deb also, the patched wpasupplicant and NetworkManager: http://www.linux2go.dk/ubuntu/pool/main/n/network-manager/network-manager_0.6.2-0ubuntu7linux2go2_i386.deb http://www.linux2go.dk/ubuntu/pool/main/w/wpasupplicant/wpasupplicant_0.4.8-3ubuntu1.1linux2go1_i386.deb the really easy way is to add: deb http://www.linux2go.dk/ubuntu dapper main to your sources.list and run: $ sudo apt-get install madwifi-ng-default wpasupplicant network-manager IMPORTANT: For these packages to work, you need to have the linux-restricted-modules installed and NOT be using the madwifi-ng drivers from SVN as there are naming differences. Cheers! -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Mon, Jul 17, 2006 at 10:33:26PM -, Michel Lesoinne wrote: I do not understand the changes you did when I installed a new version of madwifi, it removed all the new_ath_* drivers and instead installed the ath_* in their place. So why did you modify NetworkManager and wpa_supplicant? The change to networkmanager enables it to detect if you're using the madwifi-ng (new_ath_* actually). madwifi and madwifi-ng has different API's and the change I've made to wpasupplicant lets it use both depending on a commandline option (which networkmanager can give it because I've taught it to know which driver is used). I took the subversion madwifi and it did not work, as it would freeze after a little bit of time and it did not work with NetworkManager. It will work with the patched networkmanager and wpasupplicant. Now I am trying a snapshot madwifi-ng and still there are no new_ath_* modules being loaded. What am I missing? new_ath_* are the names Ubuntu uses for madwifi-ng in order to let madwifi and madwifi-ng coexist on the system. If you compile them from SVN, they'll be named ath_*. Cheers. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Still as soon as NetworkManager starts it gets the wifi in a weird state and never connects. I have to kill NetworkManager, unload the modules and reload them to be able to connect manually. Soren, do you have a package of what you did that I can install? -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Just a quick thanks for the heads up on this bug. I was just about to upgrade a Suse 10.0 machine with an Atheros Wifi adapter to Dapper but I really don't need this kind of trouble, and so will wait until this problem is flattened. Good luck with it and thanks again for keeping me out of trouble! Cheers, Chris -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I have been experiencing the same problem. I have an Apple MacBook Pro 17 and installed dapper on it. I also noticed it was network related and perhaps triggered by wpa_supplicant/knetworkmanager combo. This led me to find this thread. Unlike others, my lspci gives me slightly different numbers: 168c:001c -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Thu, Jul 13, 2006 at 04:41:33PM -, Michel Lesoinne wrote: I have been experiencing the same problem. I have an Apple MacBook Pro 17 and installed dapper on it. I also noticed it was network related and perhaps triggered by wpa_supplicant/knetworkmanager combo. This led me to find this thread. Unlike others, my lspci gives me slightly different numbers: 168c:001c That's very useful info. I've hacked together a .deb that makes madwifi-ng be loaded instead of madwifi. That fixes it for me, but apparantly some people have other problems with -ng. I'll just finish polishing it (probably tomorrow) and upload it somewhere. Cheers, Søren. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
Me tto I'm experiencing these freezes. In addition I'v an ATI video card on my Compaq Evo N800v, and it seems to be a relation between madwifi and ati: https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-ati/+bug/38181 -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I've had a terrible lockup problem since SMP was enabled by default in the kernel. Maybe try adding nosmp to the kernel line in grub's menu.lst (you may need noapic too, not sure though. I needed it, but all cases are different). I haven't tried removing that nosmp line ever since I found out it worked, and I don't plan to any time soon until I know my computer wont commit suicide whenever I download something. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
I never found the time to play with the nice patches, but the latest kernel update/restricted modules update seems to have made a difference. A bit early to cry success, but it's been on more or less the last 24 hours without a hitch. -- Glenn -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37773] [Bug 37773] Re: [madwifi] Semi-random system lockups in Dapper
On Fri, Jun 16, 2006 at 07:24:21PM -, Glenn Steen wrote: I never found the time to play with the nice patches, but the latest kernel update/restricted modules update seems to have made a difference. A bit early to cry success, but it's been on more or less the last 24 hours without a hitch. Hmm... As far as I can see there was no change with regard to the madwifi drivers, so I think it's just luck. Sorry. ;-) If it actually turns out to have made a difference please let us know. Cheers, Søren. -- [madwifi] Semi-random system lockups in Dapper https://launchpad.net/bugs/37773 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
