ath9k crashes the system

Bug #1683110 reported by Quang on 2017-04-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After upgraded to 17.04 from 16.10, my system cannot boot into the GUI anymore with kernel 4.10.0. I can boot it with the old kernel 4.8.0 from 16.10. When boot with 4.10.0 kernel, the system is crashed. I can see that ath9k caused it from dmesg.
Also this bug report is created with atk9k disabled so if there is anything missing, please ask so I could include it.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
 /dev/snd/controlC0: quang 2038 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sun Apr 16 13:57:17 2017
HibernationDevice: RESUME=UUID=d756d907-93fa-4ca5-971e-e28ffbc15946
InstallationDate: Installed on 2016-10-14 (183 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
 enp4s0f2 no wireless extensions.

 lo no wireless extensions.
MachineType: Acer EA40_CX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=a5def0bc-8223-4d88-bbca-6fc32fcec07f ro quiet splash vt.handoff=7
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago) 09/18/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.04 EA40_CX
dmi.board.vendor: Acer
dmi.board.version: V2.04
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.04
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd09/18/2013:svnAcer:pnEA40_CX:pvrV2.04:rvnAcer:rnEA40_CX:rvrV2.04:cvnAcer:ct9:cvrV2.04: EA40_CX
dmi.product.version: V2.04
dmi.sys.vendor: Acer

Quang (ngoquang2708) wrote :
description: updated
Quang (ngoquang2708) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to . Please test the latest v4.11 kernel[0].

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'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.


Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Changed in linux (Ubuntu Zesty):
status: Confirmed → Incomplete
Quang (ngoquang2708) wrote :

Tested with linux v4.11-rc7. Still the same.

tags: added: kernel-bug-exists-upstream
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.


Changed in linux (Ubuntu Zesty):
status: Incomplete → Triaged
tags: added: needs-bisect
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers