Date: Mon, 28 Apr 1997 20:45:06 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: freebsd-hackers@freebsd.org Subject: Re: A Desparate Plea for Help... Message-ID: <XFMail.970428212111.Shimon@i-Connect.Net> In-Reply-To: <199704290247.MAA18906@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Michael Smith; On 29-Apr-97 you wrote: ... > > > Are you loading/unloading LKM's on these systems? > > > > Yes. linux_mod, star_saver_mod, oss_mod (sound). > > Should I not? > > They're certainly prime suspects. Your crash looks/looked like it had > something to do with one of the device switch tables, and one possible > explanation would be that an LKM had been removed without zeroing > its switch entries. > > I have _definitely_ seen problems with the screensaver LKMs at times. > Make sure your LKMs are up to date with the kernel too. How do I do that (other than make world - which I am doing on a regular basis)? Yes, I have had severe problems with the screen savers, but they _seem_ fine now. They are not critical for this project. Not yet anyway. A prime suspect is the OSS driver, for which I have no sources. It is OFF. We may want to consider some mechanism to protect the system from LKM's blowing it up so easily. Like an unload function that will put a shorting plug in the interface, or something. I know nothing of FreeBSD LKM but in other O/S, I have seen the stubs being the default when the ``real thing'' is unplugged. I am sure we have something like that already. Another thing can be (again, if it is not there already) is a strict versioning option, which even linux has; It allows the kernel modules loader to verify that a given module is of the proper/matching version before loading. Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970428212111.Shimon>