Re: Regression Resume Lenovo T450
On Wed, May 09, 2018 at 10:06:19AM +0200, Niclas Zeising wrote: On 05/08/18 22:09, Manuel Stühn wrote: P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. What issues are you seeing with drm-next-kmod? I mixed my machines up. The one showing problems with drm-next was the T420: https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068725.html On my T450 i've never installed drm-next, only drm-stable-kmod. -- Manuel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
On 05/08/18 22:09, Manuel Stühn wrote: P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. What issues are you seeing with drm-next-kmod? Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
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 r...@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=0x03 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
On 06.05.2018 10:28, Manuel Stühn wrote: 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 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" 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 r...@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=0x03 card=0x503617aa chip=0x16168086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'HD Graphics 5500' class = display subclass = VGA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
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 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
On Fri, May 04, 2018 at 11:05:16AM -0700, Pete Wright wrote: On 05/03/2018 23:07, 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 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. Any ideas or hints? Which information can i provide to help investigating this matter? have you tried suspend/resume without having the drm-next kmod loaded? Same effect. No resume... -- Manuel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regression Resume Lenovo T450
On 05/03/2018 23:07, 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 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. Any ideas or hints? Which information can i provide to help investigating this matter? have you tried suspend/resume without having the drm-next kmod loaded? I have run into a couple instances of that breaking due to drm-next. if it does work w/o drm-next then it might be worth rebuilding the pkg locally (via "cd /usr/ports/graphics/drm-next-kmod && make package" for example) and see if that fixes it. there is also a sysctl knob i've set in the past to help in this area, i'll dig through my notes and see if i can find it... -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Regression Resume Lenovo T450
Since some time now CURRENT runs very smoothly on my Lenovo T450 in conjunction with drm-stable-kmod installed. WLAN, Suspense 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. Any ideas or hints? Which information can i provide to help investigating this matter? -- Manuel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
