System suddenly shutsdown after few seconds of logging in

dodogames

dodogames

Hi all! This is more or less a follow up to my previous post. Basically, I originally waited for quite sometime before I eventually found a temporary solution that is USB tethering which allowed me to proceed beyond installation.

To put it simple, things worked great as I setup stuff like sudo, the right graphics driver (and microcode) and eventually xfce. However, I ran into a new problem as whenever I login to xfce through lightdm, it suddenly shuts down after a few seconds (by "suddenly shuts down", I mean it throws me back into console briefly before the system turns off without having a chance to see any text displayed). Using something like single-user mode does not do this but I wasn't sure what to do there given that it's my first time touching it. I noticed that upon starting the system, I can see that / was not properly dismounted or something which makes me think that this whole thing is forced?

Could this be some kind of problem from my laptop or is there something else that i perhaps may have messed up? I'm happy to provide any details if needed.
 
dodogames said:
I can see that / was not properly dismounted or something which makes me think that this whole thing is forced?
Click to expand...
This just means the system was indeed not shutdown "cleanly", often happens after the system crashed pretty hard. Could be a hardware issue, could be a software/driver issue. Or a combination of both, panic(9).

Anything in /var/log/messages? Try to go back to before the messages showing the system boots. It typically starts with these messages:
Code: 
Nov 14 09:39:46 chibacity syslogd: kernel boot file is /boot/kernel/kernel
Nov 14 09:39:46 chibacity kernel: ---<<BOOT>>---
Nov 14 09:39:46 chibacity kernel: Copyright (c) 1992-2025 The FreeBSD Project.
Nov 14 09:39:46 chibacity kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 14 09:39:46 chibacity kernel:       The Regents of the University of California. All rights reserved.
Nov 14 09:39:46 chibacity kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 14 09:39:46 chibacity kernel: FreeBSD 15.0-STABLE stable/15-n281152-0fb0ba51d8bc GENERIC amd64
So you want to take a hard look at the messages just before that.
 
Well as it turns out, there's some big mess up in install that I may have to reinstall so which explains weird behavior.

Also, can I ask a question about ports here or do I have to open another post as well?
 
SirDice said:
This just means the system was indeed not shutdown "cleanly", often happens after the system crashed pretty hard. Could be a hardware issue, could be a software/driver issue. Or a combination of both, panic(9).

Anything in /var/log/messages? Try to go back to before the messages showing the system boots. It typically starts with these messages:
Code: 
Nov 14 09:39:46 chibacity syslogd: kernel boot file is /boot/kernel/kernel
Nov 14 09:39:46 chibacity kernel: ---<<BOOT>>---
Nov 14 09:39:46 chibacity kernel: Copyright (c) 1992-2025 The FreeBSD Project.
Nov 14 09:39:46 chibacity kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 14 09:39:46 chibacity kernel:       The Regents of the University of California. All rights reserved.
Nov 14 09:39:46 chibacity kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 14 09:39:46 chibacity kernel: FreeBSD 15.0-STABLE stable/15-n281152-0fb0ba51d8bc GENERIC amd64
So you want to take a hard look at the messages just before that.
Click to expand...
I could barely find anything except for a acpi suspend that seems to trigger without me doing anything (yes i went back to having weird behavior with correct install).

If this is about battery one then i actually have a terrible battery to the point that the very second i unplug the charger, the laptop instantly turns off and goes unusable until re-plugging the charger.

Here's the full contents of the file below.
 

Attachments

