Still em(4) broken with epoch changes

2019-10-23 Thread Konstantin Belousov
I tried to netboot my test box today with r353914 kernel, and still I get
the following panic on machine attempt to start multiuser:

Feeding entropy: .
lo0: link state changed to UP
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
panic: sleeping in an epoch section
cpuid = 7
time = 1571815747
KDB: stack backtrace:
db_trace_self_wrapper() at 0x802d070b = 
db_trace_self_wrapper+0x2b/frame 0xfe000ee9fba0
vpanic() at 0x803b79bd = vpanic+0x19d/frame 0xfe000ee9fbf0
panic() at 0x803b7753 = panic+0x43/frame 0xfe000ee9fc50
_sleep() at 0x803c38b5 = _sleep+0x4a5/frame 0xfe000ee9fcf0
pause_sbt() at 0x803c3cff = pause_sbt+0x10f/frame 0xfe000ee9fd30
e1000_write_phy_reg_mdic() at 0x80d1332e = 
e1000_write_phy_reg_mdic+0xee/frame 0xfe000ee9fd70
e1000_enable_phy_wakeup_reg_access_bm() at 0x80d16b6b = 
e1000_enable_phy_wakeup_reg_access_bm+0x2b/frame 0xfe000ee9fd90
e1000_update_mc_addr_list_pch2lan() at 0x80d3119a = 
e1000_update_mc_addr_list_pch2lan+0x3a/frame 0xfe000ee9fdd0
em_if_multi_set() at 0x80d0cb49 = em_if_multi_set+0x1c9/frame 
0xfe000ee9fe20
iflib_if_ioctl() at 0x80d87b70 = iflib_if_ioctl+0x100/frame 
0xfe000ee9fe90
if_addmulti() at 0x804b1e9f = if_addmulti+0x2af/frame 0xfe000ee9ff30
in6_joingroup_locked() at 0x8058094e = in6_joingroup_locked+0x2ee/frame 
0xfe000eea0030
in6_joingroup() at 0x80580634 = in6_joingroup+0x44/frame 
0xfe000eea0060
in6_update_ifa() at 0x80579c4c = in6_update_ifa+0x177c/frame 
0xfe000eea0210
nd6_ra_input() at 0x8059fd7f = nd6_ra_input+0x108f/frame 
0xfe000eea04b0
icmp6_input() at 0x8057359a = icmp6_input+0x69a/frame 0xfe000eea0640
ip6_input() at 0x8058b63e = ip6_input+0xb2e/frame 0xfe000eea0720
netisr_dispatch_src() at 0x804bb84a = netisr_dispatch_src+0x9a/frame 
0xfe000eea0790
ether_demux() at 0x804b6d0f = ether_demux+0x15f/frame 0xfe000eea07c0
ether_nh_input() at 0x804b814f = ether_nh_input+0x39f/frame 
0xfe000eea0810
netisr_dispatch_src() at 0x804bb84a = netisr_dispatch_src+0x9a/frame 
0xfe000eea0880
ether_input() at 0x804b71d8 = ether_input+0x58/frame 0xfe000eea08d0
_task_fn_rx() at 0x80d83610 = _task_fn_rx+0xb20/frame 0xfe000eea09e0
gtaskqueue_run_locked() at 0x80402819 = 
gtaskqueue_run_locked+0xf9/frame 0xfe000eea0a30
gtaskqueue_thread_loop() at 0x804025d8 = 
gtaskqueue_thread_loop+0x88/frame 0xfe000eea0a60
fork_exit() at 0x8037b31c = fork_exit+0xcc/frame 0xfe000eea0ab0
fork_trampoline() at 0x8063114e = fork_trampoline+0xe/frame 
0xfe000eea0ab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 0 tid 100024 ]
Stopped at  0x80403cfb = kdb_enter+0x3b:movq
$0,0x808e3968 = kdb_why

Can we please get this sorted out ?
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Still em(4) broken with epoch changes

2019-10-23 Thread Hans Petter Selasky

On 2019-10-23 09:33, Konstantin Belousov wrote:

I tried to netboot my test box today with r353914 kernel, and still I get
the following panic on machine attempt to start multiuser:

