Re: About support for rtVAX300

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

Johnny Billquist wrote:

> On 2013-01-14 11:36, Holm Tiffe wrote:
> >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.
> 
> init sould stop complaining even if you just created a plain file with 
> the name /dev/console, unless I remember wrong...
> The improtant question is that you create the file node with the right 
> values. Just saying you ran mknod don't give me much confidence. mknod 
> is not really OS specific in that way, but the values you use to mknod 
> are very OS specific, and also differ between the same OS for different 
> architectures.
> 
> So, what did you use for values with mknod?

-r-xr-xr-x  1 root  wheel     38435 14 Jan 09:30 MAKEDEV
-r-xr-xr-x  1 root  wheel      2549 13 Okt 21:22 MAKEDEV.local
drwxr-xr-x  2 root  wheel       512 13 Okt 21:05 altq
crw-rw-rw-  1 root  wheel    0,   0 14 Jan 09:31 console
crw-------  1 root  wheel    0,   1 14 Jan 09:35 constty
crw-r-----  1 root  kmem     7,   0 14 Jan 09:36 drum
drwxr-xr-x  2 root  wheel       512 13 Okt 21:05 fd
crw-------  1 root  wheel   33,   0 14 Jan 09:37 klog
crw-r-----  1 root  kmem     3,   1 14 Jan 09:36 kmem
cr--r--r--  1 root  wheel   79,   0 14 Jan 09:37 ksyms
lrwxr-xr-x  1 root  wheel        12 13 Okt 21:17 log -> /var/run/log
crw-r-----  1 root  kmem     3,   0 14 Jan 09:36 mem
crw-rw-rw-  1 root  wheel    3,   2 14 Jan 09:36 null
crw-rw-rw-  1 root  wheel   96,   0 14 Jan 10:09 scn00
crw-rw-rw-  1 root  wheel   96,   1 14 Jan 10:09 scn01
crw-rw-rw-  1 root  wheel   53,   0 14 Jan 09:38 stdin
crw-rw-rw-  1 root  wheel    2,   0 14 Jan 09:38 tty
crw-rw-rw-  1 root  wheel   96,   0 14 Jan 10:08 tty00
crw-rw-rw-  1 root  wheel   96,   1 14 Jan 10:09 tty01
crw-rw-rw-  1 root  wheel    3,  12 14 Jan 09:36 zero

... the valuesfrom the MAKEDEV script (NetBSD VAX) in /dev,
besides of scn0? and tty0?. Since the major number is my own
in in majors.vax entered 96...
> 
> Another questions would be about IPL. What do you mean by "correct" IPL? 
> IPL is interrupt priority level, and it tells what other interrupts will 
> be blocked. I don't think much, if any code should be using IPLs 
> directly, but should use the symbolic IPLs such as IPL_TTY for things at 
> the ttl level (unless I remember wrong, or something changed recently).
> Someone can surely correct me on this point.
> 
> >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?
> 
> That is the autoconfig stuff.
> 
> kern/init.main.c: main -> configure
> kern/init_main.c: configure -> cpu_configure
> arch/vax/vax/autoconf.c: cpu_configure -> rootconf
> 
> and after that, it's driven by data structures created by config. (And, 
> of course, I might remember things wrong, as usual...)

:-)

Will habe a look at it..
> 
> So, for each device that potentially can sit at a point, it will call 
> the match function, and if that succeeds, it will call the attach and 
> the print functions.
> 
> Why don't you have all the debug printing enabled???
> 
>       Johnny
> 
> -- 
> Johnny Billquist                  || "I'm on a bus
>                                   ||  on a psychedelic trip
> email: bqt%softjar.se@localhost             ||  Reading murder books
> pdp is alive!                     ||  tryin' to stay hip" - B. Idol

I can try it...

... at least TRAPDEBUG seems to be broken, it doesn't compile ...

[..]
cprng sysctl: WARNING insufficient entropy at creation.
booted from type 100 unit 0 csr 0x20008000 adapter 0 slave 0
boot device: ze0
root on ze0
mountroot: trying nfs...
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 time: 0x50f3fded
root file system type: nfs
TODR stoppedWARNING: preposterous TOD clock time
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init: copying out path `/sbin/init' 11
Mutex error: lockdebug_wantlock: locking against myself

lock address : 0x000000008020e078 type     :               spin
initialized  : 0x00000000800e4f74
shared holds :                  0 exclusive:                  1
shares wanted:                  0 exclusive:                  1
current cpu  :                  0 last held:                  0
current lwp  : 0x0000000080f3faa0 last held: 0x0000000080f3faa0
last locked* : 0x00000000800e5b8a unlocked : 000000000000000000
owner field  : 0x0000000000011700 wait/spin:                0/1

panic: LOCKDEBUG
ý

...and what does this mean?

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