[Bug 282355] [NEW] iwlagn segmentation fault and firmware errors
Public bug reported: I've been getting firmware errors with the iwlagn module recently. (Will they never go away?) After getting some firmware errors, I did 'modprobe -r iwlagn; modprobe iwlagn' to recover, and I got a segmentation fault. Furthermore, on occasion after having a firmware error and reloading the module, my computer will freeze when I try to reconnect to the network. I've attached my dmesg output. I'm running Intrepid. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- iwlagn segmentation fault and firmware errors https://bugs.launchpad.net/bugs/282355 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282355] Re: iwlagn segmentation fault and firmware errors
** Attachment added: "Dmesg" http://launchpadlibrarian.net/18468919/dmesg -- iwlagn segmentation fault and firmware errors https://bugs.launchpad.net/bugs/282355 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282355] Re: iwlagn segmentation fault and firmware errors
I have had at least one kernel panic. However, the freeze that I get is often not a complete freeze. I can minimally interact with X, bringing up menus and such, but I can't start programs or switch to a virtual terminal. Next time this problem rears its ugly head, I'll see what I can pull off the computer. This happens nearly daily, so I'll have more info soon. -- iwlagn segmentation fault and firmware errors https://bugs.launchpad.net/bugs/282355 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282355] Re: iwlagn segmentation fault and firmware errors
I'm continuing to get firmware errors, but my computer hasn't become unresponsive. I'm posting a new dmesg full of firmware errors. My network came back up without prompting after each error. It may be that the freezing issue is gone. I'll give it a few days time to be sure. ** Attachment added: "Dmesg" http://launchpadlibrarian.net/18523880/dmesg.new -- iwlagn segmentation fault and firmware errors https://bugs.launchpad.net/bugs/282355 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806582] Re: keepassx crashed with SIGSEGV in QTreeWidgetItem::executePendingSort()
I can fairly consistently crash keepassx by making a change to the database, and then sorting groups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806582 Title: keepassx crashed with SIGSEGV in QTreeWidgetItem::executePendingSort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepassx/+bug/806582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806582] Re: keepassx crashed with SIGSEGV in QTreeWidgetItem::executePendingSort()
I believe this sequence of events works consistently to duplicate the problem: 1. Delete a group 2. Sort Groups This leads to the software crashing and exiting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806582 Title: keepassx crashed with SIGSEGV in QTreeWidgetItem::executePendingSort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepassx/+bug/806582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149214] Re: [Gutsy] Intel 4965AGN wireless connection dies
Same here with a 4965AGN on an IBM R61. The connection seems to randomly die, and I usually can't reconnect until I remove the module and reload it. DMESG: [ 232.870279] iwl4965: TX Power requested while scanning! [ 232.870286] iwl4965: Error setting Tx power (-11). [ 232.871635] iwl4965: TX Power requested while scanning! [ 232.871641] iwl4965: Error setting Tx power (-11). [ 233.026727] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:00:00:00:16 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22) [ 233.074374] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:ff:35:9a:22 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22) [ 233.172414] wlan0: RX WEP frame with unknown keyidx 2 (A1=33:33:00:00:00:02 A2=00:17:9a:9a:b6:31 A3=00:0e:35:35:9a:22) [ 233.417351] iwl4965: Microcode SW error detected. Restarting 0x8200. [ 236.152880] wlan0: disassociate(reason=3) [ 237.378587] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 248.357032] ADDRCONF(NETDEV_UP): wlan0: link is not ready -- [Gutsy] Intel 4965AGN wireless connection dies https://bugs.launchpad.net/bugs/149214 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I believe this is related to bug 149214. I and others are having intermittent failures with the "Error setting Tx power (-11) " message. John -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151627] Re: [Gutsy] Update iwlwifi driver to 1.1.21 from 1.1.0 (originally 1.1.17 req) - Updated Nov. 5
1.2.0 is available now. As I understand it, the deadline for updating linux-ubuntu-modules is the new year. It doesn't look like there will be a fix soon. Also, it does look like it's gone from the git tree. Anybody know why? -- [Gutsy] Update iwlwifi driver to 1.1.21 from 1.1.0 (originally 1.1.17 req) - Updated Nov. 5 https://bugs.launchpad.net/bugs/151627 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I should also mention that I'm running the amd64 kernel. -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I began seeing the same message in dmesg as Matteo Colina when I upgraded to 1.2.0 with iwl4965. I was not getting it before I installed the new package. -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I've attached my /var/log/dmesg. Here is the order of events: Boot with the old module. (I had downgraded to the old package) Install the new package. sudo modprobe -r iwl4965; sudo modprobe iwl4965 Wait a little bit and then look at dmesg. ** Attachment added: "dmesg" http://launchpadlibrarian.net/10905333/dmesg -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
Whoops. Wrong dmesg file. Here's the right one ** Attachment added: "dmesg (correct copy)" http://launchpadlibrarian.net/10905364/dmesg -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I am still seeing infrequent microcode errors with version of iwl4965 that you posted. I have attached my dmesg ** Attachment added: "dmesg" http://launchpadlibrarian.net/10945805/dmesg -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151627] Re: [Gutsy] Update iwlwifi driver to 1.1.20 from 1.1.0 (originally 1.1.17 req) - Updated Nov. 5
It's looks like 1.1.21 is a code-cleanup as opposed to a bugfix. Might I suggest releasing 1.1.20 soon, and waiting for any kinks in 1.1.21 to get ironed out? -- [Gutsy] Update iwlwifi driver to 1.1.20 from 1.1.0 (originally 1.1.17 req) - Updated Nov. 5 https://bugs.launchpad.net/bugs/151627 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646377] Re: Brasero crashes on any video project
I also had crashes in Maverick when I attempted to copy CDs. Installing cdrdao fixed the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/646377 Title: Brasero crashes on any video project -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709331] [NEW] VMWare crashes with 3D Accel on latest PPA nvidia driver
Public bug reported: Binary package hint: nvidia-current I'm running VMWare Workstation 7.1.3 build-324285 on Ubuntu Maverick. I use the nvidia-current driver from the x-updates ppa. I'm using a "nVidia Corporation G96 [Quadro FX 580] (rev a1)" video card, according to lspci. I recently rebooted my computer to take a kernel update. Upon restart, running 2.6.35-25-generic, VMWare would freeze the entire computer just after I typed in my username and password into my Windows 7 VM. I returned to 2.6.35-24-generic, and VMWare crashed at the same place, but instead threw an error. I have attached the error log. I then disabled 3D rendering for the VM, and after a reboot (into 2.6.35-25) was able to successfully log in to my VM. It appears that the most likely culprit is the update to the nvidia drivers that I took from the x-updates ppa recently. I could confirm this if the previous driver were provided to me. :~$ lsb_release -rd Description:Ubuntu 10.10 Release:10.10 :~$ apt-cache policy nvidia-current nvidia-current: Installed: 270.18-0ubuntu1~maverick~xup1 Candidate: 270.18-0ubuntu1~maverick~xup1 Version table: *** 270.18-0ubuntu1~maverick~xup1 0 500 http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status 260.19.06-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/restricted amd64 Packages ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709331 Title: VMWare crashes with 3D Accel on latest PPA nvidia driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709331] Re: VMWare crashes with 3D Accel on latest PPA nvidia driver
** Attachment added: "VMWare Crash Log" https://bugs.launchpad.net/bugs/709331/+attachment/1812690/+files/vmware-1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709331 Title: VMWare crashes with 3D Accel on latest PPA nvidia driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709331] Re: VMWare crashes with 3D Accel on latest PPA nvidia driver
I can confirm that reverting to an earlier nvidia driver allows me to successfully re-enable 3d acceleration for the VM. :~$ apt-cache policy nvidia-current nvidia-current: Installed: 260.19.06-0ubuntu1 Candidate: 270.18-0ubuntu1~maverick~xup1 Version table: 270.18-0ubuntu1~maverick~xup1 0 500 http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/ maverick/main amd64 Packages *** 260.19.06-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/restricted amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709331 Title: VMWare crashes with 3D Accel on latest PPA nvidia driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709331] Re: VMWare crashes with 3D Accel on latest PPA nvidia driver
This is fixed with VMware Workstation Release 7.1.4: "When the latest NVIDIA 270.x drivers are installed on a Linux host system, users could not run virtual machines with 3D acceleration enabled." https://www.vmware.com/support/ws71/doc/releasenotes_ws714.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709331 Title: VMWare crashes with 3D Accel on latest PPA nvidia driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: Please enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG
** Changed in: linux (Ubuntu) Status: Incomplete => New -- Please enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: Please enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG
I filed this bug two years ago. It took you guys a year to respond to it with promises of corrective action. It's taken you a year again to realize that you still haven't even checked it out yet. I quit using Ubuntu because of this bug. I have no intentions to check whether or not this bug is fixed. It's so trivial for a developer to check, that I don't see why a user has to do your work for you. Look at the kernel config. Is CONFIG_IWL3945_DEBUG set? Is CONFIG_IWLWIFI_DEBUG set? Done. Are you guys lazy, or merely incompetent? -- Please enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] [NEW] iwl4965 does not report debug information
Public bug reported: Binary package hint: linux-backports-modules Using Ubuntu Hardy. The iwl4965 module does not respond to 'options iwl4965 debug=0x43fff' in /etc/modprobe.d/options. After getting a microcode error, nothing extra was reported in dmesg. Insmod is getting called correctly, so it would seem that debugging has somehow been disabled. Debugging info is essential for this module, given the number of microcode errors this module has. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: iwl4965 iwlwifi -- iwl4965 does not report debug information https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I can confirm that this bug still exists with the latest backports version. I'm seeing it a few times each day. One of my errors was an HW error, I'm not sure what this means. Here are some excerpts from my logs. All of these showed up with nothing else in the logs for about 20 minutes beforehand, so I don't have any useful context. Apr 22 19:14:23 shabbar kernel: [ 178.828915] iwl4965: Microcode SW error detected. Restarting 0x8200. Apr 23 10:18:56 shabbar kernel: [ 1021.111942] iwl4965: Microcode SW error detected. Restarting 0x8200. Apr 23 10:42:08 shabbar kernel: [ 1687.524693] iwl4965: Microcode HW error detected. Restarting. The version, from the logs: iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.25 I have the latest firmware. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I've been trying to capture debug information about the microcode errors, but I haven't had one in a while. Can someone who is regularly having the errors add this to /etc/modprobe.d/options? options iwl4965 debug=0x43fff It should give more information in dmesg on the nature of the bug, so that it can be fixed upstream. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: iwl4965 does not report debug information
/sys/module/iwl4965/parameters/debug has the correct value, so I can confirm that the module is getting called correctly. Something is wrong with the module itself, then. -- iwl4965 does not report debug information https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I found the same problem with debug=0x43fff not working, and have reported it as Bug #226593. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: iwl4965 does not report debug information
All right, what does it take to get a bug even looked at. I've pointed out the two relevant config options. Is there some reason why this issue is getting entirely ignored? Is there active opposition to being able to debug a flaky module? Do you all like having broken iwlwifi modules? Please, enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG. I'm tired of having my computer crash daily and being stuck filing useless bug reports. -- iwl4965 does not report debug information https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I'm still getting firmware errors, and my computer is still freezing every few times I reload the module and try using it. I've requested it in bug 226593, and I'll say it here. Can someone please enable debugging of the iwl* modules? This bug will go nowhere if debugging remains disabled. All it takes is two config options, CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282355] Re: iwlagn segmentation fault and firmware errors
Well the freezing issue isn't gone, but if the firmware errors are fixed (another bug) then they're a non-issue. -- iwlagn segmentation fault and firmware errors https://bugs.launchpad.net/bugs/282355 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: iwl4965 does not report debug information
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- iwl4965 does not report debug information https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226593] Re: iwl4965 does not report debug information
Debugging of the iwl* modules is still not enabled in the kernel. The various microcode errors that happen in these modules are nigh impossible to debug without the information reported with debugging enabled. CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG should be enabled in the kernel. ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- iwl4965 does not report debug information https://bugs.launchpad.net/bugs/226593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
The freezing issue appears to be because something called "events/1" is using 100% of the CPU, interspersed with "iwlagn/1" taking some of the CPU. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I can confirm that the problem still exists in Ibex. I get regular Microcode errors. To recover I have to unload and reload the module. Also, on occasion, when I unload and reload the module, my computer mostly freezes. I can't start programs and shutting down doesn't work. This may just be general module unloading flakiness. I've posted a recent dmesg with microcode errors. I'm currently trying backport-modules, which seems no better than the standard module. See also bug 282355, where I posted dmesg for some past Microcode errors. ** Attachment added: "dmesg" http://launchpadlibrarian.net/18811181/dmesg.10.22.08 -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
In fact, that last post was followed quickly by a microcode error. I got the dmesg. This time, I accidentally left clicked on the network manager icon and my computer solidly froze, responding to nothing. How do you enable debugging output for iwlagn? Does it even work with the ubuntu compile? I remember it being disabled in earlier kernels. ** Attachment added: "dmesg.yet.again" http://launchpadlibrarian.net/18811253/dmesg.10.22.08.yet.again -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I've put the following into /etc/modprobe.d/iwlagn options iwlagn debug=0x43fff Hopefully I can give more useful information the next time it crashes. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
I've had these messages in the past, and I also have never seen a lock- up because of them -- until Intrepid. The version in LBM is much worse than the main kernel. It caused frequent microcode errors and frequent lockups when I tried to recover. I still see both with the main kernel, but not nearly so frequently. -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200509] Re: iwl4965: Microcode SW error detected. Restarting 0x2000000
'options iwlagn debug=0x43fff' doesn't work. The kernel configuration for the iwl* modules is unacceptable. These modules cause problems on a large number of computers, but debugging is disabled. I would be willing to accept a module that is 100k larger for the ability to debug these issues. It's impossible to send any useful information upstream to help fix this bug with the current kernel config. >From /usr/src/linux-headers-2.6.27-7-generic/.config CONFIG_IWL3945=m # CONFIG_IWL3945_DEBUG is not set CONFIG_IWL3945_LEDS=y CONFIG_IWL3945_RFKILL=y CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y CONFIG_IWL4965=y CONFIG_IWL5000=y CONFIG_IWLAGN=m CONFIG_IWLAGN_LEDS=y CONFIG_IWLAGN_SPECTRUM_MEASUREMENT=y CONFIG_IWLCORE=m CONFIG_IWLWIFI=m # CONFIG_IWLWIFI_DEBUG is not set CONFIG_IWLWIFI_LEDS=y CONFIG_IWLWIFI_RFKILL=y -- iwl4965: Microcode SW error detected. Restarting 0x200 https://bugs.launchpad.net/bugs/200509 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
