From owner-freebsd-amd64@FreeBSD.ORG Mon May 19 15:01:02 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0F55106564A for ; Mon, 19 May 2008 15:01:02 +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 84BAE8FC18 for ; Mon, 19 May 2008 15:01:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 276F51A4D8B; Mon, 19 May 2008 08:01:02 -0700 (PDT) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 19 May 2008 10:10:36 -0400 User-Agent: KMail/1.9.7 References: <200805172352.m4HNquJA067685@freefall.freebsd.org> In-Reply-To: <200805172352.m4HNquJA067685@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805191010.36605.jhb@freebsd.org> Cc: matteo@freebsd.org Subject: Re: amd64/117186: [modules] kldload Unsupported file type on STABLE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 15:01:02 -0000 On Saturday 17 May 2008 07:52:56 pm matteo@freebsd.org wrote: > Synopsis: [modules] kldload Unsupported file type on STABLE amd64 > > State-Changed-From-To: open->feedback > State-Changed-By: matteo > State-Changed-When: Sab 17 Mag 2008 23:51:43 UTC > State-Changed-Why: > Sean, are you still able to reproduce this ? did you try newer FreeBSD > releases? Modules loading/unloading works just fine on my amd64. You will get the message. Specifically, sys/kern/link_elf.c will emit this message (because it can't handle an amd64 .ko) even though sys/kern/link_elf_obj.c will work ok. Basically, if link_elf.c tries the module first, you get this message. Since kernel object files are linked in alphabetical order, link_elf.c ends up always probing potential kernel modules first. -- John Baldwin