Re: installer problem on amd64

> Date: Thu, 25 Jul 2019 21:01:43 +0100 > From: Stuart Henderson > > Posting additional information back to the mailing list, I'm not > sure what would be causing it to stop at this point .. That's where interrupts get turned on. If there is an interrupt storm of some sorts that might stop the

Re: Only 3.5G memory seen on a 10G i386 P3Xeon system

> From: John DiMarco > Date: Fri, 28 Jun 2019 08:39:54 -0400 > > In message <20190628123238.gi42...@symphytum.spacehopper.org>you write: > >"high memory" support is very unlikely to ever happen on OpenBSD/i386. > > Hasn't openbsd had PAE support in i386 since around 2006? E.g. >

Re: Only 3.5G memory seen on a 10G i386 P3Xeon system

>Fix: enable PAE? Sorry, but no, that won't happen. We tried this years ago, but the changes needed to support a 64-bit paddr_t on 32-bit architectures were deemded too invasive/risky. For the same reason OpenBSD/armv7 will never support large amounts of memory either.

Re: inteldrm: cleanup_done timed out with external monitor

> Date: Mon, 3 Jun 2019 23:00:31 +0200 (CEST) > From: Mark Kettenis > > > From: "Sven M. Hallberg" > > Date: Mon, 03 Jun 2019 21:20:29 +0200 > > > > I've spent some more time poking through the drm code and think I have a > > good picture now

Re: ThinkPad P1 console freeze using chromium or firefox

> Date: Mon, 10 Jun 2019 13:45:26 -0700 > From: Bryan Vyhmeister > > On Mon, Jun 10, 2019 at 05:37:30PM +0200, Mark Kettenis wrote: > > Since you're able to log in remotely, please collect the output of "ps > > -AHlk" wen this happens again. > > Here y

Re: ThinkPad P1 console freeze using chromium or firefox

Since you're able to log in remotely, please collect the output of "ps -AHlk" wen this happens again.

Re: inteldrm: cleanup_done timed out with external monitor

leanup stage is deferred by i915 to 'system_wq'. > sys/dev/pci/drm/i915/intel_display.c intel_atomic_commit_tail(): > > INIT_WORK(>commit_work, intel_atomic_cleanup_work); > schedule_work(>commit_work); Thanks for helping figuring this out. > Mark Kettenis on Thu, May 30 2019: >

Re: inteldrm: cleanup_done timed out with external monitor

> Date: Thu, 30 May 2019 19:13:44 +1000 > From: Jonathan Gray > > On Tue, May 28, 2019 at 05:32:37PM +0200, Sven M. Hallberg wrote: > > Jonathan Gray on Tue, May 28 2019: > > > If you raise the timeout in drm_atomic_helper.c stall_checks() does > > > that also avoid the 'cleanup_done timed out'

Re: init: can't open /dev/console: Device not configured

> Date: Fri, 03 May 2019 02:06:07 -0400 > From: James Hastings > > Here is a little more debug info. > > I uncommented DRMDEBUG in sys/dev/pci/drm/include/drm/drmP.h > > root on sd0a (b9c87e5264160760.a) swap on sd0b dump on sd0b > [drm] GuC: No firmware known for this platform! > [drm] HuC:

Re: init: can't open /dev/console: Device not configured

> Date: Wed, 01 May 2019 04:57:29 -0400 > From: James Hastings > > On 05/01/2019 03:13 AM, Jonathan Gray wrote: > > On Wed, May 01, 2019 at 02:53:02AM -0400, James Hastings wrote: > >> Booting latest snapshot the system hangs at the following: > >> > >> [drm] GuC: No firmware known for this

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

> Date: Wed, 24 Apr 2019 17:33:58 +0200 > From: Matthieu Herrb > > Hi, > > I have an old Dell Optiplex 755 laying around that I use for OpenBSD > tests from time to time at work. It worked well under 6.5 development, > and I just retryed the official 6.5 release kernel. Dmesg from 6.5 > below.

Re: xenodm starts with only cursor showing

> Date: Thu, 28 Mar 2019 15:46:13 +0100 > From: Frederic Cambus > > On Tue, Mar 26, 2019 at 09:58:09PM +0500, dmitry.sensei wrote: > > Also I have kernel loop trap.. after running X and switching to 0 screen > > (Ctrl-Alt-F1) > > Thanks for your report and for sharing your dmesg. > > I just

Re: OpenBSD 6.5-BETA doesn't boot on MacBook Pro TouchBar 2017

