Date: Wed, 13 Apr 2005 11:32:16 +0800 From: "Gallagher, James" <james.gallagher@misys.com> To: "'freebsd-sparc64@freebsd.org'" <freebsd-sparc64@freebsd.org> Subject: hme0: couldn't establish interrupt (E250/after cvsup to RELENG_5) Message-ID: <A99171D862A6D511A8F700B0D0D1307F02ED34F0@singex2.misys.com>
next in thread | raw e-mail | index | archive | help
Hi, After following the 'hang at boot after makeworld on 5.3' at http://lists.freebsd.org/pipermail/freebsd-sparc64/2005-March/002867.html discussions I was wondering why I couldn't SSH onto the machine as had been suggested in that thread. After connecting on serial I discovered that the new kernel was having problems with hme0 (can't bring it up) The machine is an Enterprise 250, Ultra II, sun4u which I built from the 5.3 ISO last Friday. This is my first cvsup on the machine. Doing a grep hme0 on /var/log/messages gives me: Apr 13 02:39:01 sgfinmsg1 kernel: hme0: <Sun HME 10/100 Ethernet> mem 0x8000-0xf fff at device 1.1 on pci0 Apr 13 02:39:01 sgfinmsg1 kernel: miibus0: <MII bus> on hme0 Apr 13 02:39:01 sgfinmsg1 kernel: hme0: Ethernet address: 00:03:ba:02:41:d0 Apr 13 02:39:01 sgfinmsg1 kernel: hme0: couldn't establish interrupt Apr 13 02:39:01 sgfinmsg1 kernel: device_attach: hme0 attach returned 22 The only mention in dmesg.today of hme0 is: 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: 00:03:ba:02:41:d0 hme0: if_start running deferred for Giant hme0: [GIANT-LOCKED] I had a look on Google and at the archives for this list, but nothing leaps out at me. Any thoughts or info I've left out? Regards, James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A99171D862A6D511A8F700B0D0D1307F02ED34F0>