I'm a Windows convert and ran bullseye, bookworm and Trixie as a host.
It was reliable with all oses where I could hibernate several times a
day everyday for over a month and the uptime utility reflected that.
With Trixie a week or so ago I ran updates and the machine crashes with
1 day of uptime at most. Its been crashing repeatedly ÿever since.ÿ
When the machine crashes parts of the video gets scrambled and then the electricity usage spikes up. Reset button, power button (to hibernate),
mouse, keyboard are all unresponsive. How would you investigate to see
if its a known problem?


--- PyGate Linux v1.5.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

joel composed on 2026-01-24 13:11 (UTC-0800):

I'm a Windows convert and ran bullseye, bookworm and Trixie as a host.
It was reliable with all oses where I could hibernate several times a
day everyday for over a month and the uptime utility reflected that.
With Trixie a week or so ago I ran updates and the machine crashes with
1 day of uptime at most. Its been crashing repeatedly ÿever since.ÿ

When the machine crashes parts of the video gets scrambled and then the electricity usage spikes up. Reset button, power button (to hibernate), mouse, keyboard are all unresponsive. How would you investigate to see
if its a known problem?

Make sure /var/log/ exists. If already exists, try to start:

journalctl -b -1 p3

Otherwise, create it, then after next crash and reboot try it. Use -2 or -3 etc.
instead of -1 to check older boots if /var/log/ already existed. man journalctl --
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

--- PyGate Linux v1.5.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

joel wrote:

I'm a Windows convert and ran bullseye, bookworm and Trixie as a host.
It was reliable with all oses where I could hibernate several times a
day everyday for over a month and the uptime utility reflected that.
With Trixie a week or so ago I ran updates and the machine crashes with
1 day of uptime at most. Its been crashing repeatedly ?ever since.?

When the machine crashes parts of the video gets scrambled and then the electricity usage spikes up. Reset button, power button (to hibernate), mouse, keyboard are all unresponsive. How would you investigate to see
if its a known problem?

The first thing I would do is find the previous kernel and boot
from that.

If you're using grub, that should already be in the menu for it
at boot time.

If it continues to crash on the old kernel, it's likely a
hardware problem. If it doesn't:

a) congratulations, you have a workaround
b) you will want to send a bug report to the kernel team

-dsr-

--- PyGate Linux v1.5.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

joel <overland@recarea.com> writes:

I'm a Windows convert and ran bullseye, bookworm and Trixie as a host. It

was reliable with all oses where I could hibernate several times a day eve ryday for over a month and the uptime utility reflected that. With Trixie a
week or so ago I ran updates and the

machine crashes with 1 day of uptime at most. Its been crashing repeatedl

y ever since.

When the machine crashes parts of the video gets scrambled and then the e

lectricity usage spikes up. Reset button, power button (to hibernate), mous
e, keyboard are all unresponsive. How would you investigate to see if its a
known problem?

Do you use 6.12 kernels or newer? I cannot localise problem, but I have
an impression that this is something wrong with memory management in
newer kernels.

KJ

--
http://wolnelektury.pl/wesprzyj/teraz/
Linux jest w stanie prze?yc wyj?cie procesora - reszt? doliczy w pami
?ci.

--- PyGate Linux v1.5.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Dan, that was helpful because I found ÿkernel 6.12.57+deb13-amd64 in
the boot options and have been running that version three days with no crashing. The version I'm having a regression with is 6.12.63.ÿ
To try to narrow the problem down more before filing a bug I was going
to connect a kernel debugger, get symbols lined up and wait for it to
crash and hopefully find the culprit in the stack trace. But
onÿhttps://www.kernel.org/doc/html/v4.14/dev-tools/kgdb.htmlÿit shows
only serial bus for debugging and the debugger machine doesn't have a
serial port. It has a network jack and USB. is there another reliable
(it stays connected) way to connect a KD besides over serial?
Joel

On Sat, 2026-01-24 at 16:55 -0500, Dan Ritter wrote:

joel wrote:

I'm a Windows convert and ran bullseye, bookworm and Trixie as a
host.
It was reliable with all oses where I could hibernate several times
a
day everyday for over a month and the uptime utility reflected
that.
With Trixie a week or so ago I ran updates and the machine crashes
with
1 day of uptime at most. Its been crashing repeatedly ÿever since.ÿ

