[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-08-04 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-06-05 Thread Heinz Werner
Just stumbled over an article in ct 12/2017 Page 162 (german computer magazin). It says, USB3 can intereference with devices like 2.4Ghz WLAN, USB-receivers. References: White-Paper Intel: http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-05-23 Thread Kai-Heng Feng
Please file a new bug for USB-HDD issue. Probably needs to quirk off the device to make it work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue stuck,

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-05-23 Thread Heinz Werner
Thank you for the tip, Kai-Heng Feng, I will observere what happens, when I remove "pcie_aspm=force". I added it long time ago, Apr 2014. Reason was, that my notebook then, a Dell M2400, sometimes didn't survive resume after standby (1 of 10 times maybe). It just crashed, black screen, X11 dead.

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-05-15 Thread Kai-Heng Feng
See if removing "pcie_aspm=force" helps. Why do you need "i8042.nopnp" and "atkbd.reset"? Most Dell laptop should work out of the box, those kernel parameters are not required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-04-29 Thread Heinz Werner
Hello altogether, I am affected too. From time to time the same error occurs, showing the "queue stuck" and "Hardware restart" messages, while WiFi-connection is not working. It happens then in a loop. I am not running Ubuntu, I am running aptosid with "4.10.0-8.slh.1-aptosid-amd64 #1 SMP PREEMPT

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-03-03 Thread Radek Dostal
Just for information: my girlfriend seem to have the same issue. Updating her Lenovo IdeaPad U430 to kernel 4.8 (HWE stack from 16.04.2) did NOT help. On the other hand, reconfiguring Wi-Fi from 40MHz to 20MHz as described at https://www.mail-archive.com/linux-

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-20 Thread Christopher M. Penalver
noob saibot, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-10 Thread noob saibot
** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue stuck, Microcode SW error detected,

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-10 Thread noob saibot
Nope, I celebrated too early. I still get this error with the updated bios. Apparently less frequently. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2017-02-09 Thread noob saibot
Bios update helped in my case. I had this problem every 5-15 min. First got "Queue stuck" then "Microcode SW error detected" I have the same firmware Loaded firmware version: 16.242414.0 as the OP but a slightly newer kernel: uname -r 4.4.0-59-generic I have a Lenovo Yoga 260 and Network

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2016-10-31 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2016-09-01 Thread Christopher M. Penalver
** Tags added: bios-outdated-1.37 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1615774 Title: iwlwifi queue

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

2016-08-22 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8