freebsd-net Digest, Vol 366, Issue 7
freebsd-n...@freebsd.org
freeb...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-net
or, via email, send a message with subject or body 'help' to
freebsd-n...@freebsd.org
You can reach the person managing the list at
freebsd-...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-net digest..."
Today's Topics:
1. Re: kern/144560: [mld] [patch] mld sends packets to wrong
destination with a bad checksum (b...@FreeBSD.org)
2. Re: kern/122839: [em] FreeBSD 7 multicast routing problem
(b...@FreeBSD.org)
3. Re: bin/126822: wpa_supplicant(8): WPA PSK does not work in
adhoc mode. (bsch...@FreeBSD.org)
4. Re: Broadcom BCM5701 / HP NC6770 (Pyun YongHyeon)
5. Re: Broadcom BCM5701 / HP NC6770
(Erich Jenkins, Fuujin Group Ltd)
6. Re: Broadcom BCM5701 / HP NC6770
(Erich Jenkins, Fuujin Group Ltd)
----------------------------------------------------------------------
Message: 1
Date: Sat, 10 Apr 2010 12:04:39 GMT
From: b...@FreeBSD.org
Subject: Re: kern/144560: [mld] [patch] mld sends packets to wrong
destination with a bad checksum
To: b...@FreeBSD.org, freeb...@FreeBSD.org, b...@FreeBSD.org
Message-ID: <201004101204....@freefall.freebsd.org>
Synopsis: [mld] [patch] mld sends packets to wrong destination with a bad checksum
Responsible-Changed-From-To: freebsd-net->bms
Responsible-Changed-By: bms
Responsible-Changed-When: Sat 10 Apr 2010 12:03:56 UTC
Responsible-Changed-Why:
take this
http://www.freebsd.org/cgi/query-pr.cgi?pr=144560
------------------------------
Message: 2
Date: Sat, 10 Apr 2010 12:08:49 GMT
From: b...@FreeBSD.org
Subject: Re: kern/122839: [em] FreeBSD 7 multicast routing problem
To: 4...@legis.krsn.ru, b...@FreeBSD.org, freeb...@FreeBSD.org,
b...@FreeBSD.org
Message-ID: <201004101208....@freefall.freebsd.org>
Synopsis: [em] FreeBSD 7 multicast routing problem
State-Changed-From-To: feedback->closed
State-Changed-By: bms
State-Changed-When: Sat 10 Apr 2010 12:07:35 UTC
State-Changed-Why:
Timeout on feedback. I believe yongari has merged driver fixes where
relevant to this issue.
Responsible-Changed-From-To: freebsd-net->bms
Responsible-Changed-By: bms
Responsible-Changed-When: Sat 10 Apr 2010 12:07:35 UTC
Responsible-Changed-Why:
take this
http://www.freebsd.org/cgi/query-pr.cgi?pr=122839
------------------------------
Message: 3
Date: Sat, 10 Apr 2010 14:05:31 GMT
From: bsch...@FreeBSD.org
Subject: Re: bin/126822: wpa_supplicant(8): WPA PSK does not work in
adhoc mode.
To: bsch...@FreeBSD.org, freeb...@FreeBSD.org,
bsch...@FreeBSD.org
Message-ID: <201004101405....@freefall.freebsd.org>
Synopsis: wpa_supplicant(8): WPA PSK does not work in adhoc mode.
Responsible-Changed-From-To: freebsd-net->bschmidt
Responsible-Changed-By: bschmidt
Responsible-Changed-When: Sat Apr 10 14:05:01 UTC 2010
Responsible-Changed-Why:
mine.
http://www.freebsd.org/cgi/query-pr.cgi?pr=126822
------------------------------
Message: 4
Date: Sat, 10 Apr 2010 14:25:20 -0700
From: Pyun YongHyeon <pyu...@gmail.com>
Subject: Re: Broadcom BCM5701 / HP NC6770
To: "Erich Jenkins, Fuujin Group Ltd" <er...@fuujingroup.com>
Cc: freeb...@freebsd.org, Evgenii Davidov <da...@korolev-net.ru>
Message-ID: <2010041021...@michelle.cdnetworks.com>
Content-Type: text/plain; charset="utf-8"
On Sat, Apr 10, 2010 at 12:13:07AM -0600, Erich Jenkins, Fuujin Group Ltd wrote:
> Pyun YongHyeon wrote:
> >On Fri, Apr 09, 2010 at 02:13:00AM -0600, Erich Jenkins, Fuujin Group Ltd
> >wrote:
> >>Evgenii Davidov wrote:
> >>>Здравствуйте,
> >>>
> >>>On Fri, Apr 09, 2010 at 01:39:16AM -0600, Erich Jenkins, Fuujin Group
> >>>Ltd пишет:
> >>>
> >>>>We were previously running 5.3 on this box (I know, VERY old), but
> >>>>never had a problem. The link now fails to come up. I've tried forcing
> >>>>the port out of auto (media 1000baseSX mediaopt full-duplex) and as
> >>>>long as the port doesn't have an IP assigned via rc.conf on system
> >>>>boot, I can get the switch to see it (Cisco 6505), but no traffic to
> >>>>flow. I've checked all the obvious things (duplex setting on switch,
> >>>>cable failure, etc.), all to no avail. I fiddled with the knobs in the
> >>>>driver (rxcsum, vlan_mtu, etc) with no changes either.
> >>>sorry for silly ansver but is your interface UP ? (ifconfig bge0 up)
> >>>
> >>Actually, I was silly for not mentioning that in the original post, but
> >>yes, it's up. I've even tried up/down/up on the card a few times after
> >>fiddling with the driver knobs, but the same thing happened, no link on
> >>the switch.
> >>
> >>I've also tested this back-to-back with two machines and the same cards.
> >>Same result: no transmission of data. Interestingly enough, the link
> >>lite is lit on the cards (in back-to-back) and on the card but not the
> >>switch. Not sure if that's significant or not. In the interest if
> >>completeness, here's ifconfig output for that card:
> >>
> >>bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
> >> ether 00:08:02:28:76:4d
> >> inet 10.222.222.144 netmask 0xffffff00 broadcast 10.222.222.255
> >> media: Ethernet 1000baseSX <full-duplex>
> >> status: active
> >>
> >>I also verified the MTU size to ensure the switch ports weren't
> >>configured for jumbo frames. They are correctly set on the switch and on
> >>the FreeBSD box, but no traffic flows.
> >>
> >
> >Would you try booting to latest 7.3-RELEASE and check whether you
> >still see the issue?
> >If you see the same issue please show me verbose boot message of
> >bge(4) and its PHY driver.
> >_______________________________________________
> >freeb...@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-net
> >To unsubscribe, send any mail to "freebsd-net...@freebsd.org"
>
> Just finished the install, and ended up with the same result. I
> installed OpenBSD on this box just to be sure there wasn't something
> unrelated to the driver causing the issue. OpenBSD works fine.
>
> Where to from here?
>
It seems there is async link state change issue for BCM5701 TBI
case. Link state handling is one of the most complex thing in
bge(4) so I'm not sure whether attached patch is right thing.
Public data sheet seems to indicate bit 0 of BGE_MI_STS should be
set to enable link to the MAC state machine if autopolling is
disabled so resetting the bit to 0 does not look right to me.
Try attached patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bge.5701.diff
Type: text/x-diff
Size: 476 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20100410/cf77de59/bge.5701-0001.bin
------------------------------
Message: 5
Date: Sat, 10 Apr 2010 19:06:31 -0600
From: "Erich Jenkins, Fuujin Group Ltd" <er...@fuujingroup.com>
Subject: Re: Broadcom BCM5701 / HP NC6770
To: pyu...@gmail.com
Cc: freeb...@freebsd.org, Evgenii Davidov <da...@korolev-net.ru>
Message-ID: <4BC12097...@fuujingroup.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Pyun YongHyeon wrote:
> On Sat, Apr 10, 2010 at 12:13:07AM -0600, Erich Jenkins, Fuujin Group Ltd wrote:
>> Pyun YongHyeon wrote:
>>> On Fri, Apr 09, 2010 at 02:13:00AM -0600, Erich Jenkins, Fuujin Group Ltd
>>> wrote:
>>>> Evgenii Davidov wrote:
>>>>> ????????????,
>>>>>
>>>>> On Fri, Apr 09, 2010 at 01:39:16AM -0600, Erich Jenkins, Fuujin Group
>>>>> Ltd ?????:
>>>>>
>>>>>> We were previously running 5.3 on this box (I know, VERY old), but
>>>>>> never had a problem. The link now fails to come up. I've tried forcing
>>>>>> the port out of auto (media 1000baseSX mediaopt full-duplex) and as
>>>>>> long as the port doesn't have an IP assigned via rc.conf on system
>>>>>> boot, I can get the switch to see it (Cisco 6505), but no traffic to
>>>>>> flow. I've checked all the obvious things (duplex setting on switch,
>>>>>> cable failure, etc.), all to no avail. I fiddled with the knobs in the
>>>>>> driver (rxcsum, vlan_mtu, etc) with no changes either.
>>>>> sorry for silly ansver but is your interface UP ? (ifconfig bge0 up)
>>>>>
>>>> Actually, I was silly for not mentioning that in the original post, but
>>>> yes, it's up. I've even tried up/down/up on the card a few times after
>>>> fiddling with the driver knobs, but the same thing happened, no link on
>>>> the switch.
>>>>
>>>> I've also tested this back-to-back with two machines and the same cards.
>>>> Same result: no transmission of data. Interestingly enough, the link
>>>> lite is lit on the cards (in back-to-back) and on the card but not the
>>>> switch. Not sure if that's significant or not. In the interest if
>>>> completeness, here's ifconfig output for that card:
>>>>
>>>> bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>>>> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>>>> ether 00:08:02:28:76:4d
>>>> inet 10.222.222.144 netmask 0xffffff00 broadcast 10.222.222.255
>>>> media: Ethernet 1000baseSX <full-duplex>
>>>> status: active
>>>>
>>>> I also verified the MTU size to ensure the switch ports weren't
>>>> configured for jumbo frames. They are correctly set on the switch and on
>>>> the FreeBSD box, but no traffic flows.
>>>>
>>> Would you try booting to latest 7.3-RELEASE and check whether you
>>> still see the issue?
>>> If you see the same issue please show me verbose boot message of
>>> bge(4) and its PHY driver.
>>> _______________________________________________
>>> freeb...@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>> To unsubscribe, send any mail to "freebsd-net...@freebsd.org"
>> Just finished the install, and ended up with the same result. I
>> installed OpenBSD on this box just to be sure there wasn't something
>> unrelated to the driver causing the issue. OpenBSD works fine.
>>
>> Where to from here?
>>
>
> It seems there is async link state change issue for BCM5701 TBI
> case. Link state handling is one of the most complex thing in
> bge(4) so I'm not sure whether attached patch is right thing.
> Public data sheet seems to indicate bit 0 of BGE_MI_STS should be
> set to enable link to the MAC state machine if autopolling is
> disabled so resetting the bit to 0 does not look right to me.
> Try attached patch.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net...@freebsd.org"
Thanks for the patch, but I'm sorry to report there is no change.
Erich M. Jenkins
Fuujin Group Limited
"You should never, never doubt what no one is sure about."
-- Gene Wilder
------------------------------
Message: 6
Date: Sun, 11 Apr 2010 03:15:16 -0600
From: "Erich Jenkins, Fuujin Group Ltd" <er...@fuujingroup.com>
Subject: Re: Broadcom BCM5701 / HP NC6770
To: pyu...@gmail.com
Cc: freeb...@freebsd.org, Evgenii Davidov <da...@korolev-net.ru>
Message-ID: <4BC19324...@fuujingroup.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I've been muddling around in src/sys/dev on the old system and the new
system and there appear to be rather major changes to MII and bge,
possibly the whole stack?
There are a number of things that seem to have been merged with other
parts of the network stack, or perhaps written into the individual
drivers (someone working on the net stack would have to verify that).
For instance, some files called in 5.3-REL seem to have gone away
completely, and in the new (unpatched) version of if_bge.c under
7.3-REL, calls to these modules are gone:
- #include <vm/vm.h> /* for vtophys */
- #include <vm/pmap.h> /* for vtophys */
- #include <machine/clock.h> /* for DELAY */
- #include <machine/bus_memio.h>
- #include <dev/pci/pcireg.h> (called but something changed in here)
- #include <dev/pci/pcivar.h> (ditto above)
It appears that the checksum features have been completely rewritten,
and some of the ring settings have changed. It's interesting that the
driver only fills 256 of the rx rings in the hopes that the cpu is "fast
enough to keep up with the NIC". Would a subroutine here to grab the cpu
clock and count (number of procs/pipelines) be more trouble than it's
worth to "automagically" increase the number of rx rings the driver
fills based on the system in which it's installed?
Something also changed in pci/pcireg.h and pci/pcivar.h, but I haven't
had the time to hunt down and expand the source tree from the 5.3-REL
branch yet.
I have other machines with copper nics utilizing the bge driver, and
there are no issues at all. Perhaps I'm getting ahead of things, but
since this seems to have been broken through several releases, would it
make any sense to split the support between the BCM5701KHB chipset and
the more recent BCM chipset to avoid causing issues with cards/systems
not currently experiencing troubles?
Erich M. Jenkins
Fuujin Group Limited
"You should never, never doubt what no one is sure about."
-- Gene Wilder
------------------------------
End of freebsd-net Digest, Vol 366, Issue 7
*******************************************