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

[TOMARI Hisanobu <posco.grubb%gmail.com@localhost>]

> If you can rebuild a kernel on other host, you can disable
> SCSI DMA as mentioned in sys/arch/news68k/conf/GENERIC:
I tried following config:
        si0     at hb0 addr 0xe0cc0000 ipl 4 flags 0x20000
and it did the trick! I partitioned the original 240MB disk on the machine
then put NetBSD on it, all went really smoothly.
However, when the firmware tries to load the bootloader, it seems to use
DMA transfers, and therefore cannot boot. So I ended up creating a
"Startup Floppy" containing bootloader and kernel.
This is how it goes on my half-broken machine:

16M bytes available, 16K byte(s) reserved.

SONY NET WORK STATION MC68030 Monitor Release 1.5A
Model NWS-1460, Machine ID #10087, Ethernet address 08:00:46:00:4c:d3

NEWS> bo fh
NetBSD/news68k Primary Boot
NetBSD/news68k Secondary Boot, Revision 1.7 (from NetBSD 5.0.1_PATCH)
Booting fh(0,0,0)
1455268+34172+271228=0x1b0044

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_PATCH (NODMA) #0: Fri Oct 30 10:33:47 JST 2009
        
tomari%takosuke.is.s.u-tokyo.ac.jp@localhost:/home/tomari/netbsd/obj/sys/arch/news68k/compile/NODMA
SONY NET WORK STATION, Model NWS-1460, Machine ID #10087
total memory = 16368 KB
avail memory = 13556 KB
mainbus0 (root)
hb0 at mainbus0
le0 at hb0 addr 0xe0f00000 ipl 4: address 08:00:46:00:4c:d3
le0: 8 receive buffers, 2 transmit buffers
timer0 at hb0 addr 0xe1000000 ipl 6
mkclock0 at hb0 addr 0xe0d80000: mk48t02
zsc0 at hb0 addr 0xe0d40000 ipl 5 vect 64
zstty0 at zsc0 channel 0 (console i/o)
zstty1 at zsc0 channel 1
si0 at hb0 addr 0xe0cc0000 ipl 4: options=0x20000
scsibus0 at si0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <HITACHI, DK312C, CM73> disk fixed
sd0: 239 MB, 1081 cyl, 12 head, 37 sec, 512 bytes/sect x 490656 sectors
sd0: async, 8-bit transfers
boot device: <unknown>
root on sd0a dumps on sd0b
WARNING: preposterous TOD clock time
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
Thu Oct 29 19:28:50 JST 2009
swapctl: adding /dev/sd0b as swap device at priority 0
Starting file system checks:
/dev/rsd0a: file system is clean; not checking
Setting tty flags.
Setting sysctl variables:
kern.no_sa_support: 0 -> 1
ddb.onpanic: 1 -> 0
Starting network.
Hostname: survivor.local
Configuring network interfaces: le0.
Adding interface aliases:.
Building databases: dev, utmp, utmpx, services done
Starting syslogd.
Checking for core dump...
Mounting all filesystems...
Clearing temporary files.
Creating a.out runtime link editor directory cache.
Checking quotas: done.
Setting securelevel: kern.securelevel: 0 -> 1
Starting virecover.
Starting local daemons:.
Updating motd.
postfix: rebuilding /etc/mail/aliases (missing /etc/mail/aliases.db)
newaliases: warning: inet_protocols: IPv6 support is disabled: Address family 
not supported by protocol family
newaliases: warning: inet_protocols: configuring for IPv4 support only
newaliases: warning: valid_hostname: misplaced delimiter: 
survivor.iyo.kicks-ass.net.
newaliases: fatal: unable to use my own hostname
Oct 29 19:48:24 survivor postfix/sendmail[243]: fatal: unable to use my own 
hostname
Starting inetd.
Starting cron.
Thu Oct 29 19:48:33 JST 2009

NetBSD/news68k (survivor.local) (console)

login: root
Password:
Oct 29 20:31:36 survivor login: ROOT LOGIN (root) ON console
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_PATCH (NODMA) #0: Fri Oct 30 10:33:47 JST 2009

Welcome to NetBSD!



> If you have some spare time, I'd like to see how NetBSD 4.0.1 goes
> on the same machine..
I had tried 4.0.1 before posting anything here, but it wasn't that much
different from 5.0.1. But the 4.0.1 panics less on the broken machine in
my experience.

Again, thank you very much for your help and the news68k port.
Although it's not the fastest machine I have, not slowest either.
I'll enjoy the machine a lot, all thanks to you!

--
TOMARI Hisanobu