State of X4200 M2 (ok)

[Thomas Hurst]

* Adriaan de Groot (groot at kde.org) wrote:

> ACPI APIC Table: <SUN    X4200 M2>
> ioapic1: Changing APIC ID to 6
> ioapic1: WARNING: intbase 48 != expected base 24
> ioapic2: Changing APIC ID to 7
> ioapic2: WARNING: intbase 56 != expected base 55
> ioapic3: Changing APIC ID to 5
> ioapic3: WARNING: intbase 24 != expected base 63
>
> This is just a permutation of the ioapics, not sure why it's causing them.
>
> ioapic0 <Version 1.1> irqs 0-23 on motherboard
> ioapic3 <Version 1.1> irqs 24-47 on motherboard
> ioapic1 <Version 1.1> irqs 48-54 on motherboard
> ioapic2 <Version 1.1> irqs 56-62 on motherboard

Don't get this with the non-M2's; the IRQ assignments are different too:

MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
ioapic1 <Version 1.1> irqs 24-27 on motherboard
ioapic2 <Version 1.1> irqs 28-31 on motherboard
ioapic3 <Version 1.1> irqs 32-35 on motherboard
ioapic4 <Version 1.1> irqs 36-39 on motherboard

> 1000baseSX-FDX, 1000baseT, 1000baseT-FDX, auto
> nve0: Ethernet address: 04:4b:80:80:80:03
> 
> The machine hangs at boot for several seconds after nve0 before miibus0; I do 
> not see this in other nForce4 based machines I've got.

Urgh, so 2 of the 4 NIC's on the M2's are nVidia crap?  That's quite a
step back from the 4 e1000's in earlier models :(

> mpt0: <LSILogic SAS/SATA Adapter> port 0xe400-0xe4ff mem 
> 0xfe9bc000-0xfe9bffff,0xfe9a0000-0xfe9affff irq 58 at device 2.0 on pci134
> mpt0: [GIANT-LOCKED]
> mpt0: MPI Version=1.5.12.0
>
>
> I can't find any information on the actual LSI device in the machine; I would 
> have expected mfi(4) instead of mpt.

Same as previous X4x00's (LSI 1064) I expect:

mpt0: <LSILogic SAS/SATA Adapter> port 0xa800-0xa8ff mem
0xfc2fc000-0xfc2fffff,0xfc2e0000-0xfc2effff irq 28 at device 3.0 on pci2
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.5.9.0

> I don't get any /dev/mpt* either (but I 
> guess that's more a comment for freebsd-hardware). The device isn't 
> recognized by any of the LSI management tools (megamgr, megacli, megarc) 
> either -- but then I'm not sure there's anything to manage there yet.

There's some basic hardware RAID:

mpt0: Capabilities: ( RAID-0 RAID-1 )

I doubt it's really worth using.

> mpt0: mpt_cam_event: 0x16
> mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required).
> mpt0: mpt_cam_event: 0x12
> mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required).
> mpt0: mpt_cam_event: 0x16
> mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required).
> 
> Incomplete driver? Useless RAID notifications?

Harmless, seen them on other MPT's.

> umass0: American Megatrends Inc. Virtual Cdrom Device, rev 1.10/1.00, addr 3
> umass1: American Megatrends Inc. Virtual Floppy Device, rev 1.10/1.00, addr 4
> 
> These two are actually big pains in the butt, since it does not seem to be 
> possible to disable them, and they hurt if you touch them. See da1, below.

They can be disabled in the BIOS.  We just don't run with USB support,
since the X4100's at least had interrupt aliasing problems with the
NIC's.

> mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x00 Depth 65
> 
> I get this every boot; not sure what it means yet.

Also harmless.

> The machine hasn't had much of a stress test yet. It gets through
> buildworlds and can shuffle data around and will write on standard
> SATA laptop drives too, if you can be bothered to stick them in the
> drive bays.

Really?  I wasn't aware these LSI's, nor mpt(4) supported SATA (despite
what the names say).  Not very useful anyway, SAS drives are a far
better match for server workloads (i.e. they actually perform well and
are designed to run 24/7).

Do they get exposed via ata(4) or appear as SCSI devices over CAM?

-- 
Thomas 'Freaky' Hurst
    http://hur.st/