When the machine crashes parts of the video gets scrambled and then
the
electricity usage spikes up. Reset button, power button (to
hibernate),
mouse, keyboard are all unresponsive. How would you investigate to
see
if its a known problem?

The first thing I would do is find the previous kernel and boot
from that.

If you're using grub, that should already be in the menu for it
at boot time.

If it continues to crash on the old kernel, it's likely a
hardware problem. If it doesn't:

a) congratulations, you have a workaround
b) you will want to send a bug report to the kernel team

-dsr-

--- PyGate Linux v1.5.6
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Wed, Jan 28, 2026 at 12:41?AM joel <overland@recarea.com> wrote:

Dan, that was helpful because I found kernel 6.12.57+deb13-amd64 in the
boot options and have been running that version three days with no
crashing. The version I'm having a regression with is 6.12.63.

To try to narrow the problem down more before filing a bug I was going to connect a kernel debugger, get symbols lined up and wait for it to crash
and hopefully find the culprit in the stack trace. But on https://www.kernel.org/doc/html/v4.14/dev-tools/kgdb.html it shows only serial bus for debugging and the debugger machine doesn't have a serial
port. It has a network jack and USB. is there another reliable (it stays connected) way to connect a KD besides over serial?

Typically you help by finding the problem commit, and then turn it over to
the kernel folks. Also see <https://wiki.debian.org/DebianKernel/GitBisect

.

Jeff


--- PyGate Linux v1.5.6
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi,

On Wed, Jan 28, 2026 at 02:55:56AM -0500, Jeffrey Walton wrote:

On Wed, Jan 28, 2026 at 12:41?AM joel <overland@recarea.com> wrote:

To try to narrow the problem down more before filing a bug I was going to connect a kernel debugger, get symbols lined up and wait for it to crash and hopefully find the culprit in the stack trace. But on https://www.kernel.org/doc/html/v4.14/dev-tools/kgdb.html it shows only serial bus for debugging and the debugger machine doesn't have a serial port. It has a network jack and USB. is there another reliable (it stays connected) way to connect a KD besides over serial?

Typically you help by finding the problem commit, and then turn it over to the kernel folks. Also see <https://wiki.debian.org/DebianKernel/GitBisect

Also you may have luck with a network console:

https://manpages.debian.org/trixie/netconsole/netconsole-setup.8.en.html

Thanks,
Andy

--
https://bitfolk.com/ -- No-nonsense VPS hosting

--- PyGate Linux v1.5.6
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 28/01/2026 8:44 am, joel wrote:

I was going to connect a kernel debugger, get symbols lined up and wait
for it to crash and hopefully find the culprit in the stack trace.

After switching to KMS, i915 driver was hanging frequently. That time I
used "crash kernel" option to collect data necessary for bug reports
after reboot. The driver project site had detailed description how to do
it. It was time consuming, but it worked.

To which degree issues you faced are severe? Can you connect the machine
using ssh? Are there stack traces in system journal (Felix suggested to inspect it)?

--- PyGate Linux v1.5.6
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Felix Miata composed on 2026-01-24 16:56 (UTC-0500):

joel composed on 2026-01-24 13:11 (UTC-0800):

I'm a Windows convert and ran bullseye, bookworm and Trixie as a host.
It was reliable with all oses where I could hibernate several times a
day everyday for over a month and the uptime utility reflected that.
With Trixie a week or so ago I ran updates and the machine crashes with
1 day of uptime at most. Its been crashing repeatedly ÿever since.ÿ

When the machine crashes parts of the video gets scrambled and then the
electricity usage spikes up. Reset button, power button (to hibernate),
mouse, keyboard are all unresponsive. How would you investigate to see
if its a known problem?

Make sure /var/log/ exists. If already exists, try to start:

journalctl -b -1 p3

Was supposed to be:

journalctl -b -1 -p3

Otherwise, create it, then after next crash and reboot try it. Use -2 or -3 etc.
instead of -1 to check older boots if /var/log/ already existed. man journalctl--

Evolution as taught in public schools is, like religion,
based on faith, not based on science.

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

--- PyGate Linux v1.5.6
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)