Kernel panic on driver rtl8821ae

Bug #1327741 reported by Alessandro Sivieri
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

Since kernel version 3.13.0-27, my Asus VM40B goes into kernel panic during boot, seemingly due to an error with the WiFi driver, rtl8821ae. The attached screenshot of the screen (I have no idea how to otherwise capture the output of a kernel panic) shows the error with kernel version 3.13.0-29, but it happens exactly the same with -27.

WORKAROUND: Disabling the WiFi card or using version 3.13.0-24 does not cause any problem.

Please bear in mind, while reading the generated report, that I have disabled the WiFi card to be able to boot with kernel -29.

Revision history for this message
Alessandro Sivieri (scattino) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1327741

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
Revision history for this message
Alessandro Sivieri (scattino) wrote :

Log files collected using linux-bug.

Revision history for this message
Alessandro Sivieri (scattino) wrote :

Screenshot of the output of the kernel panic

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Alessandro Sivieri, please boot into a working kernel and execute the following at a terminal:
apport-collect 1327741

description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Shingo TADA (tada45) wrote :

I have a same problem on my ASUS VivoPC VM40B.

$ uname -a
Linux FIAP-SV-ASUS01 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
penalvch (penalvch) wrote :

Shingo TADA, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Gonçalo Rodrigues (grodrigues-math) wrote :

Same bug here in desktop ASUS M11AD with 3.13.0-30, but not in 3.13.0-24. Solved with 3.14.1 from the trusty mainline kernel.

note:
Cannot collect info with apparmor-collect because it spits out:

ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt4.QtCore

Revision history for this message
penalvch (penalvch) wrote :

Gonçalo Rodrigues, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Phillip Sz (phillip-sz)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Jean-Philippe Guérard (fevrier) wrote :

This issue also affects the latest Xubuntu installation image (xubuntu-14.04.1-desktop-amd64.iso), which is not installable on an Asus M11AD.

Revision history for this message
penalvch (penalvch) wrote :

Jean-Philippe Guérard, please test Utopic via http://cdimage.ubuntu.com/daily-live/current/ . If reproducible, please file a new report via a terminal:
ubuntu-bug linux

or if you cannot boot via:
https://bugs.launchpad.net/ubuntu/+source/linux/+filebug

Revision history for this message
Hugo Costelha (hugo-costelha) wrote :

I just dowloaded the daily image (18/08/2014, 18h GMT) and it does not go into kernel panic. When can we expect these changes in the trusty kernel?

Revision history for this message
penalvch (penalvch) wrote :

Hugo Costelha, could you please boot into the daily image, and execute at a terminal:
ubuntu-bug linux

This will allow the necessary debug information to be captured. Please feel free to subscribe me to this new report.

Revision history for this message
Hugo Costelha (hugo-costelha) wrote :

I ran the command, but was unable to associate the report to this bug. It was stored as bug #1362648.

Changed in linux (Ubuntu):
importance: Low → High
Revision history for this message
John C Hatch (henwyn) wrote :

This bug also affected me but seems to be fixed in 14.10.

Revision history for this message
valerio (passini-valerio) wrote :

This bug is present in kubuntu 14.04.1 LTS too.

Revision history for this message
Rene H. Larsen (rhl) wrote :

One of the recent kernel releases (not sure which) fixed rtl8821ae support for me.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.