On Fri, May 10, 2019, at 16:40, Jeremy O'Brien wrote: > On Fri, May 10, 2019, at 13:29, Sebastian Benoit wrote: > > Jeremy O'Brien([email protected]) on 2019.05.10 10:30:42 -0400: > > > On Fri, May 10, 2019, at 09:58, Jonathan Gray wrote: > > > > On Fri, May 10, 2019 at 09:14:00AM -0400, Ted Unangst wrote: > > > > > Jeremy O'Brien wrote: > > > > > > I've snagged the 6.5 xenocara.tar.gz, patched it with just that > > > > > > above fix, and installed it on my system which has made X > > > > > > rock-stable for me. This is totally fine for me personally, but I > > > > > > was curious if other people have run into this issue on their 6.5 > > > > > > installs, and if so, is this something worth pushing a reliability > > > > > > errata out for? I'm unfamiliar with how the process traditionally > > > > > > works so please excuse me if the question is outlandish. > > > > > > > > > > security issues and major reliability issues. but we try not to spend > > > > > all our > > > > > time making errata. that fix may be a contender. depends on how widely > > > > > reported it is. > > > > > > > > > > > > > vga arbiter is only used with multiple cards which isn't the common case > > > > > > > > > > That's how I understood the bug too, but when I enabled a debug build of > > > xenocara and examined the core dump after a crash, I had the same > > > "VGAarbiterSpriteMoveCursor" recursive-stack backtrace as in that bug > > > report. > > > > I dont know much about xenocara, but i think that including dmesg and > > maybe /var/log/Xorg.0.log output in your mail can't hurt. > > > > I already have a bug report sent to bugs@ > > https://marc.info/?l=openbsd-bugs&m=155716824903439&w=2 > >
Gah sorry. I confused myself. The report I linked has nothing to do with the (already fixed in -current) VGAarbiterSpriteMoveCursor issue.
