https://bugzilla.kernel.org/show_bug.cgi?id=216371
--- Comment #11 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- > then I don't know whether it's good or bad, because > if say bad, it wake up good > if say good, it use cpufreq instead of expected amd-pstate Because you know there is a problem with this part way through it's better to force all the tests to use acpi-cpufreq. It removes more variability in the test result. > but there is already 2 rev left, so can I leave it for you the developer? I don't know what are actually left, I think I'd need to see the whole log to see what happens. With the above guidance can you narrow down to a specific commit? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
