linux-kernel - Re: Bricked Thinkpad x220 with 6.12-rc0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=whj9dbJD0mT6VUW7i16Les5waxWBb1o_XsDKrtQ9iBO1g@mail.gmail.com>
Date: Thu, 26 Sep 2024 13:27:53 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Pavel Machek <pavel@....cz>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, linux@...mhuis.info, 
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Bricked Thinkpad x220 with 6.12-rc0

On Thu, 26 Sept 2024 at 13:01, Pavel Machek <pavel@....cz> wrote:
>
> When I press power button, it starts producing some noise (hdd
> spinning up), but power light goes pulsating, not on, and I stare at
> black screen.

No beep?

> I removed everything, let it sit for a while, but behaviour was the
> same. I'm now letting machine "cool" with everything removed,
> but... It seems EC is very confused.
>
> Should I try removing CMOS battery?

It probably won't help. Last time I had something like that, it was
the EFI variables being messed up and messing up the boot as a result.
That's all in flash.

The CMOS battery these days tends to really just be for maintaining
the real-time clock.

But if it's easy to get at, it won't hurt to try either.

> Is there some magic combination I can hold during boot?

I don't see anything  about keys during power-on in

  https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/0a60739_04.pdf

but you can try the usual suspects (hold ESC / Fn / etc during power-on).

But that lenovo pdf says
 1. Make sure that every connector is connected tightly and correctly.
 2. DIMM.
 3. System board.

for your symptoms.

That said, my first suspicion would be a dead harddisk, just because
they happen and you hear noise (but it migth just be the disk getting
power on its own, and making noise even with a dead system board).

The BIOS _might_ be trying to resume from sleep from a dead disk, and
not even initializing anything else.

And the disk is easy to get at, so try just removing it first. That
might get a stuck BIOS unstuck, and you'd get a "no harddisk" error
instead of a hung BIOS that tries to access something that doesn't
reply.

At least that way you'd have a suspect.

              Linus