State of X4200 M2 (ok)

Tue Jan 23 21:45:15 UTC 2007

Thanks to Michiel Boland (who's in an office about 200m down the road) for 
dealing with the LSI BIOS issue, the Sun X4200 M2 seems to be in good shape. 
Here's the dmesg, with comments inline:

Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE #0: Fri Jan 12 08:32:24 UTC 2007
    root at portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual-Core AMD Opteron(tm) Processor 2216 (2400.01-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x40f12  Stepping = 2

Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow>
  AMD Features2=0x1f<LAHF,CMP,<b2>,<b3>,CR8>
  Cores per package: 2
real memory  = 8589934592 (8192 MB)
avail memory = 7774466048 (7414 MB)
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
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <SUN X4200 M2> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfe3ff000-0xfe3fffff irq 20 at 
device 2.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 7 ports with 7 removable, self powered
ehci0: <NVIDIA nForce4 USB 2.0 controller> mem 0xff000000-0xff0000ff at device 
2.1 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: <NVIDIA nForce4 USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 7 ports with 7 removable, self powered
uhub1: device problem (STALLED), disabling port 6
atapci0: <nVidia nForce CK804 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 6.0 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 3.0 (no driver attached)
nve0: <NVIDIA nForce MCP9 Networking Adapter> port 0xdc00-0xdc07 mem 
0xfe3fe000-0xfe3fefff irq 21 at device 10.0 on pci0
nve0: Ethernet address 04:4b:80:80:80:03
miibus0: <MII bus> on nve0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 
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.

pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 13.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI Host-PCI bridge> on acpi0
pci128: <ACPI PCI bus> on pcib6
pci128: <memory> at device 0.0 (no driver attached)
pci128: <memory> at device 1.0 (no driver attached)
nve1: <NVIDIA nForce MCP9 Networking Adapter> port 0xfc00-0xfc07 mem 
0xfeafe000-0xfeafefff irq 44 at device 10.0 on pci128
nve1: Ethernet address 04:4b:80:80:80:04
miibus1: <MII bus> on nve1
ukphy1: <Generic IEEE 802.3u media interface> on miibus1
ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, 
1000baseSX-FDX, 1000baseT, 1000baseT-FDX, auto
nve1: Ethernet address: 04:4b:80:80:80:04

Same hang here.

pcib7: <ACPI PCI-PCI bridge> at device 11.0 on pci128
pci129: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 12.0 on pci128
pci130: <ACPI PCI bus> on pcib8
pcib9: <ACPI PCI-PCI bridge> at device 13.0 on pci128
pci131: <ACPI PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 14.0 on pci128
pci132: <ACPI PCI bus> on pcib10
pcib11: <ACPI PCI-PCI bridge> at device 16.0 on pci128
pci133: <ACPI PCI bus> on pcib11
pci128: <base peripheral, interrupt controller> at device 16.1 (no driver 
attached)
pcib12: <ACPI PCI-PCI bridge> at device 17.0 on pci128
pci134: <ACPI PCI bus> on pcib12
em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0xec00-0xec3f 
mem 0xfe9e0000-0xfe9fffff irq 56 at device 1.0 on pci134
em0: Ethernet address: 00:14:4f:49:dd:2a
em1: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0xe800-0xe83f 
mem 0xfe9c0000-0xfe9dffff irq 57 at device 1.1 on pci134
em1: Ethernet address: 00:14:4f:49:dd:2b
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. 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.

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?

pci128: <base peripheral, interrupt controller> at device 17.1 (no driver 
attached)
acpi_button0: <Power Button> on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
orm0: <ISA Option ROMs> at iomem 
0xc0000-0xc9fff,0xca000-0xcb7ff,0xcb800-0xcc7ff,0xcc800-0xcd7ff,0xd3000-0xd3fff 
on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd0: American Megatrends Inc. Virtual Keyboard and Mouse, rev 1.10/1.00, 
addr 2, iclass 3/1
kbd2 at ukbd0
ums0: American Megatrends Inc. Virtual Keyboard and Mouse, rev 1.10/1.00, addr 
2, iclass 3/1
ums0: X report 0x0002 not supported
device_attach: ums0 attach returned 6
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.

Timecounter "TSC" frequency 2400009816 Hz quality 800
Timecounters tick every 1.000 msec
md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xffffffff80a51d50
acd0: CDRW <MATSHITACD-RW CW-8124/DZ13> at ata0-master UDMA33
da0 at mpt0 bus 0 target 0 lun 0
da0: <SEAGATE ST973401LSUN72G 0556> Fixed Direct Access SCSI-3 device 
da0: 300.000MB/s transfers, Tagged Queueing Enabled
da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C)
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <AMI Virtual CDROM 1.00> Removable CD-ROM SCSI-0 device 
cd0: 1.000MB/s transfers
cd0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready 
change, medium may have changed
da1 at umass-sim1 bus 1 target 0 lun 0
da1: <AMI Virtual Floppy 1.00> Removable Direct Access SCSI-0 device 
da1: 1.000MB/s transfers
da1: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready 
change,
(da1:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
(da1:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(da1:umass-sim1:1:0:0): SCSI Status: Check Condition
(da1:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0
(da1:umass-sim1:1:0:0): Not ready to ready change, medium may have changed

Snipped 60 lines of umass errors before it gives up on the non-existent 
virtual floppy.

ukbd1: BTC USB Multimedia Keyboard, rev 1.10/1.30, addr 5, iclass 3/1
kbd3 at ukbd1
uhid0: BTC USB Multimedia Keyboard, rev 1.10/1.30, addr 5, iclass 3/1

There is some weirdness with the USB ports; the ones on the front work during 
most of the installation of FBSD 6.2-R but I had to swap around to the back 
ports later. After booting, only the back ports take the keyboard at all.

mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x00 Depth 65

I get this every boot; not sure what it means yet.

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. I had an issue 
with a cheap-ass (why does all this make it sound like I'm taking an 
expensive server and duct-taping crap to it?) USB SATA enclosure which works 
with another nForce4 board but which failed with short reads on both USB hubs 
in the X4200. Further experimentation is warranted.

-- 
KDE Quality Team  http://www.englishbreakfastnetwork.org/
GPG: FEA2 A3FE    http://people.fruitsalad.org/adridg/