Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Debian stable randomly shut down

Linux Kernel, Network, and Services configuration.
Message
Author
User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Debian stable randomly shut down

#16 Post by Head_on_a_Stick »

Head_on_a_Stick wrote:use `journalctl` to investigate said logs after the next lock up.

https://www.digitalocean.com/community/ ... stemd-logs
deadbang

Stian1979
Posts: 316
Joined: 2007-07-29 14:57

Re: Debian stable randomly shut down

#17 Post by Stian1979 »

Fresh install windows way.
Image
Debian Bullseye

Stian1979
Posts: 316
Joined: 2007-07-29 14:57

Re: Debian stable randomly shut down

#18 Post by Stian1979 »

A fresh install never fixed the problem and new versions of debian did not either.
Not been using this laptop again for a while, but decided to try to get to the root of this problem.
two versions seams to always be at the end of the kernel log when this shutdowns appear.

Code: Select all

aug. 18 22:55:18 debian kernel: kauditd_printk_skb: 14 callbacks suppressed
aug. 18 22:55:18 debian kernel: audit: type=1400 audit(1660856118.311:26): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:18 debian kernel: audit: type=1400 audit(1660856118.699:27): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:18 debian kernel: audit: type=1400 audit(1660856118.951:28): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:19 debian kernel: audit: type=1400 audit(1660856119.263:29): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:19 debian kernel: audit: type=1400 audit(1660856119.527:30): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:19 debian kernel: audit: type=1400 audit(1660856119.787:31): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:20 debian kernel: audit: type=1400 audit(1660856120.051:32): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:20 debian kernel: audit: type=1400 audit(1660856120.315:33): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:20 debian kernel: audit: type=1400 audit(1660856120.567:34): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:20 debian kernel: audit: type=1400 audit(1660856120.767:35): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:23 debian kernel: kauditd_printk_skb: 12 callbacks suppressed
aug. 18 22:55:23 debian kernel: audit: type=1400 audit(1660856123.415:48): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:55:23 debian kernel: audit: type=1400 audit(1660856123.675:49): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 23:11:14 debian kernel: perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
aug. 18 23:16:39 debian kernel: perf: interrupt took too long (3146 > 3135), lowering kernel.perf_event_max_sample_rate to 63500
aug. 18 23:21:25 debian kernel: perf: interrupt took too long (5899 > 3932), lowering kernel.perf_event_max_sample_rate to 33750

Code: Select all

aug. 18 22:38:30 debian kernel: kauditd_printk_skb: 14 callbacks suppressed
aug. 18 22:38:30 debian kernel: audit: type=1400 audit(1660855110.039:26): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:30 debian kernel: audit: type=1400 audit(1660855110.291:27): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:30 debian kernel: audit: type=1400 audit(1660855110.559:28): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:30 debian kernel: audit: type=1400 audit(1660855110.811:29): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:31 debian kernel: audit: type=1400 audit(1660855111.055:30): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:31 debian kernel: audit: type=1400 audit(1660855111.299:31): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:31 debian kernel: audit: type=1400 audit(1660855111.555:32): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:31 debian kernel: audit: type=1400 audit(1660855111.811:33): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:32 debian kernel: audit: type=1400 audit(1660855112.059:34): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:32 debian kernel: audit: type=1400 audit(1660855112.263:35): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:35 debian kernel: kauditd_printk_skb: 12 callbacks suppressed
aug. 18 22:38:35 debian kernel: audit: type=1400 audit(1660855115.199:48): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:38:35 debian kernel: audit: type=1400 audit(1660855115.479:49): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/home>
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: Machine check events logged
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 2: d4200004000d110a
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: TSC 0 ADDR 983d8ec0 
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: PROCESSOR 0:30678 TIME 1660855396 SOCKET 0 APIC 0 microcode 815
No idea about what I am looking at :(
Image
Debian Bullseye

steve_v
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 1400
Joined: 2012-10-06 05:31
Location: /dev/chair
Has thanked: 79 times
Been thanked: 175 times

Re: Debian stable randomly shut down

#19 Post by steve_v »

Stian1979 wrote: 2022-08-21 20:25No idea about what I am looking at

Code: Select all

aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: Machine check events logged
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 2: d4200004000d110a
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: TSC 0 ADDR 983d8ec0 
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: PROCESSOR 0:30678 TIME 1660855396 SOCKET 0 APIC 0 microcode 815
What you're looking at is a hardware problem. Your CPU is not pleased, and assuming you're not oveclocking or undervolting it prime suspects would be memory, power, or cooling.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

Stian1979
Posts: 316
Joined: 2007-07-29 14:57

Re: Debian stable randomly shut down

#20 Post by Stian1979 »

steve_v wrote: 2022-08-22 01:37

What you're looking at is a hardware problem. Your CPU is not pleased, and assuming you're not oveclocking or undervolting it prime suspects would be memory, power, or cooling.
I would instantly reject cooling since I can instantly turn it back on en run it for anything between 2 hours and 2minuntes. There is no consistency about what it will happen.
The OS will freeze and will reboot after about 30sec, but sometimes shut down directly.
When you say memory do you mean RAM or do you mean memory at the CPU/GPU?
Image
Debian Bullseye

steve_v
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 1400
Joined: 2012-10-06 05:31
Location: /dev/chair
Has thanked: 79 times
Been thanked: 175 times

Re: Debian stable randomly shut down

#21 Post by steve_v »

Stian1979 wrote: 2022-08-22 09:08When you say memory do you mean RAM or do you mean memory at the CPU/GPU?
I was really just going for the usual "check cooling, do a memory test, make sure your PSU is in spec". Ya know, first-things-first basic hardware checks.
If this machine is more than a few years old, it's probably worth a quick look-see over the motherboard as well, for any obvious defects like green-death or dodgy VRM capacitors.

As far as memory goes, a bad DIMM (or DIMM slot contact) is up there with the most common problems IME, and pretty easy to check with the likes of memtest86 and a bit of ye-olde parts-shuffle.
In reality though, it could be anywhere between the CPU and main memory, on-die cache included. Or the CPU itself. Or the motherboard. It could even be a BIOS or CPU microcode bug.
On that last one, this didn't start happening right after some kind of firmware update, did it?

I'm no Intel engineer, so I have no idea how to properly decode that message to figure out what's going on internally.
Maybe someone else here does, but I'm not super optimistic myself. I'd love to be proven wrong, but I suspect you'll end up having to take the empirical "eliminate whatever you can and hope you find it" route TBH.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

Stian1979
Posts: 316
Joined: 2007-07-29 14:57

Re: Debian stable randomly shut down

#22 Post by Stian1979 »

Just been running two passes with memtest that came up with nothing.
Been having the issues since i bought the PC and always assumed it was a OS issue until i did a fresh install and still having the issue.
Keeping the system monitor up to check for any temperatures or abnormal use of resources.
Hoping simply disable something or blacklist something would solve this crap, but I guess not ;(
Image
Debian Bullseye

Tozztie
Posts: 2
Joined: 2022-08-30 08:20

Re: Debian stable randomly shut down

#23 Post by Tozztie »

It can mean both. It could also be a memory bus (the highway between CPU and memory).. It pretty much means something is broken with the hardware. You might try to run rasdaemon or mcelog to find out some more details.

I'd also do a memtest86+ run and check if it sees some errors

Post Reply