From owner-freebsd-stable@FreeBSD.ORG Wed Jan 30 14:23:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DCAA16A56A for ; Wed, 30 Jan 2008 14:23:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6527C13C4F6 for ; Wed, 30 Jan 2008 14:23:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id E47F21A4D83; Wed, 30 Jan 2008 06:23:00 -0800 (PST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 30 Jan 2008 09:04:35 -0500 User-Agent: KMail/1.9.7 References: <479FE898.1030801@incunabulum.net> <200801301651.07643.doconnor@gsoft.com.au> In-Reply-To: <200801301651.07643.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801300904.35750.jhb@freebsd.org> Cc: Bruce M Simpson Subject: Re: kldload: Unsupported file type X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2008 14:23:01 -0000 On Wednesday 30 January 2008 01:21:06 am Daniel O'Connor wrote: > On Wed, 30 Jan 2008, Bruce M Simpson wrote: > > Since updating to 6.3-RELEASE on two machines I see this message a > > lot. > > Hooray I am not alone! > I have a thread in stable called ' kldstat causes kernel to print odd > message' (not the best subject since it's wrong AND undescriptive), > message ID is 200801171410.38488.doconnor@gsoft.com.au. > > > It is printed whenever a kernel module is loaded. > > The modules load OK. Nothing special or different about them. > > > > It seems to be harmless, but any idea why it's started happening > > since the release? > > It is printed by sys/kern/link_elf.c - amd64 uses this for historical > reasons. > > The issue is that it is being called before the stuff in link_elf_obj.c > and printing an error, the kernel then tries _obj and it works. > > I tried #ifdef'ing out link_elf.c but it panicd my machine on boot and I > haven't had time to find out why. The kernel is a link_elf type object I believe, so you have to have it. -- John Baldwin