Lenovo crashes on resume on battery problem

[Robert Moskowitz]

I am at a meeting and resumed on battery.  The system started up and 
pretty much shut right off.

On reboot I saw a message which I found be grepping /var/log/message

Apr  1 08:45:51 LX140e-3 kernel: ACPI: _SB_.PCI0.LPC0.EC__.HKEY: BCTG 
evaluated
  but flagged as error
Apr  1 08:45:51 LX140e-3 kernel: thinkpad_acpi: Error probing battery 2
Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension failed to 
load: ThinkP
ad Battery Extension
Apr  1 08:45:51 LX140e-3 kernel: ACPI Warning: SystemIO range 
0x0000000000000B00
-0x0000000000000B08 conflicts with OpRegion 
0x0000000000000B00-0x0000000000000B0
F (_SB.PCI0.SMB.SMB0) (20240827/utaddress-204)
Apr  1 08:45:51 LX140e-3 kernel: ACPI: OSL: Resource conflict; ACPI 
support miss
ing from driver?
Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension unregistered: 
ThinkPad
  Battery Extension
Apr  1 08:45:51 LX140e-3 kernel: input: ThinkPad Extra Buttons as 
/devices/platf
orm/thinkpad_acpi/input/input15

This is not good!

BTW, why Battery 2?  There is only one battery on this notebook (unless 
you count the BIOS battery)

Is this a bug I should submit, or is there something I should install?

thanks

[Robert Moskowitz]

And I am having no apparent issue operating on battery.

I AM going to have to find a plug soon.  And will suspend, then resume 
while being plugged in.

On 4/1/25 9:04 AM, Robert Moskowitz wrote:
> I am at a meeting and resumed on battery.  The system started up and 
> pretty much shut right off.
>
> On reboot I saw a message which I found be grepping /var/log/message
>
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: _SB_.PCI0.LPC0.EC__.HKEY: BCTG 
> evaluated
>  but flagged as error
> Apr  1 08:45:51 LX140e-3 kernel: thinkpad_acpi: Error probing battery 2
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension failed to 
> load: ThinkP
> ad Battery Extension
> Apr  1 08:45:51 LX140e-3 kernel: ACPI Warning: SystemIO range 
> 0x0000000000000B00
> -0x0000000000000B08 conflicts with OpRegion 
> 0x0000000000000B00-0x0000000000000B0
> F (_SB.PCI0.SMB.SMB0) (20240827/utaddress-204)
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: OSL: Resource conflict; ACPI 
> support miss
> ing from driver?
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension 
> unregistered: ThinkPad
>  Battery Extension
> Apr  1 08:45:51 LX140e-3 kernel: input: ThinkPad Extra Buttons as 
> /devices/platf
> orm/thinkpad_acpi/input/input15
>
> This is not good!
>
> BTW, why Battery 2?  There is only one battery on this notebook 
> (unless you count the BIOS battery)
>
> Is this a bug I should submit, or is there something I should install?
>
> thanks

[Jeffrey Walton]

On Tue, Apr 1, 2025 at 9:05 AM Robert Moskowitz  wrote:
> I am at a meeting and resumed on battery.  The system started up and
> pretty much shut right off.
>
> On reboot I saw a message which I found be grepping /var/log/message
>
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: _SB_.PCI0.LPC0.EC__.HKEY: BCTG
> evaluated
>   but flagged as error
> Apr  1 08:45:51 LX140e-3 kernel: thinkpad_acpi: Error probing battery 2
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension failed to
> load: ThinkP
> ad Battery Extension
> Apr  1 08:45:51 LX140e-3 kernel: ACPI Warning: SystemIO range
> 0x0000000000000B00
> -0x0000000000000B08 conflicts with OpRegion
> 0x0000000000000B00-0x0000000000000B0
> F (_SB.PCI0.SMB.SMB0) (20240827/utaddress-204)
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: OSL: Resource conflict; ACPI
> support miss
> ing from driver?
> Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension unregistered:
> ThinkPad
>   Battery Extension
> Apr  1 08:45:51 LX140e-3 kernel: input: ThinkPad Extra Buttons as
> /devices/platf
> orm/thinkpad_acpi/input/input15
>
> This is not good!
>
> BTW, why Battery 2?  There is only one battery on this notebook (unless
> you count the BIOS battery)
>
> Is this a bug I should submit, or is there something I should install?

Update your firmware to the latest version before you go down a rabbit hole.

Jeff

[Robert Moskowitz]

I have had this box for a lot of years (back to F32?).  I really should 
see what the firmware levels are now...

