On Sun, Sep 02, 2001 at 01:37:16AM -0000, eeh@netbsd.org wrote:
> 1) What exactly is a `SUNW,Ultra-1-Engine'?  And what problem does it
> have with that machine that this patch is supposed to fix?
> 
To be more specific about what the machine is:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.5X (GENERIC) #2: Sat Sep  1 16:56:19 EDT 2001
    root@u5:/usr/src/sys/arch/sparc64/compile/GENERIC
total memory = 65536 KB
avail memory = 46952 KB
using 422 buffers containing 3376 KB of memory
bootpath: /pci@1f,4000/network@1,1
mainbus0 (root): SUNW,Ultra-1-Engine
cpu0 at mainbus0: SUNW,UltraSPARC @ 168 MHz, version 0 FPU
cpu0: physical 4K instruction (32 b/l), 4K data (32 b/l), 2048K external (64 b/l) 
timer0 at mainbus0 addr 0xfffa7c00 irq vectors 7ec and 7ed
psycho0 at mainbus0 addr 0xfffc2000
pci108e,8000: impl 0, version 3: ign 7c0 bus range 0 to 0; PCI bus 0
DVMA map: fe000000 to 0
pci0 at psycho0
pci0: i/o space, memory space enabled
ebus0 at pci0 dev 1 function 0
ebus0: Sun Microsystems PCIO Ebus2, revision 0x01
auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 72c000-72c003, 72f000-72f003
power at ebus0 addr 724000-724003 ipl 2021 ipl 2034 not configured
SUNW,pll at ebus0 addr 504000-504002 not configured
sc at ebus0 addr 500000-500007 not configured
se at ebus0 addr 400000-40007f ipl 2027 not configured
com0 at ebus0 addr 3083f8-3083ff ipl 2025: ns16550a, working fifo
kbd0 at com0
com1 at ebus0 addr 3062f8-3062ff ipl 2026: ns16550a, working fifo
ms0 at com1
lpt0 at ebus0 addr 3043bc-3043cb, 300398-300399, 700000-70000f ipl 2018
fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 720000-720003 ipl 2023 not configured
clock0 at ebus0 addr 0-1fff: mk48t59: hostid 80877623
flashprom at ebus0 addr 0-fffff, 0-fffff not configured
beeper at ebus0 addr 722000-722003 not configured
hme0 at pci0 dev 1 function 1: address 08:00:20:87:76:23
nsphy0 at hme0 phy 1: DP83840 10/100 media interface, rev. 0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
hme0: using ivec 37e1 for interrupt
pciide0 at pci0 dev 3 function 0: National Semiconductor product 0x0002 (rev. 0x01)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel configured to native-PCI mode
pciide0: using ivec 7e0 for native-PCI interrupt
pciide0: primary channel ignored (not responding; disabled or no drives?)
pciide0: secondary channel configured to native-PCI mode
pciide0: secondary channel ignored (not responding; disabled or no drives?)
psycho1 at mainbus0 addr 0xfffd8000
pci108e,8000: impl 0, version 3: ign 7c0 bus range 128 to 128; PCI bus 128
pci1 at psycho1
pci1: i/o space, memory space enabled
pcons0 at mainbus0
Kernelized RAIDframe activated
root on hme0
nfs_boot: trying RARP (and RPC/bootparam)
nfs_boot: client_addr=63.86.104.23 (RARP from 63.86.104.12)
nfs_boot: server_addr=63.86.104.12
nfs_boot: hostname=atx.thought.net
nfs_boot: timeout...
nfs_boot: timeout...
nfs_boot: timeout...
root on u5:/export
root file system type: nfs

And right about here the machine is locked up (only XIR comes to the rescue).
This is curious because the hme -is- working (wouldn't have gotten the
address or the server address otherwise), but it never advances past
this point.

Without the patch, the psycho isn't configured at all (and the dmesg
is pretty short =).

--Jason L. Wright