NMI received for unknown reason a0 on CPU 0

[Albert Cardona]

Thinkpad T60p new from last January, core2 duo 2.33Ghz
Ubuntu 7.04 dist-upgraded to the latest.

The laptop is working great. And yet, about once a week or so I get this message in my terminals:

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] Dazed and confused, but trying to continue

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] Dazed and confused, but trying to continue

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] You have some hardware problem, likely on the PCI bus.

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] You have some hardware problem, likely on the PCI bus.

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] Uhhuh. NMI received for unknown reason a0 on CPU 0.

Message from syslogd@pad at Thu May 24 21:40:06 2007 ...
pad kernel: [264571.564000] Uhhuh. NMI received for unknown reason a0 on CPU 0

[SJ (meta-sj)]

I have the same problem on my Thinkpad x60s. It's annoying, and happens more than once a week. It may or may not be tied to the machine freaking out about wireless & its ath0 card; both happen regularly and seem to have a vague time connection.

SJ

[SJ (meta-sj)]

Answer 5537 seems to be relevant: https://answers.launchpad.net/ubuntu/+question/5537

[Sam Hathaway (sam.hathaway)]

This happened to me when I left my ThinkPad Z60m on the couch, raising the GPU temperature to 80 deg.F. or so. This error was accompanied by screen corruption. I'm keeping the machine off the couch and haven't seen it since.

[Sam Hathaway (sam.hathaway)]

Um, I meant 80 deg.C. Sorry about that.

[Jesse Buchanan (buchanan-jesse-deactivatedaccount)]

I had this happen for the only time this morning. Unlikely my temperatures were that bad, I only have a puny Intel 945GM card in my Thinkpad T60.

I'm also running madwifi svn since the ath_hal module which ships with Feisty does not work with my AR5418 card. It does seem like the wireless is related somehow - whether the cause or the effect I'm not sure.

I have far more details here:

http://ubuntuforums.org/showthread.php?p=3018229#2

[Fábio Barbosa (tentacoesdosilencio)]

Hi there.

I'm running Ubuntu on dual-boot with Windows XP on my Samsung NP-R50 laptop, Intel Centrino 1,73Ghz, 512 MB (well, right now my Ubuntu says I have 502 MB, go figure), 48 GB of harddisk, ATI Mobility Radeon X300. I've been observing the same problem you mentioned since yesterday. Better said, the message goes like this and appears at boot time:

"Uhhuh. NMI received for unknown reason a1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue".

The last events before my PC complained about being "dazed and confused" were some tweaks to my xorg.conf and the installation of Beryl, Kiba-dock and AWN (these last two from third-party repos), for I was trying to see which one worked best. Right now I'm with AWN, but what's important is that the Update Manager started to mention there were some updates to Compiz which I was not able to do, at least not integrally. After a partial update which did not come to its end, Synaptic reported I could not install nor remove any program further on, which was solved after I typed "sudo apt-get install -f" in a terminal. Synaptic was not corrupted anymore, but the newer updates of Compiz got installed too. Anyway, I did not worry about it. Later on I had to do a force reboot after a crash (Beryl, you know), and on the reboot I had that message you reported. I only got to understand what was written after several crashes, because the message disappeared in a fraction of seconds and I only could read parts of it each time.

I still don't think this is a real hardware issue. In my opinion (which is useless in actually solving the problem, but anyway I don't have enough knowledge to do so entirely on my own), the answer might be or on the xorg.conf configuration, or on a corrupted file, or on some conflict between libraries (BTW, I uninstalled the newer Compiz and reinstalled the version that comes with Feisty, after deactivating the third-party repos, but that did not solve the issue right away). This annoys me, since it is almost like a hit or a miss. I can also confirm it did not present that error message after the first today's boot, better said, after the PC was off for some hours. The error repeated itself again later and now it does not appear anymore after I made some changes in my current configuration, except maybe in some system crash, after which the following reboots show an error again.

Here is my dmesg after a clean boot:

[ 0.000000] Linux version 2.6.20-16-generic (root@terranova) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Thu Jun 7 20:19:32 UTC 2007 (Ubuntu 2.6.20-16.29-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] sanitize start
[ 0.000000] sanitize end
[ 0.000000] copy_e820_map() start: 0000000000000000 size: 000000000009f800 end: 000000000009f800 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000000009f800 size: 0000000000000800 end: 00000000000a0000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000d0000 size: 0000000000008000 end: 00000000000d8000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000dc000 size: 0000000000024000...

[Remove Me (remove-me)]

Me too. Lenovo Thinkpad T43p. Tried with vanilla v2.6.22, v2.6.23-rc3. With beryl+emerald.
It _looks_ like it is related to heavy graphics operations.

Xorg.0.log, messages, and the configs for both kernels attached.

[Remove Me (remove-me)]

Err, it says a different reason for the NMI:

  PCI: Setting latency timer of device 0000:00:01.0 to 64
  assign_interrupt_mode Found MSI capability
  Allocate Port Service[0000:00:01.0:pcie00]
  Allocate Port Service[0000:00:01.0:pcie03]
Uhhuh. NMI received for unknown reason b1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
  PCI: Setting latency timer of device 0000:00:1c.0 to 64
  assign_interrupt_mode Found MSI capability

Additionally, lspci -v output for that thinkpad

[Jesse Buchanan (buchanan-jesse-deactivatedaccount)]

When I had the madwifi SVN drivers installed, some time after suspend (2 minutes? 3 days?) it would kill my wireless connection with:

[224591.060000] wifi0: rx FIFO overrun; resetting
[224593.612000] wifi0: rx FIFO overrun; resetting
[224595.728000] wifi0: rx FIFO overrun; resetting
[224598.384000] wifi0: rx FIFO overrun; resetting
[224600.320000] wifi0: rx FIFO overrun; resetting
[224601.848000] wifi0: rx FIFO overrun; resetting
[224603.812000] wifi0: rx FIFO overrun; resetting
[224606.468000] wifi0: rx FIFO overrun; resetting

I could recover the wireless by suspending and waking up the Thinkpad again.

Keep in mind I'm using the AR5418 which is not supported by the stock Feisty madwifi drivers, and I needed to use SVN to make it work at all.

I have not received this message once since "upgrading" from Madwifi wireless drivers to ndiswrapper. Nor has my connection gone down, nor have I experienced any of the other ill effects of using madwifi with the AR5418 card (missing APs, random disconnections, etc.)

Not a perfect solution, of course, but I'd totally forgotten about this bug since moving to ndiswrapper.

[Jesse Buchanan (buchanan-jesse-deactivatedaccount)]

PS: Of course, directly before the overruns was:

[221515.800000] Uhhuh. NMI received for unknown reason b0 on CPU 0.
[221515.800000] You have some hardware problem, likely on the PCI bus.
[221515.800000] Dazed and confused, but trying to continue

[Thiago Teixeira (tvst)]

I got the same three lines today when my computer was idle. I had never seen that before. This Thinkpad T60 has had ubuntu installed on it since day 1, first with 6.10, now 7.04. I always ran XGL (I have an ATI card, bleh) and beryl or compiz. The only thing that changed lately is that I have had an sshfs folder for the past couple of days. I don't think that's the problem, though, since no-one else here mentioned it...

[Thiago Teixeira (tvst)]

I forgot to mention that, like many people here, I also have the default Atheros drivers from the Ubuntu repositories.

[Manuel (manuel-schulte)]

Hi all,

I have an Acer Aspire 1802WSMI, 2Go RAM, ATI X600 Mobility, Wifi (NDISWrapper), Pentium 4 HT 3.0GHz, Ubuntu Feisty.

I had the same problem; Although freezed (as described in previous posts) sometimes the computer was still remotely (ssh...) accessible sometimes not.

Though it did not entirely solved the issue, this helped:
1/ add kernel directive "noapic" in the kernel's startup options (/boot/grub/menu.lst).
2/ stop using Beryl...

Since I did 1/; the problem never occurred when not running Beryl!!!
When using Beryl, it still occurs, but far less frequently.

