On 11/5/07, Vasco Névoa <vasco.nevoa-8MI2nhFGehw@public.gmane.org> wrote:
> I had a similar problem, and it turned out to be the motherboard chipset
> that had an IRQ management bug (ASUS/nforce2). I disabled the APIC/LAPIC
> with "noapic nolapic" in the kernel boot line and now everything is just
> peachy. :)
> May not have anything to do with your case, but you never know... ;)


Well, I thought the same thing but I was running with noapic (not nolapic, I've since added that but haven't had time to re-bench). My machine won't even boot without either noapic or nolapic. Here is my /proc/interrupts if anybody sees anything:

           CPU0       CPU1
  0:     601671     184990    XT-PIC-XT        timer
  1:          9          1    XT-PIC-XT        i8042
  2:          0          0    XT-PIC-XT        cascade
  5:     165708      98825    XT-PIC-XT        sata_nv
  7:     633684     964184    XT-PIC-XT        sata_nv, ehci_hcd:usb1
  8:          0          0    XT-PIC-XT        rtc
  9:          0          0    XT-PIC-XT        acpi
10:          0          0    XT-PIC-XT        sata_nv
11:         54          5    XT-PIC-XT        aic7xxx, ohci_hcd:usb2
14:       4852         86    XT-PIC-XT        libata
15:          0          0    XT-PIC-XT        libata
4345:     311914       1499   PCI-MSI-edge      eth1
4346:          0     319419   PCI-MSI-edge      eth0
NMI:          0          0
LOC:     786639     786619
ERR:     549590



--
Jon

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Aoetools-discuss mailing list
Aoetools-discuss@...
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss