Dual pppoe (IPv4 + IPv6 via pppoe) Problems in 2.6.0-RELEASE ? Sleeping thread (tid 100749, pid 86381) owns a non-sleepable lock

4920441 0

Hi,

After adding another pppoe (pppoe0 + pppoe1 added, both with ipv4 and ipv6) connection to my pfsense installation I got sporadic crashes with the following crashdump which is everytime the same....:

<7>cannot forward from 2001:xxx:xx:xxx:xx:xxx:xx::   to fe80:a::aca6:cccc:cccc:cc95 nxt 58 received on lagg0.10
<3>nd6_dad_timer: called with non-tentative address fe80:20::329c:cccc:ccc:cccc(pppoe1)
<6>ovpnc8: link state changed to DOWN
Sleeping thread (tid 100749, pid 86381) owns a non-sleepable lock
KDB: stack backtrace of thread 100749:
sched_switch() at sched_switch+0x630/frame 0xfffffe0095aec610
mi_switch() at mi_switch+0xd4/frame 0xfffffe0095aec640
sleepq_wait() at sleepq_wait+0x2c/frame 0xfffffe0095aec670
_sx_xlock_hard() at _sx_xlock_hard+0x3ee/frame 0xfffffe0095aec720
vlan_ioctl() at vlan_ioctl+0x6f9/frame 0xfffffe0095aec790
if_allmulti() at if_allmulti+0x85/frame 0xfffffe0095aec7e0
X_ip_mrouter_set() at X_ip_mrouter_set+0x17b4/frame 0xfffffe0095aec8b0
rip_ctloutput() at rip_ctloutput+0xf3/frame 0xfffffe0095aec8e0
sosetopt() at sosetopt+0xe7/frame 0xfffffe0095aec940
kern_setsockopt() at kern_setsockopt+0xb0/frame 0xfffffe0095aec9a0
sys_setsockopt() at sys_setsockopt+0x24/frame 0xfffffe0095aec9c0
amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe0095aecaf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe0095aecaf0
--- syscall (105, FreeBSD ELF64, sys_setsockopt), rip = 0x8003b7dfa, rsp = 0x7fffffffeb98, rbp = 0x7fffffffebd0 ---
panic: sleeping thread
cpuid = 1
time = 1656265777
KDB: enter: panic
...................................................................................................................................................................................................................
..................................................................................................................................................panic.txt........................................................
...................................0600....0.......0.......17..........14256116061.  7140. .....................................................................................................ustar...root.......
.....................wheel.........................................................................................................................................................................................
.........................sleeping thread...........................................................................................................................................................................
...................................................................................................................................................................................................................
...................................................................................................................version.txt.....................................................................................
....0600....0.......0.......75..........14256116061.  7537. .....................................................................................................ustar...root............................wheel.....
.............................................................................................................................................................................................................FreeBS
D 12.3-STABLE RELENG_2_6_0-n226742-1285d6d205f pfSense
...................................................................................................................................................................................................................
............................................................

Until I disabled Hyperthreading (Intel i3-6100T) the crash occured every 24 to 48 hours.
I read in other freebsd related posts (which have nothing to do with pfsense) that panics which are related to sleeping threads it coud be a problem with intel hyperthreading - but they were quiet old.....

But anyway I disabled Intels HT in the Bios, so it is not used any more.
Now the panics a much less frequent - but once a week they occur though :-(

After thinking this over, it started exactly, when I added a second pppoe interface for my backup line.
Could it have really anything to do with this event?

Thanks a lot!

Cheers,,

4920441

4920441 0

Anyone? Some Ideas?

currently I took my backup.xml and re-installed a fresh pfsense 2.6 again, hope that fixes that problem....

When I have some time for the project, I think it's about time to migrate all pfsense installations to opnsense anyway, since the community support is way better - compared with 2007 e.g.......

BTW: I just tested the development 2.7 also for a (very) short time yesterday with my config and to make it short: a lot more was broken afterwards.... too much to go in detail, mainly all but one ipsec site2site were broken (all ipsec's with IPv6 gateways, even those with static IPv6 addresses....), furthermore DHCP client v6 was not working any more.... so either my config is rubbish (it grow since about 2010) or the testing is currently really deeply testing and nothing else:-)

netblues

@4920441-0 Obviously what you are experiencing isn't commonly happening.
Having two threads doing same task on different data is quite common. I doubt that hyperthreading can make a difference on just those two crashing. It must be a more general issue.

I would suspect hardware issues. Can't prove it for sure, but maybe its an option to try.

As for migrating to opnsense, for better community support, you are free to do as you wish.
However saying so here leaves something to be desired, regarding politeness and netiquette.

Have a nice day.

4920441 0

@netblues said in Dual pppoe (IPv4 + IPv6 via pppoe) Problems in 2.6.0-RELEASE ? Sleeping thread (tid 100749, pid 86381) owns a non-sleepable lock:

However saying so here leaves something to be desired, regarding politeness and netiquette.

Sorry for doing so, but this is not the only issue.... I think pfsense is running out of steam the last 5 years or so.... innovation stalls (take a look at other firewalls, sure, completely closed source) like Palo Alto and compare it with the innovation of pfsense....

Furthermore, If you report an error, mostly for the pfsense community it is automatically a "pebkac"- or a hardware Error. That is also not nice regarding netiquette....

This Error occured first when I added the second pppoe connection and 'maybe' after the upgrade to 2.6.0.
So to things were changed, the hardware is the same and build in fixed in an computercenter - sure, could be the hardware, but I doubt it, because it ran stable for more than one year, rebooting only for updates......

But you are right, it could be... could be both, though.....

Cheers

4920441

netblues

@4920441-0

Why are we comparing apples to oranges?
pfsense or even opnsense isn't a ngfw device
palo alto products built ontop of ngfw with many more bells and wistles. If you need them, you need them badly.

But not everyone needs an ngfw. Or everyone needs a soc service to look up ones logs.

pfsense and opnsense are heavily relying on freebsd
Especially ht and sleeping threads.
Why this could be any different on opn?

Switching to development version at this time isn't a good idea, anyway. Rechecking your issue with a fresh config, trying to isolate things could help.

At the end of the day, there is also pfsense plus and paid support for anyone who doesn't have time to play around.

As I said, you are free to do whatever solves your issues
Complaints are fine, on the constructive side.
If you have to suggest something, go ahead and do so

Have you ever considered walking into a bmw dealership and tried to explain how inovvative tesla's are?

4920441 0

@netblues said in Dual pppoe (IPv4 + IPv6 via pppoe) Problems in 2.6.0-RELEASE ? Sleeping thread (tid 100749, pid 86381) owns a non-sleepable lock:

Why are we comparing apples to oranges?

I am not comparing them I took this as an example that the last 15 years the innovation is rather stuck of pfsense.

What came along the last 15 years? lots of bugfixes finally IPv6 support only about 10 (?) years ago, and as an addon wireguard in 'secure' despite the build in wireguard support frist try was a security 'desaster'......

THAT is what I am referring to.

And everytime (also this time) when you refer to this, I get commands as yours.

pfsense should be more self-reflective..... that's what is bothering me more and more.... 2008 it was different in many ways!

Cheers

4920441

4920441 0

@netblues said in Dual pppoe (IPv4 + IPv6 via pppoe) Problems in 2.6.0-RELEASE ? Sleeping thread (tid 100749, pid 86381) owns a non-sleepable lock:

Have you ever considered walking into a bmw dealership and tried to explain how inovvative tesla's are?

Why should I? did you take a look at an BMW i4? Thats the thing I would buy... the only downside (despite wear and tear of batteries of all electric cars) is the pricetag.... but on a tesla that is not much difference....

But that car IS innovative and IMHO drives and looks a lot (!) better than any tesla... though, the display is a little bit smaller...

Cheers,

4920441