Victor Balada Diaz wrote:
On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev wrote:
trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but
storms are not bound to ethernet only. storm may appear on any device.
if any device generates enough interrupts rate, storm will arrive.
Yes, I just got another storm, on my ATA controller this time. Ah
well, so much for the idea of disabling unneeded devices!
-pete.
it's a kind of magic, really. I built a new kernel with KDB and DDB and
after 1 day, 13:15 I'm still waiting for storm to arrive. And I added
hw.acpi.osname="Linux" to /boot/loader.conf.
Try doing lots of IO and you will get the problem soon. You might
want to try:
while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done
FWIW, last night I changed the address of the comm port IO in my BIOS.
Then I ran the Bacula regression test suite (lots of IO). For my
machine, once the interrupt storm starts, it continues. I do not know
if that happens to everyone.
Since changing the address, I have had no interrupt storms. I have been
running the above IO loop for about ten minutes.
No storm yet (knock on wood).
--
Dan Langille
BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon - The PostgreSQL Conference: http://www.pgcon.org/
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
