Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
High
|
Paolo Pisati | ||
linux-meta-raspi2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And there's a RTL2838 DVB-T USB stick attached to monitor airplane positions for Flightradar24.
After updateing the kernel from 4.8.0-1024, which runs flawlessly, to -1025, there's a kernel panic happening 10-20 seconds after booting up to the login prompt. I thought the -1026 fixed that, but it's still no worky. The trace is scrolling so fast I can't read anything but the last page:
[<808c76c8>] (sock_sendmsg) from...
[<808c7778>] (sock_write_iter) from...
[<802c39c8>] (new_sync_write) from...
[<802c3a4c>] (__vfs_write) from...
[<802c48d8>] (vfs_write) from...
[<802c5ab4>] (SyS_write) from...
Code: e5922004 e0033002 e3530000 0a00000a (e5902034)
---[ end trace 0f53d17efe0c6ba ]---
Kernel panic - not syncing: Fatal exception in interrupt
CPU2: stopping
CPU: 2 PID: 21 Comm: migration/2 Tainted: G D 4.8.0-1026-raspi2 #29-Ubuntu
Hardware name: BCM2709
[<801120ac>] (unwind_backtrace) from ...
[<8010d2dc>] (show_stack) from ...
[<8059c38c>] (handle_IPI) from ...
[<80101564>] (bcm2836_
Exception stack(0xbb99de68 to 0xbb99deb0)
de60: 00000000 00000004 00000000 00000001 bac05de0 00000001
de80: bac05dcc 00000000 a00e0013 00000000 bac05d6c bb99dedc bb99dee0 bb99deb8
dea0: 801d367c 801d35f4 600e0013 ffffffff
[<80a49f3c>] (__irq_svc) from ...
[<801d35f4>] (multi_cpu_stop) from ...
[<801d38ec>] (cpu_stopper_
[<8014b71c>] (smpboot_thread_fn) from ...
[<80147770>] (kthread) from [<80108e28>] (ret_from_
And then this block repeats with CPU3 and CPU0.
Going back to 4.8.0-1024 makes everything work again.
Affected packages:
linux-image-
linux-image-
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jul 25 2016 seq
crw-rw---- 1 root audio 116, 33 Jul 25 2016 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-1024-raspi2.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.10
Lsusb:
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.161.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: yakkety
Uname: Linux 4.8.0-1024-raspi2 armv7l
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago)
UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users video www-data
_MarkForUpload: False
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
summary: |
- Kernel panic with 4.8.0-1025 and -1026 on RasPi 2 + Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2 |
Changed in linux-meta-raspi2 (Ubuntu): | |
status: | New → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1667160
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.