Date: Tue, 8 May 2018 22:09:14 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= <freebsdnewbie@freenet.de> To: "Ilya A. Arkhipov" <rum1cro@yandex.ru> Cc: freebsd-current@freebsd.org Subject: Re: Regression Resume Lenovo T450 Message-ID: <20180508200914.GA73930@freebsd-t450.fritz.box> In-Reply-To: <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 08, 2018 at 11:16:48AM +0300, Ilya A. Arkhipov wrote: >Hi, > >I have same issue (thinkpad T450s) after resume notebook cant wake up >but on: > FreeBSD 12.0-CURRENT #0 r332796: Fri Apr 20 00:42:44 UTC 2018 >root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >with: >drm-next-kmod-4.11.g20180224 >gpu-firmware-kmod-g20180206_1 > ># sysctl debug.bootverbose=1 ># sysctl debug.acpi.suspend_bounce=1 > >In log (I think it related): >May 8 01:05:06 m1cro kernel: vgapci0: child drmn0 requested >pci_set_powerstate >May 8 01:05:06 m1cro kernel: pci0:0:2:0: Transition from D0 to D3 >May 8 01:05:06 m1cro kernel: pci0: set ACPI power state D3 on >\_SB_.PCI0.VID_ >May 8 01:05:06 m1cro kernel: pci0: failed to set ACPI power state D3 on >\_SB_.PCI0.VID_: AE_BAD_PARAMETER > >where pci0:0:2:0: >vgapci0@pci0:0:2:0: class=0x030000 card=0x503617aa chip=0x16168086 >rev=0x09 hdr=0x00 > vendor = 'Intel Corporation' > device = 'HD Graphics 5500' > class = display > subclass = VGA My T450 does resume now with an current CURRENT(r333291), but unfortunately i do not know why... I tried to track down the phenomenon. I saw that the kernel seemed not to be involved in this matter, since the old BE equipped with a new kernel was able to resume. I cloned the BE capable of resuming and startet copying userland-stuff from the "default" BE to this BE. Stuff was like bin/sbin/lib/libexec folders from / and /usr and so on. It stayed able to resume! Then i made an installworld/installkernel of r333291 into this BE, (but without mergemaster)! Even after this it stayed able to resume! Then I backed up the /etc folder of my "default" BE (which was not able to resume) and copied the /etc from the old BE to "default". After this, "default" was also able to resume again! Long story short, i'm happy my machine resumes again, but i do not have a clue why... P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. -- Manuel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180508200914.GA73930>