ARGH! Work. But not while I am at this meeting...
On 4/1/25 11:50 AM, Roger Heflin wrote:
There is no resume when something crashes because nothing ever got
saved to resume.
And I would not assume that the last message/"error" on your screen
has anything to do with the crash. The message/"error" in question
may actually happen on EVERY boot and when it crashes you see that
always there error/warning and assume it has something to do with the
error.
I would install crash and kdump-utils and add crashkernel=auto to the
kernel command line and reboot and confirm that /proc/cmdline has a
crashkernel= entry on the command line.
And then run "systemctl enable kdump" and "systemctl start kdump" and
then a few minutes later "systemctl status kdump" to make sure it is
armed.
Once that is done on anything except a low level hardware crash/reset
it will collect a crashdump, and if it does not collect a crashdump
then that makes it a lot more likely you have a hardware problem of
some sort. The crashdump will contain any dmesg entries that are in
the dmesg buffer at the time the machine panics.
On Tue, Apr 1, 2025 at 10:30 AM Robert Moskowitz <r...@htt-consult.com> wrote:
On 4/1/25 11:03 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz <r...@htt-consult.com> wrote:
On 4/1/25 10:46 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz <r...@htt-consult.com> wrote:
How can I find out my firmware ver without rebooting into setup? Is
there some Linux tool to report this?
dmidecode
BIOS Information
Vendor: LENOVO
Version: GSET74WW (2.19 )
Release Date: 04/22/2020
So I am current wrt to the basic BIOS
Very good. Now you can proceed with kernel, driver and userland troubleshooting.
And how to proceed?
BTW, my battery level got down to 70% and I crashed. System just shut off.
And interestingly, on restart, nothing is remembered from my last
session to auto restart. I thought I had that set? It seemed to work
right in my last reboot a couple weeks ago...
And I found the following:
Handle 0x001C, DMI type 22, 26 bytes
Portable Battery
Location: Rear
Manufacturer: SANYO
Name: 45N1176
Design Capacity: 62160 mWh
Design Voltage: 10800 mV
SBDS Version: 03.01
Maximum Error: Unknown
SBDS Serial Number: 0101
SBDS Manufacture Date: 2021-02-18
SBDS Chemistry: LION
OEM-specific Information: 0x00000000
Jeff
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