> From: Joel Carnat > Date: Thu, 14 Mar 2019 18:57:36 +0100 > > aml_rwgen: unregistered RegionSpace 0x5 > Could not convert 1 to 0 > panic: aml_die aml_convert:2097. This almost certainly happens because I forgot to add the acpicmos(4) driver to the RAMDISK_CD kernel. Hopefully somebody

Re: amd64 crash when using /dev/kmem

> Date: Mon, 18 Feb 2019 14:32:34 +0100 > From: Hans-Joerg Hoexer > > Hi, > > On Mon, Feb 18, 2019 at 01:51:58PM +0100, Mark Kettenis wrote: > > > > I suspect the direct map has to work for things like GDB's "target > > kvm" to work. Otherwise

Re: amd64 crash when using /dev/kmem

ting the contents of some of the memory pools will fail. You seem to imply that you can crash the kernel by just reading some random memory address. That surprises me somewhat, even though I think I managed to do exactly that not too long ago. In principle the data is read using kcopy(9), which should

Re: idle threads say 100%

> Date: Sat, 26 Jan 2019 14:28:19 -0200 > From: Martin Pieuchot > > On 25/01/19(Fri) 02:24, Alexander Bluhm wrote: > > On Tue, Jan 22, 2019 at 12:19:11PM -0200, Martin Pieuchot wrote: > > > > There are still things I don't understand. After a while the CPU > > > > time for idle5, idle6, idle7

Re: macppc can't modify pages in swap

> Date: Tue, 25 Dec 2018 09:48:10 +0100 > From: Landry Breuil > > On Sun, Dec 23, 2018 at 09:20:11PM +0100, Mark Kettenis wrote: > > > Date: Sun, 23 Dec 2018 19:35:02 +0100 (CET) > > > From: Mark Kettenis > > > > > > > Date: Sun, 23 Dec 20

Re: macppc can't modify pages in swap

> Date: Sun, 23 Dec 2018 21:20:11 +0100 (CET) > From: Mark Kettenis > > > Date: Sun, 23 Dec 2018 19:35:02 +0100 (CET) > > From: Mark Kettenis > > > > > Date: Sun, 23 Dec 2018 12:26:17 +0100 (CET) > > > From: Mark Kettenis > > >

Re: macppc can't modify pages in swap

> Date: Sun, 23 Dec 2018 19:35:02 +0100 (CET) > From: Mark Kettenis > > > Date: Sun, 23 Dec 2018 12:26:17 +0100 (CET) > > From: Mark Kettenis > > > > That's a very good find. I think there still is a potential race in > > your diff on MP systems

Re: macppc can't modify pages in swap

> Date: Sun, 23 Dec 2018 12:26:17 +0100 (CET) > From: Mark Kettenis > > That's a very good find. I think there still is a potential race in > your diff on MP systems since you save the bits before removing the > PTE from the has tables. I'll see if I can come up with a bet

Re: macppc can't modify pages in swap

> Date: Wed, 19 Dec 2018 22:36:49 -0500 > From: George Koehler > > On Wed, 19 Dec 2018 00:13:13 -0500 > George Koehler wrote: > > > By my guess, pmap_is_modified() is broken on powerpc. It seems to > > fail to return true, so uvm wouldn't know that the page is modified, > > and then uvm

Re: inteldrm + skylake not working on a Dell Lattitude 3470

Hi Todd, We are working very hard on another drm code update. Hopefully that'll fix things. Cheers, Mark

Re: panic "data modified on freelist" on macppc

> Date: Thu, 13 Dec 2018 12:03:48 +0100 > From: Solene Rapenne > > >Synopsis:crash > >Category:kernel > >Environment: > System : OpenBSD 6.4 > Details : OpenBSD 6.4-current (GENERIC) #0: Mon Dec 10 12:32:35 CET > 2018 > >

Re: libGL error: ...

> From: "Ted Unangst" > Date: Wed, 12 Dec 2018 00:05:33 -0500 > > Roderick wrote: > > > > libGL error: Version 4 or later of flush extension not found > > libGL error: failed to load driver i915 > > This error also occurs on an HP mini 110. It appears cosmetic. glxgears still > runs, fast

Re: iked - pfkey_write: writev failed: -> issue found

Thanks David. Didn't have time to look into this. On Thu, Nov 29, 2018 at 06:44:52PM -0500, David Hill wrote: > On Wed, Nov 28, 2018 at 07:12:56PM -0200, Martin Pieuchot wrote: > > On 25/11/18(Sun) 10:52, David Hill wrote: > > > On Sat, Oct 27, 2018 at 05:35:16PM +0200,

