From owner-freebsd-sparc64@FreeBSD.ORG Mon Oct 31 17:40:18 2005 Return-Path: X-Original-To: freebsd-sparc64@hub.freebsd.org Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 025E916A41F for ; Mon, 31 Oct 2005 17:40:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF5C143D45 for ; Mon, 31 Oct 2005 17:40:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VHeHMd011115 for ; Mon, 31 Oct 2005 17:40:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9VHeHLu011108; Mon, 31 Oct 2005 17:40:17 GMT (envelope-from gnats) Date: Mon, 31 Oct 2005 17:40:17 GMT Message-Id: <200510311740.j9VHeHLu011108@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/88279: Hme driver. Failure to initialize onboard NA on Sun Enterprise 250 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:40:18 -0000 The following reply was made to PR sparc64/88279; it has been noted by GNATS. From: Marius Strobl To: =?iso-8859-1?Q?Simon_Rig=E9t?= Cc: freebsd-gnats-submit@freebsd.org Subject: Re: sparc64/88279: Hme driver. Failure to initialize onboard NA on Sun Enterprise 250 Date: Mon, 31 Oct 2005 18:34:33 +0100 On Mon, Oct 31, 2005 at 04:49:04PM +0000, Simon Rigét wrote: > > >Description: > The driver for hme fails to initialize the build in network adapter, on boot, with the following messages: > > hme0: mem 0x8000-0xffff at device 1.1 on pci0 > miibus0: on hme0 > nsphy0: on miibus0 > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > hme0: Ethernet address: 08:00:20:e6:87:de > hme0: couldn't establish interrupt > The underlying problem is an incorrect entry for the second on-board UART in the interrupt map provided by the firmware which further down the road causes hme(4) to fail to attach to the on-board HME. 6.0-RELEASE will contain a hack to work around the problem (already part of RELENG_6 and RELENG_6_0) and a proper solution is being worked on. > there is also this: > > stray vector interrupt 2029 > > Which I suspect is related. That's the interrupt of the second timer embedded in the Host-PCI bridge which is set up by the firmware and typically fires before FreeBSD can disable it. Read: unrelated and harmless. Marius -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details.