> As a more general question, what would be the right medium to
> document such device errata as it relates to a driver? Is the
> man page the best location or would it be better to add a
> table near the top of the driver file which summarizes the
> bugs and the workarounds? Is there a general
David Christensen wrote:
MSI is broken on this device (actually all PCI/PCI-X devices in the
57XX family). The interrupt will be asserted as expected
but masking
the interrupt does not work. For those newer 1Gb PCIe
devices that do
work correctly with MSI, only a single message is actually
> > MSI is broken on this device (actually all PCI/PCI-X devices in the
> > 57XX family). The interrupt will be asserted as expected
> but masking
> > the interrupt does not work. For those newer 1Gb PCIe
> devices that do
> > work correctly with MSI, only a single message is actually
> sup
Got it. Thanks.
-Boris
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On Fri, Dec 04, 2009 at 12:22:13PM -0800, Pyun YongHyeon wrote:
> On Fri, Dec 04, 2009 at 11:13:03PM +0300, Igor Sysoev wrote:
> > On Fri, Dec 04, 2009 at 11:51:40AM -0800, Pyun YongHyeon wrote:
> >
> > > On Fri, Dec 04, 2009 at 10:11:14PM +0300, Igor Sysoev wrote:
> > > > On Fri, Dec 04, 2009 at
Synopsis: [em] hangs down/up intel nic during creating vlan
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Dec 8 17:32:07 UTC 2009
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=1412
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Boris Kochergin wrote:
> Ahoy. I have an 8.0-RELEASE/i386 machine (installed clean from the CD,
> so no kernel/world mismatches are possible) on which I am trying to add
> a tun device to a bridge:
>
> # ifconfig tun0 create
> # ifconfig bridge0 creat
2009/12/8 Bruce Simpson :
> The only other thing I can think of is: is this an igmpproxy issue, ie. is
> the IGMP traffic which is causing problems, coming from igmpproxy itself?
That's possible.
> The kernel never generates IGMP control traffic related to routing. Any IGMP
> traffic generated by
Andriy Syrovenko wrote:
Perhaps Florian can shed some light on your IGMP issue? igmpproxy only
understands IGMPv2, afaik.
Yep, it is igmp v2 only indeed.
The only other thing I can think of is: is this an igmpproxy issue, ie.
is the IGMP traffic which is causing problems, coming from
2009/12/8 Bruce Simpson :
> Andriy Syrovenko wrote:
>>
>> I have switched to 8-STABLE. Kernel does not seem to crash anymore,
>> however IGMP still does not work. tcpdump complains that outgoing IGMP
>> report and leave packets have incorrect checksum- it is always 0.
>> Though I'm not sure weather
Andriy Syrovenko wrote:
I have switched to 8-STABLE. Kernel does not seem to crash anymore,
however IGMP still does not work. tcpdump complains that outgoing IGMP
report and leave packets have incorrect checksum- it is always 0.
Though I'm not sure weather it is IGMP checksum or IP checksum that
Hi
Looks like now it is required to add 'inet ' prefix to ifconfig lines,
for os <= 8.0 it was not required, although
corrected line:
ifconfig_lo0_alias0="inet 127.0.0.2/32"
> After upgrade RELENG_8 -> 9-CURRENT following line in rc.con does not
> work any more for me. (after boot no alias a
I have switched to 8-STABLE. Kernel does not seem to crash anymore,
however IGMP still does not work. tcpdump complains that outgoing IGMP
report and leave packets have incorrect checksum- it is always 0.
Though I'm not sure weather it is IGMP checksum or IP checksum that is
incorrect.
2009/12/7 B
13 matches
Mail list logo