Feeding entropy: .
lo0: link state changed to UP
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
panic: sleeping in an epoch section
cpuid = 7
time = 1571815747
KDB: stack backtrace:
db_trace_self_wrapper() at 0x802d070b = 
db_trace_self_wrapper+0x2b/frame 0xfe000ee9fba0
vpanic() at 0x803b79bd = vpanic+0x19d/frame 0xfe000ee9fbf0
panic() at 0x803b7753 = panic+0x43/frame 0xfe000ee9fc50
_sleep() at 0x803c38b5 = _sleep+0x4a5/frame 0xfe000ee9fcf0
pause_sbt() at 0x803c3cff = pause_sbt+0x10f/frame 0xfe000ee9fd30
e1000_write_phy_reg_mdic() at 0x80d1332e = 
e1000_write_phy_reg_mdic+0xee/frame 0xfe000ee9fd70
e1000_enable_phy_wakeup_reg_access_bm() at 0x80d16b6b = 
e1000_enable_phy_wakeup_reg_access_bm+0x2b/frame 0xfe000ee9fd90
e1000_update_mc_addr_list_pch2lan() at 0x80d3119a = 
e1000_update_mc_addr_list_pch2lan+0x3a/frame 0xfe000ee9fdd0
em_if_multi_set() at 0x80d0cb49 = em_if_multi_set+0x1c9/frame 
0xfe000ee9fe20
iflib_if_ioctl() at 0x80d87b70 = iflib_if_ioctl+0x100/frame 
0xfe000ee9fe90
if_addmulti() at 0x804b1e9f = if_addmulti+0x2af/frame 0xfe000ee9ff30
in6_joingroup_locked() at 0x8058094e = in6_joingroup_locked+0x2ee/frame 
0xfe000eea0030
in6_joingroup() at 0x80580634 = in6_joingroup+0x44/frame 
0xfe000eea0060
in6_update_ifa() at 0x80579c4c = in6_update_ifa+0x177c/frame 
0xfe000eea0210
nd6_ra_input() at 0x8059fd7f = nd6_ra_input+0x108f/frame 
0xfe000eea04b0
icmp6_input() at 0x8057359a = icmp6_input+0x69a/frame 0xfe000eea0640
ip6_input() at 0x8058b63e = ip6_input+0xb2e/frame 0xfe000eea0720
netisr_dispatch_src() at 0x804bb84a = netisr_dispatch_src+0x9a/frame 
0xfe000eea0790
ether_demux() at 0x804b6d0f = ether_demux+0x15f/frame 0xfe000eea07c0
ether_nh_input() at 0x804b814f = ether_nh_input+0x39f/frame 
0xfe000eea0810
netisr_dispatch_src() at 0x804bb84a = netisr_dispatch_src+0x9a/frame 
0xfe000eea0880
ether_input() at 0x804b71d8 = ether_input+0x58/frame 0xfe000eea08d0
_task_fn_rx() at 0x80d83610 = _task_fn_rx+0xb20/frame 0xfe000eea09e0
gtaskqueue_run_locked() at 0x80402819 = 
gtaskqueue_run_locked+0xf9/frame 0xfe000eea0a30
gtaskqueue_thread_loop() at 0x804025d8 = 
gtaskqueue_thread_loop+0x88/frame 0xfe000eea0a60
fork_exit() at 0x8037b31c = fork_exit+0xcc/frame 0xfe000eea0ab0
fork_trampoline() at 0x8063114e = fork_trampoline+0xe/frame 
0xfe000eea0ab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 0 tid 100024 ]
Stopped at  0x80403cfb = kdb_enter+0x3b:movq
$0,0x808e3968 = kdb_why

Can we please get this sorted out ?


PR is here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223

--HPS

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Still em(4) broken with epoch changes

