iwlwifi: Microcode SW error detected. Restarting 0x2000000

[Jonathan Davies]

This appears to be related to the older bug #200509 on my Lenovo X230.

Since Jan 4th, I'm seeing errors like:

Jan 8 14:33:32 lystena kernel: [10462.742627] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.

Running:

$ sudo modprobe -r iwlwifi; sudo modprobe iwlwifi

...fixes the issue. Attached appears to be one of the first instances of the issue.

Kernel upgrade I can see in my apt logs:

Start-Date: 2012-12-01 07:43:21
Commandline: aptdaemon role='role-commit-packages' sender=':1.1567'
Install: linux-image-extra-3.5.0-19-generic:amd64 (3.5.0-19.30), linux-image-3.5.0-19-generic:amd64 (3.5.0-19.30)
Upgrade: perl:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), perl-base:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), libboost-python1.49.0:amd64 (1.49.0-3.1ubuntu1, 1.49.0-3.1ubuntu1.1), perl-modules:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), libboost-date-time1.49.0:amd64 (1.49.0-3.1ubuntu1, 1.49.0-3.1ubuntu1.1), linux-image-generic:amd64 (3.5.0.18.21, 3.5.0.19.22), libperl5.14:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), linux-libc-dev:amd64 (3.5.0-18.29, 3.5.0-19.30)

-21 kernel was installed on the 18th of December.

[Joseph Salisbury (jsalisbury)]

Hi Jonathan,

As discussed on IRC, if you have time, it would be great if you could test the -18 or -19 kernel to see if it happens there too.

Probably test the -19 kernel first, since that was the last kernel you had running prior to December 18th.

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

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.

[Launchpad Janitor (janitor)]

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

[Cory Coager (ccoager)]

Please reopen this bug, still not resolved on kernel 3.2.0-40. Having issues daily.

[Cory Coager (ccoager)]

[ 6229.471109] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
[ 6229.471121] iwlwifi 0000:03:00.0: Loaded firmware version: 18.168.6.1
[ 6229.471228] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 6229.471234] iwlwifi 0000:03:00.0: Status: 0x0004B2E4, count: 6
[ 6229.471241] iwlwifi 0000:03:00.0: 0x0000198A | ADVANCED_SYSASSERT
[ 6229.471246] iwlwifi 0000:03:00.0: 0x00015920 | uPc
[ 6229.471250] iwlwifi 0000:03:00.0: 0x00015910 | branchlink1
[ 6229.471254] iwlwifi 0000:03:00.0: 0x00015910 | branchlink2
[ 6229.471259] iwlwifi 0000:03:00.0: 0x0000DBEA | interruptlink1
[ 6229.471263] iwlwifi 0000:03:00.0: 0x00000000 | interruptlink2
[ 6229.471267] iwlwifi 0000:03:00.0: 0x0000F1AE | data1
[ 6229.471272] iwlwifi 0000:03:00.0: 0x00000007 | data2
[ 6229.471276] iwlwifi 0000:03:00.0: 0x000001DC | line
[ 6229.471280] iwlwifi 0000:03:00.0: 0xDD012BAC | beacon time
[ 6229.471284] iwlwifi 0000:03:00.0: 0x90A8A454 | tsf low
[ 6229.471289] iwlwifi 0000:03:00.0: 0x000000B8 | tsf hi
[ 6229.471293] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 6229.471297] iwlwifi 0000:03:00.0: 0x7060ACED | time gp2
[ 6229.471301] iwlwifi 0000:03:00.0: 0x00000000 | time gp3
[ 6229.471306] iwlwifi 0000:03:00.0: 0x754312A8 | uCode version
[ 6229.471310] iwlwifi 0000:03:00.0: 0x000000B0 | hw version
[ 6229.471314] iwlwifi 0000:03:00.0: 0x00480303 | board version
[ 6229.471319] iwlwifi 0000:03:00.0: 0x0000001C | hcmd
[ 6229.471323] iwlwifi 0000:03:00.0: CSR values:
[ 6229.471327] iwlwifi 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 6229.471358] iwlwifi 0000:03:00.0: CSR_HW_IF_CONFIG_REG: 0X00480303
[ 6229.471390] iwlwifi 0000:03:00.0: CSR_INT_COALESCING: 0X00000040
[ 6229.471419] iwlwifi 0000:03:00.0: CSR_INT: 0X00000000
[ 6229.471447] iwlwifi 0000:03:00.0: CSR_INT_MASK: 0X00000000
[ 6229.471475] iwlwifi 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
[ 6229.471503] iwlwifi 0000:03:00.0: CSR_GPIO_IN: 0X00000038
[ 6229.471530] iwlwifi 0000:03:00.0: CSR_RESET: 0X00000000
[ 6229.471558] iwlwifi 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
[ 6229.471586] iwlwifi 0000:03:00.0: CSR_HW_REV: 0X000000b0
[ 6229.471614] iwlwifi 0000:03:00.0: CSR_EEPROM_REG: 0X51dc0ffd
[ 6229.471646] iwlwifi 0000:03:00.0: CSR_EEPROM_GP: 0X90000801
[ 6229.471673] iwlwifi 0000:03:00.0: CSR_OTP_GP_REG: 0X00030001
[ 6229.471701] iwlwifi 0000:03:00.0: CSR_GIO_REG: 0X00080042
[ 6229.471729] iwlwifi 0000:03:00.0: CSR_GP_UCODE_REG: 0X000071b8
[ 6229.471757] iwlwifi 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000000
[ 6229.471784] iwlwifi 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[ 6229.471812] iwlwifi 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[ 6229.471841] iwlwifi 0000:03:00.0: CSR_LED_REG: 0X00000058
[ 6229.471873] iwlwifi 0000:03:00.0: CSR_DRAM_INT_TBL_REG: 0X88421140
[ 6229.471901] iwlwifi 0000:03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[ 6229.471928] iwlwifi 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00000...

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

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.

[Cory Coager (ccoager)]

You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed. Please create a new report using "apport-bug".

[Cory Coager (ccoager)]

Please stop closing this ticket. If you need more information than use the duplicate bug attached to this one, #1102999.

[Joseph Salisbury (jsalisbury)]

This bug is being automatically closed because the apport data, specific to your system, is missing. Would it be possible for you to run the following command:

apport-collect 1099487

[Cory Coager (ccoager)]

I don't have permission to update the ticket via apport,

You are not the reporter or subscriber of this problem report, or the
report is a duplicate or already closed. Please create a new report using
"apport-bug".

On Wed, Apr 10, 2013 at 3:30 PM, Joseph Salisbury <
<email address hidden>> wrote:

> This bug is being automatically closed because the apport data, specific
> to your system, is missing. Would it be possible for you to run the
> following command:
>
> apport-collect 1099487
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1102999).
> https://bugs.launchpad.net/bugs/1099487
>
> Title:
> iwlwifi: Microcode SW error detected. Restarting 0x2000000
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> This appears to be related to the older bug #200509 on my Lenovo X230.
>
> Since Jan 4th, I'm seeing errors like:
>
> Jan 8 14:33:32 lystena kernel: [10462.742627] iwlwifi 0000:03:00.0:
> Microcode SW error detected. Restarting 0x2000000.
>
> Running:
>
> $ sudo modprobe -r iwlwifi; sudo modprobe iwlwifi
>
> ...fixes the issue. Attached appears to be one of the first instances
> of the issue.
>
> Kernel upgrade I can see in my apt logs:
>
> Start-Date: 2012-12-01 07:43:21
> Commandline: aptdaemon role='role-commit-packages' sender=':1.1567'
> Install: linux-image-extra-3.5.0-19-generic:amd64 (3.5.0-19.30),
> linux-image-3.5.0-19-generic:amd64 (3.5.0-19.30)
> Upgrade: perl:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), perl-base:amd64
> (5.14.2-13, 5.14.2-13ubuntu0.1), libboost-python1.49.0:amd64
> (1.49.0-3.1ubuntu1, 1.49.0-3.1ubuntu1.1), perl-modules:amd64 (5.14.2-13,
> 5.14.2-13ubuntu0.1), libboost-date-time1.49.0:amd64 (1.49.0-3.1ubuntu1,
> 1.49.0-3.1ubuntu1.1), linux-image-generic:amd64 (3.5.0.18.21, 3.5.0.19.22),
> libperl5.14:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), linux-libc-dev:amd64
> (3.5.0-18.29, 3.5.0-19.30)
>
> -21 kernel was installed on the 18th of December.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099487/+subscriptions
>

[Cory Coager (ccoager)]

I don't have permission to update the ticket via apport,

You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed. Please create a new report using "apport-bug".

[Joseph Salisbury (jsalisbury)]

Ahh, I see.

An alternative would be to run:

apport-bug --save /tmp/report.1099487 linux

Then you could attach the file report.1099487 to the bug.

[Cory Coager (ccoager)]

Here is the apport-bug report.

[Nikolaj Sheller (nikolajsheller)]

See on Linux 3.8.0-26-generic #38-Ubuntu SMP Mon Jun 17 21:43:33 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux:

Jul 10 13:17:09 AsusCider kernel: [ 328.721553] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
Jul 10 13:17:09 AsusCider kernel: [ 328.721565] iwlwifi 0000:03:00.0: CSR values:
Jul 10 13:17:09 AsusCider kernel: [ 328.721569] iwlwifi 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul 10 13:17:09 AsusCider kernel: [ 328.721602] iwlwifi 0000:03:00.0: CSR_HW_IF_CONFIG_REG: 0X00484b00
Jul 10 13:17:09 AsusCider kernel: [ 328.721634] iwlwifi 0000:03:00.0: CSR_INT_COALESCING: 0X0000ff40
Jul 10 13:17:09 AsusCider kernel: [ 328.721663] iwlwifi 0000:03:00.0: CSR_INT: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.721694] iwlwifi 0000:03:00.0: CSR_INT_MASK: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.721722] iwlwifi 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.721751] iwlwifi 0000:03:00.0: CSR_GPIO_IN: 0X00000038
Jul 10 13:17:09 AsusCider kernel: [ 328.721779] iwlwifi 0000:03:00.0: CSR_RESET: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.721807] iwlwifi 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 10 13:17:09 AsusCider kernel: [ 328.721839] iwlwifi 0000:03:00.0: CSR_HW_REV: 0X000000b0
Jul 10 13:17:09 AsusCider kernel: [ 328.721870] iwlwifi 0000:03:00.0: CSR_EEPROM_REG: 0X17900ffd
Jul 10 13:17:09 AsusCider kernel: [ 328.721903] iwlwifi 0000:03:00.0: CSR_EEPROM_GP: 0X90000801
Jul 10 13:17:09 AsusCider kernel: [ 328.721937] iwlwifi 0000:03:00.0: CSR_OTP_GP_REG: 0X00030001
Jul 10 13:17:09 AsusCider kernel: [ 328.721970] iwlwifi 0000:03:00.0: CSR_GIO_REG: 0X00080042
Jul 10 13:17:09 AsusCider kernel: [ 328.722004] iwlwifi 0000:03:00.0: CSR_GP_UCODE_REG: 0X000063e0
Jul 10 13:17:09 AsusCider kernel: [ 328.722037] iwlwifi 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.722069] iwlwifi 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.722096] iwlwifi 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.722125] iwlwifi 0000:03:00.0: CSR_LED_REG: 0X00000058
Jul 10 13:17:09 AsusCider kernel: [ 328.722157] iwlwifi 0000:03:00.0: CSR_DRAM_INT_TBL_REG: 0X8829c6be
Jul 10 13:17:09 AsusCider kernel: [ 328.722185] iwlwifi 0000:03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 10 13:17:09 AsusCider kernel: [ 328.722214] iwlwifi 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 10 13:17:09 AsusCider kernel: [ 328.722242] iwlwifi 0000:03:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 10 13:17:09 AsusCider kernel: [ 328.722270] iwlwifi 0000:03:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
Jul 10 13:17:09 AsusCider kernel: [ 328.722274] iwlwifi 0000:03:00.0: FH register values:
Jul 10 13:17:09 AsusCider kernel: [ 328.722315] iwlwifi 0000:03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X29dd...

[Joseph Salisbury (jsalisbury)]

@Jonathan, Can you confirm if you are still seeing this bug or not?

[reddy (reddy)]

I still see the issue on one of my systems, which is in fact pure Debian Squeeze updated to recent 3.10.1 kernel and firmware-iwlwifi from squeeze-backports, but this is not specific to any distribution, I think.

dmesg logs attached. System information below:

# cat /etc/debian_version
6.0.7

# uname -a
Linux nas 3.10.1-031001-generic #201307131550 SMP Sat Jul 13 19:59:34 UTC 2013 i686 GNU/Linux

# lcpci
...
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300

# dpkg -l | grep firmware-iwlwifi
ii firmware-iwlwifi 0.36+wheezy.1~bpo60+1 Binary firmware for Intel PRO/Wireless 3945 and 802.11n cards

[Cory Coager (ccoager)]

I too can confirm this is still happening on kernel 3.2.0-40 on Ubuntu 12.04.