Re: Trackpad not recognized on system76 Lemur laptop with intel HD gfx

The pms(4) driver doesn't attach. That might not necessarily be the problem here since on modern machines the touchpad might be attached over iic(4). But I don't see a i2c controller that is likely to be used for this purpose either. Can you figure out how the touchpad is supposed to be

Re: arm64: bnxt(4) crash running pkg_add -u on mcbin single-shot

> Date: Mon, 19 Nov 2018 20:35:44 +0100 > From: Patrick Wildt > > On Mon, Nov 19, 2018 at 08:16:31PM +0100, Patrick Wildt wrote: > > On Mon, Nov 19, 2018 at 11:27:54AM -0700, Theo de Raadt wrote: > > > > That means bnxt(4) and dwpcie(4) share the same interrupt line, but one > > > > has

Re: fetch problem with //pypi.io/packages/source/

> From: > Date: Tue, 6 Nov 2018 10:50:20 -0800 > > Both system are on the same network, hub, router etc. The amd system is on > Virtualbox on my PC and the arm system is an orangepi one. > > >From the arm system: > > op1bsdsnap1102# > op1bsdsnap1102# ftp -d -o /dev/null https://pypi.io/ >

Re: l2k18 ahoy [s_g...@telus.net: FW: SSL connection failure with ftp but not wget [...]

> Date: Mon, 5 Nov 2018 20:56:33 + > From: Stuart Henderson > > Probably worth pinging this one since l2k18 is on. > > s_graf is trying to fetch ports sources from https://pypi.org/ and is > getting a hang and eventually a timeout when attempting connection from > ftp(1) on armv7. (From

Re: idle threads say 100%

> From: "Theo de Raadt" > Date: Thu, 01 Nov 2018 14:21:43 -0600 > > There was work before release which had to be pulled since it changed > API which some ports could not handle. > > A new approach (adding a different API) is in the works from Scott. > > However, it is possible there are other

Re: iked - pfkey_write: writev failed: -> issue found

Pieuchot wrote: > On 24/09/18(Mon) 20:21, Mark Patruck wrote: > > Hi Martin, > > > > if you need additional info or have a diff to test, drop me a > > note. > > I don't have time to look at this, better send a report to bugs@, you > could also poke patrick@ t

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

> 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 we don't actually implement that functonality correc

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

surgery. Mike, it is likely this will fix your "sparkle" issue as well. Cheers, Mark Index: dev/pci/drm/i915/i915_dma.c === RCS file: /cvs/src/sys/dev/pci/drm/i915/i915_dma.c,v retrieving revision 1.26 diff -u -p -r1.26

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

I have a T400 on which I can reproduce the issue. Switching from modesetting to intel only partially fixes the issues. Running glxgears still cause the GPU to barf. I'm going to take a closer look.

Re: Supermicro 2029TP-HC0R: xhci0 msiuvm_fault

> Date: Mon, 8 Oct 2018 11:45:53 +0200 > From: Sebastian Benoit > > Supermicro SYS-2029TP-HC0R > https://www.supermicro.nl/products/system/2U/2029/SYS-2029TP-HC0R.cfm > > similar to my mail to bugs@ > Subject: Super X11SPi-TF board, xhci0 at ... "Intel C620 xHCI" ... > msiuvm_fault > but

Re: hw.ncpu=64 but hw.ncpuonline=8

> Date: Fri, 5 Oct 2018 00:34:02 -0700 > From: Philip Guenther > > On Thu, 4 Oct 2018, Georgy Yakovlev wrote: > ... > > >Description: > > After boot I noticed that on my TR2 220WX system kernel only uses > > 8 cores out of 32 with hw.smt=0 > > Not sure if it's correct. > >

iked - pfkey_write: writev failed: Invalid argument (-current)

', but 'iked[12345]: pfkey_write: writev failed: Invalid argument (every few hours) stays. (1) https://marc.info/?l=openbsd-cvs=153546931106420=2 (2) https://marc.info/?l=openbsd-cvs=153675149127886=2 Thanks, -Mark -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04

Re: panic: fork: encountered a submap during fork (illegal)

> Date: Mon, 17 Sep 2018 08:17:34 +0200 > From: Matthieu Herrb > > Hi, > > One of my amd64 boxes running -current paniced while builing ports. Is this plain -current without any local patches? > panic: fork: encountered a submap during fork (illegal) > Stopped at db_enter+0x5: popq %rdp >

Re: ldomctl coredump with init-system

, I just made some improvements to ldomctl(8) in 6.4-beta, a.k.a. -current. I'm pretty sure the new code will build fine on 6.3 so you can try checking out the -current source tree and do: # cd usr.sbin/ldomctl # make obj # make # make install to see if my changes fix this issue. Cheers, Mark

Re: Fujitsu RX2530 M4 16 cores null acpi panic

> Date: Fri, 14 Sep 2018 15:33:04 -0700 > From: Philip Guenther > > On Fri, 14 Sep 2018, Hrvoje Popovski wrote: > > On 14.9.2018. 19:44, Mark Kettenis wrote: > ... > > > Hvorje, can you boot this machine with 16 cores but acpicpu(4) > > > disabled and s

Re: Fujitsu RX2530 M4 16 cores null acpi panic

> Date: Fri, 14 Sep 2018 10:05:34 -0700 > From: Mike Larkin > > On Thu, Sep 13, 2018 at 11:17:15AM +0200, Hrvoje Popovski wrote: > > Hi all, > > > > i'm having Fujitsu PRIMERGY RX2530 M4 server with Intel Gold 6134 cpu > > with 8/16 cores. > > When booting box up to 14 cores everything seems

Re: Thinkpad X1C5 usb-c/thunderbolt3 port hotplug not detecting devices

> Date: Mon, 10 Sep 2018 16:24:23 +0200 > From: e...@xs4all.nl > > On 2018-09-09 21:01, Mark Kettenis wrote: > >> From: =?UTF-8?Q?Eric_Aug=C3=A9?= > >> Date: Sat, 8 Sep 2018 11:26:48 +0200 > >> > >> ok. > >> hth, > >> Eric. &g

Re: Thinkpad X1C5 usb-c/thunderbolt3 port hotplug not detecting devices

d into native PCIe mode by using a magic _OSC call. > On Sat, Sep 8, 2018 at 11:09 AM Mark Kettenis wrote: > > > > > Date: Sat, 8 Sep 2018 02:31:12 +0200 (CEST) > > > From: e...@unix4fun.net > > > > > 154320 Aug 13 01:25:32 klamboe /bsd: ACPIEC: got gpe &g

Re: Thinkpad X1C5 usb-c/thunderbolt3 port hotplug not detecting devices

> Date: Sat, 8 Sep 2018 02:31:12 +0200 (CEST) > From: e...@unix4fun.net > 154320 Aug 13 01:25:32 klamboe /bsd: ACPIEC: got gpe > > 154321 Aug 13 01:25:32 klamboe /bsd: GPE block: 10 40 c0 >

Re: System very slow on cold boot

Not unexpectedly, lots of acpi interrupts when booted cold.

Re: Kernel crash on i386 -current

> Date: Mon, 23 Jul 2018 11:09:28 +0200 > From: Alexander Bluhm > > On Sat, Jul 21, 2018 at 09:30:36PM +0200, Eivind Eide wrote: > > There are no crash with drm disabled. I'm attaching the dmesg to this > > mail. So the update to radeondrm are the cause. > > So we know that "ATI Radeon Mobility

Re: arm64 / panic: amap_pp_adjref: negative reference count

> Date: Sat, 21 Jul 2018 21:33:01 +0200 > From: Sebastian Benoit > > Hi, > > this is on an orange pi pc2 > > it was running cvs up at the time. Yes. Mine does that too. I have no clue what causes this. I don't see it on any of my other arm64 boards. And patrick@ says his H5-based nanopi

Re: physmem is 0 on this G5 macppc

e last two have a starting address >= 0x0001 and therefore can't be used in 32-bit mode. So these should not be counted. Cheers, Mark

Re: physmem is 0 on this G5 macppc

e physical memory below the 4GB boundary you must end up with significantly less than 4G of physical memory. Showing the eeprom -p output would help me tell you what's wrong. > On Thu, Jul 05, 2018 at 02:00:45PM +0200, Peter J. Philipp wrote: > > On Thu, Jul 05, 2018 at 11:20:51AM +020

Re: physmem is 0 on this G5 macppc

t use that memory anyway on a 32-bit OpenBSD system. And if the physmem variable includes a lot of memory that isn't actually usable, the kernel will make bad choices in sizing various things. Cheers, Mark > OpenBSD 6.3-current (GENERIC.MP) #8: Thu Jul 5 00:59:43 CEST 2018 > p...@iota

Re: witness report

> Date: Sun, 3 Jun 2018 13:51:19 +0200 (CEST) > From: Mark Kettenis > > > Date: Sat, 2 Jun 2018 15:08:14 -0700 > > From: Philip Guenther > > > > On Sat, 2 Jun 2018, Christophe Prévotaux wrote: > > > This a witness report I got on boot with snaps

Re: witness report

and retrying so progress is > made. The fix for WITNESS complaining is to mark vmmaplk as a vnode lock. > > ok? I don't think so. While we have UVM_FLAG_TRYLOCK, I don't think it is used in the code paths shown in the original report. This may still be a false positive though. Non

Re: i386 panic in uvm_addr_linsearch

> Date: Wed, 16 May 2018 09:24:05 +0200 > From: Theo Buehler > > On Mon, May 14, 2018 at 01:05:07PM +0200, Otto Moerbeek wrote: > > On Sun, May 13, 2018 at 10:34:13PM +0200, Alexander Bluhm wrote: > > > > > Hi, > > > > > > When executing the posixtestsuite port, the i386

Re: NFS blocked if virtual machine host disappears

> From: "Elias M. Mariani" > Date: Fri, 11 May 2018 14:11:36 -0300 > > I'm using a virtual machine with OpenBSD, the vm hosts nfsd, the real > machine (rm?) mounts the nfs with "doas mount_nfs host:/remote > /local". That's a really, resally, really bad idea.

Re: Wrong linkage to environ with -Wl,-nopie

> Date: Fri, 27 Apr 2018 21:32:19 -0700 > From: Josh Elsasser > > This problem still seems to be present. Anyone interested? It's a bug in our binutils that is hard to fix. Short-term fix would be to remove the -fno-pie flag, Long term fix is to switch to lld.

Re: Console resolution restricted to 848x400 on inteldrm

> From: Thomas Sullivan > Date: Sat, 28 Apr 2018 04:03:27 +1000 > > I've tried reinstalling `amd64` and booting `bsd.sp` but I'm seeing the > same thing. > > Manually resetting `force` to false inside `intel_tv_detect` causes it to > return the current connector status

Re: Samsung USB Harddisk attaches as serial cable

> Date: Thu, 26 Apr 2018 22:01:01 +0200 > From: Theo Buehler > > I have an USB-to-SATA cable with a samsung disk attached. When I plug it > in, the disk tries to attach as a uplcom0. mpi saw that this is due to a > re-used id and cooked the diff below with which it attaches as

Re: Console resolution restricted to 848x400 on inteldrm

sg. For some reason the inteldrm(4) code detects a connection on the S-Video connector. Since the default is to mirror the console framebuffer on all connected outputs, the framebuffer is configured as 848x480 such that the full contents are visible on both outputs. It seems this model does indeed have a S-Video output. Do you have that hooked up to something? Cheers, Mark

Re: panic in radeondrm_attachhook

d572d000) at radeondrm_attachhook+0x2b > > config_process_deferred_mountroot() at > > config_process_deferred_mountroot+0x2c > > main(0) at main+0x7bf > > After spending some time trying to track this down I have come up with > the diff below and included it in ~jsg

