Date: Thu, 6 Feb 2025 12:49:03 -0300 From: Renato Botelho <garga@FreeBSD.org> To: Chuck Tuffli <chuck@freebsd.org> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: pcib1: Timed out waiting for Data Link Layer Active messages after power blinking Message-ID: <f43ecd33-e0aa-4184-9e54-d3325441bdf0@FreeBSD.org> In-Reply-To: <CAKAYmMJaBhdyg8eWGEVowDfctF11ZkRNjc8Ow8YUx53_Zb3YMQ@mail.gmail.com> References: <144dcc6c-c7ba-4e29-9b17-dfbfee9c7d68@FreeBSD.org> <CAKAYmMJaBhdyg8eWGEVowDfctF11ZkRNjc8Ow8YUx53_Zb3YMQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 06/02/25 12:46, Chuck Tuffli wrote: > On Thu, Feb 6, 2025 at 4:39 AM Renato Botelho <garga@freebsd.org> wrote: >> >> I've been running FreeBSD CURRENT on a Thinkpad x230 for years. >> Yesterday there was a power outage that damaged one TV at home and this >> morning I noticed the laptop was possible affected too. I suspect power >> issue was the cause since I didn't upgrade it recently. >> >> It takes a long time to boot waiting for `usbus1` and during boot I see >> lots of repeated ACPI related messages >> >> pcib1: Timed out waiting for Data Link Layer Active > > This looks to be a PCI bridge that isn't working. Assuming this is > PCIe, connections between devices use a protocol to encapsulate > messages. The lowest layer of these is the Data Link Layer. This > message is saying the signalling required to start using the DLL never > completes. Once the OS is up, you might poke around via pciconf to see > if the device recovered, but given the damage to other hardware, > electrical damage seems like a reasonable conclusion here as well. I've added hint.pcib.1.disabled="1" to loader.conf to disable damaged hardware and it's working as expected again. I still couldn't find what is missing because of that but maybe one day I will notice. -- Renato Botelhohome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f43ecd33-e0aa-4184-9e54-d3325441bdf0>