Re: rootfs goes full during installation of 5.0.1 on NWS-1460

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

> I also tried to reset the disklabel and start over:
> > # dd if=/dev/zero of=/dev/rsd0c bs=512 count=8192
> > sd0: no disk label
> > 8192+0 records in
> > 8192+0 records out
> > 4194304 bytes transferred in 86.090 secs (48719 bytes/sec)
> > #
> Then reboot and label disk:
> ...
> sd0 at scsibus0 target 0 lun 0: <QUANTUM, FIREBALL_TM1280S, 300L> disk  
> fixed
> sd0: 1222 MB, 6810 cyl, 2 head, 183 sec, 512 bytes/sect x 2503872  
> sectors
> sd0: async, 8-bit transfers
> ...
> Terminal type? [vt100]
> Erase is backspace.
> (I)nstall, (S)hell or (H)alt ? s
> # disklabel -i -I sd0
> sd0: no disk label
> uvm_fault(0x28a810, 0xe1280000, 0x2) -> 0xe
>    type 8, code [mmu,,ssw]: 4010715
> trap type 8, code = 0x4010715, v = 0xe1280000
> kernel program counter = 0x154
> pid = 0, lid = 26, pc = 00000154, ps = 2704, sfc = 1, dfc = 1
> Registers:
>               0        1        2        3        4        5         
> 6        7
> dreg: 00000000 029EB780 00000000 00000000 00002000 003E5600 50000001  
> 00000000
> areg: 000FC4AE 03767000 029F57E0 029EBC80 00297FF0 00000000 00000000  
> FFEFFFFC
> 
> Kernel stack (000FBF98):
> 0FBF98: 000C944C 000FC01C 00000080 00000000 00000000 00002000 003E5600  
> 50000001
> 0FBFB8: 00000000 029F57E0 029EBC80 00297FF0 00000000 00000000 00000000  
> 00000001
> 0FBFD8: 00000000 00000000 00000000 00000001 00000000 00000000 00000008  
> 00000000
> 0FBFF8: 00000000 00000000
> panic: MMU fault
> 
> It seems like a hardware failure?

I'm afraid it. It looks the kernel somehow jumped into adress 0x0
where the entry point of kernel, and the address 0xe1280000 is
"AST disable" port around line 260 in locore.s.
It's really unlikely.

On my NWS-1750, the similar operation works without problem:

---
 :
scsibus0 at si0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <I-O DATA, HDVS-UM8.4G, 104S> disk fixed
sd0: 8063 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 16514064 sectors
sd0: async, 8-bit transfers
 :

# dd if=/dev/zero of=/dev/rsd0c count=100
100+0 records in
100+0 records out
51200 bytes transferred in 0.790 secs (64810 bytes/sec)
# halt
 :
NEWS> bo fh
NetBSD/news68k Primary Boot
NetBSD/news68k Secondary Boot, Revision 1.7 (from NetBSD 5.0.1)
Booting fh(0,0,0)
1020024+1501304+193876=0x2990d8

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009
    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 5.0.1 (INSTALL) #0: Thu Jul 30 05:40:38 UTC 2009
        
builds%b6.netbsd.org@localhost:/home/builds/ab/netbsd-5-0-1-RELEASE/news68k/200907292356Z-obj/home/builds/ab/netbsd-5-0-1-RELEASE/src/sys/arch/news68k/compile/INSTALL
SONY NET WORK STATION, Model NWS-1750, Machine ID #10557
total memory = 16368 KB
avail memory = 12904 KB
mainbus0 (root)

 :

erase ^H, werase ^W, kill ^U, intr ^C, status ^T
Terminal type? [vt100] 
Erase is backspace.                                                     
(I)nstall, (S)hell or (H)alt ? s
# disklabel -i -I sd0
sd0: no disk label
partition> 

---

I dig out my NWS-1460 from closet but unfortunately its SCSI bus
seems dead so I can't test to label disk on it ;-(

To check your 1460, could you try the following items?

- "tm" command on the firmware prompt
  (it will take ~one hour)
  ---
  NEWS> tm
  Testing data lines........
  Testing address lines.........................
  NEWS> 
  ---

- check types of SIMMs (8 or 9 chip SIMMs are required)
- remove some of SIMMs

To check SIMMs in NWS-14x0 and NWS-15x0,
the following page might be useful:
http://www.matsusaka.ne.jp/~ueno/techical/WS/T-NWS-1400.html
http://www.matsusaka.ne.jp/~ueno/techical/WS/T-NWS-1400.memory.html

- boot the following disk image for your 1.2GB disk
ftp://ftp.NetBSD.org/pub/NetBSD/misc/tsutsui/news68k/news68k-5.0.1.img.gz

  This image contains bootloader so you can use it by dd(1)'ing to disk,
  and this uses GENERIC which includes ddb(4).

---
Izumi Tsutsui