Re: [BUG] amdgpu GPU fault detected in VM context

El Tue, 30 Jan 2024 15:28:00 -0400 Jose Maldonado escribió: > > Hello everyone! > > I have been detecting a bug in the new DRM code corresponding to > amdgpu using an RX580 (Polaris10). I am currently running -current > > **OpenBSD 7.4 GENERIC.MP#1637 amd64** > > And I'm seeing these errors th

[BUG] amdgpu GPU fault detected in VM context

Hello everyone! I have been detecting a bug in the new DRM code corresponding to amdgpu using an RX580 (Polaris10). I am currently running -current **OpenBSD 7.4 GENERIC.MP#1637 amd64** And I'm seeing these errors that appear shortly after starting Xenocara. drm:pid13609:gmc_v8_0_process_inter

chromium on -current #1637 crashes (perhaps graphic error?)

hi, after upgrading to snapshot #1637, upgraded packages, I found chromium cannot render properly. I suspect that is an issue of the graphic driver, since I encounter the issue on Alpine Linux (running unstable mesa driver) as well. Chromium generate kilobytes of logs and megabytes of ktrace outpu

Re: TSO em(4) problem

On 30.1.2024. 13:33, Alexander Bluhm wrote: > On Tue, Jan 30, 2024 at 12:07:08PM +0100, Hrvoje Popovski wrote: >> On 30.1.2024. 9:27, Hrvoje Popovski wrote: >>> I will prepare one box for this kind of traffic and will contact you and >>> marcus >>> In theory when going through vlan interface i

kernel panic, PCe APU3, unknown trap in user mode, nodejs?

Hi, I found one of my PC Engines APU3 in kernel panic. What changed recently on this machine, I started node.js on it about two days ago. - it runs local installation of Zigbee2MQTT - nodejs / Zigbee2MQTT opens /dev/cuaU0 - cuaU0 is ITEAD SONOFF Zigbee 3.0 USB Dongle Plus V2 This is very new wor

Re: TSO em(4) problem

On Tue, Jan 30, 2024 at 12:07:08PM +0100, Hrvoje Popovski wrote: > On 30.1.2024. 9:27, Hrvoje Popovski wrote: > > I will prepare one box for this kind of traffic and will contact you and > > marcus > > > >> In theory when going through vlan interface it should remove > >> M_VLANTAG. But something

pfsync in 7.4 generating much larger amount of traffic than 7.3

Hello, I've been trying to track down what exactly is causing such a large increase in traffic on pfsync(4) interfaces on several of the firewall pairs I've upgraded to 7.4. All have recent errata applied. custedge1$ doas syspatch -l 002_msplit 003_patch 004_ospfd 005_tmux 006_httpd 007_perl 008

Re: TSO em(4) problem

On 30.1.2024. 9:27, Hrvoje Popovski wrote: > I will prepare one box for this kind of traffic and will contact you and > marcus > >> In theory when going through vlan interface it should remove >> M_VLANTAG. But something must be wrong and I wonder what. >> >> bluhm Hi, I've managed to trigger w

Re: TSO em(4) problem

On 29.1.2024. 15:29, Alexander Bluhm wrote: > On Sat, Jan 27, 2024 at 08:08:35AM +0100, Hrvoje Popovski wrote: >> On 26.1.2024. 22:47, Alexander Bluhm wrote: >>> On Fri, Jan 26, 2024 at 11:41:49AM +0100, Hrvoje Popovski wrote: I've manage to reproduce TSO em problem on anoter setup, unfortunat

Re: OpenBSD 7.4/amd64 on APU4D4 - kernel panic

> "uhidev" not "unidev", There was a typo in my previous email, but there is a correct entry in /etc/bsd.re-config. I removed "disable upd" from /etc/bsd.re-config and now my UPS is handled by ugen. ugen0 at uhub0 port 4 "American Power Conversion Smart-UPS 2200 FW:UPS 09.3 / ID=18" rev 2.00/1