em interrupt storm
wmoran at collaborativefusion.com
Tue Nov 14 06:26:38 PST 2006
In response to "Jack Vogel" <jfvogel at gmail.com>:
> On 11/13/06, Bill Moran <wmoran at collaborativefusion.com> wrote:
> > Just experienced an "interrupt storm" on an em device that disabled a
> > server until I could reboot it.
> > My initial research turned up this thread:
> > http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058336.html
> > Which seems related, even if it is a little old. I'm aware that there
> > have been problems with recent versions of the em driver but I haven't
> > been following them closely enough, and there's a LOT of mail traffic
> > on this topic.
> > Note that this is a FreeBSD 5.3-RELEASE-p37 system. An upgrade is
> > possible, but this is a production system and the problem occurs
> > infrequently, so I'm reluctant to schedule downtime unless I have good
> > reason to believe that it will fix the problem.
> > Anyone remember if the above problem was fixed in more recent versions,
> > or knows enough about the issue to comment on whether I'm barking up
> > the correct tree or not? I'm pretty early in the diagnosis on this,
> > but I'm looking for pointers to keep me from doing random upgrades or
> > other time-wasting activities.
> There were fixes to things that MIGHT be a cause of an interrupt storm
> in the em driver, but without knowing more about your specific hardware
> and the event when it happened its hard to pontificate :)
Hell, it's hard just to spell "pontificate"! ;)
> As an aside, I would think getting off 5.3 would be desireable in and of
> itself :)
It's on the TODO list, along with 1000 other things. If I can prove
that 5.5 will fix a stability problem, that will move up the TODO
list in priority.
> Can you give a vmstat -i, a pciconf -l, and maybe messages when the
> storm occurred?
Sorry ... should have done that in the first email, but yesterday
afternoon was a bit flustering ...
There was a console message to the tune of "interrupt store on em0" ...
I didn't bother to copy it down exactly, because I expected it would
end up in /var/log/messages, but it didn't.
interrupt total rate
irq4: sio0 3 0
irq8: rtc 8027965 127
irq13: npx0 1 0
irq14: ata0 58 0
irq16: uhci0 286184 4
irq18: uhci2 221609 3
irq19: uhci1 3 0
irq23: atapci0 94 0
irq34: mpt0 221609 3
irq64: em0 286144 4
irq0: clk 6272009 99
Total 15315679 244
hostb0 at pci0:0:0: class=0x060000 card=0x016c1028 chip=0x35908086 rev=0x09 hdr=0x00
pcib1 at pci0:2:0: class=0x060400 card=0x00000050 chip=0x35958086 rev=0x09 hdr=0x01
pcib4 at pci0:4:0: class=0x060400 card=0x00000050 chip=0x35978086 rev=0x09 hdr=0x01
pcib5 at pci0:5:0: class=0x060400 card=0x00000050 chip=0x35988086 rev=0x09 hdr=0x01
pcib8 at pci0:6:0: class=0x060400 card=0x00000050 chip=0x35998086 rev=0x09 hdr=0x01
uhci0 at pci0:29:0: class=0x0c0300 card=0x016c1028 chip=0x24d28086 rev=0x02 hdr=0x00
uhci1 at pci0:29:1: class=0x0c0300 card=0x016c1028 chip=0x24d48086 rev=0x02 hdr=0x00
uhci2 at pci0:29:2: class=0x0c0300 card=0x016c1028 chip=0x24d78086 rev=0x02 hdr=0x00
none0 at pci0:29:7: class=0x0c0320 card=0x016c1028 chip=0x24dd8086 rev=0x02 hdr=0x00
pcib9 at pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0xc2 hdr=0x01
isab0 at pci0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086 rev=0x02 hdr=0x00
atapci1 at pci0:31:1: class=0x01018a card=0x016c1028 chip=0x24db8086 rev=0x02 hdr=0x00
pcib2 at pci1:0:0: class=0x060400 card=0x00000044 chip=0x03298086 rev=0x09 hdr=0x01
pcib3 at pci1:0:2: class=0x060400 card=0x00000044 chip=0x032a8086 rev=0x09 hdr=0x01
mpt0 at pci3:5:0: class=0x010000 card=0x016c1028 chip=0x00301000 rev=0x08 hdr=0x00
pcib6 at pci5:0:0: class=0x060400 card=0x00000044 chip=0x03298086 rev=0x09 hdr=0x01
pcib7 at pci5:0:2: class=0x060400 card=0x00000044 chip=0x032a8086 rev=0x09 hdr=0x01
em0 at pci6:7:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00
em1 at pci7:8:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00
none1 at pci9:5:0: class=0xff0000 card=0x00111028 chip=0x00111028 rev=0x00 hdr=0x00
none2 at pci9:5:1: class=0xff0000 card=0x00121028 chip=0x00121028 rev=0x00 hdr=0x00
none3 at pci9:5:2: class=0xff0000 card=0x00141028 chip=0x00141028 rev=0x00 hdr=0x00
atapci0 at pci9:6:0: class=0x010185 card=0x06801095 chip=0x06801095 rev=0x02 hdr=0x00
none4 at pci9:13:0: class=0x030000 card=0x016c1028 chip=0x51591002 rev=0x00 hdr=0x00
Collaborative Fusion Inc.
wmoran at collaborativefusion.com
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
More information about the freebsd-stable