RE: Tyan II & SCSI Interrupts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 19 Jan 2003, Allen Curtis wrote:

> I tried this and it WORKS!
> Now I am getting messages in the log saying that /usr/lib/sa/sa1 1 1 can not
> update the log. Have you ever seen this? I do not get it when I run with a
> uni-processor.

That's not really a kernel issue, its to do with the sar(1) utilities.

> PS: Where can I find more info on "noapic" option? This has had me stumped
> for a long time. Perhaps it is something that could be detected by the
> kernel?

Broken IRQ routing, which was either not specified correctly or at all by 
your BIOS in the MP tables or perhaps even incorrect wiring to pins,slots 
on your motherboard. The noapic option disables usage of the IOAPIC for 
interrupt delivery to local CPUs and instead uses the 'XTPIC' (aka i8259). 
The kernel currently does a fair amount to detect such broken systems but 
some obviously can slip by and there is no need for extraneous heuristics 
when a simple kernel parameter can fix the not so common case.

Have a look at linux/Documentation/i386/IO-APIC.txt

	Zwane
-- 
function.linuxpower.ca


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux