https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #12 from Stephan Neuhaus ---
Created attachment 195139
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195139&action=edit
DCHPOFFER for recalcitrant bge0
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #13 from Stephan Neuhaus ---
I reply to Eugene Grosbein from comment #8
I've attached a pcap containing the DHCPOFFER. I've also dropped into a shell
from the installer. The interface name is indeed bge0 and this is what i see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #14 from Stephan Neuhaus ---
Attribution on comment #13 is wrong. Should be comment #9 instead. Sorry.
--
You are receiving this mail because:
You are the assignee for the bug.
___
f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #15 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #13)
It seems your box does not really receive a reply from DHCP server despite it
is being sent. Please verify this by entering shell again and running com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #16 from Stephan Neuhaus ---
Replying to comment #15
Yep, you're right, no DHCPOFFER seen by the NIC.
Here is what I see. (Possibility of slight typos as I'm typing this by hand.)
One thing I find odd is that the interface has
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428
--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:
Author: marius
Date: Sun Jul 15 19:04:26 UTC 2018
New revision: 336313
URL: https://svnweb.freebsd.org/changeset/base/336313
Log:
Assorted TSO fixes for em(4)
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Eugene Grosbein changed:
What|Removed |Added
Summary|On install, Broadcom|bge watchdog timeout with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #18 from Eugene Grosbein ---
OTOH, you should first try with "set dev.bge.0.msi=0" instead of disabling
hw.pci.enable_msi/hw.pci.enable_msix. This way, you only disable MSI for bge
and not for all other drivers in the system.
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #19 from Stephan Neuhaus ---
Now I get
# killall dhclient
No matching processes were found
# dhclient bge0
DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 8
DH
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Stephan Neuhaus changed:
What|Removed |Added
Summary|bge watchdog timeout with |bge watchdog timeout with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Eugene Grosbein changed:
What|Removed |Added
Status|New |Open
--- Comment #20 from Eugene
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #21 from Stephan Neuhaus ---
(Replying to Eugene Grosbein from comment #20)
Yup, that did it. I now have a working install, even though there is a
speedbump when bge0 is activated on boot: the switch shows only 100 MBit/s
initi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #22 from Stephan Neuhaus ---
Replying to my own comment #21
If you can spare the time, could you explain to me what the "bge watchdog"
does?
But anyway, thanks a lot for walking this newbie through a difficult process,
with cl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #23 from Eugene Grosbein ---
Created attachment 195169
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195169&action=edit
proposed fix
Attached patch disables MSI for this revision of the NIC.
Stephan, could you plea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #24 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #22)
"watchdog timeout" is an indication of some unexpected interrupt processing
problem. I do not know anything about Broadcom's chip internals, sorry.
--
16 matches
Mail list logo
