From owner-freebsd-bugs Sun Nov 28 4: 0:44 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A6F83156DC for ; Sun, 28 Nov 1999 04:00:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id EAA61707; Sun, 28 Nov 1999 04:00:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 28 Nov 1999 04:00:01 -0800 (PST) Message-Id: <199911281200.EAA61707@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Wemm Subject: Re: kern/15057: loading a kld module with a unresolved symbol crashes Reply-To: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15057; it has been noted by GNATS. From: Peter Wemm To: assar@stacken.kth.se Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/15057: loading a kld module with a unresolved symbol crashes Date: Sun, 28 Nov 1999 19:52:40 +0800 assar@stacken.kth.se wrote: > >Number: 15057 > >Category: kern > >Synopsis: loading a kld module with a unresolved symbol crashes > > This bug was fixed for -current in kern_module.c:1.18. The original > PR seems to have been lost, 1179 (the number mentioned in the CVS log) > is another unrelated PR and I've been unable to find the real PR. > > This fix has been in current for some time and I think it can safely > be MFC-ed to stable. And it's also quite annoying to have the kernel > crash just because it can't load a module. The 1.18 fix was for a different problem and I don't see how it's applicable to this case. newmod->file is set unconditionally when loaded. Can you give me some more information please? Such as a traceback showing where the crash is? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message