On Mon, 22 Nov 2010 14:50:50 -0800, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> On 11/22/2010 01:55 PM, Konrad Rzeszutek Wilk wrote:
> > On Mon, Nov 22, 2010 at 04:46:46PM -0500, micah anderson wrote:
> >> On Mon, 22 Nov 2010 11:28:29 -0500, Konrad Rzeszutek Wilk
> >> <konrad.wilk@xxxxxxxxxx> wrote:
> >>>> [ 16.572048] scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
> >>>> [ 16.572051] <Adaptec AIC7902 Ultra320 SCSI adapter>
> >>>> [ 16.572053] aic7902: Ultra320 Wide Channel A, SCSI Id=7,
> >>>> PCI-X 101-133MHz, 512 SCBs
> >>>> [ 16.572598] aic79xx 0000:03:02.1: found PCI INT B -> IRQ 5
> >>> That is a rather odd IRQ number that is shared amongst all of the
> >>> devices. Is there
> >>> a "OS Compatibility" BIOS option where you can select Linux?
> >> I'm intending to have the BIOS queried at the earliest convenient
> >> time. Its not near me so I can't get this information right away, but I
> >> will.
> > Take your time. I've a full plate of bugs to deal with :-(
> >>> So MA Young found an interesting issue where the IRQs below 16 don't get
> >>> programmed
> >>> correctly, which was fixed in .. some unstable version, but before we go
> >>> that route
> >>> 1) Go in the serial console and hit Ctrl-A, hit '?' and hit '*' and send
> >>> the
> >>> output. I am curious to see if the IO-APIC ends up having a proper vector
> >>> as during
> >>> bootup it looks to be set to nothing but it should have by now have a
> >>> good value.
> >> Ok, here it is:
> > .. snip ..
> >> (XEN) IRQ: 5 affinity:00000000,00000000,00000000,00000001 vec:38
> >> type=IO-APIC-edge status=00000010 in-flight=0 domain-list=0: 5(-S--),
> > So it thinks it is an edge, but if that IRQ is shared it has to be level.
> > You have
> > a really weird motherboard..
>
> I found this... interesting:
>
> > (XEN) init IO_APIC IRQs
> > (XEN) IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-17, 2-20, 2-21, 2-22, 2-23,
> > 3-0, 3-1, 3-2, 3-3, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15,
> > 3-16, 3-17, 3-18, 3-19, 3-20, 3-21, 3-22, 3-23, 4-1, 4-2, 4-3, 4-4, 4-5,
> > 4-8, 4-9, 4-10, 4-11, 4-12, 4-13, 4-14, 4-15, 4-16, 4-17, 4-18, 4-19, 4-20,
> > 4-21, 4-22, 4-23 not connected.
>
> No idea what it means, but I'd guess its the BIOS doing something screwy.
As a data point, I confirmed that the latest BIOS rev was on the
machine.
m
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home