m_move_pkthdr leaves m_nextpkt 'dangling'

2017-06-30 Thread Karim Fodil-Lemelin
Hi, As many of you know, when dealing with IP fragments the kernel will build a list of packets (fragments) chained together through the m_nextpkt pointer. This is all good until someone tries to do a M_PREPEND on one of the packet in the chain and the M_PREPEND has to create an extra mbuf to

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 oleg.nau...@gmail.com changed: What|Removed |Added CC||oleg.nau...@gmail.com --- C

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #7 from iz-rp...@hs-karlsruhe.de --- Just an intermediate result: A r320008 32-bit kernel, no hyperthreading, panics as well with "privileged instruction fault" in "tcp_lro_flush_all". Ralf -- You are receiving this mail becau

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #6 from iz-rp...@hs-karlsruhe.de --- > I also notice your hardware is 32-bit. Have you seen this issue with 64-bit > kernels? No, but on this hardware I have not run a 64-bit kernel yet. On a different hardware a very current 6

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #5 from Hans Petter Selasky --- Adding Sean Bruno. I also notice your hardware is 32-bit. Have you seen this issue with 64-bit kernels? --HPS -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #4 from iz-rp...@hs-karlsruhe.de --- There is no "option RSS" in the used kernel config. So, the answer is: No. Hyperthreading was used. As you suggested I disabled it via /boot/loader.conf, but the panic happend again. It chang

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #3 from Hans Petter Selasky --- RSS means "options RSS" in the kernel config Second question: Are you using hyperthreading? Can you try to enter: machdep.hyperthreading_allowed=0 in /boot/loader.conf Is this issue reproducib

[Bug 220217] deadlock on enc and pf

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220217 --- Comment #7 from Kristof Provost --- (In reply to Andrey V. Elsukov from comment #5) Thanks! I missed the inpcb being passed through netpfil. That explains why it usually works. -- You are receiving this mail because: You are the assig

[Bug 220358] panic in tcp_lro_flush_all

2017-06-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220358 --- Comment #2 from iz-rp...@hs-karlsruhe.de --- (In reply to Hans Petter Selasky from comment #1) Hi, not knowingly. I had to look up what RSS means. https://wiki.freebsd.org/NetworkRSS does not mention an Intel(R) PRO/1000 network interf