Date: Mon, 09 Jul 2007 14:29:29 -0700 From: Nate Lawson <nate@root.org> To: John Baldwin <jhb@freebsd.org> Cc: =?windows-1251?Q?=CC=E8=F5=E0=E8=EB_=CA=F3?=, freebsd-acpi@freebsd.org Subject: Re: Asus P5W DH Deluxe APIC/SMP IRQ problem Message-ID: <4692A8B9.6000108@root.org> In-Reply-To: <200707091414.36956.jhb@freebsd.org> References: <1387899022.20070706140143@mixey.spb.ru> <200707091414.36956.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Friday 06 July 2007 06:01:43 am Михаил Кучин wrote: >> Hi people! >> >> Sorry for my bad english. Writing for the first time. I am searching help >> =) >> >> My OS: >> FreeBSD 6.2-RELEASE >> >> 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) >> >> Problem: >> 40% of CPU is occupied by interrupts, in some cases (I tried many >> ways of solving), I have "Interrupt storm detected" message. >> >> atapci2 (see vmstat), as I understand, occupies CPU. Here is my RAID1 > controller with >> 400G Samsung Disks and other ICH7 stuff. >> >> 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 > interrupt storm on IRQ 23 to go away. It is likely a bug in interrupt > routing in your BIOS, but you can use a tunable to work around it, you just > need to figure out which _other_ PCI device (not atapci2) is sending its > interrupts to IRQ 23 rather than the IRQ the BIOS told the OS. > I've noticed it's hard to find all the devices on a given irq with vmstat -i, especially if a lot are sharing one. I guess dmesg | grep "irq 23" is the only way? -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4692A8B9.6000108>