Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA6193 ; Tue, 05 Jan 93 20:05:30 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!news.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: <1993Jan8.084810.30764@news.th-darmstadt.de>
Date: Fri, 8 Jan 1993 08:48:10 GMT
References: <veit.726430723@du9ds3>
Nntp-Posting-Host: sun2.iti.informatik.th-darmstadt.de
Organization: TH Darmstadt
X-Newsreader: Tin 1.1 PL5
Lines: 39
Holger Veit (veit@du9ds3.fb9dv.uni-duisburg.de) wrote:
> The location of the panic("syscall") line is in trap.c, that's right. But
> it does not tell anything about the real reason of the fault. Panic's occur
> for a lot of reasons, but in this case it is indeed evidence that there is
> still a bug in codrv-0.1.1.
Well, it could have been possible, that you take a look at
[trap.c]
> if (ISPL(frame.sf_cs) != SEL_UPL)
> panic("syscall");
and have at least a hint, what is wrong... :)
> As Serge Vakulenko pointed out (in a private
> letter), there is an uninitialized register variable in coprobe(), co_kbd.c.
> The first declaration there should read
> register struct consoftc *p = &consoftc;
>
> This might or might not be the bug which causes the trouble here, at least it
> is worth trying.
But it doesn't help. :( (tried just 15 minutes ago)
> You may of course wait (a little bit ;-) ) for the next version.
How long is "a little bit"?
> 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