Subject: Re: port-amd64/34259: no ps2 hardware means show stopper when usb fails
To: None <port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: George Georgalis <george@metrumrg.com>
List: netbsd-bugs
Date: 04/25/2007 18:15:06
The following reply was made to PR port-amd64/34259; it has been noted by GNATS.

From: George Georgalis <george@metrumrg.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>, gnats-bugs@NetBSD.org,
	port-amd64-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org, install-manager@NetBSD.org
Cc: 
Subject: Re: port-amd64/34259: no ps2 hardware means show stopper when usb fails
Date: Wed, 25 Apr 2007 13:11:28 -0400

 Hi All,
 
 Thanks for your help.
 
 It has been determined this blade system is not
 compatible with netbsd and it was returned.
 
 http://galis.org/blade-penguincomputing/notes.html
 
 I beleve the central problem is around the HT1000
 chip which seems to play a part in USB, Serial,
 network and other functions, with a not entirly
 standard protocol.
 
 The PR should be closed.
 
 // George
 
 
 On Fri, Aug 25, 2006 at 05:49:56PM -0400, George Georgalis wrote:
 >On Fri, Aug 25, 2006 at 10:28:20PM +0200, Manuel Bouyer wrote:
 >>On Fri, Aug 25, 2006 at 04:18:38PM -0400, George Georgalis wrote:
 >>> On Fri, Aug 25, 2006 at 10:00:35PM +0200, Manuel Bouyer wrote:
 >>> >On Fri, Aug 25, 2006 at 03:43:11PM -0400, George Georgalis wrote:
 >>> >> Is it possible for someone to make me a 3.1_RC1 install ISO with
 >>> >> installboot console=com1 and =com2 kernels available? It would
 >>> >
 >>> >Hum, just thinking about it, does the kernel see com2 ?
 >>> >I see that amd64 GENERIC and INSTALL have only com0 and com1.
 >>> 
 >>> The blade with an issue has only com2 available.
 >>
 >>So you'll need custom kernels anyway
 >
 >confirmed, all I got is:
 >com0	at isa? port 0x3f8 irq 4	# Standard PC serial ports
 >com1	at isa? port 0x2f8 irq 3
 >
 >in netbsd-3-0 HEAD INSTALL
 >http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/arch/amd64/conf/INSTALL?rev=1.27.2.9&content-type=text/plain&only_with_tag=netbsd-3-0
 >
 >>> On another USB only amd64 with an otherwise working install,
 >>> com1 is the available serial port, and it does the same thing...
 >>> boots to VGA after checksum to serial.
 >>
 >>Did you check that the kernel does actually see com1 ?
 >
 >Well in my 3.1_RC1 amd64 1-u host with a successful install.
 >
 >NetBSD rock 3.1_RC1 NetBSD 3.1_RC1 (GENERIC) #0: Sun Aug 20 22:47:46 UTC 2006  builds@b1.netbsd.org:/home/builds/ab/netbsd-3-1-RC1/amd64/200608202102Z-obj/home/builds/ab/netbsd-3-1-RC1/src/sys/arch/amd64/compile/GENERIC amd64
 >
 >http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/amd64/conf/GENERIC?f=u&only_with_tag=netbsd-3-0&logsort=date
 >
 >I see the same conf,
 >
 >com0	at isa? port 0x3f8 irq 4	# Standard PC serial ports
 >com1	at isa? port 0x2f8 irq 3
 >
 >and consdev com1, switches to VGA after the kernel checksum there
 >too. humm, better check dmesg... woha, I have com0 not com1 on the
 >1-u amd64 (dmesg below).  So I try that.
 >
 >> consdev com0
 >
 >
 >>> NetBSD/amd64 BIOS Boot, Revision 3.2
 >>> (riz@b2.netbsd.org, Thu Jul 13 20:05:49 UTC 2006)
 >>> Memory: 612/2094976 k
 >> boot hd1a:netbsd
 >booting hd1a:netbsd
 >6405232+670512+375440 [472512+288327]=0x8d5688
 >
 >and no more on serial, this time no boot messages to VGA either,
 >but I do get a getty on VGA at boot completion.
 >
 >Not sure, so I revisit bios, and find Console Redirection is
 >available only to COM1 or SMDC (a service processor to provide
 >net access to console, which connects to a sata backplane
 >with custom cables).
 >
 >So, there may be a numbering problem which I hope/suspect is not
 >really a problem; I opened the case and found a "COM2" jack which
 >will require special cables to try but I would be surprised if this
 >sunfire x2100 had a non working serial jack on the back because
 >the "standard equipment" service processor intercepted it via the
 >backplane.
 >
 >So (no more amd64s laying around to try), it still looks like
 >booting GENERIC/INSTALL kernels to serial on amd64 does not work,
 >regardless of the secondary configuration issue, for com2, on the
 >blade hardware.
 >
 >Is there some kernel option not in GENERIC, I can check/try?
 >Should I order a cable to try the onboard serial port?
 >
 >// George
 >
 >
 >NetBSD 3.1_RC1 (GENERIC) #0: Sun Aug 20 22:47:46 UTC 2006
 >	builds@b1.netbsd.org:/home/builds/ab/netbsd-3-1-RC1/amd64/200608202102Z-obj/home/builds/ab/netbsd-3-1-RC1/src/sys/arch/amd64/compile/GENERIC
 >total memory = 2046 MB
 >avail memory = 1952 MB
 >mainbus0 (root)
 >mainbus0: Intel MP Specification (Version 1.4) (OEM00000 PROD00000000)
 >cpu0 at mainbus0: apid 0 (boot processor)
 >cpu0: AMD Opteron(tm) Processor 148, 2211.45 MHz
 >cpu0: features: e7dbfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
 >cpu0: features: e7dbfbff<PGE,MCA,CMOV,PAT,PSE36,MPC,NOX,MMXX,MMX>
 >cpu0: features: e7dbfbff<FXSR,SSE,SSE2,LONG,3DNOW2,3DNOW>
 >cpu0: I-cache 64 KB 64B/line 2-way, D-cache 64 KB 64B/line 2-way
 >cpu0: L2 cache 1 MB 64B/line 16-way
 >cpu0: ITLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
 >cpu0: DTLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
 >cpu0: calibrating local timer
 >cpu0: apic clock running at 201 MHz
 >cpu0: 16 page colors
 >mpbios: bus 0 is type PCI   
 >mpbios: bus 1 is type PCI   
 >mpbios: bus 2 is type PCI   
 >mpbios: bus 3 is type PCI   
 >mpbios: bus 4 is type PCI   
 >mpbios: bus 5 is type PCI   
 >mpbios: bus 6 is type ISA   
 >ioapic0 at mainbus0 apid 2 (I/O APIC)
 >ioapic0: pa 0xfec00000, version 11, 24 pins
 >ioapic0: conflicting map entries for pin 0
 >pci0 at mainbus0 bus 0: configuration mode 1
 >pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 >NVIDIA product 0x005e (miscellaneous memory, revision 0xa3) at pci0 dev 0 function 0 not configured
 >pcib0 at pci0 dev 1 function 0
 >pcib0: NVIDIA product 0x0050 (rev. 0xa3)
 >NVIDIA nForce4 SMBus (SMBus serial bus, revision 0xa2) at pci0 dev 1 function 1 not configured
 >ohci0 at pci0 dev 2 function 0: NVIDIA product 0x005a (rev. 0xa2)
 >ohci0: interrupting at ioapic0 pin 10 (irq 10)
 >ohci0: OHCI version 1.0, legacy support
 >usb0 at ohci0: USB revision 1.0
 >uhub0 at usb0
 >uhub0: NVIDIA OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 >uhub0: 8 ports with 8 removable, self powered
 >NVIDIA product 0x005b (USB serial bus, interface 0x20, revision 0xa3) at pci0 dev 2 function 1 not configured
 >viaide0 at pci0 dev 6 function 0
 >viaide0: NVIDIA nForce4 IDE Controller (rev. 0xf2)
 >viaide0: bus-master DMA support present
 >viaide0: primary channel configured to compatibility mode
 >viaide0: primary channel interrupting at ioapic0 pin 14 (irq 14)
 >atabus0 at viaide0 channel 0
 >viaide0: secondary channel configured to compatibility mode
 >viaide0: secondary channel interrupting at ioapic0 pin 15 (irq 15)
 >atabus1 at viaide0 channel 1
 >viaide1 at pci0 dev 7 function 0
 >viaide1: NVIDIA nForce4 Serial ATA Controller (rev. 0xf3)
 >viaide1: bus-master DMA support present
 >viaide1: primary channel wired to native-PCI mode
 >viaide1: using ioapic0 pin 11 (irq 11) for native-PCI interrupt
 >atabus2 at viaide1 channel 0
 >viaide1: secondary channel wired to native-PCI mode
 >atabus3 at viaide1 channel 1
 >viaide2 at pci0 dev 8 function 0
 >viaide2: NVIDIA nForce4 Serial ATA Controller (rev. 0xf3)
 >viaide2: bus-master DMA support present
 >viaide2: primary channel wired to native-PCI mode
 >viaide2: using ioapic0 pin 10 (irq 10) for native-PCI interrupt
 >atabus4 at viaide2 channel 0
 >viaide2: secondary channel wired to native-PCI mode
 >atabus5 at viaide2 channel 1
 >ppb0 at pci0 dev 9 function 0: NVIDIA product 0x005c (rev. 0xa2)
 >pci1 at ppb0 bus 1
 >pci1: i/o space, memory space enabled
 >vga0 at pci1 dev 5 function 0: ATI Technologies Rage XL (rev. 0x27)
 >wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
 >wsmux1: connecting to wsdisplay0
 >nfe0 at pci0 dev 10 function 0: ioapic0 pin 3 (irq 3), address 00:e0:81:5c:f2:e9
 >makphy0 at nfe0 phy 1: Marvell 88E1111 Gigabit PHY, rev. 2
 >makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
 >ppb1 at pci0 dev 11 function 0: NVIDIA product 0x005d (rev. 0xa3)
 >pci2 at ppb1 bus 2
 >pci2: i/o space, memory space enabled, rd/line, wr/inv ok
 >ppb2 at pci0 dev 12 function 0: NVIDIA product 0x005d (rev. 0xa3)
 >pci3 at ppb2 bus 3
 >pci3: i/o space, memory space enabled, rd/line, wr/inv ok
 >ppb3 at pci0 dev 13 function 0: NVIDIA product 0x005d (rev. 0xa3)
 >pci4 at ppb3 bus 4
 >pci4: i/o space, memory space enabled, rd/line, wr/inv ok
 >bge0 at pci4 dev 0 function 0: Broadcom BCM5721 Gigabit Ethernet
 >bge0: interrupting at ioapic0 pin 5 (irq 5)
 >bge0: PCI-Express DMA setting 0x76180000, expected 0x76180000
 >bge0: ASIC BCM5751 A1 (0x4101), Ethernet address 00:e0:81:5c:f2:ea
 >bge0: setting short Tx thresholds
 >brgphy0 at bge0 phy 1: BCM5750 1000BASE-T media interface, rev. 0
 >brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
 >ppb4 at pci0 dev 14 function 0: NVIDIA product 0x005d (rev. 0xa3)
 >pci5 at ppb4 bus 5
 >pci5: i/o space, memory space enabled, rd/line, wr/inv ok
 >pchb0 at pci0 dev 24 function 0
 >pchb0: Advanced Micro Devices AMD64 HyperTransport configuration (rev. 0x00)
 >pchb1 at pci0 dev 24 function 1
 >pchb1: Advanced Micro Devices AMD64 Address Map configuration (rev. 0x00)
 >pchb2 at pci0 dev 24 function 2
 >pchb2: Advanced Micro Devices AMD64 DRAM configuration (rev. 0x00)
 >pchb3 at pci0 dev 24 function 3
 >pchb3: Advanced Micro Devices AMD64 Miscellaneous configuration (rev. 0x00)
 >isa0 at pcib0
 >com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 >pckbc0 at isa0 port 0x60-0x64
 >pckbd0 at pckbc0 (kbd slot)
 >pckbc0: using irq 1 for kbd slot
 >wskbd0 at pckbd0: console keyboard, using wsdisplay0
 >pcppi0 at isa0 port 0x61
 >midi0 at pcppi0: PC speaker
 >sysbeep0 at pcppi0
 >ioapic0: enabling
 >Kernelized RAIDframe activated
 >atapibus0 at atabus0: 2 targets
 >cd0 at atapibus0 drive 0: <MATSHITADVD-ROM SR-8178, , PZ16> cdrom removable
 >cd0: 32-bit data port
 >cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
 >cd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA)
 >uhub1 at uhub0 port 7
 >uhub1: Dell Dell USB Keyboard Hub, class 9/0, rev 1.10/1.00, addr 2
 >uhub1: 3 ports with 2 removable, bus powered
 >uhidev0 at uhub1 port 1 configuration 1 interface 0
 >uhidev0: Dell Dell USB Keyboard Hub, rev 1.10/1.00, addr 3, iclass 3/1
 >ukbd0 at uhidev0
 >wskbd1 at ukbd0 mux 1
 >wskbd1: connecting to wsdisplay0
 >uhidev1 at uhub1 port 1 configuration 1 interface 1
 >uhidev1: Dell Dell USB Keyboard Hub, rev 1.10/1.00, addr 3, iclass 3/0
 >uhidev1: 3 report ids
 >uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
 >uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
 >uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
 >wd0 at atabus2 drive 0: <ST380013AS>
 >wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 >wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
 >wd0: 32-bit data port
 >wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 >wd0(viaide1:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
 >wd1 at atabus3 drive 0: <ST380013AS>
 >wd1: drive supports 16-sector PIO transfers, LBA48 addressing
 >wd1: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
 >wd1: 32-bit data port
 >wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 >wd1(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
 >boot device: wd1
 >root on wd1a dumps on wd1b
 >root file system type: ffs
 >wsdisplay0: screen 1 added (80x25, vt100 emulation)
 >wsdisplay0: screen 2 added (80x25, vt100 emulation)
 >wsdisplay0: screen 3 added (80x25, vt100 emulation)
 >wsdisplay0: screen 4 added (80x25, vt100 emulation)
 >
 >
 >
 >-- 
 >George Georgalis, Information Systems Scientist, Metrum Research Group
 >2 Tunxis Road, Suite 112, Tariffville, CT 06081; direct: 860.670.4346
 >
 
 -- 
 George Georgalis, Information Systems Scientist, Metrum Research Group
 2 Tunxis Road, Suite 112, Tariffville, CT 06081; direct: 860.670.4346