iwl4965 and ACPI issues resulting in shutdowns

[XAVeRY]

Hello there.
I'm using Ubuntu 8.04 updated to Intrepid's kernel (2.6.26-5-generic), with the latest drivers for my wireless card (Intel WiFi Link 4965AGN) obtained from the compat-wireless project, dated 6 August 2008.
I'm experiencing some problems, which seem to be randomly induced. They happen when I play around with the module, remove it and insert again, and sometimes when I'm not doing anything special (I'm connected to my router through wifi).

The thing is, sometimes the system starts being irresponsive, my laptop's fan starts spinning really fast and the computer shuts down within, like, 5 seconds. (that's what happens when it overheats, but I'm 100% positive that its temperature is proper and shouldn't induce shutdowns)

I'm using a Compal FL90 laptop, with Intel Core 2 Duo.

Kernel messages preceding the shutdown are as follows :
Aug 10 10:54:44 Jurij kernel: [ 1703.007247] iwl4965: Microcode SW error detected. Restarting 0x82000000.
Aug 10 10:54:47 Jurij kernel: [ 1705.219487] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Aug 10 10:54:47 Jurij kernel: [ 1707.468905] iwl4965: Can't stop Rx DMA.
Aug 10 10:54:47 Jurij kernel: [ 1708.468968] ACPI: EC: acpi_ec_wait timeout, status = 0x19, event = "b0=1"
Aug 10 10:54:47 Jurij kernel: [ 1708.468968] ACPI: EC: read timeout, command = 130
Aug 10 10:54:47 Jurij kernel: [ 1708.468968] psmouse.c: resync failed, issuing reconnect request
Aug 10 10:54:47 Jurij kernel: [ 1708.482114] iwl4965: No space for Tx
Aug 10 10:54:47 Jurij kernel: [ 1708.482119] iwl4965: Error sending SENSITIVITY_CMD: enqueue_hcmd failed: -28
Aug 10 10:54:47 Jurij kernel: [ 1708.482122] iwl4965: SENSITIVITY_CMD failed

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Andreas Moog (ampelbein)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!