Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Jul 2007 14:14:36 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-acpi@freebsd.org, =?windows-1251?b?zOj14OjrIMrz9+jt?= <admin@mixey.spb.ru>
Subject:   Re: Asus P5W DH Deluxe APIC/SMP IRQ problem
Message-ID:  <200707091414.36956.jhb@freebsd.org>
In-Reply-To: <1387899022.20070706140143@mixey.spb.ru>
References:  <1387899022.20070706140143@mixey.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 06 July 2007 06:01:43 am =CC=E8=F5=E0=E8=EB =CA=F3=F7=E8=ED wrote:
> Hi people!
>=20
> Sorry for my bad english. Writing for the first time. I am searching help
> =3D)
>=20
> My OS:
>    FreeBSD 6.2-RELEASE
>=20
> Hardware:
>   Asus P5W DH Deluxe MB (ICH7 Chipset)
>   Intel Core 2 Duo CPU (6700)
>   Integrated Netw Card (Marvell Yukon 88E8053 based Ethernet Controller)
>   S3 Trio PCI Video Card (very-very old)
>=20
> Problem:
>   40% of CPU is occupied by interrupts, in some cases (I tried many
>   ways of solving), I have "Interrupt storm detected" message.
>=20
>   atapci2 (see vmstat), as I understand, occupies CPU. Here is my RAID1=20
controller with
>   400G Samsung Disks and other ICH7 stuff.
>=20
>   I tried to change in BIOS everything, disable everything, re-plug vga
>   card, unplug some RAM. BIOS is fresh: a week ago release. Tried 3
>   different versions.

Try turning off various device drivers (like myk) to see if you can get the=
=20
interrupt storm on IRQ 23 to go away.  It is likely a bug in interrupt=20
routing in your BIOS, but you can use a tunable to work around it, you just=
=20
need to figure out which _other_ PCI device (not atapci2) is sending its=20
interrupts to IRQ 23 rather than the IRQ the BIOS told the OS.

=2D-=20
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707091414.36956.jhb>