From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 23 21:45:15 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A44FD16A405 for ; Tue, 23 Jan 2007 21:45:15 +0000 (UTC) (envelope-from groot@kde.org) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by mx1.freebsd.org (Postfix) with ESMTP id 5835513C448 for ; Tue, 23 Jan 2007 21:45:15 +0000 (UTC) (envelope-from groot@kde.org) Received: from adsl-dc-2f63f.adsl.wanadoo.nl [83.116.148.63] (helo=[10.0.0.186]) (authen=adridg) by smeltpunt.science.ru.nl (8.13.7/5.11) with ESMTP id l0NLj8eE007967 for ; Tue, 23 Jan 2007 22:45:11 +0100 (MET) From: Adriaan de Groot Organization: KDE-NL To: freebsd-amd64@freebsd.org Date: Tue, 23 Jan 2007 21:21:58 +0100 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701232121.58985.groot@kde.org> Subject: State of X4200 M2 (ok) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 21:45:15 -0000 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@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 Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f,,CR8> Cores per package: 2 real memory = 8589934592 (8192 MB) avail memory = 7774466048 (7414 MB) ACPI APIC Table: 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 irqs 0-23 on motherboard ioapic3 irqs 24-47 on motherboard ioapic1 irqs 48-54 on motherboard ioapic2 irqs 56-62 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: 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: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: 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: 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: 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: 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: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 pcib1: at device 9.0 on pci0 pci1: on pcib1 pci1: at device 3.0 (no driver attached) nve0: port 0xdc00-0xdc07 mem 0xfe3fe000-0xfe3fefff irq 21 at device 10.0 on pci0 nve0: Ethernet address 04:4b:80:80:80:03 miibus0: on nve0 ukphy0: 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: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 pcib5: at device 14.0 on pci0 pci5: on pcib5 pcib6: on acpi0 pci128: on pcib6 pci128: at device 0.0 (no driver attached) pci128: at device 1.0 (no driver attached) nve1: port 0xfc00-0xfc07 mem 0xfeafe000-0xfeafefff irq 44 at device 10.0 on pci128 nve1: Ethernet address 04:4b:80:80:80:04 miibus1: on nve1 ukphy1: 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: at device 11.0 on pci128 pci129: on pcib7 pcib8: at device 12.0 on pci128 pci130: on pcib8 pcib9: at device 13.0 on pci128 pci131: on pcib9 pcib10: at device 14.0 on pci128 pci132: on pcib10 pcib11: at device 16.0 on pci128 pci133: on pcib11 pci128: at device 16.1 (no driver attached) pcib12: at device 17.0 on pci128 pci134: on pcib12 em0: port 0xec00-0xec3f mem 0xfe9e0000-0xfe9fffff irq 56 at device 1.0 on pci134 em0: Ethernet address: 00:14:4f:49:dd:2a em1: port 0xe800-0xe83f mem 0xfe9c0000-0xfe9dffff irq 57 at device 1.1 on pci134 em1: Ethernet address: 00:14:4f:49:dd:2b mpt0: 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: at device 17.1 (no driver attached) acpi_button0: 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: at iomem 0xc0000-0xc9fff,0xca000-0xcb7ff,0xcb800-0xcc7ff,0xcc800-0xcd7ff,0xd3000-0xd3fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: cannot reserve I/O port range sc0: 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: 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 4194304 bytes at 0xffffffff80a51d50 acd0: CDRW at ata0-master UDMA33 da0 at mpt0 bus 0 target 0 lun 0 da0: 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: 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: 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/