[Xen-devel] Re: Partial workaround for probs with 3ware Controller

[Nuno Silva <nuno.silva@xxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sven Kretzschmar wrote:
| Ok, I found a temporary workaround (not a good one though)
| for the probs with the 3ware card.
| If the option "ignorebiostables" is given as Xen kernel boot
| option, then the 3ware card is initialized and configured
| correctly with no problems. Also mounting and using
| filesystems on the connected RAID array worked.

from xendump-norm.txt:

(XEN) Initialised 1023MB memory (262128 pages) on a 1023MB machine
(XEN) Xen heap size is 10604KB
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Hyper-Threading is disabled
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000ff780
(XEN) Memory Reservation 0xff780, 4096 bytes
(XEN) Memory Reservation 0xf9500, 4096 bytes
(XEN) ACPI: RSDP (v000 ACPIAM                                    ) @
0x000f4fa0
(XEN) ACPI: RSDT (v001 A M I  OEMRSDT  0x02000304 MSFT 0x00000097) @
0x3fff0000
(XEN) ACPI: FADT (v002 A M I  OEMFACP  0x02000304 MSFT 0x00000097) @
0x3fff0200
(XEN) ACPI: MADT (v001 A M I  OEMAPIC  0x02000304 MSFT 0x00000097) @
0x3fff0300
(XEN) ACPI: OEMB (v001 A M I  OEMBIOS  0x02000304 MSFT 0x00000097) @
0x3ffff040
(XEN) ACPI: DSDT (v001  0ABBP 0ABBP000 0x00000000 INTL 0x02002026) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
(XEN) Processor #6 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
(XEN) Processor #130 invalid (max 16)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
(XEN) Processor #131 invalid (max 16)
(XEN) Using ACPI for processor (LAPIC) configuration information


Another wild guess:

Some months ago linux had a few problems counting the processors when
they were described non-sequentially (0, 6, 130, 131 -- like xen is
reporting). My guess is that Xen is using that (old) linux acpi code.
This limits the number of processors seen and may cause problems with
LAPIC/IO-APIC/etc.

IIRC, some users corrected part of this issue with a BIOS upgrade, but
not 100%. Current linux acpi code deals better with this kind of bios.

Also, don't worry about performance for now: AFAICT you are only running
with one processor. The other one is disabled ;-)

Does (non-xen) 2.6.7 reports the same acpi processor ID's? Is there a
newer BIOS for that box?

Can xen hackers confirm if the acpi code is up-to-date?

Kind regards,
Nuno Silva

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBHVP1OPig54MP17wRAmqOAKC9ZklZHQDwpQmaSA1rRiyZcBVj4gCfdpz9
3y+VflzKzDeQfEd9fYkkvok=
=K9eA
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel