Date: Tue, 21 Feb 1995 15:38:06 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users), hm@hcs.de (Hellmuth Michaelis), lim@gate.sinica.edu.tw (Carmay Lim) Subject: pcvt in -current Message-ID: <199502211438.PAA10150@uriah.heep.sax.de>
next in thread | raw e-mail | index | archive | help
Wow, i've finally tracked down why pcvt panics a -current kernel. Thanks to the guy who used to be called Carny Lim here (i know it's not your real name, but forgive me: i've forgot it), who provided me with an account on a machine in Taiwan to analyze a kernel core dump for this. The problem is that pcvt used to be a replacement driver for syscons and pccons. Hence it always used the same calling interface as its replacees, so all external entry points are named pc*. Recently, Søren decided to rename the syscons entry points to their new names though, and since we don't have pccons any longer, pcvt dissapeared from the cdevsw[] table. :-( Hellmuth, we need to test for this condition in pccnprobe() instead of falling off the end of cdevsw[] and filling the console structure with bogus values. (panic() is all we can do there, but much better pointing to the source of the evil.) Now i dunno how to handle this at best. IMHO, creating an own cdevsw[] entry is the best solution. Any other opinions? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502211438.PAA10150>