Re: OpenBSD 6.8 - softraid issue: "uvm_fault(0xffffffff821f5490, 0x40, 0, 1) -> e"

On 3/4/21 12:19 PM, Stuart Henderson wrote: No need to patch to check this, it is null, see r9 in sh reg (it is %reg9 in my disassembly) Cool! And sorry for overlook. Anyway, then "goto bad" from the patch is what we need. Just let's see if this is enough for OpenBSD to recover from this

Re: OpenBSD 6.8 - softraid issue: "uvm_fault(0xffffffff821f5490, 0x40, 0, 1) -> e"

On 3/3/21 7:45 PM, Mark Schneider wrote: I can run some tests with modified BIOS settings (IDE instead of AHCI) and the Samsung PRO 860 SSDs. From my point of view it is important to check and optimize the I/O error handling as I/O errors can always happen and in such case the OS should

Re: OpenBSD 6.8 - softraid issue: "uvm_fault(0xffffffff821f5490, 0x40, 0, 1) -> e"

On 3/3/21 3:25 PM, Stuart Henderson wrote: On 2021/03/03 15:10, Karel Gardas wrote: Looks like you are not the only one having issue with AMD chipset and new samsung SSD: https://eu.community.samsung.com/t5/computers-it/860-evo-250gb-causing-freezes-on-amd-system/td-p/575813/page/2 https

Re: OpenBSD 6.8 - softraid issue: "uvm_fault(0xffffffff821f5490, 0x40, 0, 1) -> e"

On 3/2/21 11:09 PM, Mark Schneider wrote: It looks like "not so perfect" mix of a bit outdated ASUS mainboard / it's BIOS, less old Samsung PRO 860 512GB or 1TB SSD drives and the handlig of I/O errors in OpenBSD 6.8 or 6.9beta. bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdc312018 (61 entries)

current May 12 -> May 13 snapshot using sysupgrade is not automatic.

Hello, just to report that today's snapshot obtained by sysupgrade tool from ftp.spline.de is not supporting fully automatic upgrade. The ramdisk kernel's upgrade process was stuck on classical question install/upgrade/whatever as used when automatic upgrade is not performed. Dmesg reports

Re: -current on Dell Optiplex 755: panic: attempt to execute user address 0x0 in supervisor mode

I see very similar crash here on todays -current on ThinkPad T500 too. Karel On 4/24/19 5:33 PM, Matthieu Herrb wrote: panic: attempt to execute user address 0x0 in supervisor mode Stopped at db_enter+0x10: popq%rbp TIDPIDUID PRFLAGS PFLAGS CPU COMMAND

Re: wdc_atapi_start panic in VirtualBox 6.0.2

55c3b2c3d4 != 0x7a3a0755c3b2cbd4 > > > > > > Jan 20 snapshot: > Directory does not contain SHA256.sig. Continue without verification? [no] yes > Installing bsd 0% | | 0 > --:--ETAw > dc_atapi_start: not ready, st = 40 > Installing bsd 59% |*** | 8960 00:01 > ETAf > atal protection fault in supervisor mode > trap type 4 code 0 rip 810095e5 cs 8 rflags 10286 cr2 220564000 cpl > 6 r > sp 800014bdb028 > gsbase 0x8118aff0 kgsbase 0x0 > panic: trap type 4, code=0, pc=811095e5 > syncing disks...7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 > -- Karel Gardas

Re: sshd high cpu : system freeze

Based on my experience, softdep may be very fragile on the fast system with slow drive. I guess what you see may be softdep own issue. On Sun, 20 Jan 2019 11:49:32 +0100 Thuban wrote: > I've got some more. > After mounting the disk with "softdep" option, I saw this message on the > console a

Re: X not working on T500 on today's snapshot

On Fri, 26 Oct 2018 10:20:49 +0200 (CEST) Mark Kettenis wrote: > > Date: Fri, 26 Oct 2018 09:31:56 +1100 > > From: Jonathan Gray > > > > On Thu, Oct 25, 2018 at 08:12:13PM +0200, Mark Kettenis wrote: > > > Found the issue. The kernel advertises support for the I915_MMAP_WC > > > option, but

Re: X not working on T500 on today's snapshot

On Thu, 25 Oct 2018 02:24:08 +1100 Jonathan Gray wrote: > On Wed, Oct 24, 2018 at 04:06:57PM +0200, Karel Gardas wrote: > > On Wed, Oct 24, 2018 at 3:00 PM Jonathan Gray wrote: > > > You can create /etc/X11/xorg.conf with > > > > > > Section "Devic

