Interrupt storm error

[David30]

PC-BSD 9.1 RC1 64-bit.

I switched on my desktop PC from a "cold" boot. Then I got continuous lines of text on my screen saying: interrupt storm detected on "irq17:"; throttling interrupt source

See the attached screenshot.

The computer had not frozen (it never freezes) because I was able to press Num Lock and the light would come on, then when I pressed Num Lock again the light went out. I had to restart; I pressed the reset button on the computer and then PC-BSD booted up fine.

What happened? I don't know what an "interrupt storm" means????

My computer is stable and when it was first built I ran Prime95 for 24 hours non-stop. I've never had stability problems during the entire time I've owned this PC and it has the latest BIOS version (3302 - May 2012).

[David30]

Started it up just now and got an error message about the USB, then my USB mouse stopped working - I had to unplug it and re-connect to get it working again.

What's going on????

[kmoore134]

That could be an early sign of something failing... What was the
specific error message from the USB mouse BTW?

[David30]

I've just been looking with the log file viewer and maybe this points to the problem?:

uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1

I don't believe the mouse or USB controllers are faulty because this never happens in Ubuntu - I'm not saying Ubuntu is better btw. I'm using the same mouse, right now, in PC-BSD.

I've also discovered that irq17 mentions "xhci" (USB 3.0):
xhci0: <NEC uPD720200 USB 3.0 controller> mem 0xf6500000-0xf6501fff irq 17 at device 0.0 on pci3

Does PC-BSD use power-saving on the USB ports? If so, I had to turn this off in Windows 7 (USB power saving, in the Power Saving settings) because I had the same problem at bootup with the mouse.

[kmoore134]

Ok, those are all USB related, xhci is for USB 3.0. I would bet there is
a bug there causing the issue. This is a bit beyond the scope of what we
can normally address on the forums. If you want to get this taken a look
at, then you can file a FreeBSD PR, or send the details over the the USB
mailing list:

http://www.freebsd.org/send-pr.html

http://lists.freebsd.org/mailman/listinfo/freebsd-usb

[David30]

This is still occurring on PC-BSD 9.1, which I have just installed on my desktop PC. I have submitted the bug report from your link.