4.0.1/sun3 broken?
der Mouse
perhaps I missed it.
I'm trying to run an at least vaguely modern NetBSD on one of my
Sun-3s, in response to a ping from someone interested in historical
compatability testing.
So I set up netboot and untarred the 4.0.1 distribution sets. It runs
apparently fine single-user diskless. But rather than try to do
everything diskless, I wanted to move stuff to the disk I have on it.
I got it labeled fine. But when I try to newfs it....
Sun3# newfs /dev/rsd0a
/dev/rsd0a: 4212.0MB (8626176 sectors) block size 16384, fragment size 2048
using 23 cylinder groups of 183.14MB, 11721 blks, 23168 inodes.
super-block backups (for fsck_ffs -b #) at:
trap type=0x0, code=0x145, v=0x5a972c66
kernel: Bus error trap
pid = 17, lid = 1, pc = 0E0F053C, ps = 2004, sfc = 1, dfc = 1
[...register dump...kernel stack dump...]
db>
This appears to be repeatable; I rebooted and tried again and it
crashed with the same values printed except for the pid and a few
fragments of the kernel stack.
ddb's stack trace says the call chain is syscall, syscall_plain,
sys_pwrite, dofilewrite, vn_write, VOP_WRITE, nfsspec_write,
spec_write, sdwrite, physio, vmapbuf, uvm_km_alloc, uvm_map,
uvm_map_prepare, uvm_km_va_drain, callback_run_roundrobin, trap, panic.
About all this says to me is that it's in a part of the kernel I don't
know - and that it (probably) isn't something like broken hardware
causing the sd driver to go insane.
The kernel is the stock sun3 4.0.1 GENERIC kernel, MD5
3e31d29f198ba236eafd8692b6ed9d4f. Full dmesg appears after my
signature.
Any thoughts?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Here's that dmesg:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007
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 4.0.1 (GENERIC) #0: Wed Oct 8 01:35:31 PDT 2008
builds@wb40:/home/builds/ab/netbsd-4-0-1-RELEASE/sun3/200810080053Z-obj/home/builds/ab/netbsd-4-0-1-RELEASE/src/sys/arch/sun3/compile/GENERIC
Model: sun3 60
fpu: mc68881
total memory = 24576 KB
avail memory = 21952 KB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
obio0 at mainbus0
zsc0 at obio0 addr 0x0 ipl 6: (softpri 3)
kbd0 at zsc0 channel 0: baud rate 1200
ms0 at zsc0 channel 1: baud rate 1200
zsc1 at obio0 addr 0x20000 ipl 6: (softpri 3)
zstty0 at zsc1 channel 0 (console i/o)
zstty1 at zsc1 channel 1
eeprom0 at obio0 addr 0x40000
oclock0 at obio0 addr 0x60000 ipl 5: intersil7170
memerr0 at obio0 addr 0x80000 ipl 7: (Parity memory)
intreg0 at obio0 addr 0xa0000
le0 at obio0 addr 0x120000 ipl 3: address 08:00:20:06:20:68
le0: 8 receive buffers, 2 transmit buffers
si0 at obio0 addr 0x140000 ipl 2: options=0xf
scsibus0 at si0: 8 targets, 8 luns per target
obmem0 at mainbus0
bwtwo0 at obmem0 addr 0xff000000 (1152x900)
enabling interrupts
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <SEAGATE, ST34573N, 6244> disk fixed
sd0: 4340 MB, 7501 cyl, 5 head, 237 sec, 512 bytes/sect x 8888924 sectors
sd0: async, 8-bit transfers
boot device: le0
root on le0
nfs_boot: trying RARP (and RPC/bootparam)
nfs_boot: client_addr=10.0.1.8 (RARP from 10.0.1.2)
nfs_boot: server_addr=10.0.1.2
nfs_boot: hostname=Sun3
nfs_boot: gateway=10.0.1.1
nfs_boot: my_mask=255.255.255.0
root on 10.0.1.2:/nfs/sun3
root file system type: nfs
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
David Johnson
install. I attempted to use the latest kernel but got to a similar
point. I can't say it was the exact same place you are seeing, but all
would go well into the booting process and then kernel panic dropping
into the ROM monitor. On your suggestion I went back to an earlier,
presumably smaller OS revision, and I was able to get it to boot to
multi-user mode.
It is difficult to accomplish much with a 4MB RAM space. But it was fun
and I thank you again for your help.
der Mouse
It is, especially recently. I now have the -3/60 I quoted the dmesg
from doing a diskless build of the world; I'll have to see whether
things are too bloated for it to complete in finite time. I've also
got a NeXT slab which has other issues but which I may soon have
working similarly; it's got more RAM and, while the difference is not
large (the -3/60 has 24 megs, the NeXT, 32), it doesn't take much to
have a big effect if it makes the difference between thrashing and not.
For the purposes that prompted me to start on this, pretty much any 68k
NetBSD will do fine.
> But it was fun and I thank you again for your help.
Well, you're certainly welcome. I'm glad you had fun. That's really
the major reason to play with things like sun3s these days, after all.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
--
Julian Coleman
> So I set up netboot and untarred the 4.0.1 distribution sets. It runs
> apparently fine single-user diskless. But rather than try to do
> everything diskless, I wanted to move stuff to the disk I have on it.
> I got it labeled fine. But when I try to newfs it....
>
> Sun3# newfs /dev/rsd0a
> /dev/rsd0a: 4212.0MB (8626176 sectors) block size 16384, fragment size 2048
> using 23 cylinder groups of 183.14MB, 11721 blks, 23168 inodes.
> super-block backups (for fsck_ffs -b #) at:
> trap type=0x0, code=0x145, v=0x5a972c66
> kernel: Bus error trap
> pid = 17, lid = 1, pc = 0E0F053C, ps = 2004, sfc = 1, dfc = 1
> [...register dump...kernel stack dump...]
> db>
Just as a data point, I have:
NetBSD 5.1_RC3 (SUN380) #0: Sat Aug 14 19:36:23 BST 2010
Model: sun3x 80
total memory = 16384 KB
and had no problems running `newfs` (it is sun3x and not sun3, and it boots
from internal disks).
Thanks,
J
--
My other computer also runs NetBSD / Sailing at Newbiggin
http://www.netbsd.org/ / http://www.newbigginsailingclub.org/
Izumi Tsutsui
and it might not be loaded properly.
http://mail-index.NetBSD.org/port-sun3/2008/12/26/msg000026.html
---
Izumi Tsutsui
John Carr
I'm actually running into something very similar in all installers
from 4.0.1 onward. I haven't been able to get NetBSD installed on my
3/60 (24Mb) via an installer in quite awhile. I see the same thing you
do: the newfs causes a kernel panic. And, yes, I know I should've said
something sooner... I found this when I tried to do a new install of
5.0 on my 3/60, ran into the issue, and then started
troubleshooting... and ran out of time.
What I've narrowed it down to is that it seems to have issues with
partitions over 1Gb. I've not tried 5.1 yet, but I have a feeling that
I'll run into the same thing as I last did with 5.0.2. What I did was
use the same drive & partitions to try to install everything from 3.0
up to 5.0.2. 3.0 can newfs without issue to all of my partitions.
4.0.1, 5.0, 5.0.1, and 5.0.2 installers can newfs my smaller
partitions (/ and /var, coming in around 64Mb a piece). /dev/rsd0g,
which comes in around 1400Mb, will consistently panic on newfs. I did
a little bit of messing with partition sizes and found that I can
newfs with 4.0.1+ as long as the partition is less than 1024Mb. Once
you go over, the newfs will cause the kernel panic.
Not sure what additional information folks would want/need. Stack
traces?
---
Help me race for a cure to defeat leukemia and other blood cancers!
http://pages.teamintraining.org/mi/ambbr11/jcarrn6fel