Ubuntu 12.10 x86_64 3.5.0-22 kernel panic Ralink RT3573

Bug #1127831 reported by Johnny Robertson on 2013-02-17
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

1) Description: Ubuntu 12.10
Release: 12.10

2) Linux localhost 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:47:00 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

3) what is expected to happen is the kernel does not panic with the Ralink RT3573 v2.5 driver for the Linksys AE3000 USB Wifi adapter.

4) What happens instead is a Kernel panic occurs as fast as 89 seconds into runtime. This backtrace was typed-out from a photo I captured via camera:
__netif_receive_skb+0x054a/0x620
process_backlog+0xc1/0x1a0
net_rx_action+0x123/0x220
__do_softirq+0xb6/0x1d0
? ack_apic_level+0x78/0x130
call_softirq+0x1c/0x30
do_softirq+0x75/0xb0
irq_exit+0xa5/0xb0
do_IRQ+0x63/0xe0
common_interrupt+0x6a/0x6a
<EOI>
? intel_idle+0xea/0x150
? intel_idle+0xcb/0x150
cpuidle_enter+0x19/0x20
cpuidle_idel_call+0xa9/0x240
cpu_idle+0xaf/0x120
start_secondary+0x1de/0x1e5
Code: 00 00 48 89 44 24 10 8b 87 cc 00 00 00 48 89 44 24 08 48 8b 87 e0 00 00 00 48 c7 c7 40 9e 81 48 89 04 24 31 c0 e8 e8 0a 11 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41 56 41
RIP [<ffffffff81565af4>] skb_put+0x94/0xa0
 RSP <ffff8801bfc43a50>
- - - [ end trace 954fd134cc0c79c6 ] - - -
kernel panic - not syncing: Fatal exception in interrupt

4 images captured with a camera of the kernel panic output are attached to this report:
1. Kernel panic output showing invalid opcode.
2. Kernel panic showing backtrace.
3. Kernel panic with APIC disabled (noapic)
4. Kernel panic with APIC enabled

Further debug info:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1127831/+attachment/3760671/+files/debuginfo

Johnny Robertson (mxedit10n) wrote :
Johnny Robertson (mxedit10n) wrote :
Johnny Robertson (mxedit10n) wrote :
Johnny Robertson (mxedit10n) wrote :
Johnny Robertson (mxedit10n) wrote :
summary: - 12.10 Kernel panic - not syncing: fatal exception in interrupt
+ 12.10 Kernel panic Ralink RT3573

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1127831

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: quantal
description: updated
description: updated
description: updated
description: updated
summary: - 12.10 Kernel panic Ralink RT3573
+ 12.10 3.5.0-22 Kernel panic Ralink RT3573
summary: - 12.10 3.5.0-22 Kernel panic Ralink RT3573
+ 12.10 3.5.0-22 x86_64 kernel panic Ralink RT3573
affects: linux (Ubuntu) → linux-kernel-bugs
Changed in linux-kernel-bugs:
status: Incomplete → New
summary: - 12.10 3.5.0-22 x86_64 kernel panic Ralink RT3573
+ Ubuntu 12.10 x86_64 3.5.0-22 kernel panic Ralink RT3573
summary: - Ubuntu 12.10 x86_64 3.5.0-22 kernel panic Ralink RT3573
+ Ubuntu 12.10 x86_64 3.5.0-22 kernel panic Ralink RT3573
description: updated
Changed in ubuntu:
status: New → Confirmed
Changed in linux-kernel-bugs:
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Johnny Robertson (mxedit10n) wrote :

Reproduced using Linux 3.8.0-999-generic amd64:

net_rx_action+0x134/0x260
? cpuidle_wrap_enter+0x50/0xa0
_ _do_softirq+0xc0/0x240
? ack_apic_level+0x72/0x130
call_softirq+0x1c/0x30
irq_exit+0x8e
do_IRQ+0x63/0xe0
common_interrupt+0x6d/0x6d
<EOI>
? clockevents_notify+0x4c/0x1a0
? cpuidle_wrap_enter+0x50/0xa0
? cpuidle_wrap_enter+0x49/0xa0
cpuidle_enter_tk+0x10/0x20
cpu_idle+0xcf/0x120
start_secondary+0xc3+0xc5
Code: 48 89 54 24 10 8b 97 d4 00 00 00 48 89 54 24 08 48 8b 97 e8 00 00 00 48 c7 c7 68 4a ab 81 48 89 14 24 48 8b 55 08 e8 0a 54 10 10 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5
RIP [<ffffffff815cb2c4>] skb_put+0x94/0xa0
    RSP <ffff8801bfc43a40>
    - - - [ end of trace ba9cf3f364f16653 ] - - -
Kernel panic - not syncing: Fatal exception in interupt

Johnny Robertson (mxedit10n) wrote :

kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
spacegoblin (nickprib) wrote :

A fix for 64 bit can be found at

https://github.com/ashaffer/rt3573sta

Shane Hart (shart6) wrote :

I can confirm that the fix linked in #10 works on latest kernel 3.9.8.

tags: added: needs-kernel-logs needs-upstream-testing regression-potential

Cut from Bug Description.

description: updated

Johnny Robertson, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers