WiFi disconnects suddenly automatic with reason=4 locally_generated=1

Bug #1577516 reported by Ettore Atalan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hi,

I'm experiencing suddenly automatic WiFi disconnects after upgrading to Ubuntu 16.04. Syslog reports "reason=4 locally_generated=1". Ubuntu 15.10 didn't show this problem.

Regards,
Atalanttore
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ben 2016 F.... pulseaudio
CurrentDesktop: LXDE
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2e2e5512-9f35-4996-9c32-4ee11f0ed624
InstallationDate: Installed on 2012-05-05 (1457 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=484a35a0-ae5f-45d9-afa1-982bbb6ef909 ro quiet splash acpi_backlight=vendor vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lp lpadmin netdev plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09QA
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09QA:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Ettore Atalan (atalanttore) wrote :
tags: added: apport-collected xenial
description: updated
Revision history for this message
Ettore Atalan (atalanttore) wrote : AlsaInfo.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : CRDA.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : IwConfig.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : JournalErrors.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : Lspci.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : Lsusb.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : ProcModules.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : PulseList.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : UdevDb.txt

apport information

Revision history for this message
Ettore Atalan (atalanttore) wrote : WifiSyslog.txt

apport information

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
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 v4.6 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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: needs-full-computer-model
Revision history for this message
Ettore Atalan (atalanttore) wrote :

This bug still exists with kernel v4.7-rc2 on my Samsung 300E7A Notebook.

tags: added: kernel-bug-exists-upstream
Revision history for this message
penalvch (penalvch) wrote :

Ettore Atalan, could you please provide the full computer model (ex. NP300E7A-A02UK) as noted on the sticker of the computer itself (not from the Bug Description)?

Revision history for this message
Ettore Atalan (atalanttore) wrote :

Okay, it's a Samsung NP300E7A-A02DE.

Revision history for this message
penalvch (penalvch) wrote :

Ettore Atalan, to clarify, did you upgrade directly from 12.04 to 16.04 or were you on a different release immediately prior to the upgrade to 16.04?

tags: added: kernel-bug-exists-upstream-4.7-rc2
removed: needs-full-computer-model
tags: added: needs-bisect regression-release
Revision history for this message
Ettore Atalan (atalanttore) wrote :

I upgraded to every major version of Ubuntu.

12.04 LTS => 12.10 => 13.04 => 13.10 => 14.04 LTS => 14.10 => 15.04 => 15.10 => 16.04 LTS

Revision history for this message
penalvch (penalvch) wrote :

Ettore Atalan, the next step is to fully commit bisect from kernel 4.2 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

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

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.