Date: Wed, 21 Jul 2010 11:18:46 -0700 From: Pyun YongHyeon <pyunyh@gmail.com> To: Kurt Jaeger <pi@opsec.eu> Cc: fbsd-pr@opsec.eu, freebsd-net@FreeBSD.org, yongari@FreeBSD.org Subject: Re: kern/148772: [alc] alc0 does not send/receive packets if not plugged in during boot Message-ID: <20100721181846.GB10798@michelle.cdnetworks.com> In-Reply-To: <20100721170605.GG51934@home.opsec.eu> References: <201007202234.o6KMY7oV031115@freefall.freebsd.org> <20100721062945.GA51934@home.opsec.eu> <20100721063234.GB51934@home.opsec.eu> <20100721170201.GA10798@michelle.cdnetworks.com> <20100721170605.GG51934@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 21, 2010 at 07:06:05PM +0200, Kurt Jaeger wrote: > Hi! > > > > > A reboot with connected cable follows this evening. > > > > > > A reboot with connected cable was booting successfully. > > > Would you show me verbose dmesg output? > > With verbose boot alc(4) will show additional information which may > > help to narrow down the issue. > > http://opsec.eu/backup/alc-bug/dmesg.boot-verbose > One odd thing is alc(4) failed to read station address from EEPROM. So alc(4) assumed BIOS correctly programmed station address but the station address looks wrong to me. How about cold booting? Does other OS also report the same station address? > with the patch applied (and booted with a cable). > > Before the patch: > > http://opsec.eu/backup/alc-bug/dmesg.boot > Would you try this one? http://people.freebsd.org/~yongari/alc/alc.link.patch2 > Thanks! If you need remote access... That does not work mainly because I can't unplug/plug UTP cable through remote access.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100721181846.GB10798>