kernel-packages team mailing list archive

[Peter Lomax <peter@xxxxxxxx>]

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)


** Attachment added: "Ubuntu 13.04 1099487"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099487/+attachment/3814915/+files/report.1099487.20130911.log

-- 
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/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