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. Regards, Jack -----Original Message----- From: TAKAHASHI Yoshihiro [mailto:n...@freebsd.org] Sent: Friday, January 07, 2011 7:40 PM To: jfvo...@gmail.com Cc: freebsd-...@freebsd.org; freebsd-stable@freebsd.org; Vogel, Jack Subject: Re: Supermicro Bladeserver In article <aanlktinkcvjy19nxwon_hfngae9etebtpg=szff2w...@mail.gmail.com> Jack Vogel <jfvo...@gmail.com> writes: > I am trying to track down a problem being experienced at icir.org using > SuperMicro > 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. e...@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 <n...@freebsd.org> _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