SIDE EFFECT: sometimes, the synaptic hardware (touchpad & laptop's keyboard) do not initialise properly at boot time! As a result, I end up in front the GDM screen without being able to log in or do anything whatsoever (no keyboard). Luckily, as I'm using an external usb mouse, I still have some control and I'm able to reboot. Note that sometimes I need to do it several times before it succeeds to initialise the synaptic hardware... This problem occurs almost systematically when I have my external usb HDD connected to the laptop. Unplugging the HDD helps reducing the frequency of this nasty side effect.
For now I live with this problem because I prefer it to random freezes...

Hope this will help.
Cheers,
Manu

[Anthony Campbell (ac-acampbell)]

I have recently been getting a similar message, except that it's b1 not a0, when recovering from suspend to disk on a Thinkpad Z61M. This is on Debian Sid (Sidux). It does not occur with Ubuntu 6.10 and I think, though I'm not sure, that it does not happen if I don't have X running.

I don't think it ever happened before about a week or 10 days ago but I can't relate it to any particular change. I have fglrx but removing this does not prevent it.

It doesn't happen every time I suspend to disk; I can sometimes do it once or twice but then the problem returns. However, apart from the worrying message everything else seems to be in order and working as normal; there are no crashes.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[wfaust (junk-coloraid)]

I also have a T60 running 24h/7d. From my experience, there seems to be problems with various kernels at least up to 2.6.26 and Thinkpads and the problems are not specific to Ubuntu. I do use fglrx (no beryl) and crashes appear with a quiet blank screen. I nearly always get the NMI crash after some hours backing up large amounts of data to an external USB drive. There are also various IRQ problems with eSata and modem PCI Express/PCMCIA cards. I am currently testing various boot options ( pci=assign-busses seems to be help at least with the cards but not the NMI crash, I am currently testing noirq and noapic as option).

When using cd /proc/interrupts I do see that one USB and fglrx use the same interupt and maybe that is a problem for one of the drivers (either USB or fglrx):

cat interrupts
           CPU0 CPU1
  0: 48252 1 IO-APIC-edge timer
  1: 174 0 IO-APIC-edge i8042
  3: 100 0 IO-APIC-edge serial
  4: 165 0 IO-APIC-edge serial
  7: 0 0 IO-APIC-edge parport0
  8: 10 0 IO-APIC-edge rtc
  9: 313 210584 IO-APIC-fasteoi acpi
 12: 13210 0 IO-APIC-edge i8042
 14: 20878 0 IO-APIC-edge libata
 15: 0 0 IO-APIC-edge libata
 16: 2 0 IO-APIC-fasteoi uhci_hcd:usb1, yenta, fglrx[0]@PCI:1:0:0
 20: 756632 0 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb5
 21: 115 454 IO-APIC-fasteoi uhci_hcd:usb3, HDA Intel
 22: 43 248232 IO-APIC-fasteoi uhci_hcd:usb4, sata_sil24
218: 684 17101 PCI-MSI-edge eth0
219: 19292 57607 PCI-MSI-edge ahci
NMI: 0 0
LOC: 451630 474874
ERR: 0
MIS: 0

Maybe someone else has similar experience here?

[Nick HS (nickhs)]

I can confirm this still happens on 8.10 with 2.6.27-8-generic

[Anthony Campbell (ac-acampbell)]

I'm still following this thread but the problem went away for me about a year ago after I switched from Sidux to standard Debian (Sid).

What I did notice, when it was still happening, is that it always occurred after I started X from a terminal with startx. Since Ubuntu boots directly into Gnome I suppose you would not realize this.

[Nick HS (nickhs)]

Output of uname -a

[Nick HS (nickhs)]

Output of cat /proc/version_signature

[Nick HS (nickhs)]

Output if lspci -vvnn

[Leann Ogasawara (leannogasawara)]

Nick HS, can you attach an updated dmesg output which captures the error messages for the most recent Intrepid kernel? Thanks.

[Nick HS (nickhs)]

The error is not reported in dmesg as far as I can tell, however the system becomes completely unresponsive after the error. Attached is the syslog where the error occurs (around Dec 11 17:16:45).

[Nick HS (nickhs)]

Running 2.6.27-10-generic (in intrepid-proposed) seems to have stopped the error.

[Leann Ogasawara (leannogasawara)]

Thanks for the update Nick HS. The kernel in intrepid-proposed sounds promising then. Can anyone else test the 2.6.27-10 kernel in intrepid-proposed? @Albert Cardone, since you are the original bug reporter, I'd be particularly interested in hearing back from you. To test the kernel in intrepid-proposed do the following:

1) cd /etc/apt/sources.list.d
2) create a file "intrepid-proposed.list" which contains the following two lines (sudo vim intrepid-proposed.list):