On 4/1/25 9:53 AM, Jeffrey Walton wrote:
> On Tue, Apr 1, 2025 at 9:05 AM Robert Moskowitz  wrote:
> > I am at a meeting and resumed on battery.  The system started up and
> > pretty much shut right off.
> >
> > On reboot I saw a message which I found be grepping /var/log/message
> >
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: _SB_.PCI0.LPC0.EC__.HKEY: BCTG
> > evaluated
> >    but flagged as error
> > Apr  1 08:45:51 LX140e-3 kernel: thinkpad_acpi: Error probing battery 2
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension failed to
> > load: ThinkP
> > ad Battery Extension
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI Warning: SystemIO range
> > 0x0000000000000B00
> > -0x0000000000000B08 conflicts with OpRegion
> > 0x0000000000000B00-0x0000000000000B0
> > F (_SB.PCI0.SMB.SMB0) (20240827/utaddress-204)
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: OSL: Resource conflict; ACPI
> > support miss
> > ing from driver?
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension unregistered:
> > ThinkPad
> >    Battery Extension
> > Apr  1 08:45:51 LX140e-3 kernel: input: ThinkPad Extra Buttons as
> > /devices/platf
> > orm/thinkpad_acpi/input/input15
> >
> > This is not good!
> >
> > BTW, why Battery 2?  There is only one battery on this notebook (unless
> > you count the BIOS battery)
> >
> > Is this a bug I should submit, or is there something I should install?
>
> Update your firmware to the latest version before you go down a rabbit hole.
>
> Jeff

[Robert Moskowitz]

How can I find out my firmware ver without rebooting into setup?  Is 
there some Linux tool to report this?

It looks like from

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...

That the last update was 2020.  And I SHOULD be able to create a boot 
image to update the firmware.

But specifically for battery driver, all they have is a Windows exe.

On 4/1/25 9:53 AM, Jeffrey Walton wrote:
> On Tue, Apr 1, 2025 at 9:05 AM Robert Moskowitz  wrote:
> > I am at a meeting and resumed on battery.  The system started up and
> > pretty much shut right off.
> >
> > On reboot I saw a message which I found be grepping /var/log/message
> >
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: _SB_.PCI0.LPC0.EC__.HKEY: BCTG
> > evaluated
> >    but flagged as error
> > Apr  1 08:45:51 LX140e-3 kernel: thinkpad_acpi: Error probing battery 2
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension failed to
> > load: ThinkP
> > ad Battery Extension
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI Warning: SystemIO range
> > 0x0000000000000B00
> > -0x0000000000000B08 conflicts with OpRegion
> > 0x0000000000000B00-0x0000000000000B0
> > F (_SB.PCI0.SMB.SMB0) (20240827/utaddress-204)
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: OSL: Resource conflict; ACPI
> > support miss
> > ing from driver?
> > Apr  1 08:45:51 LX140e-3 kernel: ACPI: battery: extension unregistered:
> > ThinkPad
> >    Battery Extension
> > Apr  1 08:45:51 LX140e-3 kernel: input: ThinkPad Extra Buttons as
> > /devices/platf
> > orm/thinkpad_acpi/input/input15
> >
> > This is not good!
> >
> > BTW, why Battery 2?  There is only one battery on this notebook (unless
> > you count the BIOS battery)
> >
> > Is this a bug I should submit, or is there something I should install?
>
> Update your firmware to the latest version before you go down a rabbit hole.
>
> Jeff

[Jeffrey Walton]

On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  wrote:
> How can I find out my firmware ver without rebooting into setup?  Is
> there some Linux tool to report this?

dmidecode
> It looks like from
>
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...
>
> That the last update was 2020.  And I SHOULD be able to create a boot
> image to update the firmware.
>
> But specifically for battery driver, all they have is a Windows exe.

Jeff

[Robert Moskowitz]

On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  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

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
> > It looks like from
> >
> > https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...
> >
> > That the last update was 2020.  And I SHOULD be able to create a boot
> > image to update the firmware.
> >
> > But specifically for battery driver, all they have is a Windows exe.
>
> Jeff

[Jeffrey Walton]

On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz  wrote:
> On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> > On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  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 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

[Germano Massullo]

Il 01/04/25 16:22, Robert Moskowitz ha scritto:
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...
>
> [...]
>
> But specifically for battery driver, all they have is a Windows exe.

I don't see any battery driver entry in that page

[Robert Moskowitz]

On 4/1/25 11:03 AM, Jeffrey Walton wrote:
> On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz  wrote:
> > On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> > > On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  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

[Robert Moskowitz]

On 4/1/25 11:10 AM, Germano Massullo wrote:
> Il 01/04/25 16:22, Robert Moskowitz ha scritto:
> > https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...
> >
> > [...]
> >
> > But specifically for battery driver, all they have is a Windows exe.
>
> I don't see any battery driver entry in that page

From

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-...

And the power and battery driver on that page is for Windows,

[Roger Heflin]

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  wrote:
> On 4/1/25 11:03 AM, Jeffrey Walton wrote:
> > On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz  wrote:
> > > On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> > > > On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Robert Moskowitz]

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  wrote:
> > On 4/1/25 11:03 AM, Jeffrey Walton wrote:
> > > On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz  wrote:
> > > > On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> > > > > On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz  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 -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue