On Sat, Aug 10, 2024 at 04:05:09PM -0600, Abel Abraham Camarillo Ojeda wrote: > On Sat, Aug 10, 2024, 15:46 Anon Loli <anonl...@autistici.org> wrote: > > > ----- Forwarded message from Anon Loli <anonl...@autistici.org> ----- > > (2 e-mails have been merged into this one, with a few > > additions/subtractions) > > > > Perhaps someone out there won't feel like ignoring or even banning me, this > > time. > > > > > > Date: Fri, 9 Aug 2024 21:01:26 +0000 > > From: Anon Loli <anonl...@autistici.org> > > To: t...@openbsd.org > > Subject: azalia patch: 1. crashes X11, 2. monitor loses signal entirely? > > > > Hi. > > I've compiled everything on 7.5 release and applied only 1 patch: > > https://marc.info/?l=openbsd-tech&m=171588776531605&w=2 > > > > I've noticed that while watching some videos, if I frequently spam sndioctl > > commands (aka regulate volume level): > > sndioctl output.level=+0.025 > > or > > sndioctl output.level=-0.025 > > > > then SOMETIMES X11 or something crashes... > > There are 2 types of crashes related to this bug. > > case a: > > xenodm or X11 crash and I can safely skiddadle to the 1st tty and restart > > xenodm, everything works fine after that > > > > case b: > > the entire display just stops getting signal, the computer is still > > running, > > is this some sort of harder crash? > > > > Right before both cases, the screen freezes for a few seconds. > > So basically yeah, adjusting audio volume can crash your display and stuff. > > > > Some additional info: > > I also (un)fullscreened mpv while executing shortcuts for mentioned > > sndioctl > > commands, so this might have contributed to it? > > I've ran OpenBSD for years on a few computers, and I've never had this > > happen to me, especially not a few times within like 2 hours. > > > > Tell me if you really need some more information, think of this as sendbug > > with > > the -D option for privacy, but if it's REALLY needed, I just might censor > > the > > files.. > > > > Maybe people won't ignore you if you include the needed debug information > > > > By the way, I have apmd with -L option, as well as obsdfreqd(1) runnin'. > > > > ----- End forwarded message ----- > > > >
dmesg and pcidump have been included and I've censored the most why-the-fuck-does-it-even-print-out information as well as some additional info as a precaution (like disk size). Same machine, nothing changed. apcidump won't be included because it looks sketchy as fuck, and I value my anonymity/security/literally-my-life so much that I'd rather deal with the consequences of this bug than risk sharing the acpidump information, even when decoded it's looks sketchy as fuck! You should expect as much from those that who are activist anarchists, and want to take precautions. So I hope this is enough information And usbdevs is literally just usbdevs: Controller /dev/usb0: addr 01: 1022:0000 AMD, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 Controller /dev/usb1: addr 01: 1022:0000 AMD, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub1 addr 02: 1a2c:2124 xxxxxx, USB Keyboard low speed, power 98 mA, config 1, rev 1.10 driver: uhidev0 driver: uhidev1
