[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXK3g0dVs_qi7Xcm@gallifrey>
Date: Thu, 22 Jan 2026 23:49:23 +0000
From: "Dr. David Alan Gilbert" <linux@...blig.org>
To: George R Goffe <grgoffe@...oo.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Bug found in linux-6.19-rc5.
* George R Goffe (grgoffe@...oo.com) wrote:
> Dr. Dave,
Hi George,
> That was the last line in the journal. NOTHING after that... the system was frozen though.
OK, without more it's very difficult to debug further.
Running the test outside of the GUI, with the console, tends
to get a bit more of a spew if it hangs.
It's not unusual for a hard crash to not get much to the logs.
> The Fedora folks have released a "new" kernel; 6.19.0-0.rc6.260121g6c790212c588f.44.fc44.x86_64
>
> It's installed now. It is my intent to try to repeat the crash. I call it a crash but it doesn't look like any of the crashes I've seen. Just a blinking light on the caps-lock key... no other indications. Very strange. I looked on the web for "linux vivobook s16 blinking caps-lock'. I'm not sure what to make of the search results. The results seem to "think" it could be a hardware problem but the machine was new in May 2025.
Blinking keyboard lights is the normal symptom of a hard kernel panic.
It could indeed be a hardware problem; you say it happens after a gcc build
etc; that will be a pretty good stress test, so if it's over heating
for example, that could be doing it, or if you've got some marginal
RAM.
However, if you can reliably reproduce the problem on rc5 and later, but
rc4 is fine; that's much more likely to be a kernel issue. Please test;
if it's reliably reproducable on a new version but not the old then
there is probably a kernel problem.
> I've had Fedora 42 installed up to about a month ago. FC42 crashed and burned... due to self-inflicted wounds. I tried to reinstall from the original DVD but got FC44.
>
> I will let you know what happens when this latest batch of upgrades (nearly 6500 upgrades) is installed.
If you can still trigger it then you can try:
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes
to gather a more detailed backtrace.
As it is, there's not much to know who to redirect it to.
> THANKS for your response and willingness to help,
Best of luck!
Dave
>
> Best regards,
>
> George...
>
>
>
>
>
>
>
> On Thursday, January 22, 2026 at 09:48:10 AM PST, Dr. David Alan Gilbert <linux@...blig.org> wrote:
>
>
>
>
>
> * George R Goffe (grgoffe@...oo.com) wrote:
> > Howdy,
> >
> > I'm having some trouble finding the Maintainer and the appropriate mailing list for this bug. This is probably my first kernel bug report.
> >
> > Out of desperation, I filed a bug report on Fedora 44 at bugzilla.redhat.com: https://bugzilla.redhat.com/show_bug.cgi?id=2430550
> >
> > Here;s the message I'm seeing:
> >
> > Jan 16 09:14:26 kernel: kernel BUG at kernel/irq_work.c:245!
>
> Do you have anything after that? On a good day there should be
> a bit of a backtrace below it which might help people figure out what
> triggered it.
>
> Dave
>
> >
> > I have tried to build the rc6 kernel but am having trouble buiilding it. There seems to be a problem with the binutils package that halts the build. I cloned the binutils repo but bin utils doesn't want to build either. I have two gcc versions on this build system. Both builds fail in the SAME way... the same indication. Sigh...
> >
> > Can you help me please?
> >
> > Best regards,
> >
> > George...
> >
> --
> -----Open up your eyes, open up your mind, open up your code -------
> / Dr. David Alan Gilbert | Running GNU/Linux | Happy \
> \ dave @ treblig.org | | In Hex /
> \ _________________________|_____ http://www.treblig.org |_______/
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
Powered by blists - more mailing lists