From owner-freebsd-i386@FreeBSD.ORG Mon Nov 27 16:31:21 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C251516A494 for ; Mon, 27 Nov 2006 16:31:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 298B543D77 for ; Mon, 27 Nov 2006 16:29:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kARGUSKn051948 for ; Mon, 27 Nov 2006 16:30:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kARGUSGh051947; Mon, 27 Nov 2006 16:30:28 GMT (envelope-from gnats) Date: Mon, 27 Nov 2006 16:30:28 GMT Message-Id: <200611271630.kARGUSGh051947@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Gleb Smirnoff Cc: Subject: Re: i386/105708: em driver failed to initialize on thinkpad X60 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gleb Smirnoff List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2006 16:31:21 -0000 The following reply was made to PR i386/105708; it has been noted by GNATS. From: Gleb Smirnoff To: bug-followup@FreeBSD.org Cc: Subject: Re: i386/105708: em driver failed to initialize on thinkpad X60 Date: Mon, 27 Nov 2006 19:23:52 +0300 On Mon, Nov 27, 2006 at 06:55:12PM +0300, Ruslan Ermilov wrote: R> > From: Ko Nonomura R> > To: bug-followup@FreeBSD.org, nonomura@nifty.com R> > Cc: R> > Subject: Re: i386/105708: em driver failed to initialize on thinkpad X60 R> > Date: Mon, 27 Nov 2006 23:12:06 +0900 R> > R> > putting R> > hw.pci.allow_unsupported_io_range="1" R> > R> > to R> > /boot/loader.conf solves the issue. R> > R> > Please close the case. R> > R> I doubt it. hw.pci.allow_unsupported_io_range never existed in RELENG_6, R> and now also doesn't exist in HEAD. I think you're just lucky as Gleb; R> sometimes it just boots. :-) Yes. In my case the problem disappeared after several (three, I guess) reboots. Now I have 7-CURRENT installed on this notebook and em(4) works w/o warnings. However, network is bit laggy. So, I guess, hw.pci.allow_unsupported_io_range did nothing for you, and em(4) had fixed due to same magic as in mine case :| -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE