https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #20 from Eugene Grosbein ---
(In reply to ricsip from comment #19)
Again, this is not igb(4) driver "broken", these are corresponding network
cards having no hardware support to distribute PPPoE traffic per-queue. This is
alrea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Eugene Grosbein changed:
What|Removed |Added
Resolution|FIXED |---
Hardware|amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #19 from ricsip ---
(In reply to Eugene Grosbein from comment #16)
Gents, if the igb (and any other NIC on the planet) is so fundamentally broken
for multi-queue + PPPoe, at least make this clear written in the drivers "Known
i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Stephan Neuhaus changed:
What|Removed |Added
Hardware|Any |amd64
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Stephan Neuhaus changed:
What|Removed |Added
Summary|bge watchdog timeout with |SOLVED: bge watchdog
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Stephan Neuhaus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #40 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #39)
Yes, you should. And thank you for your non-stop marathon testing despite of
all holes on the way :-)
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #39 from Stephan Neuhaus ---
Replying to Eugene Grosbein from comment #38
Success! The kernel built, I installed and rebooted, and now have a working
bge0. I still have hw.vga.textmode=1 in /boot/loader.conf, but that seems a
d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #18 from Vladimir ---
I think most people expect that igb hardware works the same way under FreeBSD
like it works under other OSes like Linux or whatever... Windows, I think this
pointed me also to think that it is driver proble
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #17 from Vladimir ---
Thanks, Eugene.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #16 from Eugene Grosbein ---
(In reply to Vladimir from comment #14)
I guess you can read Russian, please take a look at my post
https://dadv.livejournal.com/139170.html , it may make things clearer for you.
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #15 from Eugene Grosbein ---
(In reply to Vladimir from comment #14)
The problem is in hardware card not supporting PPPoE per-queue load
distribution, not in the driver. Why anyone would think that igb-supported NICs
are capabl
On Mon, 16 Jul 2018 a bug that doesn't want repl...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #37 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #35)
If this model does not support old BIOS-style boot mode, try using text mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #14 from Vladimir ---
If the problem is isolated to igb driver only, could it be igb driver problem,
no?
Why then there was patch for igb, that currently missing?
https://wiki.freebsd.org/NetworkPerformanceTuning (Traffic flow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225927
Kajetan Staszkiewicz changed:
What|Removed |Added
CC||veg...@tuxpowered.net
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #13 from Eugene Grosbein ---
(In reply to Jan Bramkamp from comment #12)
I'm not sure which lock you are talking of.
Anyway, the problem has nothing to do with igb driver as NICs supported by
igb(4) driver have no hardware sup
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #38 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #35)
Also, you can try redirect building output to a file to verify if this is video
console driver's problem:
make buildkernel >& /var/log/buildkernel.log
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #37 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #35)
If this model does not support old BIOS-style boot mode, try using text mode of
vt(4) driver:
echo hw.vga.textmode=1 >> /boot/loader.conf
instead of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #12 from Jan Bramkamp ---
I may work as intended, but that doesn't mean that it works well, because if I
remember correctly there is a single lock in each PPPoE instance as well so you
just moved the bottleneck a little bit up t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #35 from Stephan Neuhaus ---
(In reply to Eugene Grosbein in comment #34)
When I set kern.vty=sc, booting hangs after giving the EFI framebuffer
information:
EFI framebuffer information:
addr, size: 0xc001, 0x64
dimens
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #36 from Stephan Neuhaus ---
Wrong attribution in comment #35, should be comment #32, sorry.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #34 from Eugene Grosbein ---
(In reply to Rodney W. Grimes from comment #33)
Feel free to prepare a change for bge(4) manual page. I won't be doing it as
English is not my native language.
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
Eugene Grosbein changed:
What|Removed |Added
Resolution|--- |Works As Intended
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #11 from Eugene Grosbein ---
There seems to be common mis-understanging in how hardware receive queues work
in igb(4) chipsets.
First, one should read Intel's datasheet on the NIC. For example of 82576-based
NIC this is
https:/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #10 from ricsip ---
(In reply to Jan Bramkamp from comment #9)
Your reply greatly appreciated. My intention was to see if a stone is dropped
into the lake, it may create some waves and progress may happen.
TBH I was unaware o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #33 from Rodney W. Grimes ---
Though this may be a broken hardware issue, to me it does make since to at
least patch the man page in the section on DIAGNOSTICS watchdog timeout to
indicate that this may be caused by non function
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #32 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #31)
Then it should be some problem with new console video driver vt(4) using
graphics mode. Please try installing FreeBSD 11.2 back and switch it to old
st
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
--- Comment #9 from Jan Bramkamp ---
(In reply to ricsip from comment #7)
The problem exists and can be fixed, but would require non-trivial changes. I
suspect that the problem isn't specific to the Intel NIC driver and that you'll
encount
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #31 from Stephan Neuhaus ---
Replying to my own comment #29 and to Eugene Grosbein's comment #30
I've just installed Debian 9 on the MacBook and compiled gcc as a stress test.
Zero problems. Bge came up right away and there wer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #30 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #29)
FreeBSD has sysutils/memtester port (or package) that allows testing memory
using running system. Before start, one should raise the limit sysctl
vm.ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #29 from Stephan Neuhaus ---
Nope, same effect: font screwed, then apparently AHCI errors. TBH, this looks
like some kind of memory corruption to me. Trying with Debian...
--
You are receiving this mail because:
You are on the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Eugene Grosbein changed:
What|Removed |Added
CC||n...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
Eugene Grosbein changed:
What|Removed |Added
Assignee|n...@freebsd.org |eu...@freebsd.org
Har
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #28 from Stephan Neuhaus ---
(In reply to Eugene Grosbein from comment #27)
OK, kernel build running now, fingers crossed! :-)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #27 from Eugene Grosbein ---
(In reply to Stephan Neuhaus from comment #26)
As we know from that old blog post, you are not only one having bge problem
with this MacBook Pro model and I'd like not to loose the result we got
dis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #26 from Stephan Neuhaus ---
I tried again with a virgin install and from what I can see from the screwed-up
font, this time, I landed in the kernel debugger, but with an unresponsive
keyboard. Something is definitely not right
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229727
--- Comment #25 from Stephan Neuhaus ---
(In reply to Eugene Grosbein from comment #23)
I started the process but during make buldkernel, the MacBook started to act
up: the console font changed and there were kernel(?) errors (that I could
38 matches
Mail list logo