2019-10-23 Thread Konstantin Belousov
On Wed, Oct 23, 2019 at 09:39:36AM +0200, Hans Petter Selasky wrote:
> On 2019-10-23 09:33, Konstantin Belousov wrote:
> > I tried to netboot my test box today with r353914 kernel, and still I get
> > the following panic on machine attempt to start multiuser:
> > 
> > Feeding entropy: .
> > lo0: link state changed to UP
> > uhub0: 3 ports with 3 removable, self powered
> > uhub1: 3 ports with 3 removable, self powered
> > panic: sleeping in an epoch section
> > cpuid = 7
> > time = 1571815747
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at 0x802d070b = 
> > db_trace_self_wrapper+0x2b/frame 0xfe000ee9fba0
> > vpanic() at 0x803b79bd = vpanic+0x19d/frame 0xfe000ee9fbf0
> > panic() at 0x803b7753 = panic+0x43/frame 0xfe000ee9fc50
> > _sleep() at 0x803c38b5 = _sleep+0x4a5/frame 0xfe000ee9fcf0
> > pause_sbt() at 0x803c3cff = pause_sbt+0x10f/frame 0xfe000ee9fd30
> > e1000_write_phy_reg_mdic() at 0x80d1332e = 
> > e1000_write_phy_reg_mdic+0xee/frame 0xfe000ee9fd70
> > e1000_enable_phy_wakeup_reg_access_bm() at 0x80d16b6b = 
> > e1000_enable_phy_wakeup_reg_access_bm+0x2b/frame 0xfe000ee9fd90
> > e1000_update_mc_addr_list_pch2lan() at 0x80d3119a = 
> > e1000_update_mc_addr_list_pch2lan+0x3a/frame 0xfe000ee9fdd0
> > em_if_multi_set() at 0x80d0cb49 = em_if_multi_set+0x1c9/frame 
> > 0xfe000ee9fe20
> > iflib_if_ioctl() at 0x80d87b70 = iflib_if_ioctl+0x100/frame 
> > 0xfe000ee9fe90
> > if_addmulti() at 0x804b1e9f = if_addmulti+0x2af/frame 
> > 0xfe000ee9ff30
> > in6_joingroup_locked() at 0x8058094e = 
> > in6_joingroup_locked+0x2ee/frame 0xfe000eea0030
> > in6_joingroup() at 0x80580634 = in6_joingroup+0x44/frame 
> > 0xfe000eea0060
> > in6_update_ifa() at 0x80579c4c = in6_update_ifa+0x177c/frame 
> > 0xfe000eea0210
> > nd6_ra_input() at 0x8059fd7f = nd6_ra_input+0x108f/frame 
> > 0xfe000eea04b0
> > icmp6_input() at 0x8057359a = icmp6_input+0x69a/frame 
> > 0xfe000eea0640
> > ip6_input() at 0x8058b63e = ip6_input+0xb2e/frame 0xfe000eea0720
> > netisr_dispatch_src() at 0x804bb84a = 
> > netisr_dispatch_src+0x9a/frame 0xfe000eea0790
> > ether_demux() at 0x804b6d0f = ether_demux+0x15f/frame 
> > 0xfe000eea07c0
> > ether_nh_input() at 0x804b814f = ether_nh_input+0x39f/frame 
> > 0xfe000eea0810
> > netisr_dispatch_src() at 0x804bb84a = 
> > netisr_dispatch_src+0x9a/frame 0xfe000eea0880
> > ether_input() at 0x804b71d8 = ether_input+0x58/frame 
> > 0xfe000eea08d0
> > _task_fn_rx() at 0x80d83610 = _task_fn_rx+0xb20/frame 
> > 0xfe000eea09e0
> > gtaskqueue_run_locked() at 0x80402819 = 
> > gtaskqueue_run_locked+0xf9/frame 0xfe000eea0a30
> > gtaskqueue_thread_loop() at 0x804025d8 = 
> > gtaskqueue_thread_loop+0x88/frame 0xfe000eea0a60
> > fork_exit() at 0x8037b31c = fork_exit+0xcc/frame 0xfe000eea0ab0
> > fork_trampoline() at 0x8063114e = fork_trampoline+0xe/frame 
> > 0xfe000eea0ab0
> > --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
> > KDB: enter: panic
> > [ thread pid 0 tid 100024 ]
> > Stopped at  0x80403cfb = kdb_enter+0x3b:movq
> > $0,0x808e3968 = kdb_why
> > 
> > Can we please get this sorted out ?
> 
> PR is here:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
> 
The PR is closed, but for me the issue is not fixed, and sure
my backtrace is different and is not related to if_attach().
It is multicast join in nd6 RA processing, it seems.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 235524] igb ethernet interface loses active link state

2019-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235524

--- Comment #2 from Denis Ahrens  ---
it seems that r353778 - head/sys/dev/e1000 fixed my problem.

running now for 36h without a problem

will close this as fixed in a week

denis

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


TCP Congestion Control

2019-10-23 Thread vm finance
Hi,

We can set per-socket congestion control under Linux, but not under FreeBSD
(12.0).
The current available and allowed is only newReno:
net.inet.tcp.cc.available: newreno
net.inet.tcp.cc.algorithm: newreno

Any thoughts on why FreeBSD chose not to allow different cc to be set per
socket?
AFAIK, it would get complicated to have different sessions having different
congestion algos.

Thanks for any pointers!
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: TCP Congestion Control

2019-10-23 Thread Kevin Oberman
Have you loaded kernel modules for other algorithms? I believe only newreno
is in the default kernel. "man 4 mod_cc" for available modules and other
information.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Wed, Oct 23, 2019 at 11:04 PM vm finance  wrote:

> Hi,
>
> We can set per-socket congestion control under Linux, but not under FreeBSD
> (12.0).
> The current available and allowed is only newReno:
> net.inet.tcp.cc.available: newreno
> net.inet.tcp.cc.algorithm: newreno
>
> Any thoughts on why FreeBSD chose not to allow different cc to be set per
> socket?
> AFAIK, it would get complicated to have different sessions having different
> congestion algos.
>
> Thanks for any pointers!
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: TCP Congestion Control

2019-10-23 Thread vm finance
Ok - I  see there is a socket option to pick a different cc per-socket
basis.
Any experiences on loading / using different cc per socket...does it work
seamlessly?

Thanks!

On Wed, Oct 23, 2019 at 11:19 PM Kevin Oberman  wrote:

> Have you loaded kernel modules for other algorithms? I believe only
> newreno is in the default kernel. "man 4 mod_cc" for available modules and
> other information.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Wed, Oct 23, 2019 at 11:04 PM vm finance  wrote:
>
>> Hi,
>>
>> We can set per-socket congestion control under Linux, but not under
>> FreeBSD
>> (12.0).
>> The current available and allowed is only newReno:
>> net.inet.tcp.cc.available: newreno
>> net.inet.tcp.cc.algorithm: newreno
>>
>> Any thoughts on why FreeBSD chose not to allow different cc to be set per
>> socket?
>> AFAIK, it would get complicated to have different sessions having
>> different
>> congestion algos.
>>
>> Thanks for any pointers!
>> ___
>> freebsd-net@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>>
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"