User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Build Identifier: Upon booting on a laptop equipped with a Intel i5 4210U processor and a AMD R7 M260 Hybrid GPU updated to the 4.9.3 kernel. The error message "[ powerplay ] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!" appears. This message did not appear in kernel version 4.8.16. Running "glxgears" and "Chivalry: Medieval Warfare" on the secondary AMD GPU using DRI_PRIME=1 seems to work fine, so I'm unsure of the impact of the error. Reproducible: Always Steps to Reproduce: 1. Boot into Fedora on a Intel/ATI hybrid graphics laptop 2. Message appears on boot. Actual Results: Error message, Fedora boots anyway Expected Results: Clean boot
Created attachment 1241937 [details] dmesg output Attaching output of dmesg
My Dell 5547 with Intel/ATI have the same problem. The problem started with the 4.9 kernel. Attaching output of dmesg.
Created attachment 1242540 [details] dmesg Dell 5547
Hi, Any solution?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
This bug remains as of kernel 4.10.14
Created attachment 1277708 [details] updated dmesg 4.10
Created attachment 1284295 [details] dmesg Dell 5547 kernel 4.11.3-200 f25
This bug remains as of kernel 4.11.3-202.fc25.x86_64.
Created attachment 1287448 [details] dmesg Dell 5547 kernel 4.11.3-202 f25 What other information do you need?
This bug remains as of kernel 4.11.5-200.fc25.x86_64.
Created attachment 1288735 [details] mesg Dell 5547 kernel 4.11.5-200 f25
This bug remains as of kernel 4.11.6-201.fc25.x86_64.
Created attachment 1292541 [details] mesg Dell 5547 kernel 4.11.6-201 f25
(In reply to Justin M. Forbes from comment #5) > *********** MASS BUG UPDATE ************** > > We apologize for the inconvenience. There is a large number of bugs to go > through and several of them have gone stale. Due to this, we are doing a > mass bug update across all of the Fedora 25 kernel bugs. > > Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > > If you have moved on to Fedora 26, and are still experiencing this issue, > please change the version to Fedora 26. > > If you experience different issues, please open a new bug report for those. What other information do you need?
This bug remains as of kernel 4.11.7-200.fc25.x86_64.
Created attachment 1293611 [details] mesg Dell 5547 kernel 4.11.7-200 f25
This bug remains as of kernel 4.11.8-200.fc25.x86_64.
Created attachment 1294396 [details] mesg Dell 5547 kernel 4.11.8-200 f25
Fedora 26 Bug opened https://bugzilla.redhat.com/show_bug.cgi?id=1470152
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.