em(4) on FreeBSD is sometimes annoying

[Jack Vogel]

OK, so your EEPROM is does not have the bug. As I was
saying before, I would like to see what back to back behavior is.

And, BTW, back to back does NOT mean hook to the switch,
that's the very thing that is suspicious. It means NIC to NIC,
no DHCP, assigned addresses.  And then see that you pass
traffic, and then unhook cable, see if link goes down, reconnect
and it should go up.

Oh, and exactly what kernel, and driver revision are you using.

Jack


On Mon, Aug 4, 2008 at 11:52 AM, Martin <nakal at web.de> wrote:
> On Mon, 04 Aug 2008 09:35:21 -0800
> Royce Williams <royce at alaska.net> wrote:
>
>> Jack Vogel wrote, on 8/4/2008 9:18 AM:
>> > The focus here on the laptop distracted me, but someone else at work
>> > reminded me. Its very important that you run the EEPROM fix for
>> > the 82573 that i posted a long while back, search in email archive
>> > for it. Its a DOS executable that will patch your EEPROM.
>> >
>> > I am not sure if the Lenova's need it, but get it, run it, and then
>> > see if your problem goes away.
>>
>> Martin, there's also a link to it from Jeremy's "Commonly Reported
>> Issues" page:
>>
>> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues
>>
>> Look for "DOS-based EEPROM".
>
> Hi Royce,
>
> thank you for the link. I've read this issue description and I'm not
> sure if it helps. I don't have any "watchdog timeouts" and my EEPROM
> data looks clean:
>
> Interface EEPROM Dump:
> Offset
> 0x0000  xxxx xxxx xxxx xxxx xxxx xxxx ffff ffff
> 0x0010  0053 0103 026b 2001 17aa 109a 8086 80df
> 0x0020  0000 2000 7e54 0000 0014 00da 0004 2700
> 0x0030  6cc9 3150 073e 040b 298b 0000 f000 0f02
>
> (I masked out the MAC address)
>
> --
> Martin
>