On Tue, Jan 22, 2008 at 03:49:05PM -0800, Jack Vogel wrote:
> On Jan 22, 2008 9:40 AM, Patrick Oeschger <[EMAIL PROTECTED]> wrote:
> > maybe i found two issues which are em(4) related...
> > i tested the 6.3-RELEASE on a appliance which has two on-board SFP slots
> > chi
maybe i found two issues which are em(4) related...
i tested the 6.3-RELEASE on a appliance which has two on-board SFP slots
chipset: i82571eb (serdes with tbi-interface)
[EMAIL PROTECTED]:0:0: class=0x02 card=0x10761903 chip=0x10608086
rev=0x06 hdr=0x00
[EMAIL PROTECTED]:0:1: class=0x0200
OK - found the problem
the driver in 6.2-RELEASE has different code in em_identify_hardware
my hardware needs the memory access and bus master bits getting set by
the driver
beginning with 6.2-RELEASE this gets only set if PCIM_CMD_BUSMASTEREN is
*not set* and PCIM_CMD_MEMEN is *set* - it seems the
thanks for your feedback jack - i tried the MSI stuff as first task this
morning
the interface init'ed without a problem and did not complain about MSI
what i like most is that no IRQ is assigned now, everything seems to get
handled in a TASKQ (IRQs were quite weird sometimes when having a bunch of
bug description for 7.0-CURRENT - em(4) driver version 6.5.3
- frame reception is not possible (missed packets counter incrementing)
- frame transmission is not possible (driver watchdog fires)
bug exists also on 6.2-RELENG - em(4) driver version 6.2.9
bug does *not* exist on 6.1-RELENG - em(4) dri
