From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: Netdev <netdev@vger.kernel.org>
Subject: e1000e: Disabling IRQ #57 .. machine dies
Date: Tue, 11 Sep 2012 15:50:25 -0300 [thread overview]
Message-ID: <504F87F1.5040004@opensuse.org> (raw)
Hi:
In current linus tree, in a machine using the e1000e driver
hwinfo --netcard
22: PCI 400.0: 0200 Ethernet controller
[Created at pci.319]
Unique ID: rBUF.cuT2KaC3ZS1
Parent ID: HnsE.Z52SDLRIaH2
SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:04:00.0
SysFS BusID: 0000:04:00.0
Hardware Class: network
Model: "Intel 82574L Gigabit Network Connection"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x10d3 "82574L Gigabit Network Connection"
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x8369
Driver: "e1000e"
Driver Modules: "e1000e"
Device File: eth0
Memory Range: 0xf7d00000-0xf7d1ffff (rw,non-prefetchable)
I/O Ports: 0xd000-0xdfff (rw)
Memory Range: 0xf7d20000-0xf7d23fff (rw,non-prefetchable)
IRQ: 17 (no events)
Link detected: yes
Module Alias: "pci:v00008086d000010D3sv00001043sd00008369bc02sc00i00"
Driver Info #0:
Driver Status: e1000e is active
Driver Activation Cmd: "modprobe e1000e"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #15 (PCI bridge)
cat /proc/interrupts
57 IR-PCI-MSI-edge eth0
the driver works after a while, but then a single message
"Disabling IRQ #57"
is sent to the console and the machine dies, nothing else is written in
the logs and remote ikvm becames unresponsive so there is no way to
bring more debug info back.. kernel 3.5.3 works ok.
Anyone else seeing this ?
next reply other threads:[~2012-09-11 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:50 Cristian Rodríguez [this message]
2012-09-14 16:40 ` e1000e: Disabling IRQ #57 .. machine dies Wyborny, Carolyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504F87F1.5040004@opensuse.org \
--to=crrodriguez@opensuse.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.