Re: modesetting driver broke video(1)

> Date: Tue, 24 Apr 2018 10:35:36 +0200 > From: Landry Breuil > > All that to say, maybe that means that video(1) can/should be adapted to > use another method/encoding, because the camera itself works in firefox > and is supported. If YUY2 and UYVY are not going to come back

Re: mg text editor: regex anchor defects

memcpy(, _match[0], sizeof(regmatch_t)); + if (regex_match[0].rm_so == 0 && + regex_match[0].rm_eo == 0) break; regex_match[0].rm_so++; regex_match[0].rm_eo = llength(clp); } -mark On 1

Re: amd64/machdep knob: forceukb forcing wrong encoding.

> Date: Tue, 27 Mar 2018 13:40:02 +0200 > From: Martin Pieuchot > > On 05/02/18(Mon) 18:31, Artturi Alm wrote: > > On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote: > > > On 04/02/18(Sun) 11:28, Artturi Alm wrote: > > > > Hi, > > > > > > > > machdep.forceukbd=1

Re: HDMI can't be used as primary monitor

> Date: Thu, 22 Feb 2018 07:50:57 +0100 (CET) > From: j...@navratil.cz Please try a -current snapshot.

Re: Hyper-V 6.2 amd install - timeout interval 1/2 prescribed interval

