* Uhhuh. NMI received for unknown reason 2c on CPU 0.
@ 2013-01-29 20:28 Borislav Petkov
2013-01-29 21:32 ` Bjorn Helgaas
0 siblings, 1 reply; 58+ messages in thread
From: Borislav Petkov @ 2013-01-29 20:28 UTC (permalink / raw)
To: x86; +Cc: lkml
Hi,
this is rc5 + tip/master from 2 days ago, when resuming I get this fun
message:
...
[15117.684975] Restarting tasks ... done.
[15117.687201] video LNXVIDEO:00: Restoring backlight state
[15117.720469] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold
[15117.721414] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold
[15117.949185] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[15118.617192] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[15118.617198] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[15123.971346] Uhhuh. NMI received for unknown reason 2c on CPU 0.
[15123.971353] Do you have a strange power saving mode enabled?
[15123.971356] Dazed and confused, but trying to continue
Machine is thinkpad x230. Any and all sensible suggestions are welcome.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
^ permalink raw reply [flat|nested] 58+ messages in thread* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-29 20:28 Uhhuh. NMI received for unknown reason 2c on CPU 0 Borislav Petkov @ 2013-01-29 21:32 ` Bjorn Helgaas 2013-01-30 3:42 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Bjorn Helgaas @ 2013-01-29 21:32 UTC (permalink / raw) To: Borislav Petkov, x86, lkml, Konstantin Khlebnikov On Tue, Jan 29, 2013 at 1:28 PM, Borislav Petkov <bp@alien8.de> wrote: > Hi, > > this is rc5 + tip/master from 2 days ago, when resuming I get this fun > message: > > ... > [15117.684975] Restarting tasks ... done. > [15117.687201] video LNXVIDEO:00: Restoring backlight state > [15117.720469] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold > [15117.721414] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold > [15117.949185] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off > [15118.617192] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > [15118.617198] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > [15123.971346] Uhhuh. NMI received for unknown reason 2c on CPU 0. > [15123.971353] Do you have a strange power saving mode enabled? > [15123.971356] Dazed and confused, but trying to continue > > Machine is thinkpad x230. Any and all sensible suggestions are welcome. Konstantin has some fixes for an e1000e power management issue related to suspend/resume that he observed on an x220. He didn't see an NMI, and apparently his problem has been around for a long time, so no idea whether it could be related. I just noticed the conjunction of thinkpad/e1000e/resume/power saving in both reports. https://lkml.org/lkml/2013/1/18/147 ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-29 21:32 ` Bjorn Helgaas @ 2013-01-30 3:42 ` Borislav Petkov 2013-01-30 17:27 ` Bjorn Helgaas 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-01-30 3:42 UTC (permalink / raw) To: Bjorn Helgaas; +Cc: x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki On Tue, Jan 29, 2013 at 02:32:56PM -0700, Bjorn Helgaas wrote: > Konstantin has some fixes for an e1000e power management issue related > to suspend/resume that he observed on an x220. He didn't see an NMI, > and apparently his problem has been around for a long time, Yeah, this is one of those issues you don't see *every* s/r cycle and besides, I just got this box and haven't run 3.{6,7} on it yet (maybe never will :-)). > so no idea whether it could be related. I just noticed the conjunction > of thinkpad/e1000e/resume/power saving in both reports. > > https://lkml.org/lkml/2013/1/18/147 Yes, thanks Bjorn, that was a good suggestion. Btw, from reading the thread, those patches still need cooking a bit more, AFAICR people's objections/comments. Or should I go ahead and test them? It's just that I'm overly cautious every time I hear e1000e is involved: www.linux-magazine.com/content/download/62169/484085/file/Security_Lessons_Ftrace.pdf :-) Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 3:42 ` Borislav Petkov @ 2013-01-30 17:27 ` Bjorn Helgaas 2013-01-30 17:44 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Bjorn Helgaas @ 2013-01-30 17:27 UTC (permalink / raw) To: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki On Tue, Jan 29, 2013 at 8:42 PM, Borislav Petkov <bp@alien8.de> wrote: > On Tue, Jan 29, 2013 at 02:32:56PM -0700, Bjorn Helgaas wrote: >> Konstantin has some fixes for an e1000e power management issue related >> to suspend/resume that he observed on an x220. He didn't see an NMI, >> and apparently his problem has been around for a long time, > > Yeah, this is one of those issues you don't see *every* s/r cycle and > besides, I just got this box and haven't run 3.{6,7} on it yet (maybe > never will :-)). > >> so no idea whether it could be related. I just noticed the conjunction >> of thinkpad/e1000e/resume/power saving in both reports. >> >> https://lkml.org/lkml/2013/1/18/147 > > Yes, thanks Bjorn, that was a good suggestion. Btw, from reading the > thread, those patches still need cooking a bit more, AFAICR people's > objections/comments. Or should I go ahead and test them? You're right, I don't think we're quite ready to merge those patches. But if your NMI is easy to reproduce, it might be worth removing e1000e altogether to see if it still happens. I noticed in your original log that the NMI occurred 5 seconds after the e1000e message, and I could imagine some CPU or PCI response timeout being 5 seconds. > It's just that I'm overly cautious every time I hear e1000e is involved: > > www.linux-magazine.com/content/download/62169/484085/file/Security_Lessons_Ftrace.pdf Thanks for the pointer, that was an interesting read :) Bjorn ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 17:27 ` Bjorn Helgaas @ 2013-01-30 17:44 ` Borislav Petkov 2013-01-30 19:43 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-01-30 17:44 UTC (permalink / raw) To: Bjorn Helgaas; +Cc: x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: > You're right, I don't think we're quite ready to merge those patches. > But if your NMI is easy to reproduce, it might be worth removing > e1000e altogether to see if it still happens. That's the problem - I've seen it only once so far. I'll watch out for it and do the above when I find a reliable way of reproducing it. Will keep you posted. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 17:44 ` Borislav Petkov @ 2013-01-30 19:43 ` Jiri Slaby 2013-01-30 20:00 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-30 19:43 UTC (permalink / raw) To: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki [-- Attachment #1: Type: text/plain, Size: 734 bytes --] On 01/30/2013 06:44 PM, Borislav Petkov wrote: > On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: >> You're right, I don't think we're quite ready to merge those patches. >> But if your NMI is easy to reproduce, it might be worth removing >> e1000e altogether to see if it still happens. > > That's the problem - I've seen it only once so far. I'll watch out for > it and do the above when I find a reliable way of reproducing it. Will > keep you posted. It happens here too. Dunno what is the root cause. I *think* that it never happened unless I used ethernet. Other than that I see no pattern. Attaching -C 20 grep of messages over the last half year if there is something that may help somehow. -- js suse labs [-- Attachment #2: lll --] [-- Type: text/plain, Size: 73519 bytes --] messages:Jan 18 12:36:58 anemoi kernel: [ 1056.562253] PM: restore of devices complete after 1173.042 msecs messages:Jan 18 12:36:58 anemoi kernel: [ 1056.573522] PM: Image restored successfully. messages:Jan 18 12:36:58 anemoi kernel: [ 1056.573722] usb 3-2: USB disconnect, device number 2 messages:Jan 18 12:36:58 anemoi kernel: [ 1056.573524] Restarting tasks ... done. messages:Jan 18 12:36:58 anemoi kernel: [ 1056.575972] PM: Basic memory bitmaps freed messages:Jan 18 12:36:58 anemoi kernel: [ 1056.575979] video LNXVIDEO:00: Restoring backlight state messages:Jan 18 12:36:58 anemoi kernel: [ 1056.581587] xHCI xhci_drop_endpoint called with unaddressed device messages:Jan 18 12:36:58 anemoi kernel: [ 1056.581590] xHCI xhci_check_bandwidth called with unaddressed device messages:Jan 18 12:36:58 anemoi kernel: [ 1056.581640] xHCI xhci_free_dev called with unaddressed device messages:Jan 18 12:36:59 anemoi kernel: [ 1057.272377] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages:Jan 18 12:36:59 anemoi kernel: [ 1057.372995] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages:Jan 18 12:36:59 anemoi kernel: [ 1057.375690] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages:Jan 18 12:36:59 anemoi kernel: [ 1057.382402] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages:Jan 18 12:36:59 anemoi kernel: [ 1057.880209] usb 1-1.4: new full-speed USB device number 8 using ehci_hcd messages:Jan 18 12:36:59 anemoi kernel: [ 1057.969925] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages:Jan 18 12:36:59 anemoi kernel: [ 1057.969932] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages:Jan 18 12:36:59 anemoi kernel: [ 1057.969936] usb 1-1.4: Product: BCM20702A0 messages:Jan 18 12:36:59 anemoi kernel: [ 1057.969939] usb 1-1.4: Manufacturer: Broadcom Corp messages:Jan 18 12:36:59 anemoi kernel: [ 1057.969942] usb 1-1.4: SerialNumber: 083E8EE1B689 messages:Jan 18 12:37:00 anemoi kernel: [ 1058.411130] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages:Jan 18 12:37:00 anemoi kernel: [ 1058.575413] Uhhuh. NMI received for unknown reason 2c on CPU 0. messages:Jan 18 12:37:00 anemoi kernel: [ 1058.575415] Do you have a strange power saving mode enabled? messages:Jan 18 12:37:00 anemoi kernel: [ 1058.575416] Dazed and confused, but trying to continue messages:Jan 18 12:37:00 anemoi kernel: [ 1058.624334] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages:Jan 18 12:37:00 anemoi kernel: [ 1058.864128] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages:Jan 18 12:37:02 anemoi kernel: [ 1060.207351] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages:Jan 18 12:37:02 anemoi kernel: [ 1060.307498] xhci_hcd 0000:00:14.0: setting latency timer to 64 messages:Jan 18 12:37:02 anemoi kernel: [ 1060.318616] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages:Jan 18 12:37:02 anemoi kernel: [ 1060.884415] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages:Jan 18 12:37:03 anemoi kernel: [ 1062.078204] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None messages:Jan 18 12:37:03 anemoi kernel: [ 1062.078214] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO messages:Jan 18 12:37:04 anemoi kernel: [ 1062.848706] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages:Jan 18 12:37:06 anemoi kernel: [ 1064.980328] wlan0: authenticate with 02:15:6d:84:b3:8f messages:Jan 18 12:37:06 anemoi kernel: [ 1064.987064] wlan0: send auth to 02:15:6d:84:b3:8f (try 1/3) messages:Jan 18 12:37:06 anemoi kernel: [ 1064.988228] wlan0: authenticated messages:Jan 18 12:37:06 anemoi kernel: [ 1064.988411] iwlwifi 0000:03:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use messages:Jan 18 12:37:06 anemoi kernel: [ 1064.988643] wlan0: associate with 02:15:6d:84:b3:8f (try 1/3) messages:Jan 18 12:37:06 anemoi kernel: [ 1064.990024] wlan0: RX AssocResp from 02:15:6d:84:b3:8f (capab=0x11 status=0 aid=2) messages:Jan 18 12:37:06 anemoi kernel: [ 1064.992370] wlan0: associated messages:Jan 18 12:37:06 anemoi kernel: [ 1064.992447] cfg80211: Calling CRDA for country: CZ messages:Jan 18 12:37:06 anemoi kernel: [ 1065.000693] cfg80211: Regulatory domain changed to country: CZ -- messages:Jan 22 13:54:02 anemoi kernel: [ 4038.257666] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages:Jan 22 13:54:02 anemoi kernel: [ 4038.257668] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages:Jan 22 13:54:02 anemoi kernel: [ 4038.258060] ata1.00: failed to get Identify Device Data, Emask 0x1 messages:Jan 22 13:54:02 anemoi kernel: [ 4038.258737] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages:Jan 22 13:54:02 anemoi kernel: [ 4038.258740] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages:Jan 22 13:54:02 anemoi kernel: [ 4038.258953] ata2: SATA link down (SStatus 0 SControl 300) messages:Jan 22 13:54:02 anemoi kernel: [ 4038.259119] ata1.00: failed to get Identify Device Data, Emask 0x1 messages:Jan 22 13:54:02 anemoi kernel: [ 4038.259124] ata1.00: configured for UDMA/133 messages:Jan 22 13:54:02 anemoi kernel: [ 4038.262011] ata5: SATA link down (SStatus 0 SControl 300) messages:Jan 22 13:54:02 anemoi kernel: [ 4038.272050] sd 0:0:0:0: [sda] Starting disk messages:Jan 22 13:54:02 anemoi kernel: [ 4038.276939] usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages:Jan 22 13:54:02 anemoi kernel: [ 4038.492562] usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages:Jan 22 13:54:02 anemoi kernel: [ 4038.679439] usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages:Jan 22 13:54:02 anemoi kernel: [ 4038.827099] usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages:Jan 22 13:54:02 anemoi kernel: [ 4038.913365] PM: restore of devices complete after 964.665 msecs messages:Jan 22 13:54:02 anemoi kernel: [ 4038.913650] PM: Image restored successfully. messages:Jan 22 13:54:02 anemoi kernel: [ 4038.914203] usb 1-1.4: USB disconnect, device number 4 messages:Jan 22 13:54:02 anemoi kernel: [ 4038.913652] Restarting tasks ... done. messages:Jan 22 13:54:02 anemoi kernel: [ 4038.915528] PM: Basic memory bitmaps freed messages:Jan 22 13:54:02 anemoi kernel: [ 4038.915534] video LNXVIDEO:00: Restoring backlight state messages:Jan 22 13:54:02 anemoi kernel: [ 4038.920633] Uhhuh. NMI received for unknown reason 2c on CPU 0. messages:Jan 22 13:54:02 anemoi kernel: [ 4038.920639] Do you have a strange power saving mode enabled? messages:Jan 22 13:54:02 anemoi kernel: [ 4038.920641] Dazed and confused, but trying to continue messages:Jan 22 13:54:02 anemoi kernel: [ 4039.060420] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages:Jan 22 13:54:02 anemoi kernel: [ 4039.067115] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages:Jan 22 13:54:02 anemoi kernel: [ 4039.378156] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages:Jan 22 13:54:02 anemoi kernel: [ 4039.668418] usb 1-1.4: new full-speed USB device number 6 using ehci_hcd messages:Jan 22 13:54:03 anemoi kernel: [ 4039.757837] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages:Jan 22 13:54:03 anemoi kernel: [ 4039.757842] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages:Jan 22 13:54:03 anemoi kernel: [ 4039.757844] usb 1-1.4: Product: BCM20702A0 messages:Jan 22 13:54:03 anemoi kernel: [ 4039.757846] usb 1-1.4: Manufacturer: Broadcom Corp messages:Jan 22 13:54:03 anemoi kernel: [ 4039.757847] usb 1-1.4: SerialNumber: 083E8EE1B689 messages:Jan 22 13:54:04 anemoi kernel: [ 4041.267351] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages:Jan 22 13:54:06 anemoi kernel: [ 4043.287519] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages:Jan 22 13:54:07 anemoi kernel: [ 4044.176658] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 messages:Jan 22 13:54:07 anemoi kernel: [ 4044.371894] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input18 messages:Jan 22 13:54:09 anemoi kernel: [ 4045.911842] wlan0: authenticate with 00:02:6f:53:c7:ca messages:Jan 22 13:54:09 anemoi kernel: [ 4045.938132] wlan0: send auth to 00:02:6f:53:c7:ca (try 1/3) messages:Jan 22 13:54:09 anemoi kernel: [ 4045.940759] wlan0: authenticated messages:Jan 22 13:54:09 anemoi kernel: [ 4045.941007] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP messages:Jan 22 13:54:09 anemoi kernel: [ 4045.941014] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP -- messages:Jan 26 17:06:16 anemoi kernel: [ 3222.977434] PM: late freeze of devices complete after 0.100 msecs messages:Jan 26 17:06:16 anemoi kernel: [ 3222.978304] PM: noirq freeze of devices complete after 0.871 msecs messages:Jan 26 17:06:16 anemoi kernel: [ 3222.978475] ACPI: Preparing to enter system sleep state S4 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.018903] PM: Saving platform NVS memory messages:Jan 26 17:06:16 anemoi kernel: [ 3223.021467] Disabling non-boot CPUs ... messages:Jan 26 17:06:16 anemoi kernel: [ 3223.022839] smpboot: CPU 1 is now offline messages:Jan 26 17:06:16 anemoi kernel: [ 3223.024360] smpboot: CPU 2 is now offline messages:Jan 26 17:06:16 anemoi kernel: [ 3223.025759] smpboot: CPU 3 is now offline messages:Jan 26 17:06:16 anemoi kernel: [ 3223.026117] Extended CMOS year: 2000 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.026199] PM: Creating hibernation image: messages:Jan 26 17:06:16 anemoi kernel: [ 3223.063523] PM: Need to copy 323026 pages messages:Jan 26 17:06:16 anemoi kernel: [ 3223.063525] PM: Normal pages needed: 323026 + 1024, available pages: 685568 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.027657] PM: Restoring platform NVS memory messages:Jan 26 17:06:16 anemoi kernel: [ 3223.028204] Extended CMOS year: 2000 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.028257] Enabling non-boot CPUs ... messages:Jan 26 17:06:16 anemoi kernel: [ 3223.029433] smpboot: Booting Node 0 Processor 1 APIC 0x1 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.043113] CPU1 is up messages:Jan 26 17:06:16 anemoi kernel: [ 3223.043208] smpboot: Booting Node 0 Processor 2 APIC 0x2 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.056898] CPU2 is up messages:Jan 26 17:06:16 anemoi kernel: [ 3223.056973] smpboot: Booting Node 0 Processor 3 APIC 0x3 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.060476] Uhhuh. NMI received for unknown reason 3d on CPU 0. messages:Jan 26 17:06:16 anemoi kernel: [ 3223.060476] Do you have a strange power saving mode enabled? messages:Jan 26 17:06:16 anemoi kernel: [ 3223.060477] Dazed and confused, but trying to continue messages:Jan 26 17:06:16 anemoi kernel: [ 3223.070660] CPU3 is up messages:Jan 26 17:06:16 anemoi kernel: [ 3223.073432] ACPI: Waking up from system sleep state S4 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.116941] thinkpad_acpi: EC reports that Thermal Table has changed messages:Jan 26 17:06:16 anemoi kernel: [ 3223.157778] i915 0000:00:02.0: power state changed by ACPI to D0 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.157793] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.179724] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.190897] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.191274] sdhci-pci 0000:02:00.0: MMC controller base frequency changed to 50Mhz. messages:Jan 26 17:06:16 anemoi kernel: [ 3223.191762] PM: noirq restore of devices complete after 34.100 msecs messages:Jan 26 17:06:16 anemoi kernel: [ 3223.191853] PM: early restore of devices complete after 0.067 msecs messages:Jan 26 17:06:16 anemoi kernel: [ 3223.229775] xhci_hcd 0000:00:14.0: setting latency timer to 64 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.229776] i915 0000:00:02.0: setting latency timer to 64 messages:Jan 26 17:06:16 anemoi kernel: [ 3223.229789] usb usb3: root hub lost power or was reset messages:Jan 26 17:06:16 anemoi kernel: [ 3223.229790] usb usb4: root hub lost power or was reset messages:Jan 26 17:06:16 anemoi kernel: [ 3223.229987] mei 0000:00:16.0: irq 43 for MSI/MSI-X messages:Jan 26 17:06:16 anemoi kernel: [ 3223.230009] xhci_hcd 0000:00:14.0: irq 45 for MSI/MSI-X messages:Jan 26 17:06:16 anemoi kernel: [ 3223.230018] e1000e 0000:00:19.0: wake-up capability disabled by ACPI messages:Jan 26 17:06:16 anemoi kernel: [ 3223.230074] ehci_hcd 0000:00:1a.0: setting latency timer to 64 -- messages:Jan 29 17:15:02 anemoi kernel: [ 4800.207850] ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages:Jan 29 17:15:02 anemoi kernel: [ 4800.207867] usb usb2: root hub lost power or was reset messages:Jan 29 17:15:02 anemoi kernel: [ 4800.211424] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported messages:Jan 29 17:15:02 anemoi kernel: [ 4800.211435] ahci 0000:00:1f.2: setting latency timer to 64 messages:Jan 29 17:15:02 anemoi kernel: [ 4800.211614] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio. messages:Jan 29 17:15:02 anemoi kernel: [ 4800.211786] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported messages:Jan 29 17:15:02 anemoi kernel: [ 4800.237663] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off messages:Jan 29 17:15:02 anemoi kernel: [ 4800.248588] tpm_tis 00:0a: TPM is disabled/deactivated (0x6) messages:Jan 29 17:15:02 anemoi kernel: [ 4800.516041] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages:Jan 29 17:15:02 anemoi kernel: [ 4800.516796] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages:Jan 29 17:15:02 anemoi kernel: [ 4800.516798] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages:Jan 29 17:15:02 anemoi kernel: [ 4800.517844] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages:Jan 29 17:15:02 anemoi kernel: [ 4800.517848] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages:Jan 29 17:15:02 anemoi kernel: [ 4800.517987] ata5: SATA link down (SStatus 0 SControl 300) messages:Jan 29 17:15:02 anemoi kernel: [ 4800.518143] ata1.00: configured for UDMA/133 messages:Jan 29 17:15:02 anemoi kernel: [ 4800.522029] ata2: SATA link down (SStatus 0 SControl 300) messages:Jan 29 17:15:02 anemoi kernel: [ 4800.529091] sd 0:0:0:0: [sda] Starting disk messages:Jan 29 17:15:02 anemoi kernel: [ 4800.533430] Extended CMOS year: 2000 messages:Jan 29 17:15:02 anemoi kernel: [ 4800.534980] usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages:Jan 29 17:15:02 anemoi kernel: [ 4800.750651] usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages:Jan 29 17:15:02 anemoi kernel: [ 4801.070032] Uhhuh. NMI received for unknown reason 2d on CPU 0. messages:Jan 29 17:15:02 anemoi kernel: [ 4801.070032] Do you have a strange power saving mode enabled? messages:Jan 29 17:15:02 anemoi kernel: [ 4801.070032] Dazed and confused, but trying to continue messages:Jan 29 17:15:02 anemoi kernel: [ 4801.143193] usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages:Jan 29 17:15:02 anemoi kernel: [ 4801.300733] usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages:Jan 29 17:15:02 anemoi kernel: [ 4801.384819] PM: restore of devices complete after 1179.735 msecs messages:Jan 29 17:15:02 anemoi kernel: [ 4801.395414] PM: Image restored successfully. messages:Jan 29 17:15:02 anemoi kernel: [ 4801.395417] Restarting tasks ... done. messages:Jan 29 17:15:02 anemoi kernel: [ 4801.396944] PM: Basic memory bitmaps freed messages:Jan 29 17:15:02 anemoi kernel: [ 4801.396950] video LNXVIDEO:00: Restoring backlight state messages:Jan 29 17:15:02 anemoi kernel: [ 4801.776665] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X messages:Jan 29 17:15:02 anemoi kernel: [ 4801.877485] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X messages:Jan 29 17:15:02 anemoi kernel: [ 4801.878978] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages:Jan 29 17:15:02 anemoi kernel: [ 4801.885647] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages:Jan 29 17:15:03 anemoi kernel: [ 4802.151842] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages:Jan 29 17:15:03 anemoi kernel: [ 4802.188066] usb 1-1.4: new full-speed USB device number 10 using ehci_hcd messages:Jan 29 17:15:03 anemoi kernel: [ 4802.277286] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages:Jan 29 17:15:03 anemoi kernel: [ 4802.277290] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages:Jan 29 17:15:03 anemoi kernel: [ 4802.277293] usb 1-1.4: Product: BCM20702A0 messages:Jan 29 17:15:03 anemoi kernel: [ 4802.277294] usb 1-1.4: Manufacturer: Broadcom Corp messages:Jan 29 17:15:03 anemoi kernel: [ 4802.277296] usb 1-1.4: SerialNumber: 083E8EE1B689 -- messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9056.915943] tpm_tis 00:0a: TPM is disabled/deactivated (0x6) messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.188394] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.189086] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.189090] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.190122] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.190126] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.190358] ata2: SATA link down (SStatus 0 SControl 300) messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.190413] ata1.00: configured for UDMA/133 messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.192387] ata5: SATA link down (SStatus 0 SControl 300) messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.201424] sd 0:0:0:0: [sda] Starting disk messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.203762] Extended CMOS year: 2000 messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.207353] usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.422921] usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.609874] usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.757584] usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.841480] PM: restore of devices complete after 963.708 msecs messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.861412] Restarting kernel threads ... done. messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.861608] Restarting tasks ... done. messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.873126] PM: Basic memory bitmaps freed messages-20121025.xz:Oct 25 11:59:56 anemoi kernel: [ 9057.873222] video LNXVIDEO:00: Restoring backlight state messages-20121025.xz:Oct 25 11:59:57 anemoi kernel: [ 9059.585024] Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121025.xz:Oct 25 11:59:57 anemoi kernel: [ 9059.585027] Do you have a strange power saving mode enabled? messages-20121025.xz:Oct 25 11:59:57 anemoi kernel: [ 9059.585028] Dazed and confused, but trying to continue messages-20121025.xz:Oct 25 11:59:58 anemoi kernel: [ 9059.868308] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121025.xz:Oct 25 12:00:00 anemoi kernel: [ 9061.888524] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121025.xz:Oct 25 12:00:02 anemoi kernel: [ 9063.874794] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D3cold messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.191189] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.291661] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.295896] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.302739] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.398585] ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.499205] ehci_hcd 0000:00:1a.0: setting latency timer to 64 messages-20121025.xz:Oct 25 12:00:06 anemoi kernel: [ 9068.499439] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.600022] ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.600181] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.610926] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.700857] xhci_hcd 0000:00:14.0: setting latency timer to 64 messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.757909] EXT4-fs (sda3): re-mounted. Opts: data=writeback,commit=0 messages-20121025.xz:Oct 25 12:00:07 anemoi kernel: [ 9068.766714] EXT4-fs (sda1): re-mounted. Opts: data=writeback,commit=0 messages-20121025.xz:Oct 25 12:00:08 anemoi kernel: [ 9070.294759] usb 3-1: new low-speed USB device number 2 using xhci_hcd messages-20121025.xz:Oct 25 12:00:08 anemoi kernel: [ 9070.309479] usb 3-1: New USB device found, idVendor=046d, idProduct=c019 -- messages-20121104.xz:Oct 26 15:07:29 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121104.xz:Oct 26 15:07:29 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Oct 26 15:07:30 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Oct 26 15:07:30 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121104.xz:Oct 26 15:07:30 anemoi kernel: usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121104.xz:Oct 26 15:07:34 anemoi kernel: ata1: link is slow to respond, please be patient (ready=0) messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1: COMRESET failed (errno=-16) messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: PM: restore of devices complete after 10368.704 msecs messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: Restarting kernel threads ... done. messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: usb 1-1.4: USB disconnect, device number 6 messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: Restarting tasks ... done. messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: PM: Basic memory bitmaps freed messages-20121104.xz:Oct 26 15:07:39 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121104.xz:Oct 26 15:07:41 anemoi kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0. messages-20121104.xz:Oct 26 15:07:41 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121104.xz:Oct 26 15:07:41 anemoi kernel: Dazed and confused, but trying to continue messages-20121104.xz:Oct 26 15:07:42 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121104.xz:Oct 26 15:07:42 anemoi kernel: usb 1-1.4: new full-speed USB device number 7 using ehci_hcd messages-20121104.xz:Oct 26 15:07:43 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121104.xz:Oct 26 15:07:43 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121104.xz:Oct 26 15:07:43 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121104.xz:Oct 26 15:07:43 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121104.xz:Oct 26 15:07:43 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121104.xz:Oct 26 15:07:44 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: EXT4-fs (sda3): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: EXT4-fs (sda1): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121104.xz:Oct 26 15:07:49 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121104.xz:Oct 26 15:08:24 anemoi kernel: SysRq : Emergency Sync messages-20121104.xz:Oct 26 15:08:24 anemoi kernel: Emergency Sync complete messages-20121104.xz:Oct 26 15:08:30 anemoi kernel: SysRq : Terminate All Tasks messages-20121104.xz:Oct 26 15:08:30 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X -- messages-20121104.xz:Oct 27 10:16:56 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121104.xz:Oct 27 10:16:56 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Oct 27 10:16:56 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Oct 27 10:16:56 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121104.xz:Oct 27 10:16:57 anemoi kernel: usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121104.xz:Oct 27 10:17:01 anemoi kernel: ata1: link is slow to respond, please be patient (ready=0) messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1: COMRESET failed (errno=-16) messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: PM: restore of devices complete after 10372.794 msecs messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: Restarting kernel threads ... done. messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: Restarting tasks ... done. messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: PM: Basic memory bitmaps freed messages-20121104.xz:Oct 27 10:17:06 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: new full-speed USB device number 9 using ehci_hcd messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0. messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: Dazed and confused, but trying to continue messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121104.xz:Oct 27 10:17:08 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121104.xz:Oct 27 10:17:10 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121104.xz:Oct 27 10:17:17 anemoi kernel: EXT4-fs (sda3): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Oct 27 10:17:17 anemoi kernel: EXT4-fs (sda1): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Oct 27 10:17:17 anemoi kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X messages-20121104.xz:Oct 27 10:17:18 anemoi kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X messages-20121104.xz:Oct 27 10:17:18 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121104.xz:Oct 27 10:17:18 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121104.xz:Oct 27 10:17:24 anemoi kernel: wlan0: authenticate with 00:1f:c6:d6:be:73 messages-20121104.xz:Oct 27 10:17:24 anemoi kernel: wlan0: send auth to 00:1f:c6:d6:be:73 (try 1/3) messages-20121104.xz:Oct 27 10:17:24 anemoi kernel: wlan0: authenticated messages-20121104.xz:Oct 27 10:17:24 anemoi kernel: wlan0: associate with 00:1f:c6:d6:be:73 (try 1/3) messages-20121104.xz:Oct 27 10:17:24 anemoi kernel: wlan0: RX AssocResp from 00:1f:c6:d6:be:73 (capab=0x401 status=0 aid=3) -- messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121104.xz:Nov 1 11:30:34 anemoi kernel: PM: restore of devices complete after 963.531 msecs messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: usb 3-1: USB disconnect, device number 4 messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: Restarting kernel threads ... done. messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: Restarting tasks ... done. messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: PM: Basic memory bitmaps freed messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: xHCI xhci_drop_endpoint called with unaddressed device messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: xHCI xhci_check_bandwidth called with unaddressed device messages-20121104.xz:Nov 1 11:30:35 anemoi kernel: xHCI xhci_free_dev called with unaddressed device messages-20121104.xz:Nov 1 11:30:37 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121104.xz:Nov 1 11:30:38 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: Dazed and confused, but trying to continue messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: new full-speed USB device number 8 using ehci_hcd messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121104.xz:Nov 1 11:30:39 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121104.xz:Nov 1 11:30:44 anemoi kernel: EXT4-fs (sda3): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Nov 1 11:30:44 anemoi kernel: EXT4-fs (sda1): re-mounted. Opts: data=writeback,commit=600 messages-20121104.xz:Nov 1 11:30:47 anemoi kernel: wlan0: authenticate with 00:15:6d:84:ef:16 messages-20121104.xz:Nov 1 11:30:47 anemoi kernel: wlan0: send auth to 00:15:6d:84:ef:16 (try 1/3) messages-20121104.xz:Nov 1 11:30:47 anemoi kernel: wlan0: authenticated messages-20121104.xz:Nov 1 11:30:47 anemoi kernel: wlan0: waiting for beacon from 00:15:6d:84:ef:16 messages-20121104.xz:Nov 1 11:30:47 anemoi kernel: wlan0: authenticate with 06:80:48:67:64:e9 messages-20121104.xz:Nov 1 11:30:48 anemoi kernel: wlan0: send auth to 06:80:48:67:64:e9 (try 1/3) messages-20121104.xz:Nov 1 11:30:48 anemoi kernel: wlan0: authenticated messages-20121104.xz:Nov 1 11:30:48 anemoi kernel: iwlwifi 0000:03:00.0: wlan0: disabling HT as WMM/QoS is not supported messages-20121104.xz:Nov 1 11:30:48 anemoi kernel: wlan0: waiting for beacon from 06:80:48:67:64:e9 -- messages-20121121.xz:Nov 11 13:58:25 anemoi kernel: ata2: SATA link down (SStatus 0 SControl 300) messages-20121121.xz:Nov 11 13:58:25 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121121.xz:Nov 11 13:58:25 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121121.xz:Nov 11 13:58:25 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121121.xz:Nov 11 13:58:26 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121121.xz:Nov 11 13:58:26 anemoi kernel: usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121121.xz:Nov 11 13:58:30 anemoi kernel: ata1: link is slow to respond, please be patient (ready=0) messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1: COMRESET failed (errno=-16) messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: PM: restore of devices complete after 10369.799 msecs messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: Restarting kernel threads ... done. messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: Restarting tasks ... done. messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: PM: Basic memory bitmaps freed messages-20121121.xz:Nov 11 13:58:35 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121121.xz:Nov 11 13:58:36 anemoi kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121121.xz:Nov 11 13:58:36 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121121.xz:Nov 11 13:58:36 anemoi kernel: Dazed and confused, but trying to continue messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: new full-speed USB device number 23 using ehci_hcd messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121121.xz:Nov 11 13:58:37 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121121.xz:Nov 11 13:58:39 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121121.xz:Nov 11 13:58:39 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 messages-20121121.xz:Nov 11 13:58:40 anemoi kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages-20121121.xz:Nov 11 13:58:40 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages-20121121.xz:Nov 11 13:58:40 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121121.xz:Nov 11 13:58:40 anemoi kernel: xhci_hcd 0000:00:14.0: setting latency timer to 64 messages-20121121.xz:Nov 11 13:58:40 anemoi kernel: e1000e 0000:00:19.0: irq 43 for MSI/MSI-X messages-20121121.xz:Nov 11 13:58:41 anemoi kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx messages-20121121.xz:Nov 11 13:58:41 anemoi kernel: e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO -- messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: Extended CMOS year: 2000 messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: PM: restore of devices complete after 10370.129 msecs messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: Restarting kernel threads ... done. messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: Restarting tasks ... done. messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: PM: Basic memory bitmaps freed messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: new low-speed USB device number 2 using xhci_hcd messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: New USB device found, idVendor=046d, idProduct=c019 messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: Product: Logitech USB Optical Mouse messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: Manufacturer: Logitech messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: usb 3-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: input: Logitech Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input18 messages-20121121.xz:Nov 15 11:54:40 anemoi kernel: hid-generic 0003:046D:C019.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech Logitech USB Optical Mouse] on usb-0000:00:14.0-1/input0 messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0. messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: Dazed and confused, but trying to continue messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121121.xz:Nov 15 11:54:41 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: EXT4-fs (sda3): re-mounted. Opts: data=writeback,commit=0 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: EXT4-fs (sda1): re-mounted. Opts: data=writeback,commit=0 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: new full-speed USB device number 8 using ehci_hcd messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121121.xz:Nov 15 11:54:42 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121121.xz:Nov 15 11:54:44 anemoi kernel: e1000e 0000:00:19.0: irq 48 for MSI/MSI-X messages-20121121.xz:Nov 15 11:54:45 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121121.xz:Nov 15 11:54:48 anemoi kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None messages-20121121.xz:Nov 15 11:54:48 anemoi kernel: wlan0: authenticate with 06:80:48:55:c5:f8 messages-20121121.xz:Nov 15 11:54:48 anemoi kernel: wlan0: send auth to 06:80:48:55:c5:f8 (try 1/3) messages-20121121.xz:Nov 15 11:54:48 anemoi kernel: wlan0: authenticated -- messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: mei 0000:00:16.0: irq 43 for MSI/MSI-X messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ehci_hcd 0000:00:1a.0: setting latency timer to 64 messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: usb usb1: root hub lost power or was reset messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: xhci_hcd 0000:00:14.0: irq 46 for MSI/MSI-X messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: usb usb2: root hub lost power or was reset messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ahci 0000:00:1f.2: setting latency timer to 64 messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio. messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: tpm_tis 00:0a: TPM is disabled/deactivated (0x6) messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: ata2: SATA link down (SStatus 0 SControl 300) messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121121.xz:Nov 20 18:41:55 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121121.xz:Nov 20 18:41:56 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121121.xz:Nov 20 18:41:56 anemoi kernel: usb 1-1.6: reset high-speed USB device number 5 using ehci_hcd messages-20121121.xz:Nov 20 18:41:56 anemoi kernel: Uhhuh. NMI received for unknown reason 3d on CPU 0. messages-20121121.xz:Nov 20 18:41:56 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121121.xz:Nov 20 18:41:56 anemoi kernel: Dazed and confused, but trying to continue messages-20121121.xz:Nov 20 18:42:00 anemoi kernel: ata1: link is slow to respond, please be patient (ready=0) messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1: COMRESET failed (errno=-16) messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: PM: restore of devices complete after 10371.090 msecs messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: Restarting kernel threads ... done. messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: Restarting tasks ... done. messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: PM: Basic memory bitmaps freed messages-20121121.xz:Nov 20 18:42:05 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121121.xz:Nov 20 18:42:06 anemoi kernel: usb 1-1.4: new full-speed USB device number 11 using ehci_hcd messages-20121121.xz:Nov 20 18:42:06 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121121.xz:Nov 20 18:42:06 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121121.xz:Nov 20 18:42:06 anemoi kernel: usb 1-1.4: Product: BCM20702A0 -- messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: tpm_tis 00:0a: TPM is disabled/deactivated (0x6) messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: ata2: SATA link down (SStatus 0 SControl 300) messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: Extended CMOS year: 2000 messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: usb 1-1.6: reset high-speed USB device number 4 using ehci_hcd messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121213.xz:Nov 21 15:07:41 anemoi kernel: Dazed and confused, but trying to continue messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: PM: restore of devices complete after 1038.345 msecs messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: Restarting kernel threads ... done. messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: Restarting tasks ... done. messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: PM: Basic memory bitmaps freed messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=0 messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: new full-speed USB device number 8 using ehci_hcd messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121213.xz:Nov 21 15:07:42 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121213.xz:Nov 21 15:07:44 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Nov 21 15:07:46 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Nov 21 15:10:28 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 messages-20121213.xz:Nov 21 15:10:28 anemoi kernel: ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages-20121213.xz:Nov 21 15:10:28 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages-20121213.xz:Nov 21 15:10:28 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold -- messages-20121213.xz:Nov 25 22:21:52 anemoi kernel: usb 1-1.6: reset high-speed USB device number 4 using ehci_hcd messages-20121213.xz:Nov 25 22:21:52 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121213.xz:Nov 25 22:21:57 anemoi kernel: ata1: link is slow to respond, please be patient (ready=0) messages-20121213.xz:Nov 25 22:22:01 anemoi kernel: ata1: COMRESET failed (errno=-16) messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: PM: restore of devices complete after 10369.260 msecs messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: usb 3-1: USB disconnect, device number 10 messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: Restarting kernel threads ... done. messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: Restarting tasks ... done. messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: PM: Basic memory bitmaps freed messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: xHCI xhci_drop_endpoint called with unaddressed device messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: xHCI xhci_check_bandwidth called with unaddressed device messages-20121213.xz:Nov 25 22:22:02 anemoi kernel: xHCI xhci_free_dev called with unaddressed device messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0. messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: Dazed and confused, but trying to continue messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121213.xz:Nov 25 22:22:03 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121213.xz:Nov 25 22:22:05 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Nov 25 22:22:07 anemoi kernel: ehci_hcd 0000:00:1a.0: power state changed by ACPI to D3cold messages-20121213.xz:Nov 25 22:22:07 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: authenticate with 00:4f:62:08:a3:64 messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: send auth to 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: authenticated messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: iwlwifi 0000:03:00.0: wlan0: disabling HT as WMM/QoS is not supported messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: associate with 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: RX AssocResp from 00:4f:62:08:a3:64 (capab=0x411 status=0 aid=1) messages-20121213.xz:Nov 25 22:22:10 anemoi kernel: wlan0: associated messages-20121213.xz:Nov 25 22:22:44 anemoi kernel: ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 messages-20121213.xz:Nov 25 22:22:44 anemoi kernel: ehci_hcd 0000:00:1a.0: setting latency timer to 64 messages-20121213.xz:Nov 25 22:22:44 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 -- messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: ata5: SATA link down (SStatus 0 SControl 300) messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: ata1.00: configured for UDMA/133 messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: ata2: SATA link down (SStatus 0 SControl 300) messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: usb 1-1: reset high-speed USB device number 2 using ehci_hcd messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: sd 0:0:0:0: [sda] Starting disk messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: Extended CMOS year: 2000 messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: usb 1-1.6: reset high-speed USB device number 4 using ehci_hcd messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: PM: restore of devices complete after 984.229 msecs messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: PM: Image restored successfully. messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: Restarting tasks ... done. messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: PM: Basic memory bitmaps freed messages-20121213.xz:Dec 1 12:57:02 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: Dazed and confused, but trying to continue messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: new full-speed USB device number 8 using ehci_hcd messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121213.xz:Dec 1 12:57:03 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121213.xz:Dec 1 12:57:04 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 1 12:57:07 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: authenticate with 00:4f:62:08:a3:64 messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: send auth to 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: authenticated messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: iwlwifi 0000:03:00.0: wlan0: disabling HT as WMM/QoS is not supported messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: associate with 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: RX AssocResp from 00:4f:62:08:a3:64 (capab=0x411 status=0 aid=1) messages-20121213.xz:Dec 1 12:57:09 anemoi kernel: wlan0: associated messages-20121213.xz:Dec 1 12:57:28 anemoi kernel: ehci_hcd 0000:00:1a.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 1 13:02:03 anemoi kernel: ehci_hcd 0000:00:1a.0: power state changed by ACPI to D0 messages-20121213.xz:Dec 1 13:02:03 anemoi kernel: ehci_hcd 0000:00:1a.0: setting latency timer to 64 -- messages-20121213.xz:Dec 7 10:44:34 anemoi kernel: usb 2-1: reset high-speed USB device number 2 using ehci_hcd messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: usb 1-1.6: reset high-speed USB device number 4 using ehci_hcd messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: PM: restore of devices complete after 965.450 msecs messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: PM: Image restored successfully. messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: usb 1-1.4: USB disconnect, device number 6 messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: Restarting tasks ... done. messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: PM: Basic memory bitmaps freed messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: video LNXVIDEO:00: Restoring backlight state messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121213.xz:Dec 7 10:44:35 anemoi kernel: EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: new full-speed USB device number 7 using ehci_hcd messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: Product: BCM20702A0 messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: Manufacturer: Broadcom Corp messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0. messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: Do you have a strange power saving mode enabled? messages-20121213.xz:Dec 7 10:44:36 anemoi kernel: Dazed and confused, but trying to continue messages-20121213.xz:Dec 7 10:44:37 anemoi kernel: xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 7 10:44:39 anemoi kernel: ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: authenticate with 00:4f:62:08:a3:64 messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: send auth to 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: authenticated messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: iwlwifi 0000:03:00.0: wlan0: disabling HT as WMM/QoS is not supported messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: associate with 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: RX AssocResp from 00:4f:62:08:a3:64 (capab=0x411 status=0 aid=1) messages-20121213.xz:Dec 7 10:44:42 anemoi kernel: wlan0: associated messages-20121213.xz:Dec 7 11:11:24 anemoi kernel: QNX4 filesystem 0.2.3 registered. messages-20121213.xz:Dec 7 11:11:55 anemoi kernel: [ 4448.435292] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D0 messages-20121213.xz:Dec 7 11:11:55 anemoi kernel: [ 4448.535795] ehci_hcd 0000:00:1d.0: setting latency timer to 64 messages-20121213.xz:Dec 7 11:11:55 anemoi kernel: [ 4448.536156] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 messages-20121213.xz:Dec 7 11:11:55 anemoi kernel: [ 4448.546702] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 7 11:11:55 anemoi kernel: [ 4448.636617] xhci_hcd 0000:00:14.0: setting latency timer to 64 messages-20121213.xz:Dec 7 11:11:58 anemoi kernel: [ 4451.285692] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 7 11:13:01 anemoi kernel: [ 4514.224094] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 7 11:13:01 anemoi kernel: [ 4514.401898] wlan0: deauthenticating from 00:4f:62:08:a3:64 by local choice (reason=3) -- messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.057002] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.057007] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.057351] ata1.00: configured for UDMA/133 messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.068267] sd 0:0:0:0: [sda] Starting disk messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.068632] Extended CMOS year: 2000 messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.069760] PM: restore of devices complete after 10372.712 msecs messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.085201] PM: Image restored successfully. messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.085314] usb 3-1: USB disconnect, device number 3 messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.085203] Restarting tasks ... done. messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.087581] PM: Basic memory bitmaps freed messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.087586] video LNXVIDEO:00: Restoring backlight state messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.091212] xHCI xhci_drop_endpoint called with unaddressed device messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.091214] xHCI xhci_check_bandwidth called with unaddressed device messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.091273] xHCI xhci_free_dev called with unaddressed device messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.762935] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.863761] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.864878] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20121213.xz:Dec 9 17:35:47 anemoi kernel: [12782.871532] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20121213.xz:Dec 9 17:35:48 anemoi kernel: [12783.841835] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20121213.xz:Dec 9 17:35:48 anemoi kernel: [12784.068842] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20121213.xz:Dec 9 17:35:48 anemoi kernel: [12784.084589] Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20121213.xz:Dec 9 17:35:48 anemoi kernel: [12784.084592] Do you have a strange power saving mode enabled? messages-20121213.xz:Dec 9 17:35:48 anemoi kernel: [12784.084593] Dazed and confused, but trying to continue messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.174238] usb 1-1.4: new full-speed USB device number 11 using ehci_hcd messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.263046] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.263148] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.263150] usb 1-1.4: Product: BCM20702A0 messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.263151] usb 1-1.4: Manufacturer: Broadcom Corp messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.263152] usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20121213.xz:Dec 9 17:35:49 anemoi kernel: [12784.852897] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 9 17:35:51 anemoi kernel: [12786.868102] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.508168] wlan0: authenticate with 00:4f:62:08:a3:64 messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.516351] wlan0: send auth to 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.519322] wlan0: authenticated messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.519584] iwlwifi 0000:03:00.0: wlan0: disabling HT as WMM/QoS is not supported messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.520153] wlan0: associate with 00:4f:62:08:a3:64 (try 1/3) messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.531000] wlan0: RX AssocResp from 00:4f:62:08:a3:64 (capab=0x411 status=0 aid=3) messages-20121213.xz:Dec 9 17:35:54 anemoi kernel: [12789.534184] wlan0: associated messages-20121213.xz:Dec 9 18:30:19 anemoi kernel: [16050.235220] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20121213.xz:Dec 9 18:30:20 anemoi kernel: [16050.587645] wlan0: deauthenticating from 00:4f:62:08:a3:64 by local choice (reason=3) messages-20121213.xz:Dec 9 18:30:20 anemoi kernel: [16050.604520] cfg80211: Calling CRDA to update world regulatory domain -- messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11238.917955] usb 1-1.3: reset full-speed USB device number 3 using ehci_hcd messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11239.075552] usb 1-1.6: reset high-speed USB device number 4 using ehci_hcd messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11243.535861] ata1: link is slow to respond, please be patient (ready=0) messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11243.841319] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11243.957057] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100) messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11243.957060] ata1.00: revalidation failed (errno=-5) messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.136332] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.137045] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.137047] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.138105] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.138106] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.138432] ata1.00: configured for UDMA/133 messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.149365] sd 0:0:0:0: [sda] Starting disk messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.149717] Extended CMOS year: 2000 messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.150719] PM: restore of devices complete after 10983.567 msecs messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.170301] PM: Image restored successfully. messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.170433] usb 3-1: USB disconnect, device number 4 messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.170304] Restarting tasks ... done. messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.173959] PM: Basic memory bitmaps freed messages-20130101.xz:Dec 13 14:31:40 anemoi kernel: [11249.173967] video LNXVIDEO:00: Restoring backlight state messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.174946] Uhhuh. NMI received for unknown reason 2c on CPU 0. messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.175984] Do you have a strange power saving mode enabled? messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.176948] Dazed and confused, but trying to continue messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.179352] xHCI xhci_drop_endpoint called with unaddressed device messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.179354] xHCI xhci_check_bandwidth called with unaddressed device messages-20130101.xz:Dec 13 14:31:41 anemoi kernel: [11249.179494] xHCI xhci_free_dev called with unaddressed device messages-20130101.xz:Dec 13 14:31:42 anemoi kernel: [11251.186436] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11252.764523] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11252.865435] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11252.870683] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11252.877392] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.063415] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.163903] usb 1-1.4: new full-speed USB device number 11 using ehci_hcd messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.206646] ehci_hcd 0000:00:1d.0: power state changed by ACPI to D3cold messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.253036] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.253040] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.253042] usb 1-1.4: Product: BCM20702A0 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.253043] usb 1-1.4: Manufacturer: Broadcom Corp messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.253045] usb 1-1.4: SerialNumber: 083E8EE1B689 messages-20130101.xz:Dec 13 14:31:44 anemoi kernel: [11253.279986] EXT4-fs (sda2): re-mounted. Opts: data=writeback,commit=600 messages-20130101.xz:Dec 13 14:31:51 anemoi kernel: [11259.812446] wlan0: authenticate with 00:80:48:4f:18:4d ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 19:43 ` Jiri Slaby @ 2013-01-30 20:00 ` Borislav Petkov 2013-01-30 20:33 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-01-30 20:00 UTC (permalink / raw) To: Jiri Slaby Cc: Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki On Wed, Jan 30, 2013 at 08:43:55PM +0100, Jiri Slaby wrote: > On 01/30/2013 06:44 PM, Borislav Petkov wrote: > > On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: > >> You're right, I don't think we're quite ready to merge those patches. > >> But if your NMI is easy to reproduce, it might be worth removing > >> e1000e altogether to see if it still happens. > > > > That's the problem - I've seen it only once so far. I'll watch out for > > it and do the above when I find a reliable way of reproducing it. Will > > keep you posted. > > It happens here too. Dunno what is the root cause. I *think* that it > never happened unless I used ethernet. Other than that I see no pattern. > > Attaching -C 20 grep of messages over the last half year if there is > something that may help somehow. Cool, so it happens once a day, not every day, everytime during resume, and with e1000e. Can you try Bjorn's suggestion to remove e1000e altogether and see if it still happens? -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 20:00 ` Borislav Petkov @ 2013-01-30 20:33 ` Jiri Slaby 2013-01-30 21:39 ` Rafael J. Wysocki 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-30 20:33 UTC (permalink / raw) To: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov, Rafael J. Wysocki [-- Attachment #1: Type: text/plain, Size: 1483 bytes --] On 01/30/2013 09:00 PM, Borislav Petkov wrote: > On Wed, Jan 30, 2013 at 08:43:55PM +0100, Jiri Slaby wrote: >> On 01/30/2013 06:44 PM, Borislav Petkov wrote: >>> On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: >>>> You're right, I don't think we're quite ready to merge those patches. >>>> But if your NMI is easy to reproduce, it might be worth removing >>>> e1000e altogether to see if it still happens. >>> >>> That's the problem - I've seen it only once so far. I'll watch out for >>> it and do the above when I find a reliable way of reproducing it. Will >>> keep you posted. >> >> It happens here too. Dunno what is the root cause. I *think* that it >> never happened unless I used ethernet. Other than that I see no pattern. >> >> Attaching -C 20 grep of messages over the last half year if there is >> something that may help somehow. > > Cool, so it happens once a day, not every day, everytime during resume, > and with e1000e. Can you try Bjorn's suggestion to remove e1000e > altogether and see if it still happens? No, e1000e is not to blame at all. I moved e1000e out of /lib/modules and it still happens. What is cool is that I have steps to reproduce: 1) boot 2) run the attached script (turn on all possible power savings -- in fact everything what powertop suggests) 3) suspend to _disk_ (mem is not enough, BIOS apparently has to interfere here) 4) resume from disk 5) boom I tried to remove also wireless drivers, no change. -- js suse labs [-- Attachment #2: power --] [-- Type: text/plain, Size: 856 bytes --] #!/bin/bash DIRTY_WB=1500 GOVERN=conservative POWERMODE=auto NMI=0 LINK_POW=min_power POW_SAVE=1 POW_SAVE_TXT=on if [ "0$1" -eq 1 ]; then # DIRTY_WB=1500 GOVERN=performance POWERMODE=on NMI=1 LINK_POW=max_performance POW_SAVE=0 POW_SAVE_TXT=off fi /bin/echo -n "$DIRTY_WB" > /proc/sys/vm/dirty_writeback_centisecs /bin/echo -n "$NMI" > /proc/sys/kernel/nmi_watchdog /bin/echo -n "$POW_SAVE" > /sys/module/snd_hda_intel/parameters/power_save iw dev wlan0 set power_save "$POW_SAVE_TXT" ethtool -s eth0 wol d for BUS in usb pci; do for DEV in /sys/bus/$BUS/devices/*/power/control; do /bin/echo -n "$POWERMODE" > $DEV done done for CPU in /sys/devices/system/cpu/*/cpufreq/scaling_governor; do /bin/echo -n "$GOVERN" > $CPU done for HOST in /sys/class/scsi_host/host*/link_power_management_policy; do /bin/echo -n "$LINK_POW" > $HOST done ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 20:33 ` Jiri Slaby @ 2013-01-30 21:39 ` Rafael J. Wysocki 2013-01-30 22:17 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-01-30 21:39 UTC (permalink / raw) To: Jiri Slaby Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Wednesday, January 30, 2013 09:33:27 PM Jiri Slaby wrote: > On 01/30/2013 09:00 PM, Borislav Petkov wrote: > > On Wed, Jan 30, 2013 at 08:43:55PM +0100, Jiri Slaby wrote: > >> On 01/30/2013 06:44 PM, Borislav Petkov wrote: > >>> On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: > >>>> You're right, I don't think we're quite ready to merge those patches. > >>>> But if your NMI is easy to reproduce, it might be worth removing > >>>> e1000e altogether to see if it still happens. > >>> > >>> That's the problem - I've seen it only once so far. I'll watch out for > >>> it and do the above when I find a reliable way of reproducing it. Will > >>> keep you posted. > >> > >> It happens here too. Dunno what is the root cause. I *think* that it > >> never happened unless I used ethernet. Other than that I see no pattern. > >> > >> Attaching -C 20 grep of messages over the last half year if there is > >> something that may help somehow. > > > > Cool, so it happens once a day, not every day, everytime during resume, > > and with e1000e. Can you try Bjorn's suggestion to remove e1000e > > altogether and see if it still happens? > > No, e1000e is not to blame at all. I moved e1000e out of /lib/modules > and it still happens. > > What is cool is that I have steps to reproduce: > 1) boot > 2) run the attached script (turn on all possible power savings -- in > fact everything what powertop suggests) > 3) suspend to _disk_ (mem is not enough, BIOS apparently has to > interfere here) No, I don't think it's the BIOS. Most likely the boot kernel. > 4) resume from disk > 5) boom > > I tried to remove also wireless drivers, no change. Is the resume boot kernel the same as the one in the image? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 21:39 ` Rafael J. Wysocki @ 2013-01-30 22:17 ` Jiri Slaby 2013-01-30 22:45 ` Rafael J. Wysocki 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-30 22:17 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/30/2013 10:39 PM, Rafael J. Wysocki wrote: >> What is cool is that I have steps to reproduce: >> 1) boot >> 2) run the attached script (turn on all possible power savings -- in >> fact everything what powertop suggests) >> 3) suspend to _disk_ (mem is not enough, BIOS apparently has to >> interfere here) > > No, I don't think it's the BIOS. Most likely the boot kernel. Or that... >> 4) resume from disk >> 5) boom >> >> I tried to remove also wireless drivers, no change. > > Is the resume boot kernel the same as the one in the image? Yeah, the same ones: 3.7.5 -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 22:17 ` Jiri Slaby @ 2013-01-30 22:45 ` Rafael J. Wysocki 2013-01-30 23:12 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-01-30 22:45 UTC (permalink / raw) To: Jiri Slaby Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Wednesday, January 30, 2013 11:17:06 PM Jiri Slaby wrote: > On 01/30/2013 10:39 PM, Rafael J. Wysocki wrote: > >> What is cool is that I have steps to reproduce: > >> 1) boot > >> 2) run the attached script (turn on all possible power savings -- in > >> fact everything what powertop suggests) > >> 3) suspend to _disk_ (mem is not enough, BIOS apparently has to > >> interfere here) > > > > No, I don't think it's the BIOS. Most likely the boot kernel. > > Or that... > > >> 4) resume from disk > >> 5) boom > >> > >> I tried to remove also wireless drivers, no change. > > > > Is the resume boot kernel the same as the one in the image? > > Yeah, the same ones: 3.7.5 Well, I guess that we leak some state from the boot kernel to the image kernel. I have no idea what it is, but I suspect something arch-specific. I wonder what the affected systems have in common apart from e1000e? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 22:45 ` Rafael J. Wysocki @ 2013-01-30 23:12 ` Jiri Slaby 2013-01-30 23:47 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-30 23:12 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/30/2013 11:45 PM, Rafael J. Wysocki wrote: > On Wednesday, January 30, 2013 11:17:06 PM Jiri Slaby wrote: >> On 01/30/2013 10:39 PM, Rafael J. Wysocki wrote: >>>> What is cool is that I have steps to reproduce: >>>> 1) boot >>>> 2) run the attached script (turn on all possible power savings -- in >>>> fact everything what powertop suggests) >>>> 3) suspend to _disk_ (mem is not enough, BIOS apparently has to >>>> interfere here) >>> >>> No, I don't think it's the BIOS. Most likely the boot kernel. >> >> Or that... >> >>>> 4) resume from disk >>>> 5) boom >>>> >>>> I tried to remove also wireless drivers, no change. >>> >>> Is the resume boot kernel the same as the one in the image? >> >> Yeah, the same ones: 3.7.5 > > Well, I guess that we leak some state from the boot kernel to the image kernel. > I have no idea what it is, but I suspect something arch-specific. > > I wonder what the affected systems have in common apart from e1000e? Everything as I have thinkpad x230 too :). Is there any other report than Borislav's? I think I will start with commenting parts of `power' script to see exactly which of the power savings cause this. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 23:12 ` Jiri Slaby @ 2013-01-30 23:47 ` Jiri Slaby 2013-01-31 0:54 ` Rafael J. Wysocki 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-30 23:47 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/31/2013 12:12 AM, Jiri Slaby wrote: > I think I will start with commenting parts of `power' script to see > exactly which of the power savings cause this. ... NMI watchdog. If I remove it from the script, the problem disappears. If I try it alone, I have those NMIs. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-30 23:47 ` Jiri Slaby @ 2013-01-31 0:54 ` Rafael J. Wysocki 2013-01-31 7:09 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-01-31 0:54 UTC (permalink / raw) To: Jiri Slaby Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: > On 01/31/2013 12:12 AM, Jiri Slaby wrote: > > I think I will start with commenting parts of `power' script to see > > exactly which of the power savings cause this. > > ... NMI watchdog. If I remove it from the script, the problem > disappears. If I try it alone, I have those NMIs. Well, beats me. :-( I suspect that it doesn't quiesce itself sufficiently before image restoration and we get some crosstalk between the boot kernel and the image kernel. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 0:54 ` Rafael J. Wysocki @ 2013-01-31 7:09 ` Borislav Petkov 2013-01-31 8:14 ` Jiri Slaby 2013-01-31 8:28 ` Jiri Slaby 0 siblings, 2 replies; 58+ messages in thread From: Borislav Petkov @ 2013-01-31 7:09 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: > On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: > > On 01/31/2013 12:12 AM, Jiri Slaby wrote: > > > I think I will start with commenting parts of `power' script to see > > > exactly which of the power savings cause this. > > > > ... NMI watchdog. If I remove it from the script, the problem > > disappears. If I try it alone, I have those NMIs. > > Well, beats me. :-( > > I suspect that it doesn't quiesce itself sufficiently before image restoration > and we get some crosstalk between the boot kernel and the image kernel. Well, I did what Jiri said causes it: echo 0 > /proc/sys/kernel/nmi_watchdog No NMI. BUT(!), if I start powertop and set all tunables in the "Tunables" tab to "Good", then suspend to disk, when I resume I get the NMI and this time the unknown reason is 0x3c. Sounds like this needs bisection... Btw, this is latest -rc5 + tip/master and Jiri triggers it on 3.7-stable ... Btw, this e1000e thing has another problem: when I unplug the network cable and replug it again, it cannot ping local network anymore. Normally, when you plug the network cable back in, it does some sort if link detection saying eth link is back up but it doesn't say it on that box - only a reboot fixes it. Hmm. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 7:09 ` Borislav Petkov @ 2013-01-31 8:14 ` Jiri Slaby 2013-01-31 13:12 ` Rafael J. Wysocki 2013-01-31 8:28 ` Jiri Slaby 1 sibling, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-31 8:14 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/31/2013 08:09 AM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: >> On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: >>> On 01/31/2013 12:12 AM, Jiri Slaby wrote: >>>> I think I will start with commenting parts of `power' script to see >>>> exactly which of the power savings cause this. >>> >>> ... NMI watchdog. If I remove it from the script, the problem >>> disappears. If I try it alone, I have those NMIs. >> >> Well, beats me. :-( >> >> I suspect that it doesn't quiesce itself sufficiently before image restoration >> and we get some crosstalk between the boot kernel and the image kernel. > > Well, I did what Jiri said causes it: > > echo 0 > /proc/sys/kernel/nmi_watchdog > > No NMI. > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > to "Good", then suspend to disk, when I resume I get the NMI and this > time the unknown reason is 0x3c. Sounds like this needs bisection... > Btw, this is latest -rc5 + tip/master and Jiri triggers it on 3.7-stable > ... And 3.6(.0) was the first one I _tried_ and had that issue too. Not sure if there is any bisect-good kernel to start with. > Btw, this e1000e thing has another problem: when I unplug the network > cable and replug it again, it cannot ping local network anymore. > Normally, when you plug the network cable back in, it does some sort if > link detection saying eth link is back up but it doesn't say it on that > box - only a reboot fixes it. Hmm. I think this is what Konstantin fixes with his patches. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 8:14 ` Jiri Slaby @ 2013-01-31 13:12 ` Rafael J. Wysocki 2013-01-31 13:10 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-01-31 13:12 UTC (permalink / raw) To: Jiri Slaby, Borislav Petkov Cc: Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thursday, January 31, 2013 09:14:00 AM Jiri Slaby wrote: > On 01/31/2013 08:09 AM, Borislav Petkov wrote: > > On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: > >> On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: > >>> On 01/31/2013 12:12 AM, Jiri Slaby wrote: > >>>> I think I will start with commenting parts of `power' script to see > >>>> exactly which of the power savings cause this. > >>> > >>> ... NMI watchdog. If I remove it from the script, the problem > >>> disappears. If I try it alone, I have those NMIs. > >> > >> Well, beats me. :-( > >> > >> I suspect that it doesn't quiesce itself sufficiently before image restoration > >> and we get some crosstalk between the boot kernel and the image kernel. > > > > Well, I did what Jiri said causes it: > > > > echo 0 > /proc/sys/kernel/nmi_watchdog > > > > No NMI. > > > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > > to "Good", then suspend to disk, when I resume I get the NMI and this > > time the unknown reason is 0x3c. Sounds like this needs bisection... > > Btw, this is latest -rc5 + tip/master and Jiri triggers it on 3.7-stable > > ... > > And 3.6(.0) was the first one I _tried_ and had that issue too. Not sure > if there is any bisect-good kernel to start with. > > > Btw, this e1000e thing has another problem: when I unplug the network > > cable and replug it again, it cannot ping local network anymore. > > Normally, when you plug the network cable back in, it does some sort if > > link detection saying eth link is back up but it doesn't say it on that > > box - only a reboot fixes it. Hmm. > > I think this is what Konstantin fixes with his patches. Yes, there are two bugs in e1000e, it appears. Konstantin's patch [2/5] fixes one of them, but the other one has to be fixed differently. Boris, would you be able to test a couple of e1000e patches for me? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:12 ` Rafael J. Wysocki @ 2013-01-31 13:10 ` Borislav Petkov 2013-02-02 23:04 ` Rafael J. Wysocki 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-01-31 13:10 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Jan 31, 2013 at 02:12:58PM +0100, Rafael J. Wysocki wrote: > Yes, there are two bugs in e1000e, it appears. Konstantin's > patch [2/5] fixes one of them, but the other one has to be fixed > differently. > > Boris, would you be able to test a couple of e1000e patches for me? Sure, send them on. You can add 2/5 in the mix too. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:10 ` Borislav Petkov @ 2013-02-02 23:04 ` Rafael J. Wysocki 2013-02-03 14:46 ` Borislav Petkov 2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 Jiri Slaby 0 siblings, 2 replies; 58+ messages in thread From: Rafael J. Wysocki @ 2013-02-02 23:04 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov [-- Attachment #1: Type: text/plain, Size: 665 bytes --] On Thursday, January 31, 2013 02:10:34 PM Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 02:12:58PM +0100, Rafael J. Wysocki wrote: > > Yes, there are two bugs in e1000e, it appears. Konstantin's > > patch [2/5] fixes one of them, but the other one has to be fixed > > differently. > > > > Boris, would you be able to test a couple of e1000e patches for me? > > Sure, send them on. You can add 2/5 in the mix too. There you go. The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ The other two are attached. I suppose the ordering doesn't matter. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. [-- Attachment #2: pci-pm-fix-e1000e-runtime-suspend.patch --] [-- Type: text/x-patch, Size: 2247 bytes --] --- drivers/net/ethernet/intel/e1000e/netdev.c | 1 + drivers/pci/pci.c | 1 + drivers/pci/pci.h | 1 - include/linux/pci.h | 1 + 4 files changed, 3 insertions(+), 1 deletion(-) Index: linux-pm/drivers/pci/pci.c =================================================================== --- linux-pm.orig/drivers/pci/pci.c +++ linux-pm/drivers/pci/pci.c @@ -1840,6 +1840,7 @@ int pci_finish_runtime_suspend(struct pc return error; } +EXPORT_SYMBOL_GPL(pci_finish_runtime_suspend); /** * pci_dev_run_wake - Check if device can generate run-time wake-up events. Index: linux-pm/drivers/pci/pci.h =================================================================== --- linux-pm.orig/drivers/pci/pci.h +++ linux-pm/drivers/pci/pci.h @@ -64,7 +64,6 @@ extern int pci_set_platform_pm(struct pc extern void pci_update_current_state(struct pci_dev *dev, pci_power_t state); extern void pci_power_up(struct pci_dev *dev); extern void pci_disable_enabled_device(struct pci_dev *dev); -extern int pci_finish_runtime_suspend(struct pci_dev *dev); extern int __pci_pme_wakeup(struct pci_dev *dev, void *ign); extern void pci_wakeup_bus(struct pci_bus *bus); extern void pci_config_pm_runtime_get(struct pci_dev *dev); Index: linux-pm/include/linux/pci.h =================================================================== --- linux-pm.orig/include/linux/pci.h +++ linux-pm/include/linux/pci.h @@ -936,6 +936,7 @@ int pci_back_from_sleep(struct pci_dev * bool pci_dev_run_wake(struct pci_dev *dev); bool pci_check_pme_status(struct pci_dev *dev); void pci_pme_wakeup_bus(struct pci_bus *bus); +int pci_finish_runtime_suspend(struct pci_dev *dev); static inline int pci_enable_wake(struct pci_dev *dev, pci_power_t state, bool enable) Index: linux-pm/drivers/net/ethernet/intel/e1000e/netdev.c =================================================================== --- linux-pm.orig/drivers/net/ethernet/intel/e1000e/netdev.c +++ linux-pm/drivers/net/ethernet/intel/e1000e/netdev.c @@ -5696,6 +5696,7 @@ static int e1000_runtime_suspend(struct bool wake; __e1000_shutdown(pdev, &wake, true); + pci_finish_runtime_suspend(pdev); } return 0; [-- Attachment #3: pci-pm-clear-state_saved-during-suspend.patch --] [-- Type: text/x-patch, Size: 1028 bytes --] --- drivers/pci/pci-driver.c | 4 ++++ 1 file changed, 4 insertions(+) Index: linux-pm/drivers/pci/pci-driver.c =================================================================== --- linux-pm.orig/drivers/pci/pci-driver.c +++ linux-pm/drivers/pci/pci-driver.c @@ -628,6 +628,7 @@ static int pci_pm_suspend(struct device goto Fixup; } + pci_dev->state_saved = false; if (pm->suspend) { pci_power_t prev = pci_dev->current_state; int error; @@ -774,6 +775,7 @@ static int pci_pm_freeze(struct device * return 0; } + pci_dev->state_saved = false; if (pm->freeze) { int error; @@ -862,6 +864,7 @@ static int pci_pm_poweroff(struct device goto Fixup; } + pci_dev->state_saved = false; if (pm->poweroff) { int error; @@ -987,6 +990,7 @@ static int pci_pm_runtime_suspend(struct if (!pm || !pm->runtime_suspend) return -ENOSYS; + pci_dev->state_saved = false; pci_dev->no_d3cold = false; error = pm->runtime_suspend(dev); suspend_report_result(pm->runtime_suspend, error); ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-02 23:04 ` Rafael J. Wysocki @ 2013-02-03 14:46 ` Borislav Petkov 2013-02-03 20:15 ` Rafael J. Wysocki 2013-02-14 14:39 ` Borislav Petkov 2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 Jiri Slaby 1 sibling, 2 replies; 58+ messages in thread From: Borislav Petkov @ 2013-02-03 14:46 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > > The other two are attached. I suppose the ordering doesn't matter. Ok, the eth link cable hotplugging issue seems fixed, plugging and unplugging the cable works as expected. The issue I triggered earlier: > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > to "Good", then suspend to disk, when I resume I get the NMI and this > time the unknown reason is 0x3c. ... still happens: [ 123.250870] PM: Creating hibernation image: [ 123.504940] PM: Need to copy 95667 pages <--- suspend to disk [ 123.252841] Enabling non-boot CPUs ... <--- resume [ 123.254021] SMP alternatives: lockdep: fixing up alternatives [ 123.254026] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 123.275566] CPU1 is up [ 123.275697] SMP alternatives: lockdep: fixing up alternatives [ 123.275699] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 123.297581] CPU2 is up [ 123.297699] SMP alternatives: lockdep: fixing up alternatives [ 123.297701] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 123.319358] CPU3 is up [ 123.321928] i915 0000:00:02.0: power state changed by ACPI to D0 [ 123.321992] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 [ 123.333256] ehci-pci 0000:00:1a.0: power state changed by ACPI to D0 [ 123.344541] ehci-pci 0000:00:1d.0: power state changed by ACPI to D0 [ 123.345012] sdhci-pci 0000:02:00.0: MMC controller base frequency changed to 50Mhz. [ 123.345744] PM: noirq restore of devices complete after 24.061 msecs [ 123.346684] PM: early restore of devices complete after 0.836 msecs [ 123.389863] i915 0000:00:02.0: setting latency timer to 64 [ 123.389870] xhci_hcd 0000:00:14.0: setting latency timer to 64 [ 123.389887] ehci-pci 0000:00:1a.0: setting latency timer to 64 [ 123.389907] usb usb3: root hub lost power or was reset [ 123.389908] usb usb1: root hub lost power or was reset [ 123.389909] usb usb2: root hub lost power or was reset [ 123.390034] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X [ 123.390171] xhci_hcd 0000:00:14.0: irq 45 for MSI/MSI-X [ 123.390308] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X [ 123.391013] ehci-pci 0000:00:1d.0: setting latency timer to 64 [ 123.391038] usb usb4: root hub lost power or was reset [ 123.393798] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported [ 123.394115] ahci 0000:00:1f.2: setting latency timer to 64 [ 123.394229] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio. [ 123.394923] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported [ 123.697314] usb 3-1: reset high-speed USB device number 2 using ehci-pci [ 123.698252] ata2: SATA link down (SStatus 0 SControl 300) [ 123.699286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 123.701259] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 123.701287] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 123.701291] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 123.702699] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 123.702703] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 123.703222] ata5: SATA link down (SStatus 0 SControl 300) [ 123.704603] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 123.704606] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 123.705938] ata3.00: configured for UDMA/100 [ 123.706033] sd 2:0:0:0: [sdb] Starting disk [ 123.706041] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 123.706045] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 123.735336] ata1.00: configured for UDMA/133 [ 123.735662] sd 0:0:0:0: [sda] Starting disk [ 123.912740] usb 4-1: reset high-speed USB device number 2 using ehci-pci [ 124.129520] PM: restore of devices complete after 741.589 msecs [ 124.174684] Restarting tasks ... done. [ 124.177521] video LNXVIDEO:00: Restoring backlight state [ 124.186033] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold [ 124.214931] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold [ 124.214970] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold [ 124.394882] Uhhuh. NMI received for unknown reason 3c on CPU 0. <--- FUN. [ 124.394890] Do you have a strange power saving mode enabled? [ 124.394892] Dazed and confused, but trying to continue [ 124.407438] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 127.035581] ehci-pci 0000:00:1a.0: power state changed by ACPI to D0 [ 127.135668] ehci-pci 0000:00:1a.0: setting latency timer to 64 [ 127.135910] ehci-pci 0000:00:1d.0: power state changed by ACPI to D0 [ 127.146500] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold [ 127.236381] ehci-pci 0000:00:1d.0: setting latency timer to 64 [ 127.236658] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 [ 127.247244] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold [ 127.337137] xhci_hcd 0000:00:14.0: setting latency timer to 64 [ 127.348286] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X [ 127.348975] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold [ 129.255203] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 129.255215] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-03 14:46 ` Borislav Petkov @ 2013-02-03 20:15 ` Rafael J. Wysocki 2013-02-03 20:58 ` Borislav Petkov 2013-02-14 14:39 ` Borislav Petkov 1 sibling, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-02-03 20:15 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sunday, February 03, 2013 03:46:56 PM Borislav Petkov wrote: > On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: > > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > > > > The other two are attached. I suppose the ordering doesn't matter. > > Ok, the eth link cable hotplugging issue seems fixed, plugging and > unplugging the cable works as expected. Cool, thanks. > The issue I triggered earlier: > > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > > to "Good", then suspend to disk, when I resume I get the NMI and this > > time the unknown reason is 0x3c. > > ... still happens: > > [ 123.250870] PM: Creating hibernation image: > [ 123.504940] PM: Need to copy 95667 pages <--- suspend to disk > [ 123.252841] Enabling non-boot CPUs ... <--- resume > [ 123.254021] SMP alternatives: lockdep: fixing up alternatives > [ 123.254026] smpboot: Booting Node 0 Processor 1 APIC 0x1 > [ 123.275566] CPU1 is up > [ 123.275697] SMP alternatives: lockdep: fixing up alternatives > [ 123.275699] smpboot: Booting Node 0 Processor 2 APIC 0x2 > [ 123.297581] CPU2 is up > [ 123.297699] SMP alternatives: lockdep: fixing up alternatives > [ 123.297701] smpboot: Booting Node 0 Processor 3 APIC 0x3 > [ 123.319358] CPU3 is up > [ 123.321928] i915 0000:00:02.0: power state changed by ACPI to D0 > [ 123.321992] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 > [ 123.333256] ehci-pci 0000:00:1a.0: power state changed by ACPI to D0 > [ 123.344541] ehci-pci 0000:00:1d.0: power state changed by ACPI to D0 > [ 123.345012] sdhci-pci 0000:02:00.0: MMC controller base frequency changed to 50Mhz. > [ 123.345744] PM: noirq restore of devices complete after 24.061 msecs > [ 123.346684] PM: early restore of devices complete after 0.836 msecs > [ 123.389863] i915 0000:00:02.0: setting latency timer to 64 > [ 123.389870] xhci_hcd 0000:00:14.0: setting latency timer to 64 > [ 123.389887] ehci-pci 0000:00:1a.0: setting latency timer to 64 > [ 123.389907] usb usb3: root hub lost power or was reset > [ 123.389908] usb usb1: root hub lost power or was reset > [ 123.389909] usb usb2: root hub lost power or was reset > [ 123.390034] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X > [ 123.390171] xhci_hcd 0000:00:14.0: irq 45 for MSI/MSI-X > [ 123.390308] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X > [ 123.391013] ehci-pci 0000:00:1d.0: setting latency timer to 64 > [ 123.391038] usb usb4: root hub lost power or was reset > [ 123.393798] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported > [ 123.394115] ahci 0000:00:1f.2: setting latency timer to 64 > [ 123.394229] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio. > [ 123.394923] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported > [ 123.697314] usb 3-1: reset high-speed USB device number 2 using ehci-pci > [ 123.698252] ata2: SATA link down (SStatus 0 SControl 300) > [ 123.699286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 123.701259] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 123.701287] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded > [ 123.701291] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out > [ 123.702699] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded > [ 123.702703] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out > [ 123.703222] ata5: SATA link down (SStatus 0 SControl 300) > [ 123.704603] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded > [ 123.704606] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out > [ 123.705938] ata3.00: configured for UDMA/100 > [ 123.706033] sd 2:0:0:0: [sdb] Starting disk > [ 123.706041] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded > [ 123.706045] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out > [ 123.735336] ata1.00: configured for UDMA/133 > [ 123.735662] sd 0:0:0:0: [sda] Starting disk > [ 123.912740] usb 4-1: reset high-speed USB device number 2 using ehci-pci > [ 124.129520] PM: restore of devices complete after 741.589 msecs > [ 124.174684] Restarting tasks ... done. > [ 124.177521] video LNXVIDEO:00: Restoring backlight state > [ 124.186033] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold > [ 124.214931] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold > [ 124.214970] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold > [ 124.394882] Uhhuh. NMI received for unknown reason 3c on CPU 0. <--- FUN. > [ 124.394890] Do you have a strange power saving mode enabled? > [ 124.394892] Dazed and confused, but trying to continue > [ 124.407438] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off > [ 127.035581] ehci-pci 0000:00:1a.0: power state changed by ACPI to D0 > [ 127.135668] ehci-pci 0000:00:1a.0: setting latency timer to 64 > [ 127.135910] ehci-pci 0000:00:1d.0: power state changed by ACPI to D0 > [ 127.146500] ehci-pci 0000:00:1a.0: power state changed by ACPI to D3cold > [ 127.236381] ehci-pci 0000:00:1d.0: setting latency timer to 64 > [ 127.236658] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0 > [ 127.247244] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold > [ 127.337137] xhci_hcd 0000:00:14.0: setting latency timer to 64 > [ 127.348286] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X > [ 127.348975] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold > [ 129.255203] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > [ 129.255215] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO Is suspend-to-RAM triggering that as too? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-03 20:15 ` Rafael J. Wysocki @ 2013-02-03 20:58 ` Borislav Petkov 2013-02-03 21:06 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-02-03 20:58 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sun, Feb 03, 2013 at 09:15:12PM +0100, Rafael J. Wysocki wrote: > Is suspend-to-RAM triggering that as too? Nope, not really. But, just to confirm: s2r is echo "shutdown" > /sys/power/disk echo "mem" > /sys/power/state right? Btw, this bug is very strange. So I did a couple more s2disk runs, i.e. echo "shutdown" > /sys/power/disk echo "disk" > /sys/power/state and it seemed to me that when the eth cable is plugged in, it would suspend and resume fine. When I then boot, unplug the cable, set all tunables to "Good", suspend to disk and resume, no NMI message. When I plug the cable back, only *then* the message triggered. I need to play with this a bit more to get a better sense of when exactly it happens. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-03 20:58 ` Borislav Petkov @ 2013-02-03 21:06 ` Borislav Petkov 2013-02-03 21:15 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-02-03 21:06 UTC (permalink / raw) To: Rafael J. Wysocki, Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sun, Feb 03, 2013 at 09:58:57PM +0100, Borislav Petkov wrote: > and it seemed to me that when the eth cable is plugged in, it would > suspend and resume fine. When I then boot, unplug the cable, set all > tunables to "Good", suspend to disk and resume, no NMI message. When I > plug the cable back, only *then* the message triggered. > > I need to play with this a bit more to get a better sense of when > exactly it happens. Ok, not really. It is not influenced by the cable being plugged - it happens when I plug in the cable or simply shortly after resume, without the cable. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-03 21:06 ` Borislav Petkov @ 2013-02-03 21:15 ` Borislav Petkov 0 siblings, 0 replies; 58+ messages in thread From: Borislav Petkov @ 2013-02-03 21:15 UTC (permalink / raw) To: Rafael J. Wysocki, Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sun, Feb 03, 2013 at 10:06:45PM +0100, Borislav Petkov wrote: > On Sun, Feb 03, 2013 at 09:58:57PM +0100, Borislav Petkov wrote: > > and it seemed to me that when the eth cable is plugged in, it would > > suspend and resume fine. When I then boot, unplug the cable, set all > > tunables to "Good", suspend to disk and resume, no NMI message. When I > > plug the cable back, only *then* the message triggered. > > > > I need to play with this a bit more to get a better sense of when > > exactly it happens. > > Ok, not really. > > It is not influenced by the cable being plugged - it happens when I plug > in the cable or simply shortly after resume, without the cable. Ok, just did 10 s2ram cycles back-to-back - no issue whatsoever, no matter when I (un-)plug the cable. Changed the suspend script to echo "disk" > /sys/power/state and did an 11th suspend-resume run. It triggered right after resuming from disk. So I'd guess the image kernel might be the required condition for the triggering of the issue. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-03 14:46 ` Borislav Petkov 2013-02-03 20:15 ` Rafael J. Wysocki @ 2013-02-14 14:39 ` Borislav Petkov 2013-02-14 17:17 ` Bjorn Helgaas 1 sibling, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-02-14 14:39 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Sun, Feb 03, 2013 at 03:46:56PM +0100, Borislav Petkov wrote: > On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: > > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > > > > The other two are attached. I suppose the ordering doesn't matter. > > Ok, the eth link cable hotplugging issue seems fixed, plugging and > unplugging the cable works as expected. Q: what happened to those, are they going upstream for 3.9 or are you sending them now for 3.8? They fix at least the cable hotplugging issue so at least one thing is covered. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-14 14:39 ` Borislav Petkov @ 2013-02-14 17:17 ` Bjorn Helgaas 2013-02-14 19:12 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Bjorn Helgaas @ 2013-02-14 17:17 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Feb 14, 2013 at 7:39 AM, Borislav Petkov <bp@suse.de> wrote: > On Sun, Feb 03, 2013 at 03:46:56PM +0100, Borislav Petkov wrote: >> On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: >> > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ >> > >> > The other two are attached. I suppose the ordering doesn't matter. >> >> Ok, the eth link cable hotplugging issue seems fixed, plugging and >> unplugging the cable works as expected. > > Q: what happened to those, are they going upstream for 3.9 or are you > sending them now for 3.8? > > They fix at least the cable hotplugging issue so at least one thing is > covered. I haven't done anything with the e1000e patches; I assume the e1000e maintainers will take care of those. I merged the following patches for v3.9: * pci/konstantin-runtime-pm: PCI/PM: Clear state_saved during suspend PCI: Use atomic_inc_return() rather than atomic_add_return() PCI: Catch attempts to disable already-disabled devices PCI: Disable Bus Master unconditionally in pci_device_shutdown() You can see the actual patches I merged at: http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=shortlog;h=refs/heads/next It's pretty late for v3.8, but let me know if you think they're critical. Bjorn ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-14 17:17 ` Bjorn Helgaas @ 2013-02-14 19:12 ` Borislav Petkov 2013-02-15 8:54 ` Konstantin Khlebnikov 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-02-14 19:12 UTC (permalink / raw) To: Bjorn Helgaas, Rafael J. Wysocki Cc: Jiri Slaby, x86, lkml, Konstantin Khlebnikov On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote: > On Thu, Feb 14, 2013 at 7:39 AM, Borislav Petkov <bp@suse.de> wrote: > > On Sun, Feb 03, 2013 at 03:46:56PM +0100, Borislav Petkov wrote: > >> On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: > >> > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > >> > > >> > The other two are attached. I suppose the ordering doesn't matter. > >> > >> Ok, the eth link cable hotplugging issue seems fixed, plugging and > >> unplugging the cable works as expected. > > > > Q: what happened to those, are they going upstream for 3.9 or are you > > sending them now for 3.8? > > > > They fix at least the cable hotplugging issue so at least one thing is > > covered. > > I haven't done anything with the e1000e patches; I assume the e1000e > maintainers will take care of those. > > I merged the following patches for v3.9: > > * pci/konstantin-runtime-pm: > PCI/PM: Clear state_saved during suspend > PCI: Use atomic_inc_return() rather than atomic_add_return() > PCI: Catch attempts to disable already-disabled devices > PCI: Disable Bus Master unconditionally in pci_device_shutdown() > > You can see the actual patches I merged at: > http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=shortlog;h=refs/heads/next > > It's pretty late for v3.8, but let me know if you think they're critical. Ok, I meant those: http://marc.info/?l=linux-kernel&m=135984592927219 They fix the link detection issue on my x230. So let's see. The first one is: * https://patchwork.kernel.org/patch/2001211/ (e1000e: fix pci device enable counter balance) Rafael said this one is a real bugfix. Looks like e1000e maintainers are picking that one? * pci-pm-fix-e1000e-runtime-suspend.patch I don't see that one in your tree. * pci-pm-clear-state_saved-during-suspend.patch I can see this one in your tree: http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commitdiff;h=82fee4d67ab86d6fe5eb0f9a9e988ca9d654d765 With the imminence of the 3.8 release, we probably want to wait for after the merge window and retest again, then apply and packport stuff, if needed. And the NMI issue is still unfixed so this needs more work, AFAICT. Oh well, after the merge window. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-14 19:12 ` Borislav Petkov @ 2013-02-15 8:54 ` Konstantin Khlebnikov 2013-02-15 9:16 ` Borislav Petkov 2013-03-01 12:51 ` e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] Jiri Slaby 0 siblings, 2 replies; 58+ messages in thread From: Konstantin Khlebnikov @ 2013-02-15 8:54 UTC (permalink / raw) To: Borislav Petkov, Bjorn Helgaas, Rafael J. Wysocki, Jiri Slaby, x86, lkml Borislav Petkov wrote: > On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote: >> On Thu, Feb 14, 2013 at 7:39 AM, Borislav Petkov<bp@suse.de> wrote: >>> On Sun, Feb 03, 2013 at 03:46:56PM +0100, Borislav Petkov wrote: >>>> On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote: >>>>> The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ >>>>> >>>>> The other two are attached. I suppose the ordering doesn't matter. >>>> >>>> Ok, the eth link cable hotplugging issue seems fixed, plugging and >>>> unplugging the cable works as expected. >>> >>> Q: what happened to those, are they going upstream for 3.9 or are you >>> sending them now for 3.8? >>> >>> They fix at least the cable hotplugging issue so at least one thing is >>> covered. >> >> I haven't done anything with the e1000e patches; I assume the e1000e >> maintainers will take care of those. >> >> I merged the following patches for v3.9: >> >> * pci/konstantin-runtime-pm: >> PCI/PM: Clear state_saved during suspend >> PCI: Use atomic_inc_return() rather than atomic_add_return() >> PCI: Catch attempts to disable already-disabled devices >> PCI: Disable Bus Master unconditionally in pci_device_shutdown() >> >> You can see the actual patches I merged at: >> http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=shortlog;h=refs/heads/next >> >> It's pretty late for v3.8, but let me know if you think they're critical. > > Ok, I meant those: > > http://marc.info/?l=linux-kernel&m=135984592927219 > > They fix the link detection issue on my x230. So let's see. The first one is: > > * https://patchwork.kernel.org/patch/2001211/ (e1000e: fix pci device enable > counter balance) please use this instead: [PATCH v2 1/7] e1000e: fix pci-device enable-counter balance https://lkml.org/lkml/2013/2/4/190 from v2 patchset: https://lkml.org/lkml/2013/2/4/185 > > Rafael said this one is a real bugfix. Looks like e1000e maintainers are > picking that one? > > * pci-pm-fix-e1000e-runtime-suspend.patch > > I don't see that one in your tree. > > * pci-pm-clear-state_saved-during-suspend.patch > > I can see this one in your tree: http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commitdiff;h=82fee4d67ab86d6fe5eb0f9a9e988ca9d654d765 > > With the imminence of the 3.8 release, we probably want to wait for > after the merge window and retest again, then apply and packport stuff, > if needed. > > And the NMI issue is still unfixed so this needs more work, AFAICT. Oh > well, after the merge window. > ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-15 8:54 ` Konstantin Khlebnikov @ 2013-02-15 9:16 ` Borislav Petkov 2013-03-04 21:50 ` Borislav Petkov 2013-03-01 12:51 ` e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] Jiri Slaby 1 sibling, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-02-15 9:16 UTC (permalink / raw) To: Konstantin Khlebnikov Cc: Bjorn Helgaas, Rafael J. Wysocki, Jiri Slaby, x86, lkml On Fri, Feb 15, 2013 at 12:54:12PM +0400, Konstantin Khlebnikov wrote: > >* https://patchwork.kernel.org/patch/2001211/ (e1000e: fix pci device enable > >counter balance) > > please use this instead: > > [PATCH v2 1/7] e1000e: fix pci-device enable-counter balance > https://lkml.org/lkml/2013/2/4/190 > > from v2 patchset: https://lkml.org/lkml/2013/2/4/185 So it looks Bjorn has taken most of them and the e1000e one will go through the e1000e maintainers. I'll test after the merge window is done. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-15 9:16 ` Borislav Petkov @ 2013-03-04 21:50 ` Borislav Petkov 2013-03-05 0:16 ` Bjorn Helgaas 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-03-04 21:50 UTC (permalink / raw) To: Konstantin Khlebnikov, Bjorn Helgaas, Rafael J. Wysocki, Jiri Slaby, x86, lkml On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: > So it looks Bjorn has taken most of them and the e1000e one will go > through the e1000e maintainers. I'll test after the merge window is > done. Issue still persists on 3.9-rc1 :-( : Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-04 21:50 ` Borislav Petkov @ 2013-03-05 0:16 ` Bjorn Helgaas 2013-03-05 9:42 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Bjorn Helgaas @ 2013-03-05 0:16 UTC (permalink / raw) To: Borislav Petkov, Konstantin Khlebnikov, Bjorn Helgaas, Rafael J. Wysocki, Jiri Slaby, x86, lkml Cc: e1000-devel, Jeff Kirsher, Bruce Allan [+cc e1000-devel, Jeff, Bruce] On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote: > On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: >> So it looks Bjorn has taken most of them and the e1000e one will go >> through the e1000e maintainers. I'll test after the merge window is >> done. > > Issue still persists on 3.9-rc1 :-( : > > Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. > Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? > Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue The e1000e changes didn't get merged, did they? I don't see the following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in 3.9-rc1: e1000e: fix pci-device enable-counter balance e1000e: fix runtime power management transitions e1000e: fix accessing to suspended device ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 0:16 ` Bjorn Helgaas @ 2013-03-05 9:42 ` Jiri Slaby 2013-03-05 9:58 ` Borislav Petkov 2013-03-05 10:01 ` Jeff Kirsher 0 siblings, 2 replies; 58+ messages in thread From: Jiri Slaby @ 2013-03-05 9:42 UTC (permalink / raw) To: Bjorn Helgaas, Borislav Petkov, Konstantin Khlebnikov, Rafael J. Wysocki, x86, lkml Cc: e1000-devel, Jeff Kirsher, Bruce Allan On 03/05/2013 01:16 AM, Bjorn Helgaas wrote: > [+cc e1000-devel, Jeff, Bruce] > > On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote: >> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: >>> So it looks Bjorn has taken most of them and the e1000e one will go >>> through the e1000e maintainers. I'll test after the merge window is >>> done. >> >> Issue still persists on 3.9-rc1 :-( : >> >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue > > The e1000e changes didn't get merged, did they? I don't see the > following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in > 3.9-rc1: > > e1000e: fix pci-device enable-counter balance > e1000e: fix runtime power management transitions > e1000e: fix accessing to suspended device You're right. They are not even in -next :(. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 9:42 ` Jiri Slaby @ 2013-03-05 9:58 ` Borislav Petkov 2013-03-05 10:01 ` Jiri Slaby 2013-03-05 10:02 ` Jeff Kirsher 2013-03-05 10:01 ` Jeff Kirsher 1 sibling, 2 replies; 58+ messages in thread From: Borislav Petkov @ 2013-03-05 9:58 UTC (permalink / raw) To: Jiri Slaby, Rafael J. Wysocki Cc: Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Jeff Kirsher, Bruce Allan On Tue, Mar 05, 2013 at 10:42:17AM +0100, Jiri Slaby wrote: > On 03/05/2013 01:16 AM, Bjorn Helgaas wrote: > > [+cc e1000-devel, Jeff, Bruce] > > > > On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote: > >> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: > >>> So it looks Bjorn has taken most of them and the e1000e one will go > >>> through the e1000e maintainers. I'll test after the merge window is > >>> done. > >> > >> Issue still persists on 3.9-rc1 :-( : > >> > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue > > > > The e1000e changes didn't get merged, did they? I don't see the > > following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in > > 3.9-rc1: > > > > e1000e: fix pci-device enable-counter balance > > e1000e: fix runtime power management transitions > > e1000e: fix accessing to suspended device > > You're right. They are not even in -next :(. Oh, and there's another issue with this driver I reported yesterday: http://marc.info/?l=linux-kernel&m=136243374114892&w=2: "Trying to free already-free IRQ 20" which happens during suspend so it seems also related. Rafael, what's the state of those patches here: https://lkml.org/lkml/2013/2/4/185, are they ready to be tested or you still have issues with them? Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 9:58 ` Borislav Petkov @ 2013-03-05 10:01 ` Jiri Slaby 2013-03-05 10:02 ` Jeff Kirsher 1 sibling, 0 replies; 58+ messages in thread From: Jiri Slaby @ 2013-03-05 10:01 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Jeff Kirsher, Bruce Allan On 03/05/2013 10:58 AM, Borislav Petkov wrote: > Rafael, what's the state of those patches here: > https://lkml.org/lkml/2013/2/4/185, are they ready to be tested or you > still have issues with them? Note there is a resend version: https://lkml.org/lkml/2013/2/25/3 with a note from Jeff Kirsher: I have added this patch to my e1000e patch queue. thanks, -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 9:58 ` Borislav Petkov 2013-03-05 10:01 ` Jiri Slaby @ 2013-03-05 10:02 ` Jeff Kirsher 2013-03-05 10:14 ` Borislav Petkov 1 sibling, 1 reply; 58+ messages in thread From: Jeff Kirsher @ 2013-03-05 10:02 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan [-- Attachment #1: Type: text/plain, Size: 2086 bytes --] On Tue, 2013-03-05 at 10:58 +0100, Borislav Petkov wrote: > On Tue, Mar 05, 2013 at 10:42:17AM +0100, Jiri Slaby wrote: > > On 03/05/2013 01:16 AM, Bjorn Helgaas wrote: > > > [+cc e1000-devel, Jeff, Bruce] > > > > > > On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote: > > >> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: > > >>> So it looks Bjorn has taken most of them and the e1000e one will go > > >>> through the e1000e maintainers. I'll test after the merge window is > > >>> done. > > >> > > >> Issue still persists on 3.9-rc1 :-( : > > >> > > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. > > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? > > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue > > > > > > The e1000e changes didn't get merged, did they? I don't see the > > > following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in > > > 3.9-rc1: > > > > > > e1000e: fix pci-device enable-counter balance > > > e1000e: fix runtime power management transitions > > > e1000e: fix accessing to suspended device > > > > You're right. They are not even in -next :(. > > Oh, and there's another issue with this driver I reported yesterday: > http://marc.info/?l=linux-kernel&m=136243374114892&w=2: > > "Trying to free already-free IRQ 20" > > which happens during suspend so it seems also related. > > Rafael, what's the state of those patches here: > https://lkml.org/lkml/2013/2/4/185, are they ready to be tested or you > still have issues with them? They are in my queue of e1000e patches for net and are being testing currently. I should be able to push them upstream this week. [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 10:02 ` Jeff Kirsher @ 2013-03-05 10:14 ` Borislav Petkov 2013-03-05 10:29 ` Jeff Kirsher 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-03-05 10:14 UTC (permalink / raw) To: Jeff Kirsher Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Tue, Mar 05, 2013 at 02:02:48AM -0800, Jeff Kirsher wrote: > They are in my queue of e1000e patches for net and are being testing > currently. I should be able to push them upstream this week. Right, if you'd like me to run them here too, let me know. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 10:14 ` Borislav Petkov @ 2013-03-05 10:29 ` Jeff Kirsher 2013-03-05 11:27 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Jeff Kirsher @ 2013-03-05 10:29 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan [-- Attachment #1: Type: text/plain, Size: 461 bytes --] On Tue, 2013-03-05 at 11:14 +0100, Borislav Petkov wrote: > > On Tue, Mar 05, 2013 at 02:02:48AM -0800, Jeff Kirsher wrote: > > They are in my queue of e1000e patches for net and are being testing > > currently. I should be able to push them upstream this week. > > Right, if you'd like me to run them here too, let me know. Any additional testing is very much appreciated, so feel free to test the patches with what hardware you have. Thanks! [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 10:29 ` Jeff Kirsher @ 2013-03-05 11:27 ` Borislav Petkov 2013-03-05 11:33 ` Jeff Kirsher 2013-03-06 0:13 ` Rafael J. Wysocki 0 siblings, 2 replies; 58+ messages in thread From: Borislav Petkov @ 2013-03-05 11:27 UTC (permalink / raw) To: Jeff Kirsher Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Tue, Mar 05, 2013 at 02:29:01AM -0800, Jeff Kirsher wrote: > On Tue, 2013-03-05 at 11:14 +0100, Borislav Petkov wrote: > > > > On Tue, Mar 05, 2013 at 02:02:48AM -0800, Jeff Kirsher wrote: > > > They are in my queue of e1000e patches for net and are being testing > > > currently. I should be able to push them upstream this week. > > > > Right, if you'd like me to run them here too, let me know. > > Any additional testing is very much appreciated, so feel free to test > the patches with what hardware you have. Yep, it looks good, machine suspends ok again. I'll watch it in the next couple of days. The only problem that remains is this: [ 103.137024] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold [ 103.161032] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold [ 103.462328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 103.462342] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO [ 108.472847] Uhhuh. NMI received for unknown reason 3c on CPU 0. <--- [ 108.472850] Do you have a strange power saving mode enabled? [ 108.472851] Dazed and confused, but trying to continue AFAIR, Rafael said it had something to do with the suspend kernel not picking up settings done to the main kernel on time. Or something to that effect, my memory is hazy. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 11:27 ` Borislav Petkov @ 2013-03-05 11:33 ` Jeff Kirsher 2013-03-05 11:42 ` Borislav Petkov 2013-03-06 0:13 ` Rafael J. Wysocki 1 sibling, 1 reply; 58+ messages in thread From: Jeff Kirsher @ 2013-03-05 11:33 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan [-- Attachment #1: Type: text/plain, Size: 1532 bytes --] On Tue, 2013-03-05 at 12:27 +0100, Borislav Petkov wrote: > On Tue, Mar 05, 2013 at 02:29:01AM -0800, Jeff Kirsher wrote: > > On Tue, 2013-03-05 at 11:14 +0100, Borislav Petkov wrote: > > > > > > On Tue, Mar 05, 2013 at 02:02:48AM -0800, Jeff Kirsher wrote: > > > > They are in my queue of e1000e patches for net and are being testing > > > > currently. I should be able to push them upstream this week. > > > > > > Right, if you'd like me to run them here too, let me know. > > > > Any additional testing is very much appreciated, so feel free to test > > the patches with what hardware you have. > > Yep, it looks good, machine suspends ok again. I'll watch it in the next > couple of days. > > The only problem that remains is this: > > [ 103.137024] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold > [ 103.161032] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold > [ 103.462328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > [ 103.462342] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > [ 108.472847] Uhhuh. NMI received for unknown reason 3c on CPU 0. <--- > [ 108.472850] Do you have a strange power saving mode enabled? > [ 108.472851] Dazed and confused, but trying to continue > > AFAIR, Rafael said it had something to do with the suspend kernel not > picking up settings done to the main kernel on time. Or something to > that effect, my memory is hazy. > Would you like me to add your Tested-by: to the patches? [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 11:33 ` Jeff Kirsher @ 2013-03-05 11:42 ` Borislav Petkov 0 siblings, 0 replies; 58+ messages in thread From: Borislav Petkov @ 2013-03-05 11:42 UTC (permalink / raw) To: Jeff Kirsher Cc: Jiri Slaby, Rafael J. Wysocki, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Tue, Mar 05, 2013 at 03:33:45AM -0800, Jeff Kirsher wrote: > Would you like me to add your Tested-by: to the patches? Sure, if you'd like to: Tested-by: Borislav Petkov <bp@suse.de> Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 11:27 ` Borislav Petkov 2013-03-05 11:33 ` Jeff Kirsher @ 2013-03-06 0:13 ` Rafael J. Wysocki 2013-03-06 0:19 ` Borislav Petkov 1 sibling, 1 reply; 58+ messages in thread From: Rafael J. Wysocki @ 2013-03-06 0:13 UTC (permalink / raw) To: Borislav Petkov Cc: Jeff Kirsher, Jiri Slaby, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Tuesday, March 05, 2013 12:27:37 PM Borislav Petkov wrote: > On Tue, Mar 05, 2013 at 02:29:01AM -0800, Jeff Kirsher wrote: > > On Tue, 2013-03-05 at 11:14 +0100, Borislav Petkov wrote: > > > > > > On Tue, Mar 05, 2013 at 02:02:48AM -0800, Jeff Kirsher wrote: > > > > They are in my queue of e1000e patches for net and are being testing > > > > currently. I should be able to push them upstream this week. > > > > > > Right, if you'd like me to run them here too, let me know. > > > > Any additional testing is very much appreciated, so feel free to test > > the patches with what hardware you have. > > Yep, it looks good, machine suspends ok again. I'll watch it in the next > couple of days. > > The only problem that remains is this: > > [ 103.137024] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3cold > [ 103.161032] ehci-pci 0000:00:1d.0: power state changed by ACPI to D3cold > [ 103.462328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > [ 103.462342] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > [ 108.472847] Uhhuh. NMI received for unknown reason 3c on CPU 0. <--- > [ 108.472850] Do you have a strange power saving mode enabled? > [ 108.472851] Dazed and confused, but trying to continue > > AFAIR, Rafael said it had something to do with the suspend kernel not > picking up settings done to the main kernel on time. Or something to > that effect, my memory is hazy. I suspected that during resume from hibernation the boot kernel (the one that loaded the image) did something to hardware and the restored kernel didn't handle that change properly. It is hard do say what piece of hardware that was, however (it might or might not be the NIC, it may be pure coincidence that the NMI messages appear in the log at this point). Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-06 0:13 ` Rafael J. Wysocki @ 2013-03-06 0:19 ` Borislav Petkov 2013-03-08 16:47 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-03-06 0:19 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jeff Kirsher, Jiri Slaby, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Wed, Mar 06, 2013 at 01:13:23AM +0100, Rafael J. Wysocki wrote: > I suspected that during resume from hibernation the boot kernel (the > one that loaded the image) did something to hardware and the restored > kernel didn't handle that change properly. It is hard do say what > piece of hardware that was, however (it might or might not be the NIC, > it may be pure coincidence that the NMI messages appear in the log at > this point). Agreed with the second part. About the first part, who communicates what to whom, come to think of it, it might not be related to any devices at all. Here's why I think so: So one of the things I did to trigger this is boot the machine, run powertop and set all the knobs in the "Tunables" tab to "Good". One of the tunables is turn-off-nmi-watchdog something which turns off the watchdog which is using the perf infrastructure which generates NMIs when the counter overflows. Now, imagine I do that in the "normal" kernel, then suspend, ...<something happens or does not happen>, then resume back into the normal kernel and it somehow "forgets" the fact that we disabled the NMI watchdog before the suspend cycle. And boom, it gets a single spurious NMI. Does it make sense? I dunno - I'm just connecting the dots here between the observation points which are most likely. Anyway, it's getting late, good night. :) -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-06 0:19 ` Borislav Petkov @ 2013-03-08 16:47 ` Borislav Petkov 0 siblings, 0 replies; 58+ messages in thread From: Borislav Petkov @ 2013-03-08 16:47 UTC (permalink / raw) To: Rafael J. Wysocki, Jeff Kirsher, Jiri Slaby, Bjorn Helgaas, Konstantin Khlebnikov, x86, lkml, e1000-devel, Bruce Allan On Wed, Mar 06, 2013 at 01:19:32AM +0100, Borislav Petkov wrote: > On Wed, Mar 06, 2013 at 01:13:23AM +0100, Rafael J. Wysocki wrote: > > I suspected that during resume from hibernation the boot kernel (the > > one that loaded the image) did something to hardware and the restored > > kernel didn't handle that change properly. It is hard do say what > > piece of hardware that was, however (it might or might not be the NIC, > > it may be pure coincidence that the NMI messages appear in the log at > > this point). > > Agreed with the second part. About the first part, who communicates what > to whom, come to think of it, it might not be related to any devices at > all. > > Here's why I think so: > > So one of the things I did to trigger this is boot the machine, run > powertop and set all the knobs in the "Tunables" tab to "Good". One of > the tunables is turn-off-nmi-watchdog something which turns off the > watchdog which is using the perf infrastructure which generates NMIs > when the counter overflows. > > Now, imagine I do that in the "normal" kernel, then suspend, > ...<something happens or does not happen>, then resume back into the > normal kernel and it somehow "forgets" the fact that we disabled the NMI > watchdog before the suspend cycle. And boom, it gets a single spurious > NMI. > > Does it make sense? I dunno - I'm just connecting the dots here between > the observation points which are most likely. > > Anyway, it's getting late, good night. :) Exactly as I thought: so I'm running the machine with NMI watchdog enabled, i.e. powertop says: PowerTOP v2.0 Overview Idle stats Frequency stats Device stats Tunables >> Bad NMI watchdog should be turned off Good VM writeback timeout .... and no more spurious NMIs. I'd say the plot thickens: disabling NMIs and suspending to disk right afterwards doesn't seem to really disable the watchdog. Or the disable gets delayed leading to one last spurious NMI when resuming... I probably need to go stare at the code though... -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 9:42 ` Jiri Slaby 2013-03-05 9:58 ` Borislav Petkov @ 2013-03-05 10:01 ` Jeff Kirsher 2013-03-05 10:04 ` Jiri Slaby 1 sibling, 1 reply; 58+ messages in thread From: Jeff Kirsher @ 2013-03-05 10:01 UTC (permalink / raw) To: Jiri Slaby Cc: Bjorn Helgaas, Borislav Petkov, Konstantin Khlebnikov, Rafael J. Wysocki, x86, lkml, e1000-devel, Bruce Allan [-- Attachment #1: Type: text/plain, Size: 1560 bytes --] On Tue, 2013-03-05 at 10:42 +0100, Jiri Slaby wrote: > On 03/05/2013 01:16 AM, Bjorn Helgaas wrote: > > [+cc e1000-devel, Jeff, Bruce] > > > > On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote: > >> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote: > >>> So it looks Bjorn has taken most of them and the e1000e one will go > >>> through the e1000e maintainers. I'll test after the merge window is > >>> done. > >> > >> Issue still persists on 3.9-rc1 :-( : > >> > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0. > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled? > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue > > > > The e1000e changes didn't get merged, did they? I don't see the > > following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in > > 3.9-rc1: > > > > e1000e: fix pci-device enable-counter balance > > e1000e: fix runtime power management transitions > > e1000e: fix accessing to suspended device > > You're right. They are not even in -next :(. > I have them in my queue for net, so I should be pushing them later this week once validation has a chance to look at them. [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-05 10:01 ` Jeff Kirsher @ 2013-03-05 10:04 ` Jiri Slaby 0 siblings, 0 replies; 58+ messages in thread From: Jiri Slaby @ 2013-03-05 10:04 UTC (permalink / raw) To: jeffrey.t.kirsher Cc: Bjorn Helgaas, Borislav Petkov, Konstantin Khlebnikov, Rafael J. Wysocki, lkml, e1000-devel, Bruce Allan -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/05/2013 11:01 AM, Jeff Kirsher wrote: > On Tue, 2013-03-05 at 10:42 +0100, Jiri Slaby wrote: >>> The e1000e changes didn't get merged, did they? I don't see >>> the following changes mentioned at >>> https://lkml.org/lkml/2013/2/4/185 in 3.9-rc1: >>> >>> e1000e: fix pci-device enable-counter balance e1000e: fix >>> runtime power management transitions e1000e: fix accessing to >>> suspended device >> >> You're right. They are not even in -next :(. >> > > I have them in my queue for net, so I should be pushing them later > this week once validation has a chance to look at them. Yeah, I've just noticed that here https://lkml.org/lkml/2013/2/25/3 Thanks a lot. - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRNcMQAAoJEL0lsQQGtHBJ+ZkP/3AokrLy82YOmecMvuFssino jpS9MSjr3Fq8H6WvDmqyhFkKiL8wW0liQU1ZHU8csAFOmTCYUUhrN7QyjZZLt3Ek QeUhPCi40uaL+jjfDh2TFy6dI/kvtiLxwUfQ4YcGOnNoJSMsN14E4PFiwWcQ/vfX rOsw9z+MkqJ4je2ZuDFBxZBcUYgdb1Mlrk7gPTVwADz+DnE3PN7DKIYWy3grI5/U uI9QkyESv4YEdpBBEphqdK3TNWWZS4QyiOq2glNgllnoksybI1JnYAWt+O2Khcef Os9O/ccZcUiQK6K6HvEYvJvp9eGhPNVt7Fyr+JBV3bzKoPlIcHOIgktahuisUuiZ zZsxshj3pFYBhCGlGkjbkMkB74hkgenJoT9e36JMPtov00E11B+DazqGodZm1jto e70821Y6MQ5gavTZrrdcmzJmzSwEsdww7ALs+FCTIBpc8Re0MrZMIp+XrTFnue2L aA23fYLu6/1uqd11PGNb+82P5s6dYpFCR9NHV29TPuXk50yH60z1Me8n3wMCzm8Y rIvrk6Xd3XATqepM6qG6O/cDPpvxo9itZldKBvi1SD088n3qEUdJWmLRzpaxisrt v0pCuUNx+pZE6gTE+tsxbv2k5d0RtNYPsnDJrds7EKMyhIwam7NDJcX490tu9pU8 VLndALzYj0O07N4wCQP1 =MGO1 -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 58+ messages in thread
* e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] 2013-02-15 8:54 ` Konstantin Khlebnikov 2013-02-15 9:16 ` Borislav Petkov @ 2013-03-01 12:51 ` Jiri Slaby 1 sibling, 0 replies; 58+ messages in thread From: Jiri Slaby @ 2013-03-01 12:51 UTC (permalink / raw) To: Konstantin Khlebnikov, Borislav Petkov, Bjorn Helgaas, Rafael J. Wysocki, lkml, e1000-devel, ML netdev On 02/15/2013 09:54 AM, Konstantin Khlebnikov wrote: > Borislav Petkov wrote: >> On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote: >>> It's pretty late for v3.8, but let me know if you think they're >>> critical. >> >> Ok, I meant those: >> >> http://marc.info/?l=linux-kernel&m=135984592927219 >> >> They fix the link detection issue on my x230. So let's see. The first >> one is: >> >> * https://patchwork.kernel.org/patch/2001211/ (e1000e: fix pci device >> enable >> counter balance) > > please use this instead: Hi, I am a bit confused. Is this fixed in -next yet? And if so, is it known which commit IDs are needed to fix the issue in 3.7 (see below)? > [PATCH v2 1/7] e1000e: fix pci-device enable-counter balance > https://lkml.org/lkml/2013/2/4/190 > > from v2 patchset: https://lkml.org/lkml/2013/2/4/185 So this is now in -next as: commit e34f7147d93afe5efc574734bbff6584c0cc4a02 Author: Konstantin Khlebnikov <khlebnikov@openvz.org> Date: Mon Feb 25 09:19:04 2013 +0400 e1000e: fix pci-device enable-counter balance >> I don't see that one in your tree. >> >> * pci-pm-clear-state_saved-during-suspend.patch This is: commit 82fee4d67ab86d6fe5eb0f9a9e988ca9d654d765 Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Date: Mon Feb 4 15:56:05 2013 +0400 PCI/PM: Clear state_saved during suspend >> Rafael said this one is a real bugfix. Looks like e1000e maintainers are >> picking that one? >> >> * pci-pm-fix-e1000e-runtime-suspend.patch Is this one replaced by a different fix in the end? Which one? I don't think it is in -next yet, right? confused, -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-02 23:04 ` Rafael J. Wysocki 2013-02-03 14:46 ` Borislav Petkov @ 2013-02-06 13:54 ` Jiri Slaby 2013-02-06 21:29 ` Rafael J. Wysocki 1 sibling, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-02-06 13:54 UTC (permalink / raw) To: Rafael J. Wysocki, Borislav Petkov Cc: Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 02/03/2013 12:04 AM, Rafael J. Wysocki wrote: > On Thursday, January 31, 2013 02:10:34 PM Borislav Petkov wrote: >> On Thu, Jan 31, 2013 at 02:12:58PM +0100, Rafael J. Wysocki wrote: >>> Yes, there are two bugs in e1000e, it appears. Konstantin's >>> patch [2/5] fixes one of them, but the other one has to be fixed >>> differently. >>> >>> Boris, would you be able to test a couple of e1000e patches for me? >> >> Sure, send them on. You can add 2/5 in the mix too. > > There you go. > > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > > The other two are attached. I suppose the ordering doesn't matter. Just a side question, are these going to be merged some time soon? I don't even see them in -next and I would like to backport them to opensuse as they affect also 3.7... -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 Jiri Slaby @ 2013-02-06 21:29 ` Rafael J. Wysocki 0 siblings, 0 replies; 58+ messages in thread From: Rafael J. Wysocki @ 2013-02-06 21:29 UTC (permalink / raw) To: Jiri Slaby Cc: Borislav Petkov, Borislav Petkov, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Wednesday, February 06, 2013 02:54:00 PM Jiri Slaby wrote: > On 02/03/2013 12:04 AM, Rafael J. Wysocki wrote: > > On Thursday, January 31, 2013 02:10:34 PM Borislav Petkov wrote: > >> On Thu, Jan 31, 2013 at 02:12:58PM +0100, Rafael J. Wysocki wrote: > >>> Yes, there are two bugs in e1000e, it appears. Konstantin's > >>> patch [2/5] fixes one of them, but the other one has to be fixed > >>> differently. > >>> > >>> Boris, would you be able to test a couple of e1000e patches for me? > >> > >> Sure, send them on. You can add 2/5 in the mix too. > > > > There you go. > > > > The [2/5] is at: https://patchwork.kernel.org/patch/2001211/ > > > > The other two are attached. I suppose the ordering doesn't matter. > > Just a side question, are these going to be merged some time soon? I > don't even see them in -next and I would like to backport them to > opensuse as they affect also 3.7... Not these particular patches, but there's a series on linux-pci from Konstantin Khlebnikov that is functionally equivalent. I'm not sure who's going to take that, though. I've acked it. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 7:09 ` Borislav Petkov 2013-01-31 8:14 ` Jiri Slaby @ 2013-01-31 8:28 ` Jiri Slaby 2013-01-31 13:18 ` Borislav Petkov 1 sibling, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-01-31 8:28 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/31/2013 08:09 AM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 01:54:56AM +0100, Rafael J. Wysocki wrote: >> On Thursday, January 31, 2013 12:47:40 AM Jiri Slaby wrote: >>> On 01/31/2013 12:12 AM, Jiri Slaby wrote: >>>> I think I will start with commenting parts of `power' script to see >>>> exactly which of the power savings cause this. >>> >>> ... NMI watchdog. If I remove it from the script, the problem >>> disappears. If I try it alone, I have those NMIs. >> >> Well, beats me. :-( >> >> I suspect that it doesn't quiesce itself sufficiently before image restoration >> and we get some crosstalk between the boot kernel and the image kernel. > > Well, I did what Jiri said causes it: > > echo 0 > /proc/sys/kernel/nmi_watchdog > > No NMI. > > BUT(!), if I start powertop and set all tunables in the "Tunables" tab > to "Good", then suspend to disk, when I resume I get the NMI and this > time the unknown reason is 0x3c. Sounds like this needs bisection... And, does it happen if you switch all of them but NMI wtd in there? And if I pass nmi_watchdog=0 to the image kernel, it should be gone I guess. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 8:28 ` Jiri Slaby @ 2013-01-31 13:18 ` Borislav Petkov 2013-01-31 13:24 ` Borislav Petkov ` (2 more replies) 0 siblings, 3 replies; 58+ messages in thread From: Borislav Petkov @ 2013-01-31 13:18 UTC (permalink / raw) To: Jiri Slaby Cc: Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Jan 31, 2013 at 09:28:12AM +0100, Jiri Slaby wrote: > And, does it happen if you switch all of them but NMI wtd in there? No, but something else happens. Here's the whole dance: 1. Switch all tunables except "NMI watchdog should be turned off" to "Good" 2. suspend to disk 3. resume... all good 4. switch "NMI watchdog should be turned off" to "Good" 5. suspend to disk 6. resume... all good 7. start powertop, toggle "Wireless Power Saving for interface wlan0" twice. I.e., "Good" -> "Bad"; "Bad" -> "Good". -> Boom! Unknown reason NMI. It happened right during the toggle because it appeared in the framebuffer console (no X) right during me toggling this. So, it is something getting fishy *after* the watchdog gets disabled. Something remains funny and dangling, causing it to fire an NMI because it is an NMI watchdog (doh!)... Could it be that the watchdog_disable fact doesn't get communicated to the image kernel somehow, or maybe delayed? > And if I pass nmi_watchdog=0 to the image kernel, it should be gone I > guess. How do you pass options the image kernel? -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:18 ` Borislav Petkov @ 2013-01-31 13:24 ` Borislav Petkov 2013-03-01 12:55 ` Jiri Slaby 2013-01-31 13:29 ` Rafael J. Wysocki 2013-02-03 21:29 ` Jiri Slaby 2 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-01-31 13:24 UTC (permalink / raw) To: Jiri Slaby Cc: Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Jan 31, 2013 at 02:18:05PM +0100, Borislav Petkov wrote: > > And if I pass nmi_watchdog=0 to the image kernel, it should be gone I > > guess. > > How do you pass options the image kernel? Yep, passing "nmi_watchdog=0" to the kernel (both when you boot and when you resume) fixes the issue - no more unknown NMIs. Did only 3 s/r cycles though. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:24 ` Borislav Petkov @ 2013-03-01 12:55 ` Jiri Slaby 2013-04-04 7:32 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-03-01 12:55 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/31/2013 02:24 PM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 02:18:05PM +0100, Borislav Petkov wrote: >>> And if I pass nmi_watchdog=0 to the image kernel, it should be gone I >>> guess. >> >> How do you pass options the image kernel? > > Yep, passing "nmi_watchdog=0" to the kernel (both when you boot and > when you resume) fixes the issue - no more unknown NMIs. Did only 3 s/r > cycles though. FWIW the last time I saw the unhandled NMI was on 31st Jan. Since I disabled NMI watchdog no more unhandled NMIs. I have to add that I don't use ethernet at all. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-03-01 12:55 ` Jiri Slaby @ 2013-04-04 7:32 ` Jiri Slaby 2013-04-04 9:33 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-04-04 7:32 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 03/01/2013 01:55 PM, Jiri Slaby wrote: > On 01/31/2013 02:24 PM, Borislav Petkov wrote: >> On Thu, Jan 31, 2013 at 02:18:05PM +0100, Borislav Petkov wrote: >>>> And if I pass nmi_watchdog=0 to the image kernel, it should be gone I >>>> guess. >>> >>> How do you pass options the image kernel? >> >> Yep, passing "nmi_watchdog=0" to the kernel (both when you boot and >> when you resume) fixes the issue - no more unknown NMIs. Did only 3 s/r >> cycles though. > > FWIW the last time I saw the unhandled NMI was on 31st Jan. Since I > disabled NMI watchdog no more unhandled NMIs. I have to add that I don't > use ethernet at all. And yesterday I plugged in an ethernet cable for a wihle and guess what happened today: Uhhuh. NMI received for unknown reason 2c on CPU 0. Still holds that this is the first time since Jan. -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-04-04 7:32 ` Jiri Slaby @ 2013-04-04 9:33 ` Borislav Petkov 2013-04-04 9:38 ` Jiri Slaby 0 siblings, 1 reply; 58+ messages in thread From: Borislav Petkov @ 2013-04-04 9:33 UTC (permalink / raw) To: Jiri Slaby Cc: Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Apr 04, 2013 at 09:32:09AM +0200, Jiri Slaby wrote: > And yesterday I plugged in an ethernet cable for a wihle and guess > what happened today: Uhhuh. NMI received for unknown reason 2c on CPU > 0. > > Still holds that this is the first time since Jan. Yeah, you could try my sure-fire way to trigger it: * boot the box without any "nmi_watchdog" tweaks on the kernel cmdline - i.e. it should be enabled. * turn off NMI watchdog through powertop or directly through /proc/sys/kernel/nmi_watchdog * suspend to disk Now when you resume, you should either see unknown reason 2c or 3c. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-04-04 9:33 ` Borislav Petkov @ 2013-04-04 9:38 ` Jiri Slaby 2013-04-04 9:58 ` Borislav Petkov 0 siblings, 1 reply; 58+ messages in thread From: Jiri Slaby @ 2013-04-04 9:38 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 04/04/2013 11:33 AM, Borislav Petkov wrote: > On Thu, Apr 04, 2013 at 09:32:09AM +0200, Jiri Slaby wrote: >> And yesterday I plugged in an ethernet cable for a wihle and guess >> what happened today: Uhhuh. NMI received for unknown reason 2c on CPU >> 0. >> >> Still holds that this is the first time since Jan. > > Yeah, you could try my sure-fire way to trigger it: > > * boot the box without any "nmi_watchdog" tweaks on the kernel cmdline - > i.e. it should be enabled. > > * turn off NMI watchdog through powertop or directly through > /proc/sys/kernel/nmi_watchdog > > * suspend to disk > > Now when you resume, you should either see unknown reason 2c or 3c. Oh, this reminds me that this time it might be unrelated to yesterday's use of ethernet. Because today, I resumed the system by a kernel which I didn't pass nmi_watchdog=0 to. Hmm. So you can silently ignore the report I sent today :). And sure, the way you describe above "works" for me to trigger the issue... I just wanted to note the ethernet may interfere. Anyway, I will bake some hack to disable NMI before jumping to the resumed kernel and will see what happens... -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-04-04 9:38 ` Jiri Slaby @ 2013-04-04 9:58 ` Borislav Petkov 0 siblings, 0 replies; 58+ messages in thread From: Borislav Petkov @ 2013-04-04 9:58 UTC (permalink / raw) To: Jiri Slaby Cc: Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thu, Apr 04, 2013 at 11:38:21AM +0200, Jiri Slaby wrote: > Oh, this reminds me that this time it might be unrelated to > yesterday's use of ethernet. Because today, I resumed the system by a > kernel which I didn't pass nmi_watchdog=0 to. > > Hmm. So you can silently ignore the report I sent today :). > > And sure, the way you describe above "works" for me to trigger the > issue... I just wanted to note the ethernet may interfere. > > Anyway, I will bake some hack to disable NMI before jumping to the > resumed kernel and will see what happens... Yeah, Rafael said something about the resume kernel not getting the disabling of the watchdog in time or so... The issue looks like a last forgotten NMI which fires although we've disabled the watchdog already. The certainly aren't any other coming up after this last one. Hmm. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:18 ` Borislav Petkov 2013-01-31 13:24 ` Borislav Petkov @ 2013-01-31 13:29 ` Rafael J. Wysocki 2013-02-03 21:29 ` Jiri Slaby 2 siblings, 0 replies; 58+ messages in thread From: Rafael J. Wysocki @ 2013-01-31 13:29 UTC (permalink / raw) To: Borislav Petkov Cc: Jiri Slaby, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On Thursday, January 31, 2013 02:18:05 PM Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 09:28:12AM +0100, Jiri Slaby wrote: > > And, does it happen if you switch all of them but NMI wtd in there? > > No, but something else happens. Here's the whole dance: > > 1. Switch all tunables except "NMI watchdog should be turned off" to "Good" > 2. suspend to disk > 3. resume... all good > 4. switch "NMI watchdog should be turned off" to "Good" > 5. suspend to disk > 6. resume... all good > 7. start powertop, toggle "Wireless Power Saving for interface wlan0" twice. > I.e., "Good" -> "Bad"; "Bad" -> "Good". > > -> Boom! Unknown reason NMI. It happened right during the toggle because > it appeared in the framebuffer console (no X) right during me toggling > this. > > So, it is something getting fishy *after* the watchdog gets disabled. > Something remains funny and dangling, causing it to fire an NMI because > it is an NMI watchdog (doh!)... Could it be that the watchdog_disable > fact doesn't get communicated to the image kernel somehow, or maybe > delayed? The image kernel has no idea whether or not the watchdog has been disabled in the boot kernel. It needs to be disabled in both. > > > And if I pass nmi_watchdog=0 to the image kernel, it should be gone I > > guess. > > How do you pass options the image kernel? The image kernel has the same set of command line options that was used by that kernel before hibernation. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 58+ messages in thread
* Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. 2013-01-31 13:18 ` Borislav Petkov 2013-01-31 13:24 ` Borislav Petkov 2013-01-31 13:29 ` Rafael J. Wysocki @ 2013-02-03 21:29 ` Jiri Slaby 2 siblings, 0 replies; 58+ messages in thread From: Jiri Slaby @ 2013-02-03 21:29 UTC (permalink / raw) To: Borislav Petkov, Rafael J. Wysocki, Bjorn Helgaas, x86, lkml, Konstantin Khlebnikov On 01/31/2013 02:18 PM, Borislav Petkov wrote: > On Thu, Jan 31, 2013 at 09:28:12AM +0100, Jiri Slaby wrote: >> And, does it happen if you switch all of them but NMI wtd in there? > > No, but something else happens. Here's the whole dance: > > 1. Switch all tunables except "NMI watchdog should be turned off" to "Good" > 2. suspend to disk > 3. resume... all good > 4. switch "NMI watchdog should be turned off" to "Good" > 5. suspend to disk > 6. resume... all good > 7. start powertop, toggle "Wireless Power Saving for interface wlan0" twice. > I.e., "Good" -> "Bad"; "Bad" -> "Good". > > -> Boom! Unknown reason NMI. It happened right during the toggle because > it appeared in the framebuffer console (no X) right during me toggling > this. Right, for me too. Even if I disable nmi watchdog in both the boot and image kernel, the NMI eventually occurs (dunno what's the trigger now though). Given the above I'm thinking about switching that intel wi-fi card to ath9k which I have at hand and retest... -- js suse labs ^ permalink raw reply [flat|nested] 58+ messages in thread
end of thread, other threads:[~2013-04-04 9:58 UTC | newest] Thread overview: 58+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2013-01-29 20:28 Uhhuh. NMI received for unknown reason 2c on CPU 0 Borislav Petkov 2013-01-29 21:32 ` Bjorn Helgaas 2013-01-30 3:42 ` Borislav Petkov 2013-01-30 17:27 ` Bjorn Helgaas 2013-01-30 17:44 ` Borislav Petkov 2013-01-30 19:43 ` Jiri Slaby 2013-01-30 20:00 ` Borislav Petkov 2013-01-30 20:33 ` Jiri Slaby 2013-01-30 21:39 ` Rafael J. Wysocki 2013-01-30 22:17 ` Jiri Slaby 2013-01-30 22:45 ` Rafael J. Wysocki 2013-01-30 23:12 ` Jiri Slaby 2013-01-30 23:47 ` Jiri Slaby 2013-01-31 0:54 ` Rafael J. Wysocki 2013-01-31 7:09 ` Borislav Petkov 2013-01-31 8:14 ` Jiri Slaby 2013-01-31 13:12 ` Rafael J. Wysocki 2013-01-31 13:10 ` Borislav Petkov 2013-02-02 23:04 ` Rafael J. Wysocki 2013-02-03 14:46 ` Borislav Petkov 2013-02-03 20:15 ` Rafael J. Wysocki 2013-02-03 20:58 ` Borislav Petkov 2013-02-03 21:06 ` Borislav Petkov 2013-02-03 21:15 ` Borislav Petkov 2013-02-14 14:39 ` Borislav Petkov 2013-02-14 17:17 ` Bjorn Helgaas 2013-02-14 19:12 ` Borislav Petkov 2013-02-15 8:54 ` Konstantin Khlebnikov 2013-02-15 9:16 ` Borislav Petkov 2013-03-04 21:50 ` Borislav Petkov 2013-03-05 0:16 ` Bjorn Helgaas 2013-03-05 9:42 ` Jiri Slaby 2013-03-05 9:58 ` Borislav Petkov 2013-03-05 10:01 ` Jiri Slaby 2013-03-05 10:02 ` Jeff Kirsher 2013-03-05 10:14 ` Borislav Petkov 2013-03-05 10:29 ` Jeff Kirsher 2013-03-05 11:27 ` Borislav Petkov 2013-03-05 11:33 ` Jeff Kirsher 2013-03-05 11:42 ` Borislav Petkov 2013-03-06 0:13 ` Rafael J. Wysocki 2013-03-06 0:19 ` Borislav Petkov 2013-03-08 16:47 ` Borislav Petkov 2013-03-05 10:01 ` Jeff Kirsher 2013-03-05 10:04 ` Jiri Slaby 2013-03-01 12:51 ` e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] Jiri Slaby 2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 Jiri Slaby 2013-02-06 21:29 ` Rafael J. Wysocki 2013-01-31 8:28 ` Jiri Slaby 2013-01-31 13:18 ` Borislav Petkov 2013-01-31 13:24 ` Borislav Petkov 2013-03-01 12:55 ` Jiri Slaby 2013-04-04 7:32 ` Jiri Slaby 2013-04-04 9:33 ` Borislav Petkov 2013-04-04 9:38 ` Jiri Slaby 2013-04-04 9:58 ` Borislav Petkov 2013-01-31 13:29 ` Rafael J. Wysocki 2013-02-03 21:29 ` Jiri Slaby
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).