jack.vogel at intel.com
Mon Jan 10 21:45:54 UTC 2011
We attempted to repro this problem with the 82566DM (ich8 btw) in house and failed, it worked correctly for my testers.
Oh, and just so the mailing lists have an update, the SM Blade problem was not an issue in the driver, it was a local change in the loader.conf that caused the problem.
From: TAKAHASHI Yoshihiro [mailto:nyan at FreeBSD.org]
Sent: Friday, January 07, 2011 7:40 PM
To: jfvogel at gmail.com
Cc: freebsd-net at freebsd.org; freebsd-stable at freebsd.org; Vogel, Jack
Subject: Re: Supermicro Bladeserver
In article <AANLkTinkCvJy19NxWoN_hfNgae9ETEBtpG=szFf2WZT2 at mail.gmail.com>
Jack Vogel <jfvogel at gmail.com> writes:
> I am trying to track down a problem being experienced at icir.org using
> bladeservers, the SERDES 82575 interfaces are having connectivity or perhaps
> autoneg problems, resulting in link transitions and watchdog resets.
> The closest hardware my org at Intel has is a Fujitsu server who's blades
> also have
> this device, but testing on that has failed to repro the problem.
> I was wondering if anyone else out there has this hardware, if so could you
> let me
> know your experience, have you had problems or not, etc etc?
My machine has the following em(4) device and it has a autoneg
problem. When I was using 8-stable kernel at 2010/11/01, it has no
problem. But I update to 8-stable at 2010/12/01, the kernel is only
linked up as 10M.
em0 at pci0:0:25:0: class=0x020000 card=0x13d510cf chip=0x104a8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82566DM Gigabit Network Connection'
class = network
subclass = ethernet
TAKAHASHI Yoshihiro <nyan at FreeBSD.org>
More information about the freebsd-stable