re: kern/49744 console is blank drm2/radeon

[matthew green <mrg%eterna23.net@localhost>]

Rin Okuyama writes:
> Martin Neitzel kindly reports that X11 works just fine on
> HP Proliant DL360-Gen6 with ATI ES1000, if the workaround for
> this PR is disabled:
>
> https://mail-index.netbsd.org/current-users/2024/10/10/msg045709.html
>
> Note that DL380 with ATI ES1000 did not work at that time.
>
> Can we switch `radeon_pci_ignore_r100_r200` to false by default,
> or just revert the workaround itself?
>
> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/external/bsd/drm2/radeon/radeon_pci.c.diff?r1=1.9&r2=1.10&f=h
>
> Can someone still test recent -current or netbsd-10 on the
> affected machines?

unfortunately, nothing has changed for me on my affected old
system.  X11 hangs when starting up, and there's this spew in
dmesg every second:

[  3358.002691] radeon0: error: error: ring 0 stalled for more than 72010msec
[  3358.002691] radeon0: warn: GPU lockup (current fence id 0x0000000000000003 last fence id 0x0000000000000005 on ring 0)
[  3358.502708] radeon0: error: error: ring 0 stalled for more than 72510msec
[  3358.502708] radeon0: warn: GPU lockup (current fence id 0x0000000000000003 last fence id 0x0000000000000005 on ring 0)

wsfb works.  perhaps we could enable r100/r200, but make the
default driver for these in X itself be wsfb not radeon, and
then it becomes much easier to test with a basic xorg.conf
vs. a patched kernel.

actually, this userland is older, and i only upgraded the
kernel, so i'll try that next.


.mrg.