bringing up 10ec:8185 wifi module freezes the system

[Rüdiger Kupper]

When 10ec:8185 module is modprobed this causes a complete freeze of the system.

This issue is severe for two reasons:
* My computer is unable to connect to the network via wifi through a native linux driver;
* because 10ec:8185 is modprobed at startup, the liveCD will show a black screen without any error message.

Affected Ubuntu releases: Intrepid, Jaunty, Karmic, Natty, Oneiric, Precise beta 1

Workarounds:
* ndiswrapper:
    * works on Intrepid and Natty but not on Jaunty

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 1: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: default [USB Audio CODEC ], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ruediger 1531 F.... pulseaudio
 /dev/snd/pcmC1D0p: ruediger 1531 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card1.Amixer.info:
 Card hw:1 'default'/'Burr-Brown from TI USB Audio CODEC at usb-0000:00:1d.1-1, full s'
   Mixer name : 'USB Mixer'
   Components : 'USB08bb:2902'
   Controls : 2
   Simple ctrls : 1
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=d1a3595d-1554-4fe1-a3bb-5bda0053418d
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: exone D1562
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-11-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.52
RfKill:

Tags: natty
Uname: Linux 2.6.38-11-generic i686
UpgradeStatus: Upgraded to natty on 2011-04-30 (124 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/24/2003
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 4.06 Rev. 1.06.1562
dmi.board.name: D1562
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D1562
dmi.chassis.type: 6
dmi.chassis.vendor: exone
dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.06.1562:bd09/24/2003:svnexone:pnD1562:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
dmi.product.name: D1562
dmi.sys.vendor: exone
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 1: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ruediger 2345 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card1.Amixer.info:
 Card hw:1 'CODEC'/'Burr-Brown from TI USB Audio CODEC at usb-0000:00:1d.0-2, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB08bb:2902'
   Controls : 2
   Simple ctrls : 1
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=d1a3595d-1554-4fe1-a3bb-5bda0053418d
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: exone D156200
Package: linux (not installed)
PciMultimedia:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-16-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-16-generic N/A
 linux-backports-modules-3.0.0-16-generic N/A
 linux-firmware 1.60
RfKill:

Tags: oneiric running-unity
Uname: Linux 3.0.0-16-generic i686
UpgradeStatus: Upgraded to oneiric on 2012-02-24 (31 days ago)
UserGroups: adm admin audio cdrom dialout floppy lpadmin plugdev sambashare
dmi.bios.date: 04/23/2004
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 4.06 Rev. 1.09.1562
dmi.board.name: D1562
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D1562
dmi.chassis.type: 6
dmi.chassis.vendor: exone
dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
dmi.product.name: D156200
dmi.sys.vendor: exone

[Olivier (olivier-redhat-bugs)]

Created attachment 344269
sosreport of the system

Description of problem:

Ther system experiences hard hang when using WIFI with the rtl8180 kernel module. The system ends in such a state that sysrq is inefficient (sysrq-t, sysrq-m, sysrq-c do nothing) and quite often require a complete electrical unplug for several seconds to be able to reboot.

Console logs or /var/log/message show no oops or kernel backtrace.

Blacklisting the module rtl8180 or removing the Belkin WIFI G PCI card cures the problem but does not help with WIFI connectivity ^_~

Version-Release number of selected component (if applicable):

kernel-PAE-2.6.29.3-140.fc11.i686 (But occurs on older kernel as well, including F10)

How reproducible:

100% reproducible

Steps to Reproduce:

1. Install the Belkin Wireless G dektop PCI card Based on the Realtek 818x
2. Boot the system

Actual results:

System will hang either at login or at logout

Expected results:

System remains stable and functional

Additional info:

The WIFI connection uses hidden ESSID and WPA/WPA2 security. The problem occurs either when NetworkManager connects to the network or when it terminates (logging out from the user session leads to a 100% hang).

Same happens if NetworkManager exits or needs to reconnect. The same hardware works perfectly under Windows with Belkin's provided driver though.

I am attaching the sosreport of the system, unfortunately I am unable to debug this issue much further and I could not come up with a usable workaround for the issue.

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Skippy (skippy-redhat-bugs)]

I can confirm this bug for Fedora 12 with the following wifi card : Zyxel G-302 v3.