> Date: Tue, 13 Feb 2018 15:30:39 -0800 > From: Mike Larkin > > On Wed, Feb 14, 2018 at 11:01:00AM +1300, Megan wrote: > > We have recently installed OpenBSD 6.2 onto the latest version of > > Microsoft's Hyper-V. It is all running smoothly with the exception of one > >

Re: firefox (or some rthread / network stuff) broken in -current

> From: "Peter N. M. Hansteen" > Date: Sun, 11 Feb 2018 12:49:49 +0100 > > n 02/11/18 12:37, Matthieu Herrb wrote: > > I ugraded my laptop from sources to -current yesterday. Since then > > firefox stops resolving host names after a dozen of minutes or so. > > The

Re: Problems when resuming on Skylake

> From: Maximilian Pichler > Date: Mon, 5 Feb 2018 21:29:11 +0100 > > On Sat, Sep 23, 2017 at 6:56 AM, Niels Kobschaetzki > wrote: > > Sep 22 22:38:41 netcat /bsd: drm:pid71340:i915_drm_suspend *ERROR* GEM idle > > failed, resume might fail > >

Re: sparc64 ldom: interrupt_vector: spurious vector 40 at pil 15

> From: Jeremie Courreges-Anglas > Date: Sun, 28 Jan 2018 21:41:06 +0100 > > Just spotted this, the ldom is currently unresponsive and nothing more > appeared on the serial output. fwiw this was spotted after rebooting > the domain 50+ times since yesterday. Have seen that

