From: Folkert van Heusden <folkert@vanheusden.com>
To: Bernard Pidoux <bernard.pidoux@free.fr>
Cc: David Ranch <dranch@trinnet.net>,
linux-hams@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Date: Mon, 18 Aug 2025 12:04:17 +0200 [thread overview]
Message-ID: <af3344165cd51561f92449a27841f41d@vanheusden.com> (raw)
In-Reply-To: <acd04154-25a5-4721-a62b-36827a6e4e47@free.fr>
Looks like the issue I reported a few weeks ago.
In my case not related to rose, only new connections.
On 2025-08-18 12:00, Bernard Pidoux wrote:
> Hi,
>
> I captured a screen picture of kernel panic in linux-6.16.0 that
> displays [mkiss]. See included picture.
>
> Bernard
>
>
> Le 16/08/2025 à 20:45, Bernard Pidoux a écrit :
>> David,
>>
>> For some reason my messages are not accepted by vger.kernel.org
>> despite I configured thunderbird not to send html.
>>
>> I just compiled and loaded kernel 6.15.1.
>>
>> Up to now FPAC 4.1.4 is running fine and performing connexions with
>> neighbour ROSE nodes.
>>
>> I will let it run a while before starting to apply progressively the
>> AX25 and ROSE patches committed in kernels 15.2 to 15.10
>>
>> I will start with ax25 ones and see what happens.
>>
>> 73 de Bernard f6bvp / ai7bg
>>
>>
>>
>> Le 16/08/2025 à 19:49, Bernard Pidoux a écrit :
>>> Hi David,
>>>
>>> Actually Ubuntu stops responding without any message. No more
>>> response from keyboard or mouse. Only switch power !
>>>
>>> I am working on activating kernel messages on oops.
>>>
>>> The bug is already present in 6.15.10 so there is no reason to look
>>> at a more recent version.
>>>
>>> I will report any progress if I find something interesting.
>>>
>>> This is quite a challenge for me as I did not perform this kind of
>>> kernel investigations since nearly a decade...and I am not getting
>>> younger !
>>>
>>> 73 de Bernard, f6bvp / ai7bg
>>>
>>>
>>> Le 16/08/2025 à 19:32, David Ranch a écrit :
>>>>
>>>> Hey Bernard,
>>>>
>>>> Thanks for posting this issue. Can you copy/paste in the Oops
>>>> you're seeing? I did see a recent ROSE issue on
>>>> 6.16.0-rc6-next-20250718- syzkaller and I wonder if that could have
>>>> created this issue:
>>>>
>>>> https://groups.google.com/g/syzkaller-bugs/c/0TmBbcJ2PKE
>>>>
>>>> Btw, I would say that posting this to netdev@vger.kernel.org would
>>>> probably be more important than this Debian list since this is most
>>>> likely a kernel issue and not a distro issue per se.
>>>>
>>>> --David
>>>> KI6ZHD
>>>>
>>>>
>>>> On 08/16/2025 10:02 AM, Bernard Pidoux wrote:
>>>>> Hi,
>>>>>
>>>>> I am continuously working on AX25 ROSE/FPAC node since decades,
>>>>> running a number of RaspBerry Pi (Raspi OS 64bit) plus Ubuntu LTS
>>>>> on a mini PC.
>>>>>
>>>>> Stable FPAC version 4.1.4 is performing packet switch quite well
>>>>> although some improvements are underway.
>>>>>
>>>>> FPAC runs flawlessly with kernel 6.14.11.
>>>>>
>>>>> However, trying FPAC under stable kernel 6.15.10 experienced a
>>>>> frozen system when issuing some commands like connect request.
>>>>>
>>>>> Investigations seem to show that ax25 connect is fine and that the
>>>>> bug is probably in ROSE module .
>>>>>
>>>>> I am presently trying to find the faulty bug that triggers the
>>>>> kernel oops by compiling and installing previous kernel versions
>>>>> starting with 6.15.1.
>>>>>
>>>>> 73s de Bernard, f6bvp / ai7bg
>>>>>
>>>>> http://f6bvp.org
>>>>>
>>>>
>>
--
www.vanheusden.com
next prev parent reply other threads:[~2025-08-18 10:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11c5701d-4bf9-4661-ad8a-06690bbe1c1c@free.fr>
[not found] ` <fff0b3eb-ea42-4475-970d-30622dc25dca@free.fr>
2025-08-16 18:45 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops Bernard Pidoux
2025-08-18 10:00 ` Bernard Pidoux
2025-08-18 10:04 ` Folkert van Heusden [this message]
2025-08-18 14:19 ` F6BVP
2025-08-18 16:30 ` Dan Cross
2025-08-18 18:28 ` F6BVP
2025-08-18 22:11 ` Dan Cross
2025-08-18 22:31 ` F6BVP
2025-08-20 8:50 ` F6BVP
2025-08-20 19:33 ` kworker/u16 Not tainted F6BVP
2025-08-21 11:28 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops F6BVP
2025-08-21 17:49 ` F6BVP
2025-08-21 22:39 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops F6BVP
2025-08-22 3:10 ` Folkert van Heusden
2025-08-24 14:04 ` F6BVP
2025-08-25 12:40 ` Dan Carpenter
2025-08-26 13:31 ` F6BVP
2025-08-26 13:36 ` Eric Dumazet
2025-08-27 14:16 ` F6BVP
2025-08-27 17:30 ` Florian Westphal
2025-08-28 16:39 ` F6BVP
2025-08-30 23:37 ` F6BVP
2025-09-01 12:04 ` Eric Dumazet
2025-09-01 12:05 ` Eric Dumazet
[not found] ` <cd0461e0-8136-4f90-df7b-64f1e43e78d4@trinnet.net>
2025-09-01 15:59 ` F6BVP
2025-09-01 16:03 ` Eric Dumazet
2025-09-01 19:10 ` David Ranch
2025-09-01 19:16 ` Eric Dumazet
2025-09-02 7:44 ` F6BVP
2025-09-02 7:55 ` Eric Dumazet
2025-09-03 9:51 ` [BUG] [ROSE] slab-use-after-free in lock_timer_base Bernard Pidoux
2025-09-03 10:01 ` Eric Dumazet
2025-09-03 10:11 ` F6BVP
2025-09-03 11:07 ` Takamitsu Iwai
2025-09-01 19:04 ` [ROSE] [AX25] 6.15.10 long term stable kernel oops David Ranch
2025-09-02 7:54 ` F6BVP
2025-08-19 21:17 ` [OT] " Miroslav Skoric
2025-08-16 17:02 Bernard Pidoux
2025-08-16 17:35 ` David Ranch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af3344165cd51561f92449a27841f41d@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=bernard.pidoux@free.fr \
--cc=dranch@trinnet.net \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox