Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA6126 ; Tue, 05 Jan 93 04:12:45 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!math.fu-berlin.de!news.th-darmstadt.de!iti.informatik.th-darmstadt.de!deeken
From: deeken@iti.informatik.th-darmstadt.de (Hans-Christoph Deeken)
Subject: Re: codrv problems..
Sender: news@news.th-darmstadt.de (The News System)
Message-ID: <1993Jan7.164904.41040@news.th-darmstadt.de>
Date: Thu, 7 Jan 1993 16:49:04 GMT
References: <1993Jan6.184438.5175@lgc.com>
Nntp-Posting-Host: sun2.iti.informatik.th-darmstadt.de
Organization: TU Darmstadt
Keywords: 386BSD, codrv
Lines: 27
In article <1993Jan6.184438.5175@lgc.com>, danson@lgc.com (Doug Anson) writes:
> HI:
>
[ description of codrv problems ]
>
> I have the 386BSD 0.1 kernel with 1-58 patches applied + pcfs.
Exactly the same problem here. Also "panic: syscall", also 386BSD 0.1.pl58.
The kernel prints out the devices as they are probed/attached(?), but dies
after that with a "panic: syscall", before /etc/rc output starts.
The only occurance of panic("syscall") that I've found is in
/sys/i386/i386/trap.c, at the start of syscall(). Since I don't know anything
about the stuff done in trap.c, I'm stuck.
> Any help would be appreciated.
> Doug
Me too. Holger?
Hannes
--
Hans-Christoph Deeken | hannes@flinx.{RoBIN.de,hotb.sub.org} (home)
Gerauer Str. 20 | deeken@iti.informatik.th-darmstadt.de (university)
6000 Frankfurt/M 71 | IRC: Glenlivet
"Das Beispiel hinkt nicht, das sitzt im Rollstuhl" -- Marsi