[eepro100] Re: Compaq ProLiant DL360 on-board eepro

Sorensen, Glenn Glenn.Sorensen@compaq.com
Thu, 17 Aug 2000 13:22:50 -0500


It is worth mentioning that for ALL Compaq servers the APIC table may be set
to full-table or full-table mapped depending on the OS selection in the
system configuration utility.  SmartStart 4.6 or later will have a "Linux"
OS selection which will set the APIC mode to full table-mapped.  

-----Original Message-----
From: Chaskiel M Grundman [mailto:cg2v+@andrew.cmu.edu]
Sent: Thursday, August 17, 2000 11:44 AM
To: eepro100@scyld.com
Subject: Re: [eepro100] Re: Compaq Proliant DL360 on-board eepro


Excerpts from internet.computing.linux-eepro100: 17-Aug-100 Re:
[eepro100] Re: Compaq P.. by Patrick Schaaf@bof.de 
>   7:          0          0          XT-PIC  eth1
This is your problem. You have a PCI device claiming to be using an IRQ
that linux does not believe is useable by the IOAPIC. This means that
when you in apic mode, you will never get interrupts from the device

I could go into some detail as to why linux believes this, but I think
its a bios problem rather than a problem with the linux PCI code (the
MPS table does not signify that the apic is capable of dealing with IRQ
7 from a PCI device. It does not appear that it will even deal with IRQ
7 from an ISA device, which is real wacky) If you boot your kernel with
the "noapic" command line option, your machine should work. This is
obviously suboptimal though... If you wish to confirm that the problem
is not with the linux PCI code, you should build and boot a 2.2.16 SMP
kernel, and try things again. The /proc/interrupts and lspci output
might be significantly different, so if you post results from 2.2.16,
you should include that information again. 

_______________________________________________
eepro100 mailing list
eepro100@scyld.com
http://www.scyld.com/mailman/listinfo/eepro100