[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d073ac34a39c02287be6d67622229a1e@vanheusden.com>
Date: Fri, 22 Aug 2025 05:10:14 +0200
From: Folkert van Heusden <folkert@...heusden.com>
To: F6BVP <f6bvp@...e.fr>
Cc: linux-hams@...r.kernel.org, netdev <netdev@...r.kernel.org>, Dan Cross
<crossd@...il.com>, David Ranch <dranch@...nnet.net>
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Bernard,
I skimmed over the diff between the latest 6.14.y and latest 6.15.y tags
of the raspberry pi linux kernel and didn't saw anything relevant
changed. Altough changes in 'arch' could in theory affect everything.
On 2025-08-22 00:39, F6BVP wrote:
> As I already reported mkiss never triggered any Oops kernel panic up to
> linux-6.14.11.
>
> In that version I put a number of printk inside of mkiss.c in order to
> follow the normal behaviour and content outside and during FPAC
> functionning especially when issuing a connect request.
>
> On the opposite an FPAC connect request systematically triggers a
> kernel panic with linux-6.15.2 and following kernels.
>
> In 6.14.11 I observe that when mkiss runs core/dev is never activated
> i.e. neither __netif_receive_skb nor __netif_receive_skb_one_core.
>
> These functions appear in kernel 6.15.2 panics after mkiss_receive_buf.
>
> One can guess that mkiss_receive_buf() is triggering something wrong in
> kernel 6.15.2 and all following kernels up to net-next.
>
> The challenge to locate the bug is quite difficult as I did not find
> the way to find relevant code differences between both kernels in
> absence of inc patch...
>
> I sincerely regret not knowing how to go further.
>
> Bernard,
> hamradio f6bvp /ai7bg
--
www.vanheusden.com
Powered by blists - more mailing lists