Date: Sun, 6 May 2018 09:28:35 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= <freebsdnewbie@freenet.de> To: freebsd-current@freebsd.org Subject: Re: Regression Resume Lenovo T450 Message-ID: <20180506072835.GA87831@freebsd-t450.fritz.box> In-Reply-To: <20180504060717.GA88565@freebsd-t450.fritz.box> References: <20180504060717.GA88565@freebsd-t450.fritz.box>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 04, 2018 at 08:07:17AM +0200, Manuel Stühn wrote: > >Since some time now CURRENT runs very smoothly on my Lenovo T450 in >conjunction with drm-stable-kmod installed. WLAN, Suspense&Resume worked >out of the box (at least ... until now). Due to pkg(8) complaining about >wrong ABI of packages, I've made an update from r332385 (1200061) to >r333091 (1200062), and now the T450 does not resume anymore; i have to >hold the power button for some time to power it down. The >ZFS-Boot-Environment I've made beforehand updating is still capable of >resuming. > >I tried to find out which commit broke the resume for me by installing >older kernels, but even installing r332385 kernel (into the actual >r333091 userland) does not restore its capability to resume. > Some more testing has happened: Since I have a BootEnvironment capable of suspend/resume, I've tried some combinations of kernels (in fact, whole boot-folders) and unserlands. I copied the boot-folder from the BE r332385 (which works) into the current BE and restarted. This combination was NOT able to resume. But the other way around is (current boot-folder (r333091) in the r332385 based BootEnvironment) It seems to me, that not the kernel but either some change in userland or package broke the resume somehow. But I do not have a clue, which of those even can impact the resume procedure at all. Two packages came to my mind: 1. graphics/drm-stable-kmod, but the installed packages are identical for both, the "old" and the current BE. (both packages are installed from ports along with the respective buildworld+buildkernel) 2. The firmwares used by sysutils/cpupdate, but after replacing the firmware files with the firmwares from the old BE resume still doesn't work. Any ideas? -- Manuel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180506072835.GA87831>