Date: Mon, 12 Jul 2004 16:47:37 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: John Polstra <jdp@polstra.com> Cc: freebsd-current@freebsd.org Subject: Re: kldload won't load Message-ID: <Pine.NEB.3.96L.1040712164608.52015D-100000@fledge.watson.org> In-Reply-To: <XFMail.20040712133036.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Jul 2004, John Polstra wrote: > > When a kernel module doesn't load correctly, this is your cue to > > run "dmesg" and look at the messages printed in the kernel message > > buffer. That will tell you why it didn't load. Of course, nobody > > ever remembers this, and apparently running xconsole is no longer > > in vogue. > > > > This needs to be a FAQ. > > No, it needs to be fixed. It's printing a totally incorrect error > message, and nobody should have to use dmesg to find out what's really > happened. Well, the problem here is that the errno error-reporting mechanism can report but not describe errors. We could add a new EKLDLINKER to point at a linker error (or the like), or a whole set of new errnos, but the mechanism even then couldn't report which symbols are missing, etc. One or more linker-specific error values would probably be a useful start. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040712164608.52015D-100000>