Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Feb 2016 10:48:56 -0800
From:      John Baldwin <jhb@freebsd.org>
To:        Alexey Dokuchaev <danfe@nsu.ru>
Cc:        current@freebsd.org, mobile@freebsd.org
Subject:   Re: Thinkpad T410: resume broken
Message-ID:  <1677027.G58VU7gWm8@ralph.baldwin.cx>
In-Reply-To: <20160219123827.GA27878@regency.nsu.ru>
References:  <53762216.8020205@gmx.net> <3029262.DlAcg8ENfU@ralph.baldwin.cx> <20160219123827.GA27878@regency.nsu.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, February 19, 2016 06:38:27 PM Alexey Dokuchaev wrote:
> On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote:
> > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> > > # pciconf -lc pci0:0:0
> > > hostb0@pci0:0:0:0:      class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00
> > >     cap 09[e0] = vendor (length 9) Intel cap 2 version 1
> > 
> > Humm, perhaps PCI0 is not at 0:0.  Can you find the _ADR method for
> > _SB_.PCI0?  That contains the "slot" and "function" as two words, e.g.
> > 0x10002 would correspond to the 'pci0:1:2' device (or possibly pci0:2:1,
> > don't recall the order off the top of my head).
> 
> Seems it's all zeros:
> 
>     Device (PCI0)
>     {
>         ...
>         Name (_ADR, 0x00)  // _ADR: Address
> 
> I've uploaded the dump on freefall [1], perhaps I've missed something so
> you can have a better/sharper look.

Ok, so your BIOS is just odd / broken.  It's asked us to power that device
down to D2, but it doesn't support any power management at all, so we whine.
In practice it should be harmless and something you can ignore.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1677027.G58VU7gWm8>