Crash when having CONFIG_NET_SCH_DUALPI2=m

[Jorge Bastos]

Sorry,

It's the contrary, dualpi2 need to be enabled!
Without it enabled, fireqos crashes

Working scenario:
CONFIG_NET_SCH_DUALPI2=m

Not working scenario with kernel crash:
#CONFIG_NET_SCH_DUALPI2 not set

On 2026-08-16 20:39, Jorge Bastos wrote:

> Hi List,
> 
> I discovered that when i have CONFIG_NET_SCH_DUALPI2=m on the kernel, 
> fireqos crashes the kernel on start,
> Disabling this module, makes everything work OK,
> 
> Jorge,
> 
> On 2026-07-19 9:47, Jorge Bastos wrote:
> 
>> Marc,
>> 
>> I compiled a 7.1x kernel without seccomp, and i can confirm you that:
>> 
>> - kernel 7.1 with seccomp, fireqos/tc craches
>> - kernel 7.1 without seccomp, fireqos/tc craches
>> - kernel 8.18 as you stated also crashes
>> 
>> iproute2 tools are 7.1 (just a coincidence with the kernel version)
>> 
>> which list should i report this, can you help?
>> 
>> On 2026-07-18 19:42, Marc Lavallée wrote:
>> 
>> I just saw that you are running kernel 6.13:
>> 
>> CPU: 0 UID: 0 PID: 50796 Comm: tc Not tainted 6.18.38 #3 PREEMPT(none)
>> Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, 
>> > BIOS 090007 05/18/2018
>> So I guess my advice would not help.
>> 
>> But still, instead of running Debian sid with your own vanilla kernel,
>> maybe it'd work with the kernel provided with Debian
>> and openssh also from Debian.
>> 
>> Marc
>> 
>> Le 2026-07-18 à 14 h 28, Marc Lavallée a écrit : hi Jorge,
>> 
>> Another possibility: maybe it's a Microsoft VM bug,
>> and/or a compatibility issue with kernel 7.13.
>> 
>> So maybe it'd work with an earlier version of Debian,
>> (running an earlier kernel), with a backport of openssh 10:
>> 
>> https://packages.debian.org/bookworm-backports/openssh-server
>> or:
>> https://packages.debian.org/trixie-backports/openssh-server
>> 
>> Marc
>> 
>> Le 2026-07-18 à 13 h 45, Jorge Bastos a écrit : Hi,
>> 
>> OK, going to try to report to kernel, but maybe would be more 
>> productive if is was fireqos reporting kernel, i believe they would 
>> give a different attention,
>> 
>> Would that be possible?
>> 
>> On 2026-07-18 9:11, Marcin Mirosław wrote:
>> 
>> W dniu 14.07.2026 o 13:25, Jorge Bastos pisze:
>> 
>> Howdy,
>> 
>> I've been using fireqos and perfect,
>> But now that i have to use SECCOMP due to SSH 10.4+ needs, fireqos 
>> crashes my kernel. Hi,
>> I think this is kernel side bug not fireqos.