Re: random userland segfaults/abort with latest arm64 snapshot

> Date: Sun, 28 Jan 2018 07:27:49 +0100 > From: Sebastien Marie > > Hi, > > I recently installed latest -current snapshot of arm64 using > qemu-system-aarch64 -M virt. > > $ doas what /bsd > /bsd > OpenBSD 6.2-current (GENERIC) #160: Wed Jan 24 18:26:59 MST 2018 > >

Re: arm: kernel hang

> Date: Sun, 21 Jan 2018 00:07:47 +0200 > From: Artturi Alm I don't understand this. The code works fine on my Cubox-i. I doubt the reset is instant. What would make more sense is to change the code such that it waits until the ETHEREN bit clears. > On Thu, Jan 11,

Re: Kernel panics after some hours of use (likely related to modeset)

> Date: Tue, 9 Jan 2018 12:32:49 +1100 > From: Jonathan Gray > > On Mon, Jan 08, 2018 at 05:20:39PM -0800, Mike Larkin wrote: > > On Tue, Jan 09, 2018 at 12:44:04AM +0100, azarus wrote: > > > To: bugs@openbsd.org > > > Subject: Kernel panics after some hours of use (likely

Re: Degraded timing performance - QEMU, KVM - OpenBSD 6.2

ll change the way we do clock interrupts at some point in the future. It would probably help vmm(4). But this is not a trivial task and won't happen overnight. Working around bugs in someone else's software certainly isn't enough motivation for me to implement it. Cheers, Mark > On

Re: arm64/pine64p: memory loss?

> Date: Wed, 27 Dec 2017 09:35:38 +0200 > From: Artturi Alm > > Hi, > > a64pine# eeprom -p > Node 0x48 > name: '' > serial-number: '92c000ba40e5f79b' > interrupt-parent: 0001 > #address-cells: 0001 > #size-cells: 0001 > model: 'Pine64+'

bug in master src/lib/libc/hash/siphash.c

for reading this report, hopefully you will find it useful. Best regards, Mark Karpilovskij, developer at CZ.NIC labs https://www.knot-dns.cz/

Re: MSI Radeon HD 6450 configured as "ATI Radeon HD 7450"

> From: Luke Small > Date: Thu, 23 Nov 2017 11:40:22 + > > It doesn't show anything ever and without seeing the screen, I entered > startkde4 with the normal user, per usual and it didn't show anything even > with a different xorg.conf Your dmesg shows: radeondrm0:

Re: apmd(8) autoactions aren't trigger

> I seem to have the same issue with your patch as I do with my own > though. When I run apmd with "-A -t 10 -z 10", it suspends again after > immediate resume. Like Mark suggested, maybe it's better to register > another kevent? The problem with the system suspending i

Re: apmd(8) autoactions aren't trigger

Hi Jesper, Thanks for the reply, and the patch! I'll have to download the src etc. so I'll try this over the weekend. Might it be "better" to register a `t` second EVFILT_TIMER kevent with the kqueue to handle polling? All the best, Mark On Fri, 13 Oct 2017 at 11:25 Jesper W

apmd(8) autoactions aren't trigger

might effect I can't say. I hope that I've managed to provide enough information to confirm that a bug exists and gone some way to helping isolate it. All the best, Mark OpenBSD 6.2 (GENERIC.MP) #134: Tue Oct 3 21:22:29 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/

Re: keyboard not working and no wireless found on laptop Asus L200HA-FD0093T

> Date: Sun, 13 Aug 2017 14:56:49 +0200 > From: Stefan Sperling > > On Sun, Aug 06, 2017 at 12:16:45AM +0200, Cesare Gargano wrote: > > Hi, > > works fine with your suggestion. I tested this with Asus E200HA (dmesg > > attached), T420s, T400, T23, > > and all runs without

Re: -pg broken with clang

> Date: Thu, 10 Aug 2017 12:27:10 -0400 > From: Martin Pieuchot <m...@openbsd.org> > > On 10/08/17(Thu) 18:21, Mark Kettenis wrote: > > > Date: Thu, 10 Aug 2017 12:10:27 -0400 > > > From: Martin Pieuchot <m...@openbsd.org> > > > > > > B

Re: -pg broken with clang

> Date: Thu, 10 Aug 2017 12:10:27 -0400 > From: Martin Pieuchot > > Building a profiled binary, using -pg with clang doesn't work as > expected. A gmon.out is properly generated when the binary exit, > but it doesn't include any profiling data. Seems to work when I pass

Re: X server segfaults in VESA driver as Linux KVM guest

> Date: Mon, 7 Aug 2017 20:53:59 +0200 > From: Matthieu Herrb <matth...@herrb.eu> > > On Mon, Aug 07, 2017 at 05:04:46PM +0200, Mark Kettenis wrote: > > > Date: Mon, 7 Aug 2017 16:46:42 +0200 (CEST) > > > From: Mark Kettenis <mark.kette...@xs4all.nl> >

Re: X server segfaults in VESA driver as Linux KVM guest

> Date: Mon, 7 Aug 2017 16:46:42 +0200 (CEST) > From: Mark Kettenis <mark.kette...@xs4all.nl> > > > Date: Sun, 6 Aug 2017 19:44:49 -0700 > > From: Max Parmer <m...@trystero.is> > > > > >Synopsis: X server segfaults in VESA driver as Linux K

Re: X server segfaults in VESA driver as Linux KVM guest

> Date: Sun, 6 Aug 2017 19:44:49 -0700 > From: Max Parmer > > >Synopsis:X server segfaults in VESA driver as Linux KVM guest > >Category:system > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current (GENERIC.MP) #45: Sat Aug 5

Re: Thinkpad x200 headphone jack does not mute speakers

nected to a gpio pin that needs to be set up properly to trigger when you insert the headphones. It is not inconceivable that the original BIOS handled this in SMM mode. Not much that we can do about this in OpenBSD. The best thing would be to look at the libreboot code and see if you can fix it to set things up correctly. Cheers, Mark

Re: keyboard not working and no wireless found on laptop Asus L200HA-FD0093T

eyboard and touchpad work configuring node->parent deps. > > > As Mark says, it's a order problem, we should attach all deps drivers > > > before > > > attaching the device driver itself. > > > > > > Attached diff and a (old) dmesg. > > > >

Re: upgrade to latest amd64 snapshot insists on trying hd0a as boot device

> From: "Peter N. M. Hansteen" > Date: Mon, 31 Jul 2017 08:49:58 +0200 > > On 07/31/17 01:44, Bryan Vyhmeister wrote: > > On Sun, Jul 30, 2017 at 10:05:15PM +0200, pe...@bsdly.net wrote: > >>> Synopsis: Latest amd64 snapshot upgrade apparently fails to install > >>> correct

Re: Kernel panic (possibly inteldrm related)

> Date: Thu, 27 Jul 2017 18:18:34 +0200 (CEST) > From: Mark Kettenis <mark.kette...@xs4all.nl> > > > The only "leak" I'm seeing is the 'drmreq' pool. It grows until the > > application is closed. Note that with my fix the allocated size

Re: Kernel panic (possibly inteldrm related)

> Date: Thu, 27 Jul 2017 17:59:00 +0200 > From: Martin Pieuchot <m...@openbsd.org> > > On 26/07/17(Wed) 13:13, Mark Kettenis wrote: > > > Date: Wed, 26 Jul 2017 12:11:31 +0200 > > > From: Martin Pieuchot <m...@openbsd.org> > > > > > >

Re: armv7/sunxi/sxie

> Date: Mon, 24 Jul 2017 23:07:00 +0300 > From: Artturi Alm <artturi@gmail.com> > > On Sun, Jul 23, 2017 at 07:45:53PM +0200, Mark Kettenis wrote: > > > Date: Sat, 22 Jul 2017 11:21:31 +0300 > > > From: Artturi Alm <artturi@gmail.com> > &

Re: inteldrm regressions

> Date: Mon, 24 Jul 2017 10:58:12 +0200 > From: Martin Pieuchot > > I'm running GNOME3 on my main laptop, an X1 carbon gen 3, dmesg below. > Since the last inteldrm update my laptop freeze in the following cases: > > - When watching a video fullscreen, either with mplayer or

Re: armv7/sunxi/sxie

> Date: Sat, 22 Jul 2017 11:21:31 +0300 > From: Artturi Alm > > Hi, > > anyone else having issues with sxie? w/bsd.rd from latest snapshot > it was unable to get ip from dhcpd even. > > this is what it does look like at the other side: > > 11:01:15.170089

Re: x250 inteldrm freeze on 4:3 external monitor

> Date: Thu, 20 Jul 2017 16:27:20 +0200 (CEST) > From: Mark Kettenis <mark.kette...@xs4all.nl> > > > Date: Thu, 20 Jul 2017 15:51:55 +0300 > > From: Paul Irofti <p...@irofti.net> > > > > > >Fix: > > > Unknown. > > >

Re: x250 inteldrm freeze on 4:3 external monitor

> Date: Thu, 20 Jul 2017 15:51:55 +0300 > From: Paul Irofti > > > >Fix: > > Unknown. > > Here is a potential fix. Can you try this diff instead? Index: dev/pci/drm/drmP.h === RCS file:

Re: resume from suspend fails from time to time

> Date: Fri, 7 Jul 2017 23:07:35 +0200 > From: Jesper Wallin > > >Synopsis: resume from suspend fails from time to time. > >Category: inteldrm or acpi (guessing) > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current (GENERIC.MP)

Re: regression using vncviewer (net/ssvnc) on inteldrm

> Date: Wed, 12 Jul 2017 13:11:25 +0100 > From: Stuart Henderson > > On 2017/07/12 07:46, Paul de Weerd wrote: > > Note that vncviewer was never really blazing fast, but at least it was > > workable. Obviously, vncviewer is doing something weird because other > > programs

Re: Hang since inteldrm works when stopping X or running xrandr

> Date: Wed, 12 Jul 2017 21:14:47 +0200 > From: Frank Groeneveld <fr...@frankgroeneveld.nl> > > Mark Kettenis <mark.kette...@xs4all.nl> schreef op 12 juli 2017 19:50:50 CEST: > >> Date: Wed, 12 Jul 2017 10:08:42 +0200 (CEST) > >> From: fr...@frankgroene

Re: static PIE & corrupted trace

> Date: Wed, 12 Jul 2017 19:54:11 +0200 > From: Martin Pieuchot <m...@openbsd.org> > > On 12/07/17(Wed) 19:06, Mark Kettenis wrote: > > > Date: Tue, 11 Jul 2017 14:45:36 +0200 > > > From: Martin Pieuchot <m...@openbsd.org> > > > > > &g

Re: Hang since inteldrm works when stopping X or running xrandr

> Date: Wed, 12 Jul 2017 10:08:42 +0200 (CEST) > From: fr...@frankgroeneveld.nl > > >Synopsis:System hangs when X is stopped or xrandr is run after disabling > >builtin screen > >Category:system > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current

Re: static PIE & corrupted trace

> Date: Tue, 11 Jul 2017 14:45:36 +0200 > From: Martin Pieuchot > > Binaries linked with '-static -pie' produce unusable core dumps at least > on amd64. This is a real problem to debug isakmpd(8)/iked(8) crashing on > production machines. Did you try using the gdb from ports?

Re: inteldrm(4) regression and multi screen at boot

85 > cpu0: Enhanced SpeedStep 1662 MHz: speeds: 1667, 1333, 1000 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03 > inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03 > drm0 at inteldrm0 > intagp0 at inteldrm0 > agp0 at intagp0: aperture at 0xe000, size 0x1000 > inteldrm0: apic 1 int 16 > inteldrm0: 848x480, 32bpp That is an odd resolution. The native resolution of your panel is 1280x800 I presume? For some reason the initial mode set for the kernel framebuffer selects this weird resolution. Building a kernel with DRMDEBUG un sys/dev/pci/drm/drmP.h uncommented might provide some hints what is going wrong here. Cheers, Mark

<    1   2   3   4   5   6   7   >