Re: About support for rtVAX300

[Holm Tiffe <holm%freibergnet.de@localhost>]

Mouse wrote:

> > root on unicorn:/data/home/exports/rtvax
> > root file system type: nfs
> > [...]
> > warning: no /dev/console
> > panic: init died (signal 0, exit 11)
> 
> > ..no clue why init is dying, but I really don't have device entries.
> 
> As of 5.1 (the most recent source tree I have at hand), if init finds
> /dev/console missing, it forks a process to run ./sh ./MAKEDEV -MM init
> (in /dev/), or if ./MAKEDEV isn't executable then /etc/MAKEDEV.  Exit
> code 11 means that even after running that, /dev/console still doesn't
> exist.  You may want to check the source for the version you're using
> to see if it's true there too.
> 
> > Have to look how I could create them..
> 
> If the NFS server (unicorn, in your case) is unixy enough, you may be
> able to cd to /data/home/exports/rtvax/dev and run ./MAKEDEV there.
> I'd suggest "./MAKEDEV std", which should at least provide console.
> 
> > But this isn't my question here.  [...]
> 
> That question I'm not competent to answer.
> 
> /~\ The ASCII                           Mouse
> \ / Ribbon Campaign
>  X  Against HTML              mouse%rodents-montreal.org@localhost
> / \ Email!         7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B


Ok, THX.

At least I could made some devices with mknod, don't know if this is the
right way, since if my memory is correct they have to be created with the
tools from the target OS.
Init doesn't complain about a missing /dev/console anymore.

Now I have a question about the loading and initializing of device drivers
in the kernel.
There are is this static compiled in device list in ka650.c:

static const char * const ka650_devs[] = { "cpu", "sgec", "lance", "uba", NULL 
};

Those drivers are initialized relative early while booting what the console
is still running in polled mode.
To which time the kernel searches for the other devices that are listed in
the kernel config file like dz or my scn?

This is b'cause..

Using IP address: 192.168.50.20
myip: rtvax (192.168.50.20)
root addr=192.168.50.50 path=/data/home/exports/rtvax
2069020+92264 [154768+147806]=0x259c94
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    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 6.0 (RTVAX300-test) #217: Mon Jan 14 11:15:47 CET 2013

holm%beast.freibergnet.de@localhost:/home/holm/tmp/netbsd/root6/usr/src/sys/arch/vax/compile/RTVAX
Embedded VAX rtVAX 300
total memory = 16380 KB
avail memory = 13068 KB
mainbus0 (root)
cpu0 at mainbus0: RTVAX300, CVAX microcode rev 6 Firmware rev 17
ze0 at mainbus0
ze0: hardware address 00:00:f8:50:93:14
lance at mainbus0 not configured
uba at mainbus0 not configured
boot device: ze0
root on ze0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.50.50
nfs_boot: my_name=rtvax
nfs_boot: my_addr=192.168.50.20
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.50.254
root on unicorn:/data/home/exports/rtvax
root file system type: nfs
TODR stoppedWARNING: preposterous TOD clock time
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
dev: 0
r0=0000001f r1=00000000 r2=00000000 r3=00000017 r4=802f1000 r5=83719d00
r6=00000000 r7=00000000
r8=80ef7d10 r9=83719eb4 r10=00000036 r11=83719eb4
ap=83719cb8 fp=83719ca0 sp=7fffd8dc pc=800f278c
panic: SEGV in kernel mode: pc 0x800f278c addr 0x194

.. I get this panic which is from inside scn_write() from the scn driver:

scnwrite(dev_t dev, struct uio *uio, int flags)
{
        struct scn_softc *sc = SOFTC(DEV_UNIT(dev));
        aprint_normal("dev: %lx\n",(long unsigned int)sc);
        struct tty *tp = sc->sc_tty;
        __asm("halt");

        return ((*tp->t_linesw->l_write) (tp, uio, flags));
}

sc-sc_tty doesn't seem to exists here, it is a null pointer.
(segv is just before the halt), that means the sc->softc isn't initialized
jet.

It seems, that the dz driver is using a automatism with mfpr(PR_MAPEN)
to find out if the machine is running in VM mode and is reinitializing
then..

In short I now to make the driver interrupt capable..

Any hints? Ragge?

Regards,

Holm


-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741