From: George R Goffe <grgoffe@yahoo.com>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bug found in linux-6.19-rc5.
Date: Thu, 22 Jan 2026 20:10:40 +0000 (UTC) [thread overview]
Message-ID: <1906048706.3314028.1769112640889@mail.yahoo.com> (raw)
In-Reply-To: <aXJi2Dy7BG6ysdKD@gallifrey>
Dr. Dave,
That was the last line in the journal. NOTHING after that... the system was frozen though.
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.
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.
THANKS for your response and willingness to help,
Best regards,
George...
On Thursday, January 22, 2026 at 09:48:10 AM PST, Dr. David Alan Gilbert <linux@treblig.org> wrote:
* George R Goffe (grgoffe@yahoo.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 |_______/
next prev parent reply other threads:[~2026-01-22 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1925253747.3045658.1769044192390.ref@mail.yahoo.com>
2026-01-22 1:09 ` George R Goffe
2026-01-22 17:48 ` Dr. David Alan Gilbert
2026-01-22 20:10 ` George R Goffe [this message]
2026-01-22 23:49 ` Dr. David Alan Gilbert
2026-01-22 23:39 ` George R Goffe
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=1906048706.3314028.1769112640889@mail.yahoo.com \
--to=grgoffe@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.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
all inboxes | Powered by JetHome®