[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 v3.11 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.11-rc5-saucy/

[Mike (pmike2001)]

Same bug with Linux kernel 3.11.rc7 (3.11.0-031100rc7-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc7-saucy/, x86_64).

>lspci
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

>cat /etc/hostapd/hostapd.conf
interface=wlan0
ssid=MySSID
hw_mode=g
wpa_pairwise=CCMP
wpa=2
wpa_passphrase=MyPASSWORD
channel=7

WiFi works as AP w/o errors about 2 days before the fault.

[Peter Lomax (h-peter-c)]

Wed Sep 11 10:49:55 BST 2013

ubuntu 13.04 - Error

iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000.

plomax@plomax-Latitude-E6410:/etc$ date
Wed Sep 11 10:49:55 BST 2013

plomax@plomax-Latitude-E6410:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu 13.04"

plomax@plomax-Latitude-E6410:/etc$ cat /etc/debian_version
wheezy/sid

plomax@plomax-Latitude-E6410:~$ uname -a
Linux plomax-Latitude-E6410 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:52:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

plomax@plomax-Latitude-E6410:~$ lspci|grep -i Net
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

plomax@plomax-Latitude-E6410:/etc$ dpkg -l | grep wifi
ii libnm-gtk-common 0.9.8.0-1ubuntu2 all network management framework (common files for wifi and mobile)
ii libnm-gtk0 0.9.8.0-1ubuntu2 amd64 network management framework (GNOME dialogs for wifi and mobile)

[Sharath (sharathcshekhar)]

I have this issue on my Dell XPS 14 too. I have tried all combinations of driver options and none seem to work.
This is a related bug. I am not sure if it's a exact duplicate.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226728

[bibon (bibonz)]

# date
vendredi 6 décembre 2013, 19:09:05 (UTC+0100)

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10

# cat /etc/debian_version
wheezy/sid

# uname -a
Linux lenouveau 3.11.0-15-generic #22-Ubuntu SMP Mon Dec 2 23:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

#dpkg -l | grep wifi
ii libnm-gtk-common 0.9.8.0-1ubuntu5 all network management framework (common files for wifi and mobile)
ii libnm-gtk0 0.9.8.0-1ubuntu5 amd64 network management framework (GNOME dialogs for wifi and mobile)

# dpkg -l | grep -i wpa
ii wpasupplicant 1.0-3ubuntu2.1 amd64 client support for WPA and WPA2 (IEEE 802.11i)

Dec 6 17:55:54 lenouveau kernel: [ 320.971559] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Dec 6 17:55:54 lenouveau kernel: [ 320.971570] iwlwifi 0000:02:00.0: CSR values:
Dec 6 17:55:54 lenouveau kernel: [ 320.971575] iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Dec 6 17:55:54 lenouveau kernel: [ 320.971583] iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X00489204
Dec 6 17:55:54 lenouveau kernel: [ 320.971590] iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X0000ff40
Dec 6 17:55:54 lenouveau kernel: [ 320.971597] iwlwifi 0000:02:00.0: CSR_INT: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971603] iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971610] iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971616] iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971623] iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971629] iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Dec 6 17:55:54 lenouveau kernel: [ 320.971636] iwlwifi 0000:02:00.0: CSR_HW_REV: 0X00000144
Dec 6 17:55:54 lenouveau kernel: [ 320.971642] iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971649] iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X80000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971655] iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0X803a0000
Dec 6 17:55:54 lenouveau kernel: [ 320.971662] iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X00080044
Dec 6 17:55:54 lenouveau kernel: [ 320.971668] iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971674] iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971680] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971687] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Dec 6 17:55:54 lenouveau kernel: [ 320.971693] iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000060
Dec ...

[bibon (bibonz)]

On a LENOVO IdeaPad U330P

# lspci|grep Net
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)

[Mike (pmike2001)]

Kernel 3.12.3-031203-generic is affected too. Probably firmware error.

[bibon (bibonz)]

$sudo modprobe -r iwlmvm; sudo modprobe iwlmvm

is a temporary fix on ubuntu

$ lsmod |grep iwl
iwlmvm 161378 0
iwlwifi 165675 1 iwlmvm
mac80211 597268 1 iwlmvm
cfg80211 480503 3 iwlwifi,mac80211,iwlmvm

[penalvch (penalvch)]

Jonathan Davies, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release while ethernet connected from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

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

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc6

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.

[Mike (pmike2001)]

This bug is reproducible with lastest kernel (3.13-rc6 at the moment). Part of syslog with relevant lines attached.

uname -a
>Linux h1 3.13.0-031300rc6-generic #201312291935 SMP Mon Dec 30 00:37:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Mike, thank you for your comment. 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 a Ubuntu repository 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
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.

Thank you for your understanding.

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

[Jaakko Kyro (jkyro-korjaussarja)]

I saw this one too on my Lenovo IdeaPad u330p.

However, I installed the 3.13.0-rc8 mainline build and the issue seems to be gone.

jasu@jIdeaPad-U330p:~$ uname -r
3.13.0-031300rc8-generic
jasu@IdeaPad-U330p:~$

so I guess this is Fixed upstream?

[penalvch (penalvch)]

Jaakko Kyro, thank you for your comment. 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 a Ubuntu repository 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
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.

Thank you for your understanding.

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

[Launchpad Janitor (janitor)]

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

[Mike (pmike2001)]

The bug still have rare ocassions with kernel 3.14.2

uname -a
>Linux h1 3.14.2-031402-generic #201404262053 SMP Sun Apr 27 00:54:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Mike, thank you for your comment. 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 a Ubuntu repository 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
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.

Thank you for your understanding.

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