deb http://archive.ubuntu.com/ubuntu/ intrepid-proposed main
deb-src http://archive.ubuntu.com/ubuntu/ intrepid-proposed main

3) sudo apt-get update
4) sudo apt-get install linux-image-2.6.27-10-generic
5) sudo rm /etc/apt/sources.list.d/intrepid-proposed.list
6) sudo apt-get update

Steps 5 and 6 basically undo the enabling of intrepid-proposed. Of course you'll finally need to reboot into the 2.6.27-10.20 kernel to test. Please let us know your results. Thanks.

[Nick HS (nickhs)]

I had the error popup again today, however it is much, much more stable then before

[Nick HS (nickhs)]

Error does not appear in 2.6.28-6-generic with Jaunty.

[Manuel (manuel-schulte)]

Hi,

As far as I'm concerned, that error didn't appeared since Hardy Heron on my
laptop (Acer Aspire WSMI 1802 / 1800 series). And it never appeared with my
other pc's (ranging from old Pentium II / III and recent Core2Duo's).
I remain convinced (imho) that the cause was not purely kernel related, but
rather a combination of hardware / drivers hiccups.

In the time I signalled the problem, I could almost certainly provoke it by
using compiz (advanced effects) / firefox and that on my P4 / ATI Radeon
mobility (X600) video card base laptop. (Note: with the free Radeon driver
as with the non free fgrlx driver made no difference).

Deactivating compiz did vastly reduced the occurence of the error. At that
time Compiz was also far least stable has it has become... it may also be
related, although it was certainly not the only cause for deactivate it only
reduced the frequency of occurrence of the error.

Cheers,
Manuel

2009/2/12 Nick HS <email address hidden>

> Error does not appear in 2.6.28-6-generic with Jaunty.
>
> --
> NMI received for unknown reason a0 on CPU 0
> https://bugs.launchpad.net/bugs/116752
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Mak-Fan (dmakfan)]