For some other reason I cannot achieve a proper install right now so I can confirm only with the live CD, but symptoms are exactly the same as above : boot ok, user session ok, if I click on the NetworkManager icon I can select the network, then connect to it, enter my WEP key, and then the system will freeze (while asking for the keyring password, secondarily). If I don't try to connect, everything works fine but the system won't shutdown (didn't try to logout).

Similar issues happen with Ubuntu, cf https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679

[Sylvain (sylvain-redhat-bugs)]

I too confirm this kernel hang with a TRENDdet TEW-423PI (C1.0R) on a up to date Fedora 12 the only message when manually activating the connection was some "invalid parameter" message when using the GUI
Otherwise when on startup or command line nothing is showing but only the endless hang

BTW this is a blocker on the rescue mode if the interface is checked on as managed by the NetworkManager
My workaround has been to let this card disabled :(
obviously that was not my goal

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[John (john-redhat-bugs)]

Created attachment 410552
rtl8180: fix tx status reporting

[John (john-redhat-bugs)]

http://koji.fedoraproject.org/koji/taskinfo?taskID=2149629

I don't get any such hang on F-12 w/ my cardbus rtl8185 device. However, I did get rather poor performance.

Are you still seeing this hang with the test kernels above?

[Steven (steven-redhat-bugs)]

I just installed f12 on my wife's computer (she finally got frustrated enough with Windows to let me do it), and it hit this bug.

I have the following card:

ZyXEL ZyAIR G-302

From lspci -vv

02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
 Subsystem: ZyXEL Communication Corporation Device 340d
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at 2000 [size=256]
 Region 1: Memory at e8100000 (32-bit, non-prefetchable) [size=512]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: rtl8180
 Kernel modules: rtl8180

Seems to be a race condition. It gets past setting up the wlan0 every other boot or so. Once it is up and running, everything is fine. I tried suspend and resume once, and that locked up on resume too (even though this is a desktop, it should still support s2r).

I'm currently doing a "yum update", I'll report again with the results of the latest kernel.

[Steven (steven-redhat-bugs)]

After doing a "yum update" and updating all packages since the fresh f12 install (which included the kernel package), I have yet to hit this bug.

I've rebooted 4 times and suspend and resumed twice. So far, so good.

[Steven (steven-redhat-bugs)]

Spoke too soon. Seems the race condition is smaller. While showing my wife how to use her box, it locked up on suspend and resume while (I think) initializing the network.

[John (john-redhat-bugs)]

Steven, and logs available? Perhaps you could capture a trace using netconsole (over a wired port)?

[Steven (steven-redhat-bugs)]

John, investigating this further, the lockup seemed to have nothing to do with the network card. It looks like a drm/i915 bug. But it takes out the network too, although I don't know why.

It looks like I'm hitting this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=573177

As far as I can tell from the logs when it locks up now. It does not seem to be related to the wifi nic, but to the video. I don't understand why I lose my wireless on the X lockup. I'm fine on serial. I'll try again with a wired connection, but as far as I'm concerned, it looks like this BZ is done.

I would like a working system before I conclude that though ;-)

[Steven (steven-redhat-bugs)]

Interesting, after pulling the pci wireless card, I can not make X lockup. I wonder if it is related.

[Steven (steven-redhat-bugs)]

Nevermind, I was able to finally reproduce the hang without the wireless card.

[John (john-redhat-bugs)]

I can't recreate any problems -- this driver works reasonably well for me.

[Sylvain (sylvain-redhat-bugs)]

(In reply to comment #14)
> I can't recreate any problems -- this driver works reasonably well for me.
It just means the card you own works fine with it....
Btw do you own a realtek branded one ?
Thanks in advance

[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 839019

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.

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[penalvch (penalvch)]

Rüdiger Kupper, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Rüdiger Kupper (ruediger.kupper)]

Dear Christopher,
this problem persists with Ubuntu Precise beta 1:

WHAT HAPPENS:
With my WLAN card (RTL 8185L chip) stuck into my machine, Ubuntu's boot precess freezes. I need to pyhsically power off my machine (not even SysRq-Keys do work).

WHAT I EXPECT:
Ubuntu boots up normally and I can use my WLAN card. If my card is not supported, Ubuntu still boots up normally, but not WLAN is availabe.

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

apport information

[Rüdiger Kupper (ruediger.kupper)]

The problem persists with the latest upstream kernel.

[penalvch (penalvch)]

Rüdiger Kupper, could you please capture the oops following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ?

[Rüdiger Kupper (ruediger.kupper)]

Chistopher, I've been trying hard to capture *any* useful output, but it seems I can't get anything:

- using linux-crashdump is no good. There's no kernel oops, the system freezes during startup and cannot be reactivated. The backup kernel does not even boot.
- there is no /var/log/kern.log
- there is /var/log/dmesg, but I don't see anything useful in there. I attach the file.
- screen output does not show anything useful either

I did not try netconsole, since I do not think it will yield anything more than what can be seen from /var/log/dmesg.

If I can help any further, please tell me.

[Rüdiger Kupper (ruediger.kupper)]

/var/log/dmesg of the system freezing during bootup with WLAN card plugged in (precise beta 2).

[penalvch (penalvch)]

Rüdiger Kupper, one thing I noticed about the Bug Description:
> Description:
On computers with some rtl818x chip based wifi cards, when module rtl8180 is modprobed this causes a complete freeze of the system.

Let us not turn this into multi-hardware/vendor ID mega bug report, as they tend to be neglected due to being too broad. Hence, this report will only focus on the vendor ID you apported initially 10ec:8185.

[penalvch (penalvch)]

Rüdiger Kupper, could you please report the results following https://wiki.ubuntu.com/DebuggingKernelBoot ?

[Rüdiger Kupper (ruediger.kupper)]

Here is some new information:

- I can boot into recovery mode.
- From there I can modprobe the "rtl8180" module, which works fine.
- lsmod shows that the module is loaded and used by these other modules: "mac80211", "eeprom_93cx6", "cfg80211".
- I then configure the wlan0 interface in /etc/network/interfaces
- As soon as I try to bring up the wlan0 interface (ifup wlan0), the system freezes

This means, the freeze does not occur until I try to bring up the interface. Modprobe is not the point of failure.

[Rüdiger Kupper (ruediger.kupper)]

If we can't find a way to fix the issue, can we at least blacklist the module? This would at least allow the users to boot up a live cd and install precise. Their wifi will not work, but they can then use ndiswrapper to install the windows drivers, which seem to work.

If things stay as they are now, users of the affected wifi cards can' even boot precise. They will get stuck with a black screen and a computer doing nothing.

[Rüdiger Kupper (ruediger.kupper)]

I just confirmed that this issue is still present in 12.10. I suggest st least blacklisting the module for 13.04 so that people can boot their machines.

[Gustavo Carreno (guscarreno)]

This looks like a bug that has been around for quite some time.

I'll bet it's been inherited from kernel 2.4 or 2.6, since the available drivers from Realtek (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=1&PFid=1&Level=6&Conn=5&DownTypeID=3&GetDown=false&Downloads=true#RTL8185L) have 2.4 and 2.6 on the Makefile.

Could it be possible to use that source code and port it to a more 3.x solution?

[penalvch (penalvch)]

Gustavo Carreno, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Rüdiger Kupper (ruediger.kupper)]

I confirm that this issue is still present in 13.04.

[penalvch (penalvch)]

Rüdiger Kupper, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[penalvch (penalvch)]

Eric Shattow, please do not adjust the Tags. Instead, 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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

[Eric Shattow (eshattow)]

Same hardware here:

$ lspci -nn | grep 8185
01:0d.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller [10ec:8185] (rev 20)

$ uname -a
Linux boss 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10) i686 GNU/Linux

Mainline 3.18-rc2 same problems apply. Found a hack / workaround is to wrap iowriteNN with udelay()'s ; or to use ndiswrapper will also make the device functional. Distro should probably blacklist the driver until a proper fix is decided.

See upstream bug report https://bugzilla.kernel.org/show_bug.cgi?id=86861

[penalvch (penalvch)]

Eric Shattow, "Me too!" comments are simply unhelpful. If you want your issue address, then please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/839019/comments/48 .

[Eric Shattow (eshattow)]

Rüdiger Kupper, can you confirm that upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=86861 is what you are experiencing?

[Rüdiger Kupper (ruediger.kupper)]

Eric Shattow, yes, these are the exact symptoms I experience.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Rüdiger Kupper, the lastest Ubuntu release you've advised this issue was reproducible in is EOL as per https://wiki.ubuntu.com/Releases.

Could you please advise if this issue is reproducible in a supported release?

If so, could you please test the latest mainline kernel and advise to the results?

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

[Rüdiger Kupper (ruediger.kupper)]

I do not use the respective hardware any longer, but it still exists. Going to test it if I find the time. Thanks.