Re: Unable to boot -current without disabling amdgpu

On Tue, Jan 23, 2024 at 12:07:05PM -0500, Josh Rickmar wrote: > On Tue, Jan 23, 2024 at 10:55:26AM -0500, Josh Rickmar wrote: > > Latest -current is unhappy with my amd64 desktop. I'm assuming this > > is due to the recent drm sync to newer Linux. My GPU is a RX Vega 64. > > > > It seems to

GPU acceleration (amdgpu) works with MBR install, but not with GPT install

>Synopsis: GPU acceleration (amdgpu) works with MBR install, but not with >GPT install >Category: system >Environment: System : OpenBSD 7.3 Details : OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT 2023

Re: Reproducible crash on repeatedly running OpenGL-accelerated games

On Mon, May 02, 2022 at 04:56:30PM +1000, Jonathan Gray wrote: > On Mon, May 02, 2022 at 10:16:16AM -0600, Thomas Frohwein wrote: > > > > Here, it triggered after running the game twice with less than 30 > > seconds of gameplay and then launching it a third time. > > &

Re: Reproducible crash on repeatedly running OpenGL-accelerated games

I have switched the drive into my older Skylake laptop and I get the same problem there, too. This time, I ran into the following error showing up in the console after the application crashed: panic: Data modified on freelist: word 4 of object 0x81d7e800 size 0x258 previous type temp

Reproducible crash on repeatedly running OpenGL-accelerated games

>Synopsis: Reproducible crash on repeatedly running mono+SDL2 games >Category: kernel amd64 >Environment: System : OpenBSD 7.1 Details : OpenBSD 7.1-current (GENERIC.MP) #487: Sat Apr 30 09:14:44 MDT 2022

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Wed, 2 Feb 2022 10:41:06 +1100 Jonathan Gray wrote: > > does this diff to provide stolen memory data help? > > I have committed this minus the printf change > would still be interested to hear if it helps This fixed it! I built a new kernel after checking out the latest commits below, and

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Tue, 1 Feb 2022 14:56:22 +1100 Jonathan Gray wrote: > > I don't understand which process is triggering the fault. Maybe > > somebody (jsg@?) could craft a diff to figure out if this same address > > fault and which thread/context is faulting it in SP and/or with > > pool_debug = 2. > >

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Sat, 29 Jan 2022 12:15:10 -0300 Martin Pieuchot wrote: > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote: > > On Sat, 29 Jan 2022 15:19:20 +1100 > > Jonathan Gray wrote: > > > > > does this diff to revert uvm_fault.c rev 1.124 change anything? > > &

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Thu, 27 Jan 2022 06:16:04 -0700 Thomas Frohwein wrote: > > > Wanted to clarify my reddit post: > > > There is a problem when the install is encrypted (full disk encryption, w > > > bioctl). > > > Unencrypted version works fine (got to the login). > &g

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Thu, 27 Jan 2022 21:15:12 +1100 Jonathan Gray wrote: > thfr said those changes didn't help, I imagine it would be the same for > you. Both were committed. That is correct > > > > > Wanted to clarify my reddit post: > > There is a problem when the install is encrypted (full disk

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Tue, 25 Jan 2022 10:59:26 +1100 Jonathan Gray wrote: > > if you revert the previous and try this does it still boot? > > this would be more interesting to try > > corresponds to 'drm/i915: Add object locking to vm_fault_cpu' > 9fa1f4785f2a54286ccb8a850cda5661f0a3aaf9 > >

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote: > On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote: > > On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote: > > > On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote: > >

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote: > On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote: > > On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote: > > > On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...

Re: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote: > On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote: [...] > > The backtrace is kinda nonsensical, showing a copyout() call with no > > predecessor, but maybe that's just from copy*() not setting up a proper > >

crash on booting GENERIC.MP since upgrade to Jan 18 snapshot

>Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot >Category: kernel amd64 >Environment: System : OpenBSD 7.0 Details : OpenBSD 7.0-current (GENERIC) #265: Wed Jan 19 11:41:29 MST 2022

Ryzen HDA stops acceping MSI interrupts (follow-up on: sndiod stops and doesn't resume until reboot)

>Synopsis: HD audio device on Ryzen systems locks up after variable amounts of time. >Category: kernel system >Environment: System : OpenBSD 6.5 Details : OpenBSD 6.5-beta (GENERIC.MP) #50: Fri Mar 15 08:06:42 PDT 2019

Re: sndiod stops and doesn't resume until reboot

Thanks so much for looking at this! Here what I found: (Not sure if it's related to the problem, but I noticed that azalia1 attaches to "unknown product..." in dmesg.) > To confirm this, the next time this happens, after mpv terminates, > could you run in one terminal: > > cat /dev/zero