Just another data point, I just did a fresh install of 8.10 onto a T43p thinkpad and I get this problem too. I am not using the ATI restricted drivers (they won't activate... seperate issue I guess).

Unfortunately, this makes 8.10 pretty useless on my thinkpad.

[blackmx (net-surf)]

I have ubuntu 9.04 on sony vaio VGN-CR11Z/R and on shut-down show me this message: " Uhhuh. NMI received for unknown reason a0 on CPU 0"

[David Mak-Fan (dmakfan)]

I noticed a little wihle back that sometimes it works, and when it does, Bluetooth isn't working. So I turned off the integrated Bluetooth controller in the BIOS, and it's been suspending fine now (I've only been testing for about a day now though :) ). No Bluetooth though, but I'll take suspend over BT for now.

[TJ (tj)]

David, thank-you for that revelation.

That indicates that the Bluetooth device-driver might not be doing everything it should when handling the PM suspend event, or it might be that the hardware is doing something unexpected that is probably handled as a quirk in Windows drivers (I assume the same doesn't affect Windows?).

Because the reports cover several systems and devices I don't think we are going to be able to easily determine if there is a common cause, or just a common symptom.

[TJ (tj)]

NMI is non-maskable interrupt. It is usually caused by a memory parity error.

The obvious question is, has the memory been thoroughly tested or alternative known-good modules been tried. The linkage to devices tends to indicate RAM is fine but it would be good if we could authoritatively rule it out.

The alternative is that the devices are somehow messing with the system bus.

The kernel handles it in
arch/x86/kernel/traps.c::mem_parity_error():
{
 printk(KERN_EMERG
  "Uhhuh. NMI received for unknown reason %02x on CPU %d.\n",
   reason, smp_processor_id());

 printk(KERN_EMERG
  "You have some hardware problem, likely on the PCI bus.\n");

#if defined(CONFIG_EDAC)
 if (edac_handler_set()) {
  edac_atomic_assert_error();
  return;
 }
#endif

 if (panic_on_unrecovered_nmi)
  panic("NMI: Not continuing");

 printk(KERN_EMERG "Dazed and confused, but trying to continue\n");

 /* Clear and disable the memory parity error line. */
 reason = (reason & 0xf) | 4;
 outb(reason, 0x61);
}

[TJ (tj)]

I found this LKML commentary from 2003. I think the general idea still applies so I'll add it as reference material:

"One way to cause an intermittent NMI is by having power management enabled
with devices that don't support it. They see the world caving in when power
goes away and sometimes generate an NMI."

[John Gilmore (gnu-gilmore)]

I get "Uhhuh. NMI received for unknown reason a1 on CPU 0." (and the other two lines) the first time I tried booting Ubuntu Karmic UNR *beta* release (from a USB-attached SD card) on Dell Mini 10v netbook. This beta uses kernel 2.6.31-11-generic.
The netbook doesn't have bluetooth. There might be bad parity in memory, but I've never seen this happen before (and if
it saw bad parity, why didn't it report the address of the error, and kill the process that was using the memory???) This netbook has a Broadcom wifi chip that is only halfassed supported.

[papukaija (papukaija)]

Confirming in Lucid.

[Marco Ciampa (ciampix)]

Confirmed in Lucid 10.04.1 2.6.32-24-generic (i386) with a desktop computer AMD Athlon 64 3500+ & ATI RV370 (Radeon X300SE) without any wireless network (only integrated SiS 190 ethernet)

[matyas (albertmatyi)]

Confirmed. It happens most frequently after hibernation - after a using it for ~5-10min. But also in every 30hrs of normal uptime (/w sleep)

OS: ubuntu 10.04 2.6.32-25 x86
IBM/lenovo Thinkpad T60

[Neo23x0 (neo-x)]

Same problem here.
Ubuntu 10.10 (upgrade from 10.04) on Thinkpad T60 with ATI graphic card.
Linux ubuntu 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 GNU/Linux

Its the only thing that still bothers me about my Ubuntu installation and its the worst I had to face .. ever.

I tried almost everything:
- ACPI settings (BIOS)
- TLP (Software to handle Thinkpad ACPI settings)
- Pulse Audio deactivation and use of ALSA again .... fixed it for a long time I thought
- WLAN ?? tried several drivers .. still an open point
- ATI graphic card ... I am using the GPL drivers with "options radeon modeset=0"

Dec 16 11:53:09 ubuntu kernel: [10378.753076] padlock: VIA PadLock not detected.
Dec 16 11:55:17 ubuntu kernel: [10506.679450] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Dec 16 11:58:48 ubuntu kernel: [10717.542329] device usb0 entered promiscuous mode
...
Dec 16 13:37:03 ubuntu kernel: [16613.004065] Uhhuh. NMI received for unknown reason b1 on CPU 0.
Dec 16 13:37:03 ubuntu kernel: [16613.004073] You have some hardware problem, likely on the PCI bus.
Dec 16 13:37:03 ubuntu kernel: [16613.004078] Dazed and confused, but trying to continue
Dec 16 13:37:36 ubuntu kernel: [16645.625938] iwl3945 0000:03:00.0: Card state received: HW:Kill SW:On
Dec 16 13:37:36 ubuntu kernel: [16645.664053] iwl3945 0000:03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x040003DD

I hope that this issue will be fixed in newer kernel versions.
It pretty disturbing during presentations ... and work in general.

[Neo23x0 (neo-x)]

Closer to the source of the problem.
I deactivated the internal WLAN card of my Thinkpad T60 in BIOS configuration and used a external USB-Card for about 3 weeks without any freeze. While I was working on some virtual machines copied from external hard disks it froze again.

I checked the kern.log and found:

Jan 2 11:53:50 ubuntu kernel: [ 1443.498163] Initializing USB Mass Storage driver...
Jan 2 11:53:50 ubuntu kernel: [ 1443.498532] scsi6 : usb-storage 1-5:1.0
Jan 2 11:53:50 ubuntu kernel: [ 1443.498731] usbcore: registered new interface driver usb-storage
Jan 2 11:53:50 ubuntu kernel: [ 1443.498734] USB Mass Storage support registered.
Jan 2 11:53:51 ubuntu kernel: [ 1444.501178] scsi 6:0:0:0: Direct-Access WDC WD50 00AAKS-00YGA0 PQ: 0 ANSI: 2
Jan 2 11:53:51 ubuntu kernel: [ 1444.502002] sd 6:0:0:0: Attached scsi generic sg2 type 0
Jan 2 11:53:51 ubuntu kernel: [ 1444.506387] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Jan 2 11:53:51 ubuntu kernel: [ 1444.509534] sd 6:0:0:0: [sdb] Write Protect is off
Jan 2 11:53:51 ubuntu kernel: [ 1444.509539] sd 6:0:0:0: [sdb] Mode Sense: 38 00 00 00
Jan 2 11:53:51 ubuntu kernel: [ 1444.509543] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 11:53:51 ubuntu kernel: [ 1444.512893] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 11:53:51 ubuntu kernel: [ 1444.512904] sdb: sdb1
Jan 2 11:53:51 ubuntu kernel: [ 1444.526780] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 11:53:51 ubuntu kernel: [ 1444.526789] sd 6:0:0:0: [sdb] Attached SCSI disk

Jan 2 13:06:19 ubuntu kernel: [ 5793.020774] WARNING! power/level is deprecated; use power/control instead
Jan 2 13:06:20 ubuntu kernel: [ 5793.107742] usb 1-5: USB disconnect, address 6
Jan 2 13:06:45 ubuntu kernel: [ 5818.089093] usb 1-5: new high speed USB device using ehci_hcd and address 7
Jan 2 13:06:46 ubuntu kernel: [ 5819.067943] scsi7 : usb-storage 1-5:1.0
Jan 2 13:06:46 ubuntu kernel: [ 5819.068341] usbcore: registered new interface driver ums-cypress
Jan 2 13:06:47 ubuntu kernel: [ 5820.068602] scsi 7:0:0:0: Direct-Access WDC WD16 00BEVE-11UYT0 0000 PQ: 0 ANSI: 0
Jan 2 13:06:47 ubuntu kernel: [ 5820.075311] sd 7:0:0:0: Attached scsi generic sg2 type 0
Jan 2 13:06:47 ubuntu kernel: [ 5820.078521] sd 7:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Jan 2 13:06:47 ubuntu kernel: [ 5820.079597] sd 7:0:0:0: [sdb] Write Protect is off
Jan 2 13:06:47 ubuntu kernel: [ 5820.079605] sd 7:0:0:0: [sdb] Mode Sense: 27 00 00 00
Jan 2 13:06:47 ubuntu kernel: [ 5820.079611] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 13:06:47 ubuntu kernel: [ 5820.082336] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 13:06:47 ubuntu kernel: [ 5820.082344] sdb: sdb1
Jan 2 13:06:47 ubuntu kernel: [ 5820.137699] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Jan 2 13:06:47 ubuntu kernel: [ 5820.137705] sd 7:0:0:0: [sdb] Attached SCSI disk
Jan 2 13:14:58 ubuntu kernel: [ 6311.622584] device eth0 entered promiscuous mode
Jan 2 13:15:02 ubuntu kernel: [ 6315.170077] lo: Disabled Privacy Extensions
Jan 2 13:29:47 ubuntu ke...

[Neo23x0 (neo-x)]

Currently I run the system with the following script executed by cron every 5 minutes to ensure that every connected devices it set correctly:

for i in /sys/bus/usb/devices/*/power/control; do echo on > $i; done
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo -1 > $i; done

No freeze up to now.
Perhaps this could be a quick help for someone.
Remember that this would cause a slightly higher power consumption due to the deactivation of the autosuspend and power level feature for USB devices.

[Neo23x0 (neo-x)]

What does that status mean?

> status: In Progress → Triaged

All my efforts in controlling the usb and pci devices turned out to be useless. I did not have a crash for more than a week.
Yesterday I used two virtualbox machines at the same time and my system crahed every 20 minutes.
(perhaps of the swap space use? excessive vbox network card usage? High cpu load has been no problem in the past week)

> Uhhuh. NMI received for unknown reason b1 on CPU 0.

Messages showed a "b1" this time.
I am absolutely disappointed. I dont want to buy new hardware to get rid of this and I dont want to use Windows again.

[papukaija (papukaija)]

The status change means that intuitivenipple (TJ) isn't anymore working on this bug,but this bug has enough info for a developer to work on this bug; that's why it was changed to triaged and not confirmed from 'in progress'.

[penalvch (penalvch)]

Albert Cardona, 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 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>

Also, 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

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.

[Launchpad Janitor (janitor)]

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