kernel BUG at /build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198 and subsequent panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Stefan Bader | ||
Bug Description
kernel BUG message and then a kernel panic at random when running wireless. Machine locks up with flashing caps-lock. No messages in /var/log. Kernel BUG message and panic collected by serial console.
No known trigger other than running wireless, but the BUG message clearly identifies the line in the iwlwifi sources where it happens and the oops can be avoided by running a wired network connection.
This appears to be the same problem reported against hardy linux-backports
lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10
apt-cache policy linux-image-
linux-image-
Installed: 2.6.27-4.6
Candidate: 2.6.27-4.6
Version table:
*** 2.6.27-4.6 0
500 http://
100 /var/lib/
[ 7192.033059] kernel BUG at /build/
[ 7192.033059] invalid opcode: 0000 [1] SMP
[ 7192.033059] CPU 1
[ 7192.033059] Modules linked in: ipv6 af_packet binfmt_misc bridge stp bnep rfcomm l2cap ppdev acpi_cpufreq cpufreq_powersave cpufreq_ondemand cpufreq_userspace cpufreq_stats freq_table cpufreq_
[ 7192.033059] Pid: 7182, comm: firefox Tainted: P 2.6.27-4-generic #1
[ 7192.033059] RIP: 0010:[<
[ 7192.033059] RSP: 0000:ffff88011f
[ 7192.033059] RAX: 0000000000000046 RBX: ffff88011a804c60 RCX: ffff88011d543e50
[ 7192.033059] RDX: ffffffff8066c248 RSI: 0000000000000086 RDI: 0000000000000082
[ 7192.033059] RBP: ffff88011f05be20 R08: 0000000000001eff R09: 00000000fffffa00
[ 7192.033059] R10: 0000000000000000 R11: 00000000ffffffff R12: ffff88011a801a00
[ 7192.033059] R13: ffff88011a804c60 R14: 00000000000000c8 R15: 0000000000000008
[ 7192.033059] FS: 00007fd1bc3546f
[ 7192.033059] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7192.033059] CR2: 000000000b8b1238 CR3: 000000010073c000 CR4: 00000000000006e0
[ 7192.033059] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 7192.033059] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 7192.033059] Process firefox (pid: 7182, threadinfo ffff8801006dc000, task ffff8800dd4e9670)
[ 7192.033059] Stack: ffff88011a804c60 ffff88011a801a00 0000000000000001 00000000000000c8
[ 7192.033059] ffff88011f05be80 ffffffffa0ae40e2 ffffffff8023dd1e 000000000185d700
[ 7192.033059] ffff88011a805b94 ffff88011a805b80 000000c90185d700 ffff88011a801a00
[ 7192.033059] Call Trace:
[ 7192.033059] <IRQ> [<ffffffffa0ae4
[ 7192.033059] [<ffffffff8023d
[ 7192.033059] [<ffffffffa0ae6
[ 7192.033059] [<ffffffff80254
[ 7192.033059] [<ffffffff80254
[ 7192.033059] [<ffffffffa0ae6
[ 7192.033059] [<ffffffff80214
[ 7192.033059] [<ffffffff80215
[ 7192.033059] [<ffffffff80254
[ 7192.033059] [<ffffffff80215
[ 7192.033059] [<ffffffff80212
[ 7192.033059] <EOI>
[ 7192.033059]
[ 7192.033059] Code: 4c 89 e7 ff d0 85 c0 75 83 49 c7 45 08 00 00 00 00 0f 1f 00 e9 73 ff ff ff 0f b6 51 04 48 c7 c7 58 3c ad a0 31 c0 e8 33 bc a4 df <0f> 0b eb fe 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 83 ec
[ 7192.033059] RIP [<ffffffffa0acd
[ 7192.033059] RSP <ffff88011f05be00>
[ 7192.033059] ---[ end trace baeeb32c2931cd0f ]---
[ 7192.033059] Kernel panic - not syncing: Aiee, killing interrupt handler!
Thanks. There is no Oops in your log. There is a BUG message and then you get a kernel panic straight afterwards, and then a warning. I have removed the kernel-oops tag and replaced it with a kernel-bug tag.
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/KernelTeamB ugPolicies Thanks in advance!