Was linux-image-6.1.0-22-amd64 spontaneously rebooting?

[Mike]

I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.

Then that upgraded linux-image-6.1.0-22-amd64 to -23-. So far, the system
seems stable. I'll let it run for awhile before I believe that.

So the question is: Has there recently been such an issue with the -22-
package? It seems that there were a *lot* of changes from the upstream
6.1.94 to 6.1.99, so maybe something was repaired.

I'm not sure what to doubt right now: the CPU (Intel's been having issues
with Raptor Lake, but mine's a "T" series), the motherboard (may have been
mishandled by the retailer), or Linux.

This is an offbeat question, so I understand if I never get an answer.

[George at Clug]

Mike,

My thought would be to run a memory test.

Either download from the memtest86 web site, and make a bootable USB, or install the Debian memtest86+ package and then reboot and select memtest86+.

memtest86 has helped me a few times. Once with picking up mismatched RAM modules and one time with faulty RAM.

https://www.memtest.org/
Memtest86+ v6 is a unified, free, open-source memory testing tool, released under GNU GPL v2.0

There are still plenty of other sources that can cause the odd strange reboot.

If you can (e.g. have the free time, and maybe a different disk drive), maybe try another new installation?

My main computer does it from time to time, but so infrequently, I still keep using it. I guess one day the computer will die, but until then...

I had heard that Intel have been experiencing some instability which has been of concern.

I will be curious what others may suggest, like using stress-ng or s-tui ?

https://support.system76.com/articles/hardware-failure/

FYI: To my knowledge, a new installation (when connected to the Internet) should result in a totally up to date system, such if you run "apt update && apt full-upgrade -y" afterwards, there should be no updates to apply. Your comment "Then that upgraded linux-image-6.1.0-22-amd64 to -23-" does concern me, I would prefer to start with a new, clean, working installation, even if that means installing all over again.

George.

Post by Mike
I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.
Then that upgraded linux-image-6.1.0-22-amd64 to -23-. So far, the system
seems stable. I'll let it run for awhile before I believe that.
So the question is: Has there recently been such an issue with the -22-
package? It seems that there were a *lot* of changes from the upstream
6.1.94 to 6.1.99, so maybe something was repaired.
I'm not sure what to doubt right now: the CPU (Intel's been having issues
with Raptor Lake, but mine's a "T" series), the motherboard (may have been
mishandled by the retailer), or Linux.
This is an offbeat question, so I understand if I never get an answer.
M

[Mike]

Post by George at Clug
run a memory test.

Did that already, right after the build. Memtest86+.

Also ran S-TUI stress for awhile. Temps never got above 60C.

Post by George at Clug
Intel have been experiencing some instability

That's only affected their "K" and "S" series Raptor Lake CPUs. I have an
i9-14900T. And it's been seemingly a thermal issue, with the chips running
at 90-100C.

Post by George at Clug
I would prefer to start with a new, clean, working installation

Well that's what this is. I just assembled the hardware, and just installed
Debian last night.

If I have the time, I may try that, i.e., "downgrade" to a new Debian 12.6.0
install to see if the instability returns. But only after I've let the
current 6.1.99 kernel show its strength.


So, anyways, my question still is just what the subject line says.

[Justin Piszcz]

Post by Mike
I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.
Then that upgraded linux-image-6.1.0-22-amd64 to -23-. So far, the system
seems stable. I'll let it run for awhile before I believe that.
So the question is: Has there recently been such an issue with the -22-
package? It seems that there were a *lot* of changes from the upstream
6.1.94 to 6.1.99, so maybe something was repaired.
I'm not sure what to doubt right now: the CPU (Intel's been having issues
with Raptor Lake, but mine's a "T" series), the motherboard (may have been
mishandled by the retailer), or Linux.
This is an offbeat question, so I understand if I never get an answer.

I posted to this list awhile ago thinking my issues were related to
the stable kernel used by debian stable. I was running into NVME
errors and seeing stack smashing errors, my i9-14900k began to fail:
https://forum.level1techs.com/t/debian-linux-stable-on-pro-ws-w680-ace-ipmi-application-segfaults-kernel-panic/212854/2

After RMA'ing the CPU with Intel and getting a new one, so far all of
the errors have resolved (for now..)

Not sure if your CPU is impacted but until I ran across the various
threads about the i9-13900/14900k (and some CPUs below are impacted as
well), it was very difficult to troubleshoot as this is the first CPU
I ever had that went bad. As others have mentioned, start with memory
tests, test the NVME drives, try to rule out other things first. Then
if everything else checks out OK, it may be worth focusing on
troubleshooting the CPU.

Justin

[Mike]

I'll call this "resolved", not "solved".

Post by Mike
I'll let it run for awhile before I believe that.

I ran the -23- kernel for four days without issue. Then I rebooted into the
previous -22- kernel, still installed. That has run for a day so far. So
the problems no longer seem to be present.

I don't know what caused them. Maybe it was just a burn-in issue with the
power brick, the motherboard, the memory, or the NVMe SSD.

[songbird]

Post by Mike
I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.
Then that upgraded linux-image-6.1.0-22-amd64 to -23-. So far, the system
seems stable. I'll let it run for awhile before I believe that.
So the question is: Has there recently been such an issue with the -22-
package? It seems that there were a *lot* of changes from the upstream
6.1.94 to 6.1.99, so maybe something was repaired.
I'm not sure what to doubt right now: the CPU (Intel's been having issues
with Raptor Lake, but mine's a "T" series), the motherboard (may have been
mishandled by the retailer), or Linux.
This is an offbeat question, so I understand if I never get an answer.

i didn't even see this post to begin with (busy time so i did
skip some message reading for a few weeks)...

however, i will note that when you are dealing with live
images you pretty much need to look at that specific thing
because other common assumptions about installation and
booting may be different than the regular images.

it's been many many years since i last booted Knoppix or
anything other than a netinst image copied to a USB stick.

on top of that if you are using new hardware the manufacturer
of the motherboard may have the bios set to do certain things
upon the first power on.

to help in the future it would have gotten a few more
eyeballs and braincells engaged had you specified which live
image and details about the motherboard.

i hope things remain stable. :)


songbird

[Andrew M.A. Cater]

Post by songbird

Post by Mike
I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.
Then that upgraded linux-image-6.1.0-22-amd64 to -23-. So far, the system
seems stable. I'll let it run for awhile before I believe that.
So the question is: Has there recently been such an issue with the -22-
package? It seems that there were a *lot* of changes from the upstream
6.1.94 to 6.1.99, so maybe something was repaired.

<snip>>

Post by songbird
however, i will note that when you are dealing with live
images you pretty much need to look at that specific thing
because other common assumptions about installation and
booting may be different than the regular images.

<snip>

Post by songbird
i hope things remain stable. :)
songbird

If you have problems after using a live image, it might be that the first
of those was to use a live image :(

The netinst and DVD installers are more mature and potentially better tested.
The live installer generally relies on different code if you use calamares,
for example.

Repeat the install with a netinst if possible and report back.

All the very best, as ever,

Andy
(***@debian.org)

[Mike]

Post by Andrew M.A. Cater
If you have problems after using a live image, it might be that the first
of those was to use a live image :(
The netinst and DVD installers are more mature and potentially better tested.
The live installer generally relies on different code if you use calamares,
for example.
Repeat the install with a netinst if possible and report back.

I repeated the install with the Live USB image.

While doing so, I recalled that *during* the "Finish the installation" step,
I initially had the system spontaneous rebooting; later attempts finished
that step properly. That alone points not to the image, but to the hardware.

The Live install--reformatting but not repartitioning the storage--completed
successfully. So, again, I don't think it was the Debian image.