Ubuntu
linux package

Wifi stops working sporadically

Bug #1629603 reported by drwt on 2016-10-01

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Low	Unassigned

Bug Description

Since 16.04 I have been having trouble with WIFI stopping working daily and requiring a reboot to fix.

This happens at worst multiple times a day and I dont know what could trigger it, the connection just stops working with no apparent reason and I cant get it back without a reboot.

I did not have this problem with 15.10.

My access point is ASUS RT-N12E_B1. I did not experience this issue when I was using a different access point for a few days so I'm not sure whether the cause is something specific to this wifi environment.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-generic 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lelux 2188 F.... pulseaudio
CurrentDesktop: MATE
Date: Sat Oct 1 22:56:40 2016
HibernationDevice: RESUME=UUID=f9484e9d-673f-4b04-9e39-52035ccf958b
InstallationDate: Installed on 2016-09-28 (3 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha i386 (20160921)
MachineType: LENOVO 7665WM6
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.8.0-17-generic N/A
linux-backports-modules-4.8.0-17-generic N/A
linux-firmware 1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 7665WM6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7665WM6:pvrThinkPadT61:rvnLENOVO:rn7665WM6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7665WM6
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

Tags:

Revision history for this message

drwt (6lobe) wrote on 2016-10-01:

AlsaInfo.txt Edit (30.9 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (227 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (72.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (504 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (73.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (599 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.5 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (24.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (183 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (134.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (122.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-10-01: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2016-10-02:

drwt, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.