https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #17 from Kubilay Kocak ---
(In reply to Eugene Grosbein from comment #14)
The initial report is fine to be classified against the port. Once the root
cause(s) is confirmed, implicated or identified, a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
Borja Marcos changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208343
Warren Block changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #19 from Cassiano Peixoto ---
Comment on attachment 175989
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175989
crash-bt
I'm having random crashes. BT attached.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
Cassiano Peixoto changed:
What|Removed |Added
CC|
Hi Kubilay,
Yes, i think all issues are related with this one. I already attached many
info about these crashes there, but looks like nobody cares about it.
This PR is assigned to Ermal, but he's not working on it because his last
PR change was in January.
If you or someone else is interested
On 10/19/16 11:25, Hans Petter Selasky wrote:
>
> Hi,
>
> Search the idVendor and idProduct values in the Linux kernel. I think you
> need to implement some propritary miibus to
> get it working. CDC ethernet does not define any miibus.
>
> --HPS
>
Thank you for the quick response.
Do you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #9 from Kristjan ---
ifconfig -m bxe0
bxe0: flags=8843 metric 0 mtu 1500
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #10 from Borja Marcos ---
And what if you try to mess with the options?
Try this:
ifconfig bxe0 -rxcsum
ifconfig bxe1 -rxcsum
I'm just wondering, maybe by doing that you can coerce the driver to complete