[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: About support for rtVAX300
Johnny Billquist wrote:
> On 2013-01-14 13:47, Holm Tiffe wrote:
> >Johnny Billquist wrote:
> >>On 2013-01-14 11:36, Holm Tiffe wrote:
> >>>Mouse wrote:
> >>>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
> >>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
> Looks good.
> >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...
> Did you create both tty00 and scn00? They are, in this case, just two
> different names for the same device.
Yes I did and I know.
> Btw, you also need to make the mapping from number to device driver in
> the kernel code. I don't remember offhand where that is located, but it
> exists somewhere (obviously).
> >>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?
> Yuck! That means something is very broken. Unless it's related to some
> fiddling of yours, it means someone needs to take a look for NetBSD/vax
> in general, or possibly even the MI parts of NetBSD...
This panic only occurs if I have LOCKDEBUG set in the config file.
Without that I get the SIGSEGV panic:
oot on unicorn:/data/home/exports/rtvax
root time: 0x50f406cd
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
r0=0000001f r1=00000000 r2=00000000 r3=00000017 r4=80305400 r5=8371ad00
r8=80ef5d10 r9=8371aeb4 r10=00000036 r11=8371aeb4
ap=8371acb8 fp=8371aca0 sp=7fffd8dc pc=800f806a
panic: SEGV in kernel mode: pc 0x800f806a addr 0x194
where the pc is inside the scnwrite in my driver.
Besides of this, what should the panic do when it is an his end?
Every time I get an "ý" as last char and have to reset the machine
(which is time consuming. the halt key doesn't work, ist this normal?)
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
Main Index |
Thread Index |