linux-kernel - RE: 3.6.0 ACPI: e1000e - Invalid Power Resource to register! (Supermicro X9SCM-F)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <01c001cda59a$99179aa0$cb46cfe0$@lucidpixels.com>
Date:	Mon, 8 Oct 2012 17:19:26 -0400
From:	"Justin Piszcz" <jpiszcz@...idpixels.com>
To:	<linux-kernel@...r.kernel.org>, "'al piszcz'" <ap@...arrain.com>
Cc:	<linux-acpi@...r.kernel.org>, <e1000-devel@...ts.sf.net>
Subject: RE: 3.6.0 ACPI: e1000e - Invalid Power Resource to register! (Supermicro X9SCM-F) - Disabling IRQ #44

Kernel: 3.6.0 (x86_64)
Distribution: Debian Testing

I was copying 600GB of files from Samba/Linux to a Windows host, it
copied around 500GB, then this happened, it disabled the network
interface on my Supermicro X9CM-F board (on-board) -- the first
interface, any idea why this happened?

[93593.565667] irq 44: nobody cared (try booting with the "irqpoll" option)
[93593.565673] Pid: 0, comm: swapper/0 Not tainted 3.6.0 #4
[93593.565675] Call Trace:
[    0.971861] ACPI: Invalid Power Resource to register!
[93593.565677]  <IRQ>  [<ffffffff810a6fe1>] __report_bad_irq+0x31/0xd0
[93593.565690]  [<ffffffff810a72c3>] note_interrupt+0x1a3/0x1f0
[93593.565694]  [<ffffffff810a4e59>] handle_irq_event_percpu+0x89/0x160
[93593.565697]  [<ffffffff810a4f6c>] handle_irq_event+0x3c/0x60
[93593.565700]  [<ffffffff810a7b7f>] handle_edge_irq+0x6f/0x110
[93593.565705]  [<ffffffff81003c6d>] handle_irq+0x1d/0x30
[93593.565709]  [<ffffffff81003b65>] do_IRQ+0x55/0xd0
[93593.565714]  [<ffffffff815fdb27>] common_interrupt+0x67/0x67
[93593.565715]  <EOI>  [<ffffffff8107d1ed>] ?
__hrtimer_start_range_ns+0x1bd/0x3b0
[93593.565728]  [<ffffffff81383894>] ? acpi_idle_enter_c1+0xaa/0xcf
[93593.565731]  [<ffffffff81383873>] ? acpi_idle_enter_c1+0x89/0xcf
[93593.565735]  [<ffffffff814a1719>] cpuidle_enter+0x19/0x20
[93593.565738]  [<ffffffff814a1a98>] cpuidle_idle_call+0x88/0x100
[93593.565750]  [<ffffffff8100a39f>] cpu_idle+0x5f/0xd0
[93593.565752]  [<ffffffff815e9a24>] rest_init+0x68/0x74
[93593.565755]  [<ffffffff81a8ca86>] start_kernel+0x2a8/0x2b5
[93593.565756]  [<ffffffff81a8c5dd>] ? repair_env_string+0x5e/0x5e
[93593.565758]  [<ffffffff81a8c2fd>] x86_64_start_reservations+0x101/0x105
[93593.565759]  [<ffffffff81a8c3d9>] x86_64_start_kernel+0xd8/0xdc
[93593.565760] handlers:
[93593.565762] [<ffffffff8140c330>] e1000_msix_other
[93593.565763] Disabling IRQ #44

---

A known issue with this hardware/nics it appears:
https://www.centos.org/modules/newbb/viewtopic.php?topic_id=34820

Hopefully someone from Intel can chime in.

Justin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/