Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?
Ok, I will try.
Also, is it possible and/or worthwhile trying to bisect firmware versions from
the linux-firmware repo? How coupled is the firmware with the kernel
driver? E.g., can I try using firmware files from 1 year ago with current
kernel and Mesa?
> We haven't been able to repro this.
One thing that’s a bit “fishy” about my machine is that it doesn’t seem to
have a good clock:
[ 0.211436] TSC synchronization [CPU#0 -> CPU#1]:
[ 0.211436] Measured 3304683447 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.211436] tsc: Marking TSC unstable due to check_tsc_sync_source failed
…
[ 0.252117] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.252117] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[ 0.253970] clocksource: Switched to clocksource hpet
…
[ 0.580451] Unstable clock detected, switching default tracing clock to "global"
If you want to keep using the local clock, then add: "trace_clock=local"
on the kernel command line
Thanks for your input.
Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?
Ok, I will try.
Also, is it possible and/or worthwhile trying to bisect firmware versions from
the linux-firmware repo? How coupled is the firmware with the kernel
driver? E.g., can I try using firmware files from 1 year ago with current
kernel and Mesa?
> We haven't been able to repro this.
One thing that’s a bit “fishy” about my machine is that it doesn’t seem to
have a good clock:
[ 0.211436] TSC synchronization [CPU#0 -> CPU#1]: sync_source failed
"trace_ clock=local"
[ 0.211436] Measured 3304683447 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.211436] tsc: Marking TSC unstable due to check_tsc_
…
[ 0.252117] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.252117] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[ 0.253970] clocksource: Switched to clocksource hpet
…
[ 0.580451] Unstable clock detected, switching default tracing clock to "global"
If you want to keep using the local clock, then add:
on the kernel command line
Could this bug be related to that?
> I think it may be related to a change in mesa. Specifically mesa commit /gitlab. freedesktop. org/mesa/ mesa/-/ issues/ 4866
> 820dec3f7c7. For more info see
> https:/
I’ll run with Mario’s build of Mesa with that patch backported.
Thanks, Mario!
> ** Bug watch added: gitlab. freedesktop. org/mesa/ mesa/-/ issues #4866 /gitlab. freedesktop. org/mesa/ mesa/-/ issues/ 4866
> https:/
Other upstream issues that look similar:
https:/ /gitlab. freedesktop. org/drm/ amd/-/issues/ 1598 /gitlab. freedesktop. org/drm/ amd/-/issues/ 920
https:/