Re: X not working on T500 on today's snapshot

On Wed, 24 Oct 2018 15:13:36 +0100 Stuart Henderson wrote: > On 2018/10/24 16:09, Karel Gardas wrote: > > On Wed, Oct 24, 2018 at 4:06 PM Karel Gardas wrote: > > > > > > On Wed, Oct 24, 2018 at 3:00 PM Jonathan Gray wrote: > > > > You can create /etc/X11

Re: X not working on T500 on today's snapshot

On Wed, Oct 24, 2018 at 4:06 PM Karel Gardas wrote: > > On Wed, Oct 24, 2018 at 3:00 PM Jonathan Gray wrote: > > You can create /etc/X11/xorg.conf with > > > > Section "Device" > > Identifier "intel device" > > Driver &q

Re: X not working on T500 on today's snapshot

On Wed, Oct 24, 2018 at 3:00 PM Jonathan Gray wrote: > You can create /etc/X11/xorg.conf with > > Section "Device" > Identifier "intel device" > Driver "intel" > EndSection This works nicely and I'm again in X window System although it now behaves a bit differently with second

Re: X not working on T500 on today's snapshot

On Wed, Oct 24, 2018 at 1:48 PM Jonathan Gray wrote: > > The xserver currently tries to load the modesetting driver on >= gen 4 > for intel (gm45 is gen4). Does forcing the "intel" driver to load > instead change anything? Looking into how to do that. Anyway, remark: Sunday's Oct 21 snapshot

X not working on T500 on today's snapshot

Hello, after updating to today's current (obtained 2018-10-24 around 8-9 CET from ftp.spline.de) snapshot my T500 stopped showing Xenodm logging window and rcctl tells that xenodm failed to start. My attempt to startx as ordinary user also failed. On console I see those kernel messages:

Snapshot bsd.rd fails to boot on Fujitsu TX1320M1

Hello, snapshot obtained from spline.de, build from Sep 14 stops booting (bsd.rd) on Fujitsu Primergy TX 1320 M1. The machine BIOS/BMC firmware was updated June/July 2018. The output of boot looks: booting hd0a:/bsd.rd.snap: 3502922+1496064+3887944+0+598016

upgrade not working on -current as of today.

Hello, attempt to updrade to todays' -current (CEST time) was not successful since upgrade script looks kind of broken. - it lists a lot of errors of rm /dev/ running over all drives and all letters and - after selecting keyboard layout and after selecting drive, it simply finishes

Re: uvm_fault while running X and quitting Firefox

I've been running Nov 1 snapshot. The problem is that on EU-based mirror no new snapshot than Nov 1 exist yet. On Fri, Nov 3, 2017 at 9:22 PM, Alexander Bluhm wrote: > On Fri, Nov 03, 2017 at 07:06:34PM +0100, Matthias Schmidt wrote: >> my system dropped into ddb when

Re: uvm_fault while running X and quitting Firefox

I've seen very similar issue while running chrome over ssh -X tunnel from my OpenBSD machine, displaying on my Solaris' X11 display. So it's not only firefox related... On Fri, Nov 3, 2017 at 7:17 PM, Matthias Schmidt wrote: > Hi, > > * Matthias Schmidt wrote: >> Hi, >> >> my

Re: Relayd memory leak crashes system with large file transfer

I'm also hit by this, but I'm not sure if this is a bug or rather simplified implementation. My scenario is to use relayd as a tls-accelerator for Nexus. I've needed to allocate 12GB RAM to OpenBSD VM in order to be able to push 2.5GB file to Nexus. Please note that although relayd basically

relayd: child sigsegv on relayctl poll cmd.

Hello, tested on 6.2 and on 6.2-current. relayctl poll command invoked even as ordinary user may segfault one of relayd child processes hence failing whole relayd. The process which fails is "relayd: hce (relayd)" and it fails with following crash backtrace: Program received signal SIGSEGV,

X -configure crashes on 5.7 while running inside VirtualBox

Synopsis: X server crashes when X -configure is run Category: system Environment: System : OpenBSD 5.7 Details : OpenBSD 5.7 (GENERIC.MP) #881: Sun Mar 8 11:04:17 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Re: X -configure crashes on 5.7 while running inside VirtualBox

As additional information I'm attaching xorg.log file. Also I've tried to have a look at core file, but it looks like it's not generated even if it's allowed (verified by `ulimit` which claims unlimited block for corefile). I've attempted to run X in gdb, but this is even more confusing