Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!zaphod.mps.ohio-state.edu!howland.reston.ans.net!agate!ames!olivea!quack!mrapple From: mrapple@quack.kfu.com (Nick Sayer) Newsgroups: comp.os.386bsd.bugs Subject: Some bug reports Message-ID: <f0U0DZw@quack.kfu.com> Date: 22 Mar 93 17:40:16 GMT Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'. Lines: 29 I have looked in the official bug list on agate and don't see these listed, so I thought I'd pass them along and see what you all thought. If you're running X and the kernel panics, the panic code ought to do some sort of screen reset. Otherwise the system just seems to freeze. My natural reaction was to whomp on the keyboard to see if it was stuck or something, which no doubt aborted the memory dump, which kept savecore from saving anything useful. I find that I have to increase KMEM_MAPENT to 10000 to keep the kmem_malloc: kmem_map too small panics from hapening. I have 16M of RAM and make heavy use of NFS and X. The .l file for vtwm 5.1 makes uncompilable code under 386bsd. Running that file through Sun's lex makes compilable code. Ergo a bug in lex? I could try diffing, but I imagine there's more different than similar in the two .c files. Ditto for olvwm's .l file if YYDEBUG is defined as 1. If these have been seen before, then I appologise. Could anyone tell me were a more up-to-date bug list is kept? Still, I say it's not bad for free. -- Nick Sayer <mrapple@quack.kfu.com> | "Turn around. Stick it out. N6QQQ @ N0ARY.#NOCAL.CA.USA.NOAM | Even white boys got ta shout: +1 408 249 9630, log in as 'guest' | Baby got back!" PGP 2.1 public key via finger | -- Sir Mixalot