From: David Ranch <linux-hams@trinnet.net>
To: linux-hams@vger.kernel.org
Subject: Re: [ROSE] [AX25] 6.15.10 long term stable kernel oops
Date: Sat, 16 Aug 2025 10:35:12 -0700 [thread overview]
Message-ID: <58b534b6-98e5-0e55-d65b-eaff719cfa18@trinnet.net> (raw)
In-Reply-To: <57258a4d-50bd-47a1-b83a-c47051c54876@free.fr>
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
>
next prev parent reply other threads:[~2025-08-16 17:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 17:02 [ROSE] [AX25] 6.15.10 long term stable kernel oops Bernard Pidoux
2025-08-16 17:35 ` David Ranch [this message]
[not found] <11c5701d-4bf9-4661-ad8a-06690bbe1c1c@free.fr>
[not found] ` <fff0b3eb-ea42-4475-970d-30622dc25dca@free.fr>
2025-08-16 18:45 ` Bernard Pidoux
2025-08-18 10:00 ` Bernard Pidoux
2025-08-18 10:04 ` Folkert van Heusden
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-21 11:28 ` F6BVP
2025-08-21 22:39 ` 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-01 19:04 ` David Ranch
2025-09-02 7:54 ` F6BVP
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=58b534b6-98e5-0e55-d65b-eaff719cfa18@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=linux-hams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.