Today I found that my server was down and went look for what could have cause it, so far, it only looks that near the last logs time this was the errors/warnings that have been logged:
I can’t interpret them though. What does that mean? Thanks!
The log is reset on every reboot. The message show are created right after system start. They are not related to the crash.
Yeah, it looks like messages from the boot process. With the flag -T you can convert the timestamps in an actual time and date. dmesg -l err,crit,warn,alert,emerg -T
You can enable persistent logs with dietpi-software and have a look at them after the next crash.
Also it would be quite nice if you can fill out the troubleshoot template, which is generated when you start a new thread in “troubleshooting” category.
Can you also share some info about your system, do you boot from an external USB device?
While I might agree with you, that’s something odd because when I woke up today the system was unresponsive and I had to power off/on at around 10 am. Then, I checked the logs and I had those logs (along with others) up until 4 am and then logs from 10 am (after reboot) onwards. So it seems that it kept logs before the reboot and that what I posted is actually (and that I’m sure) before the reboot.
Edit: I think I already have that flag set to persist the logs after the reboot so that might explain.
Kernel logs above are created after reboot. You do don’t share anything from before.
I guess you’re system crashed after 4am. Therefore time stamp of first system messages should be at around 4:17 after reboot. Because your system is recovering a fixed time we save every hour at the 17th minute. This time is valid until your system successfully completed a network time sync. At this point you will see time jumping from 4am to the current time.
The thing is that the system didn’t reboot on its own. It was unresponsive in the morning, I had to plug it off/on to reboot it. Couldn’t even access it before that.
The system usually don’t reboot on it is own. If it goes down due to whatever reason, it stays down. As said above, logs will be cleared on reboot or power cycle. To keep them, you would need to make them persistent.
But that’s what I’ve been trying to say. I already had it persistent enabled. That log was before the manual reboot.
you mean the 4 lines you shared on your screenshot on your first post? They are created directly after reboot. The last line has a time stap of 4 seconds after system has been started.
I don’t get it. To be honest, either I’m explaining wrong or something is off. Those 4 lines happened at 4 AM. Until 4 AM, I had a lot of other (normal) logs. I woke up at 10 AM, checked and my server was not working. I did a manual reboot at that time and checked the logs. Then I start having logs with timestamps of 10 AM and onwards. Between 4 AM and 10 AM there are no logs registered. How is is possible that:
- The system rebooted “alone” at 4 AM?
- Then it stop being responsive at that time as well (?)
You shared a picture containing 4 lines. Nothing else. These 4 lines have a timestep in seconds relative to system start up. Means, the 4th line hast been created 4 seconds after system has been started. Not at 4am.
But this is because the screenshot cut that part, but there’s a timestamp if you just use journalctl and I saw that it was a 4 am, I can provide the full log but it’s quite big.
You can put the log to a file and attach it.
But as said, during reboot, system will restore the last valid time stamp from disk. The time stamp we save once the hour at the 17th minute. If you see the firs time stamp at 4:17, means the system is using the backup time is it doesn’t know the current time. This does not indicate a time or log entry from before the crash. These backup time will be used until your system successfully complete a network time sync. Usually there you should see time jumping from 4:17 to your current local time.
Hi, the system crashed (all services became unresponsive and had to force reboot it) again. I can’t really tell what’s causing it, other than saying that previously this didn’t happen and this last week it happened twice.
Heres the journalctl | grep kernel after the reboot, maybe something catches your eye or you might be able to provide me another command that can help me diagnose what may be causing it.
root@DietPi:~# journalctl | grep kernel
Jul 11 19:17:02 DietPi kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd083]
Jul 11 19:17:02 DietPi kernel: Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
Jul 11 19:17:02 DietPi kernel: random: crng init done
Jul 11 19:17:02 DietPi kernel: Machine model: Raspberry Pi 4 Model B Rev 1.2
Jul 11 19:17:02 DietPi kernel: efi: UEFI not found.
Jul 11 19:17:02 DietPi kernel: Reserved memory: created CMA memory pool at 0x000000002ac00000, size 64 MiB
Jul 11 19:17:02 DietPi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jul 11 19:17:02 DietPi kernel: Zone ranges:
Jul 11 19:17:02 DietPi kernel: DMA [mem 0x0000000000000000-0x000000003fffffff]
Jul 11 19:17:02 DietPi kernel: DMA32 [mem 0x0000000040000000-0x00000000fbffffff]
Jul 11 19:17:02 DietPi kernel: Normal empty
Jul 11 19:17:02 DietPi kernel: Movable zone start for each node
Jul 11 19:17:02 DietPi kernel: Early memory node ranges
Jul 11 19:17:02 DietPi kernel: node 0: [mem 0x0000000000000000-0x000000003e5fffff]
Jul 11 19:17:02 DietPi kernel: node 0: [mem 0x0000000040000000-0x00000000fbffffff]
Jul 11 19:17:02 DietPi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00000000fbffffff]
Jul 11 19:17:02 DietPi kernel: On node 0, zone DMA32: 6656 pages in unavailable ranges
Jul 11 19:17:02 DietPi kernel: On node 0, zone DMA32: 16384 pages in unavailable ranges
Jul 11 19:17:02 DietPi kernel: percpu: Embedded 29 pages/cpu s78504 r8192 d32088 u118784
Jul 11 19:17:02 DietPi kernel: pcpu-alloc: s78504 r8192 d32088 u118784 alloc=29*4096
Jul 11 19:17:02 DietPi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jul 11 19:17:02 DietPi kernel: Detected PIPT I-cache on CPU0
Jul 11 19:17:02 DietPi kernel: CPU features: detected: Spectre-v2
Jul 11 19:17:02 DietPi kernel: CPU features: detected: Spectre-v3a
Jul 11 19:17:02 DietPi kernel: CPU features: detected: Spectre-v4
Jul 11 19:17:02 DietPi kernel: CPU features: detected: Spectre-BHB
Jul 11 19:17:02 DietPi kernel: CPU features: kernel page table isolation forced ON by KASLR
Jul 11 19:17:02 DietPi kernel: CPU features: detected: Kernel page table isolation (KPTI)
Jul 11 19:17:02 DietPi kernel: CPU features: detected: ARM erratum 1742098
Jul 11 19:17:02 DietPi kernel: CPU features: detected: ARM errata 1165522, 1319367, or 1530923
Jul 11 19:17:02 DietPi kernel: alternatives: applying boot alternatives
Jul 11 19:17:02 DietPi kernel: Built 1 zonelists, mobility grouping on. Total pages: 1009408
Jul 11 19:17:02 DietPi kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=0 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:78:1F:66 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 usb-storage.quirks=7825:a2a4:u root=PARTUUID=9ecd0193-02 rootfstype=ext4 rootwait fsck.repair=yes net.ifnames=0 logo.nologo console=tty1
Jul 11 19:17:02 DietPi kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
Jul 11 19:17:02 DietPi kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Jul 11 19:17:02 DietPi kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Jul 11 19:17:02 DietPi kernel: software IO TLB: area num 4.
Jul 11 19:17:02 DietPi kernel: software IO TLB: mapped [mem 0x000000003a600000-0x000000003e600000] (64MB)
Jul 11 19:17:02 DietPi kernel: Memory: 3866800K/4102144K available (11776K kernel code, 2106K rwdata, 3688K rodata, 4160K init, 1077K bss, 169808K reserved, 65536K cma-reserved)
Jul 11 19:17:02 DietPi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jul 11 19:17:02 DietPi kernel: ftrace: allocating 39744 entries in 156 pages
Jul 11 19:17:02 DietPi kernel: ftrace: allocated 156 pages with 4 groups
Jul 11 19:17:02 DietPi kernel: trace event string verifier disabled
Jul 11 19:17:02 DietPi kernel: rcu: Preemptible hierarchical RCU implementation.
Jul 11 19:17:02 DietPi kernel: rcu: RCU event tracing is enabled.
Jul 11 19:17:02 DietPi kernel: rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Jul 11 19:17:02 DietPi kernel: Trampoline variant of Tasks RCU enabled.
Jul 11 19:17:02 DietPi kernel: Rude variant of Tasks RCU enabled.
Jul 11 19:17:02 DietPi kernel: Tracing variant of Tasks RCU enabled.
Jul 11 19:17:02 DietPi kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Jul 11 19:17:02 DietPi kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Jul 11 19:17:02 DietPi kernel: NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Jul 11 19:17:02 DietPi kernel: Root IRQ handler: gic_handle_irq
Jul 11 19:17:02 DietPi kernel: GIC: Using split EOI/Deactivate mode
Jul 11 19:17:02 DietPi kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
Jul 11 19:17:02 DietPi kernel: arch_timer: cp15 timer(s) running at 54.00MHz (phys).
Jul 11 19:17:02 DietPi kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
Jul 11 19:17:02 DietPi kernel: sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
Jul 11 19:17:02 DietPi kernel: Console: colour dummy device 80x25
Jul 11 19:17:02 DietPi kernel: printk: console [tty1] enabled
Jul 11 19:17:02 DietPi kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=216000)
Jul 11 19:17:02 DietPi kernel: pid_max: default: 32768 minimum: 301
Jul 11 19:17:02 DietPi kernel: LSM: Security Framework initializing
Jul 11 19:17:02 DietPi kernel: Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jul 11 19:17:02 DietPi kernel: Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jul 11 19:17:02 DietPi kernel: cgroup: Disabling memory control group subsystem
Jul 11 19:17:02 DietPi kernel: cblist_init_generic: Setting adjustable number of callback queues.
Jul 11 19:17:02 DietPi kernel: cblist_init_generic: Setting shift to 2 and lim to 1.
Jul 11 19:17:02 DietPi kernel: cblist_init_generic: Setting shift to 2 and lim to 1.
Jul 11 19:17:02 DietPi kernel: cblist_init_generic: Setting shift to 2 and lim to 1.
Jul 11 19:17:02 DietPi kernel: rcu: Hierarchical SRCU implementation.
Jul 11 19:17:02 DietPi kernel: rcu: Max phase no-delay instances is 1000.
Jul 11 19:17:02 DietPi kernel: EFI services will not be available.
Jul 11 19:17:02 DietPi kernel: smp: Bringing up secondary CPUs ...
Jul 11 19:17:02 DietPi kernel: Detected PIPT I-cache on CPU1
Jul 11 19:17:02 DietPi kernel: CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
Jul 11 19:17:02 DietPi kernel: Detected PIPT I-cache on CPU2
Jul 11 19:17:02 DietPi kernel: CPU2: Booted secondary processor 0x0000000002 [0x410fd083]
Jul 11 19:17:02 DietPi kernel: Detected PIPT I-cache on CPU3
Jul 11 19:17:02 DietPi kernel: CPU3: Booted secondary processor 0x0000000003 [0x410fd083]
Jul 11 19:17:02 DietPi kernel: smp: Brought up 1 node, 4 CPUs
Jul 11 19:17:02 DietPi kernel: SMP: Total of 4 processors activated.
Jul 11 19:17:02 DietPi kernel: CPU features: detected: 32-bit EL0 Support
Jul 11 19:17:02 DietPi kernel: CPU features: detected: 32-bit EL1 Support
Jul 11 19:17:02 DietPi kernel: CPU features: detected: CRC32 instructions
Jul 11 19:17:02 DietPi kernel: CPU: All CPU(s) started at EL2
Jul 11 19:17:02 DietPi kernel: alternatives: applying system-wide alternatives
Jul 11 19:17:02 DietPi kernel: devtmpfs: initialized
Jul 11 19:17:02 DietPi kernel: Enabled cp15_barrier support
Jul 11 19:17:02 DietPi kernel: Enabled setend support
Jul 11 19:17:02 DietPi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Jul 11 19:17:02 DietPi kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jul 11 19:17:02 DietPi kernel: pinctrl core: initialized pinctrl subsystem
Jul 11 19:17:02 DietPi kernel: DMI not present or invalid.
Jul 11 19:17:02 DietPi kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Jul 11 19:17:02 DietPi kernel: DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Jul 11 19:17:02 DietPi kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Jul 11 19:17:02 DietPi kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Jul 11 19:17:02 DietPi kernel: audit: initializing netlink subsys (disabled)
Jul 11 19:17:02 DietPi kernel: audit: type=2000 audit(0.016:1): state=initialized audit_enabled=0 res=1
Jul 11 19:17:02 DietPi kernel: thermal_sys: Registered thermal governor 'step_wise'
Jul 11 19:17:02 DietPi kernel: cpuidle: using governor menu
Jul 11 19:17:02 DietPi kernel: hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Jul 11 19:17:02 DietPi kernel: ASID allocator initialised with 32768 entries
Jul 11 19:17:02 DietPi kernel: Serial: AMBA PL011 UART driver
Jul 11 19:17:02 DietPi kernel: bcm2835-mbox fe00b880.mailbox: mailbox enabled
Jul 11 19:17:02 DietPi kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2023-03-17T10:50:56, variant start_cd
Jul 11 19:17:02 DietPi kernel: raspberrypi-firmware soc:firmware: Firmware hash is 82f3750a65fadae9a38077e3c2e217ad158c8d54
Jul 11 19:17:02 DietPi kernel: KASLR enabled
Jul 11 19:17:02 DietPi kernel: bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1
Jul 11 19:17:02 DietPi kernel: SCSI subsystem initialized
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver usbfs
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver hub
Jul 11 19:17:02 DietPi kernel: usbcore: registered new device driver usb
Jul 11 19:17:02 DietPi kernel: usb_phy_generic phy: supply vcc not found, using dummy regulator
Jul 11 19:17:02 DietPi kernel: usb_phy_generic phy: dummy supplies not allowed for exclusive requests
Jul 11 19:17:02 DietPi kernel: pps_core: LinuxPPS API ver. 1 registered
Jul 11 19:17:02 DietPi kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Jul 11 19:17:02 DietPi kernel: PTP clock support registered
Jul 11 19:17:02 DietPi kernel: vgaarb: loaded
Jul 11 19:17:02 DietPi kernel: clocksource: Switched to clocksource arch_sys_counter
Jul 11 19:17:02 DietPi kernel: VFS: Disk quotas dquot_6.6.0
Jul 11 19:17:02 DietPi kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 11 19:17:02 DietPi kernel: FS-Cache: Loaded
Jul 11 19:17:02 DietPi kernel: CacheFiles: Loaded
Jul 11 19:17:02 DietPi kernel: NET: Registered PF_INET protocol family
Jul 11 19:17:02 DietPi kernel: IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
Jul 11 19:17:02 DietPi kernel: tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
Jul 11 19:17:02 DietPi kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jul 11 19:17:02 DietPi kernel: TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
Jul 11 19:17:02 DietPi kernel: TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
Jul 11 19:17:02 DietPi kernel: TCP: Hash tables configured (established 32768 bind 32768)
Jul 11 19:17:02 DietPi kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
Jul 11 19:17:02 DietPi kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
Jul 11 19:17:02 DietPi kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Jul 11 19:17:02 DietPi kernel: RPC: Registered named UNIX socket transport module.
Jul 11 19:17:02 DietPi kernel: RPC: Registered udp transport module.
Jul 11 19:17:02 DietPi kernel: RPC: Registered tcp transport module.
Jul 11 19:17:02 DietPi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jul 11 19:17:02 DietPi kernel: PCI: CLS 0 bytes, default 64
Jul 11 19:17:02 DietPi kernel: hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
Jul 11 19:17:02 DietPi kernel: kvm [1]: IPA Size Limit: 44 bits
Jul 11 19:17:02 DietPi kernel: kvm [1]: vgic interrupt IRQ9
Jul 11 19:17:02 DietPi kernel: kvm [1]: Hyp mode initialized successfully
Jul 11 19:17:02 DietPi kernel: Initialise system trusted keyrings
Jul 11 19:17:02 DietPi kernel: workingset: timestamp_bits=46 max_order=20 bucket_order=0
Jul 11 19:17:02 DietPi kernel: zbud: loaded
Jul 11 19:17:02 DietPi kernel: NFS: Registering the id_resolver key type
Jul 11 19:17:02 DietPi kernel: Key type id_resolver registered
Jul 11 19:17:02 DietPi kernel: Key type id_legacy registered
Jul 11 19:17:02 DietPi kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jul 11 19:17:02 DietPi kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Jul 11 19:17:02 DietPi kernel: Key type asymmetric registered
Jul 11 19:17:02 DietPi kernel: Asymmetric key parser 'x509' registered
Jul 11 19:17:02 DietPi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
Jul 11 19:17:02 DietPi kernel: io scheduler mq-deadline registered
Jul 11 19:17:02 DietPi kernel: io scheduler kyber registered
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0x0400000000
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff])
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: PME# supported from D0 D3hot
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulator
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulator
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:01: supply vpcie12v not found, using dummy regulator
Jul 11 19:17:02 DietPi kernel: brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC)
Jul 11 19:17:02 DietPi kernel: pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
Jul 11 19:17:02 DietPi kernel: pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Jul 11 19:17:02 DietPi kernel: pci 0000:01:00.0: PME# supported from D0 D3cold
Jul 11 19:17:02 DietPi kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
Jul 11 19:17:02 DietPi kernel: pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: PCI bridge to [bus 01]
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]
Jul 11 19:17:02 DietPi kernel: bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
Jul 11 19:17:02 DietPi kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jul 11 19:17:02 DietPi kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Jul 11 19:17:02 DietPi kernel: iproc-rng200 fe104000.rng: hwrng registered
Jul 11 19:17:02 DietPi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3f000000 mem_size:0x3f600000(1014 MiB)
Jul 11 19:17:02 DietPi kernel: gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
Jul 11 19:17:02 DietPi kernel: brd: module loaded
Jul 11 19:17:02 DietPi kernel: loop: module loaded
Jul 11 19:17:02 DietPi kernel: Loading iSCSI transport class v2.0-870.
Jul 11 19:17:02 DietPi kernel: bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
Jul 11 19:17:02 DietPi kernel: unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver r8152
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver lan78xx
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver smsc95xx
Jul 11 19:17:02 DietPi kernel: pci 0000:00:00.0: enabling device (0000 -> 0002)
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: enabling device (0000 -> 0002)
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000e40000000890
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
Jul 11 19:17:02 DietPi kernel: xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
Jul 11 19:17:02 DietPi kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Jul 11 19:17:02 DietPi kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 11 19:17:02 DietPi kernel: usb usb1: Product: xHCI Host Controller
Jul 11 19:17:02 DietPi kernel: usb usb1: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
Jul 11 19:17:02 DietPi kernel: usb usb1: SerialNumber: 0000:01:00.0
Jul 11 19:17:02 DietPi kernel: hub 1-0:1.0: USB hub found
Jul 11 19:17:02 DietPi kernel: hub 1-0:1.0: 1 port detected
Jul 11 19:17:02 DietPi kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
Jul 11 19:17:02 DietPi kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 11 19:17:02 DietPi kernel: usb usb2: Product: xHCI Host Controller
Jul 11 19:17:02 DietPi kernel: usb usb2: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
Jul 11 19:17:02 DietPi kernel: usb usb2: SerialNumber: 0000:01:00.0
Jul 11 19:17:02 DietPi kernel: hub 2-0:1.0: USB hub found
Jul 11 19:17:02 DietPi kernel: hub 2-0:1.0: 4 ports detected
Jul 11 19:17:02 DietPi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jul 11 19:17:02 DietPi kernel: dwc_otg: FIQ enabled
Jul 11 19:17:02 DietPi kernel: dwc_otg: NAK holdoff enabled
Jul 11 19:17:02 DietPi kernel: dwc_otg: FIQ split-transaction FSM enabled
Jul 11 19:17:02 DietPi kernel: Module dwc_common_port init
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver uas
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver usb-storage
Jul 11 19:17:02 DietPi kernel: mousedev: PS/2 mouse device common for all mice
Jul 11 19:17:02 DietPi kernel: sdhci: Secure Digital Host Controller Interface driver
Jul 11 19:17:02 DietPi kernel: sdhci: Copyright(c) Pierre Ossman
Jul 11 19:17:02 DietPi kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Jul 11 19:17:02 DietPi kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jul 11 19:17:02 DietPi kernel: hid: raw HID events driver (C) Jiri Kosina
Jul 11 19:17:02 DietPi kernel: usbcore: registered new interface driver usbhid
Jul 11 19:17:02 DietPi kernel: usbhid: USB HID core driver
Jul 11 19:17:02 DietPi kernel: NET: Registered PF_PACKET protocol family
Jul 11 19:17:02 DietPi kernel: Key type dns_resolver registered
Jul 11 19:17:02 DietPi kernel: registered taskstats version 1
Jul 11 19:17:02 DietPi kernel: Loading compiled-in X.509 certificates
Jul 11 19:17:02 DietPi kernel: Key type .fscrypt registered
Jul 11 19:17:02 DietPi kernel: Key type fscrypt-provisioning registered
Jul 11 19:17:02 DietPi kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jul 11 19:17:02 DietPi kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jul 11 19:17:02 DietPi kernel: of_cfs_init
Jul 11 19:17:02 DietPi kernel: of_cfs_init: OK
Jul 11 19:17:02 DietPi kernel: mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
Jul 11 19:17:02 DietPi kernel: Waiting for root device PARTUUID=9ecd0193-02...
Jul 11 19:17:02 DietPi kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
Jul 11 19:17:02 DietPi kernel: usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
Jul 11 19:17:02 DietPi kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jul 11 19:17:02 DietPi kernel: usb 1-1: Product: USB2.0 Hub
Jul 11 19:17:02 DietPi kernel: hub 1-1:1.0: USB hub found
Jul 11 19:17:02 DietPi kernel: hub 1-1:1.0: 4 ports detected
Jul 11 19:17:02 DietPi kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
Jul 11 19:17:02 DietPi kernel: usb 2-1: New USB device found, idVendor=7825, idProduct=a2a4, bcdDevice=41.01
Jul 11 19:17:02 DietPi kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 11 19:17:02 DietPi kernel: usb 2-1: Product: Best USB Device
Jul 11 19:17:02 DietPi kernel: usb 2-1: Manufacturer: ULT-Best
Jul 11 19:17:02 DietPi kernel: usb 2-1: SerialNumber: 235678C218CA
Jul 11 19:17:02 DietPi kernel: usb 2-1: UAS is ignored for this device, using usb-storage instead
Jul 11 19:17:02 DietPi kernel: usb 2-1: UAS is ignored for this device, using usb-storage instead
Jul 11 19:17:02 DietPi kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
Jul 11 19:17:02 DietPi kernel: usb-storage 2-1:1.0: Quirks match for vid 7825 pid a2a4: 800000
Jul 11 19:17:02 DietPi kernel: scsi host0: usb-storage 2-1:1.0
Jul 11 19:17:02 DietPi kernel: usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
Jul 11 19:17:02 DietPi kernel: usb 2-2: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 0.00
Jul 11 19:17:02 DietPi kernel: usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jul 11 19:17:02 DietPi kernel: usb 2-2: Product: 225
Jul 11 19:17:02 DietPi kernel: usb 2-2: Manufacturer: Asm
Jul 11 19:17:02 DietPi kernel: usb 2-2: SerialNumber: 123456789A3C
Jul 11 19:17:02 DietPi kernel: scsi host1: uas
Jul 11 19:17:02 DietPi kernel: scsi 1:0:0:0: Direct-Access Asm 225 0 PQ: 0 ANSI: 6
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] 4096-byte physical blocks
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Write Protect is off
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Jul 11 19:17:02 DietPi kernel: sda: sda1
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Jul 11 19:17:02 DietPi kernel: scsi 0:0:0:0: Direct-Access CT240BX5 00SSD1 4101 PQ: 0 ANSI: 6
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: [sdb] Write Protect is off
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: [sdb] Mode Sense: 47 00 00 08
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 11 19:17:02 DietPi kernel: sdb: sdb1 sdb2
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: [sdb] Attached SCSI disk
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): INFO: recovery required on readonly filesystem
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): write access will be enabled during recovery
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): orphan cleanup on readonly fs
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): 1 orphan inode deleted
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): recovery complete
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): mounted filesystem with ordered data mode. Quota mode: none.
Jul 11 19:17:02 DietPi kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:18.
Jul 11 19:17:02 DietPi kernel: devtmpfs: mounted
Jul 11 19:17:02 DietPi kernel: Freeing unused kernel memory: 4160K
Jul 11 19:17:02 DietPi kernel: Run /sbin/init as init process
Jul 11 19:17:02 DietPi kernel: with arguments:
Jul 11 19:17:02 DietPi kernel: /sbin/init
Jul 11 19:17:02 DietPi kernel: with environment:
Jul 11 19:17:02 DietPi kernel: HOME=/
Jul 11 19:17:02 DietPi kernel: TERM=linux
Jul 11 19:17:02 DietPi kernel: NET: Registered PF_INET6 protocol family
Jul 11 19:17:02 DietPi kernel: Segment Routing with IPv6
Jul 11 19:17:02 DietPi kernel: In-situ OAM (IOAM) with IPv6
Jul 11 19:17:02 DietPi systemd[1]: Starting Create list of static device nodes for the current kernel...
Jul 11 19:17:02 DietPi kernel: fuse: init (API version 7.37)
Jul 11 19:17:02 DietPi systemd[1]: Finished Create list of static device nodes for the current kernel.
Jul 11 19:17:02 DietPi kernel: EXT4-fs (sdb2): re-mounted. Quota mode: none.
Jul 11 19:17:02 DietPi kernel: Adding 2097148k swap on /swapfile. Priority:-2 extents:10 across:2777084k FS
Jul 11 19:17:02 DietPi kernel: loop0: detected capacity change from 0 to 100544
Jul 11 19:17:02 DietPi systemd-udevd[180]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Jul 11 19:17:02 DietPi kernel: loop1: detected capacity change from 0 to 100600
Jul 11 19:17:02 DietPi kernel: loop2: detected capacity change from 0 to 95056
Jul 11 19:17:02 DietPi kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jul 11 19:17:02 DietPi kernel: loop3: detected capacity change from 0 to 95056
Jul 11 19:17:02 DietPi kernel: mc: Linux media interface: v0.10
Jul 11 19:17:02 DietPi kernel: videodev: Linux video capture interface: v2.00
Jul 11 19:17:02 DietPi kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Jul 11 19:17:02 DietPi kernel: rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned.
Jul 11 19:17:02 DietPi kernel: rpivid feb10000.codec: Device registered as /dev/video19
Jul 11 19:17:02 DietPi kernel: vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Jul 11 19:17:02 DietPi kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Jul 11 19:17:02 DietPi kernel: bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Jul 11 19:17:02 DietPi kernel: [vc_sm_connected_init]: start
Jul 11 19:17:02 DietPi kernel: vc_sm_cma_vchi_init: failed to open VCHI service (-1)
Jul 11 19:17:02 DietPi kernel: [vc_sm_connected_init]: failed to initialize shared memory service
Jul 11 19:17:02 DietPi kernel: sd 0:0:0:0: Attached scsi generic sg1 type 0
Jul 11 19:17:02 DietPi kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Jul 11 19:17:02 DietPi kernel: bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Jul 11 19:17:03 DietPi kernel: bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
Jul 11 19:17:04 DietPi kernel: bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
Jul 11 19:17:04 DietPi kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jul 11 19:17:07 DietPi kernel: loop4: detected capacity change from 0 to 8
Jul 11 19:17:08 DietPi kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Jul 11 19:17:21 DietPi kernel: EXT4-fs (sda1): recovery complete
Jul 11 19:17:21 DietPi kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
Jul 11 21:08:20 DietPi systemd[1]: Startup finished in 2.465s (kernel) + 2min 15.106s (userspace) = 2min 17.571s.
the last line (21:08) was after reboot. Also I don’t know why is it possible to have all the logs at 19:17:02 in the same second, weird.
Edit: one of the few things that I remember having done lately was setting the overclock to energy saving overvolt (-2v). Can this be the cause?
This is the boot log. There is nothing to see from before the crash. As I have tried to explain twice before, your system uses a fixed time stamp when booting until it has synchronised time with an NTP server. This initial time is always the 17th minute of an hour because we automatically run a job once an hour to update these times. (at the 17th minute) If you run journalctl without any further input, you should see the time update and change from the initial time to the current system time.
I would recommend resetting the overclocking profile first. It may be causing instability.
Never undervolt…unless you are literally underclocking the processor (forcing it to run at a CPU frequency LOWER than the advertised base clock)…the stock voltage is designed for stable un-overclocked state…if overclocking it needs more voltage…but undervolting a “stock” clocked CPU invites wonky results
RPi processors automatically adjust clock speeds and voltages based upon CPU load…
If you are looking to reduce the power usage of the RPi, I recommend using a powered USB hub, this way the power feeding the external devices no longer have to pull power THRU the RPi, might even be able to setup the cpufrequtils to “conservative” on it’s ramping profile so it return to a lower frequency/power state faster, and/or limit the top CPU frequency…but never reduce the power to the CPU…it can really cause odd behavior
Hi, I just did it because of this. I don’t have to do it, actually. It was because based on this I was left with the idea that I’d have the same performance with lower consumption/heat.
I think also it’s save.
Undervolting does not mean underclocking, the frequency stays the same, only core voltage is a bit lowered, which could lead in extreme circumstances too instabilities.
On (modern) Desktop CPUs undervolting could actually lead to higher frequencies, bc less voltage means leas heat, so the CPU has more thermal budget and the CPU tries to use that. (higher clocks or it’s able to boost for longer time)
Bc of that it’s not recommended to use a value lass than -2.
1 Like
Maybe because my server runs a lot of services (more than 10) and a few (one or two) are a bit demanding, it could result in some instability with -2v anyways. I reverted it back to 0 and will see if it doesn’t happen anymore, if it does, then that was the cause.
You can still have a look into the logs from the previous boots, if you have persistent logging enabled.
ls -la /var/log | grep syslog*
The log from the actual session is just called syslog. From the boot before is syslog.1 (or even syslog.1(.gz), from the before syslog.2.gz etc.)