Do you have the problem with snapshot's kernel? I'd assume 'no'
but that's not stated so.

	Andrey

On Thu, Sep 27, 2001 at 02:25:24PM +0200, Jarle Greipsland wrote:
> Hi,
> 
> I recently acquired a second hand Ultra Sparc 5 and installed the
> snapshot from August 21st.  Generally this worked quite well.  My
> only grievance is that the sysinst tool will neither let me see
> nor change the 'cylinders per group' parameter for the file
> system partitions, but that's a minor problem, I guess.
> 
> After the initial installation was over with, I decided to try
> and upgrade the system to -current.  I build a new kernel, and
> rebooted.  The new kernel booted fine until it brought up the
> hme0 network interface.  Then the kernel started spewing out
> console messages like:
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> 
> Come to think of it there might have been a period of no
> activity, or at least a pause, until I typed something on the
> console (it's running with a serial console, and there is no
> mouse or keyboard attached to the system).  The messages
> continued to be printed out until I did a 'ifconfig hme0 down'.
> 
> Have anyone else observed something similar?  Known problem?
> Easy fix?  Should I send-pr it?
> 
> 					-jarle
> 
> NetBSD 1.5Y (OMO) #3: Wed Sep 26 18:32:32 CEST 2001
>     jarle@omo:/usr/src/sys/arch/sparc64/compile/OMO
> total memory = 256 MB
> avail memory = 230 MB
> using 1651 buffers containing 13208 KB of memory
> bootpath: /pci@1f,0/pci@1,1/ide@3,0/disk@0,0
> mainbus0 (root): SUNW,Ultra-5_10
> cpu0 at mainbus0: SUNW,UltraSPARC-IIi @ 400 MHz, version 0 FPU
> cpu0: physical 4K instruction (32 b/l), 4K data (32 b/l), 2048K external (64 b/l) 
> psycho0 at mainbus0 addr 0xfffc4000
> SUNW,sabre: impl 0, version 0: ign 7c0 bus range 0 to 2; PCI bus 0
> DVMA map: c0000000 to e0000000
> pci0 at psycho0
> pci0: i/o space, memory space enabled
> ppb0 at pci0 dev 1 function 1: Sun Microsystems Simba PCI bridge (rev. 0x13)
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled
> ebus0 at pci1 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 37 not configured
> SUNW,pll at ebus0 addr 504000-504002 not configured
> se at ebus0 addr 400000-40007f ipl 43 not configured
> com0 at ebus0 addr 3083f8-3083ff ipl 41: ns16550a, working fifo
> kbd0 at com0
> com1 at ebus0 addr 3062f8-3062ff ipl 42: ns16550a, working fifo
> ms0 at com1
> lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 700000-70000f ipl 34
> fdthree at ebus0 addr 3023f0-3023f7, 706000-70600f, 720000-720003 ipl 39 not configured
> clock0 at ebus0 addr 0-1fff: mk48t59: hostid 80d150b4
> flashprom at ebus0 addr 0-fffff not configured
> SUNW,CS4231 at ebus0 addr 200000-2000ff, 702000-70200f, 704000-70400f, 722000-722003 ipl 35 ipl 36 not configured
> hme0 at pci1 dev 1 function 1: address 08:00:20:d1:50:b4
> nsphy0 at hme0 phy 1: DP83840 10/100 media interface, rev. 1
> nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> hme0: using ivec 3021 for interrupt
> ATI Technologies Mach64 B (VGA display, revision 0x5c) at pci1 dev 2 function 0 not configured
> pciide0 at pci1 dev 3 function 0: CMD Technology PCI0646 (rev. 0x03)
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to native-PCI mode
> pciide0: using ivec 1820 for native-PCI interrupt
> atapibus0 at pciide0 channel 0: 2 targets
> cd0 at atapibus0 drive 1: <CDU5211, , YYS2> type 5 cdrom removable
> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
> wd0 at pciide0 channel 0 drive 0: <IC35L040AVER07-0>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 39266 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 80418240 sectors
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> cd0(pciide0:0:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> pciide0: secondary channel configured to native-PCI mode
> pciide0: disabling secondary channel (no drives)
> ppb1 at pci0 dev 1 function 0: Sun Microsystems Simba PCI bridge (rev. 0x13)
> pci2 at ppb1 bus 2
> pci2: i/o space, memory space enabled
> pcons0 at mainbus0
> No counter-timer -- using %tick at 400MHz as system clock.
> root on wd0a dumps on wd0b
> root file system type: ffs