So i decided to take a specific part of the output file to perhaps find something, i only however found this specific part repeating on each boot:
Code: 
Nov 22 16:42:53 myusb kernel:   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Nov 22 16:42:53 myusb kernel: ACPI APIC Table: <PTLTD       APIC  >
Nov 22 16:42:53 myusb kernel: acpi0: <SECCSD LH43STAR>
Nov 22 16:42:53 myusb kernel: acpi0: Power Button (fixed)
Nov 22 16:42:53 myusb kernel: cpu0: <ACPI CPU> on acpi0
Nov 22 16:42:53 myusb kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Nov 22 16:42:53 myusb kernel: atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
Nov 22 16:42:53 myusb kernel: attimer0: <AT timer> port 0x40-0x43,0x50-0x53 on acpi0
Nov 22 16:42:53 myusb kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Nov 22 16:42:53 myusb kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Nov 22 16:42:53 myusb kernel: acpi_ec0: <Embedded Controller: GPE 0x17> port 0x62,0x66 on acpi0
Nov 22 16:42:53 myusb kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Nov 22 16:42:53 myusb kernel: pci0: <ACPI PCI bus> on pcib0
Nov 22 16:42:53 myusb kernel: pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Nov 22 16:42:53 myusb kernel: pci1: <ACPI PCI bus> on pcib1
Nov 22 16:42:53 myusb kernel: pcib2: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
Nov 22 16:42:53 myusb kernel: pci2: <ACPI PCI bus> on pcib2
Nov 22 16:42:53 myusb kernel: pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
Nov 22 16:42:53 myusb kernel: pci3: <ACPI PCI bus> on pcib3
Nov 22 16:42:53 myusb kernel: acpi_acad0: <AC Adapter> on acpi0
Nov 22 16:42:53 myusb kernel: acpi_lid0: <Control Method Lid Switch> on acpi0
Nov 22 16:42:53 myusb kernel: acpi_button0: <Power Button> on acpi0
Nov 22 16:42:53 myusb kernel: acpi_button1: <Sleep Button> on acpi0
Nov 22 16:42:53 myusb kernel: pcib4: <ACPI Host-PCI bridge> on acpi0
Nov 22 16:42:53 myusb kernel: pci4: <ACPI PCI bus> on pcib4
Nov 22 16:42:53 myusb kernel: acpi_tz0: <Thermal Zone> on acpi0
Nov 22 16:42:53 myusb kernel: acpi_tz1: <Thermal Zone> on acpi0
Nov 22 16:42:53 myusb kernel: atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Nov 22 16:42:53 myusb kernel: battery0: <ACPI Control Method Battery> on acpi0
Nov 22 16:59:45 myusb kernel:   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Nov 22 18:42:30 myusb kernel:   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Nov 22 18:42:30 myusb kernel: ACPI APIC Table: <PTLTD       APIC  >
Nov 22 18:42:30 myusb kernel: acpi0: <SECCSD LH43STAR>
Nov 22 18:42:30 myusb kernel: acpi0: Power Button (fixed)
Nov 22 18:42:30 myusb kernel: cpu0: <ACPI CPU> on acpi0
Nov 22 18:42:30 myusb kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Nov 22 18:42:30 myusb kernel: atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
Nov 22 18:42:30 myusb kernel: attimer0: <AT timer> port 0x40-0x43,0x50-0x53 on acpi0
Nov 22 18:42:30 myusb kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Nov 22 18:42:30 myusb kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Nov 22 18:42:30 myusb kernel: acpi_ec0: <Embedded Controller: GPE 0x17> port 0x62,0x66 on acpi0
Nov 22 18:42:30 myusb kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Nov 22 18:42:30 myusb kernel: pci0: <ACPI PCI bus> on pcib0
Nov 22 18:42:30 myusb kernel: pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Nov 22 18:42:30 myusb kernel: pci1: <ACPI PCI bus> on pcib1
Nov 22 18:42:30 myusb kernel: pcib2: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
Nov 22 18:42:30 myusb kernel: pci2: <ACPI PCI bus> on pcib2
Nov 22 18:42:30 myusb kernel: pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
Nov 22 18:42:30 myusb kernel: pci3: <ACPI PCI bus> on pcib3
Nov 22 18:42:30 myusb kernel: acpi_acad0: <AC Adapter> on acpi0
Nov 22 18:42:30 myusb kernel: acpi_lid0: <Control Method Lid Switch> on acpi0
Nov 22 18:42:30 myusb kernel: acpi_button0: <Power Button> on acpi0
Nov 22 18:42:30 myusb kernel: acpi_button1: <Sleep Button> on acpi0
Nov 22 18:42:30 myusb kernel: pcib4: <ACPI Host-PCI bridge> on acpi0
Nov 22 18:42:30 myusb kernel: pci4: <ACPI PCI bus> on pcib4
Nov 22 18:42:30 myusb kernel: acpi_tz0: <Thermal Zone> on acpi0
Nov 22 18:42:30 myusb kernel: acpi_tz1: <Thermal Zone> on acpi0
Nov 22 18:42:30 myusb kernel: atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Nov 22 18:42:30 myusb kernel: battery0: <ACPI Control Method Battery> on acpi0
Nov 22 18:42:30 myusb kernel:   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Nov 22 18:43:12 myusb acpi[1401]: suspend at 20251122 18:43:12

Additionally, waiting on the console for a while doing nothing will interrupt my input with a error saying that battery0
failed to initialize before it gives up trying. At this point, i am confident this is about battery but how do i get ACPI to stop sending suspend then?

I only thought of 2 options:

1. Remove the battery and retry again (the battery barely does anything so i doubt smth bad will happen)
2. Configure how acpi(4) works if possible?
 
You must log in or register to reply here.
Back
Top