sparc64/88279: Hme driver. Failure to initialize onboard NA on
Sun Enterprise 250
marius at alchemy.franken.de
Mon Oct 31 09:40:18 PST 2005
The following reply was made to PR sparc64/88279; it has been noted by GNATS.
From: Marius Strobl <marius at alchemy.franken.de>
To: =?iso-8859-1?Q?Simon_Rig=E9t?= <s1 at paragi.dk>
Cc: freebsd-gnats-submit at 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:
> The driver for hme fails to initialize the build in network adapter, on boot, with the following messages:
> hme0: <Sun HME 10/100 Ethernet> mem 0x8000-0xffff at device 1.1 on pci0
> miibus0: <MII bus> on hme0
> nsphy0: <DP83840 10/100 media interface> 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
> 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.
This mail was scanned by AntiVir Milter.
This product is licensed for non-commercial use.
See www.antivir.de for details.
More information about the freebsd-sparc64