constantly freezing on high wifi load

[asgard2]

My device is constantly freezing on high wifi load.

I tested multiple distros and linux kernels.
Such as:
- xubuntu 16.04
- xubuntu 16.10 and the current mainline kernel
- current ubuntu 17.04 daily build
- manjaro
- fedora

It seems to be a general problem with this hardware.
Compared to windows 10, it's not freezing.

Changing /proc/irq/42/smp_affinity to f also did not help.

Device: HP Notebook – 15-ba029ng(X7F58EA)
- RTL8723BE PCIe Wireless Network Adapter
- AMD E2-7110
Regards
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: xubuntu 1901 F.... pulseaudio
 /dev/snd/controlC0: xubuntu 1901 F.... pulseaudio
CasperVersion: 1.379
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
LiveMediaBuild: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: HP HP Notebook
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash ---
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic N/A
 linux-firmware 1.161
Tags: yakkety
Uname: Linux 4.8.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/02/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.17
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 81F5
dmi.board.vendor: HP
dmi.board.version: 66.30
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/02/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F5:rvr66.30:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

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

apport-collect 1647605

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.

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[asgard2 (kamp000x)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 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.9-rc8

[asgard2 (kamp000x)]

@jsalisbury:

I already tested the mainline kernel (v4.9-rc7 - daily build) with xubuntu 16.10 (bug description).

Still the same problem.

[penalvch (penalvch)]

asgard2:
1) Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)?
2) To keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now ) as it is released.

Could you please advise?

[Launchpad Janitor (janitor)]

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