I was too fast to post previous message after some 10 minutes of
testing. However a recent driver upgrade from 3.13.0-45-generic to
3.13.0-46-generic (with the same firmware) has apparently solved this
issue for me. At least, dmesg does not contain such errors after an hour
of heavy network usage
I am running Ubuntu 14.04.1 LTS and experiencing this issue (broken wifi
until reconnection, Microcode SW error detected. Restarting
0x2000 in dmesg) on Lenovo G550 which has Intel WiMAX/WiFi Link
5150 with the following configuration: broadcast=yes driver=iwlwifi
I am also seeing this with 3.13.0-24-generic.
** Attachment added: crash.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/944271/+attachment/4294331/+files/crash.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I am seeing the same crash in 14.10, kernel 3.13.0-24-generic
Log + Hardware : https://gist.github.com/sp4ke/5f3ee40a028880da12e9
--
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/944271
I'm seeing this crash on 14.04, running 3.13.0-23-generic. Hardware is
Centrino Advanced-N 6235.
Log here: https://gist.github.com/f6ce150f833b2cef3f21
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I noticed recently this happens ONLY when I start using a bluetooth device.
My system:
09:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow
Peak] (rev 34)
on
HP-ENVY-15-Notebook-PC 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC
2014 x86_64 x86_64 x86_64
This bug is present in upstream (3.13 as of rc7) so I don't think it can
be marked fixed.
$ uname -a
Linux lappy-486 3.13.0-rc7 #3 SMP Fri Jan 10 21:08:47 EST 2014 x86_64 x86_64
x86_64 GNU/Linux
[28625.731410] iwlwifi :02:00.0: Microcode SW error detected. Restarting
0x200.
I have the same problem on the ASUS UX31A (problem is known).
Disabling n-Standard is not really a solution but a very dirty workaround.
This error happens more often if I use Skype.
** Attachment added: log.txt
dmidecode
System Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: UX32VD
Version: 1.0
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION=Ubuntu 13.04
uname -a
Linux damir-laptop 3.8.0-27-generic
9 matches
Mail list logo
