On Tue, Jul 30, 2019 at 10:18:54PM -0600, Theo de Raadt wrote:
| vn_write.
|
| You are using vnd. There are other reports this got broken recently.
Not that I'm aware of. All filesystems are either directly on
physical devices or through softraid crypto on physical devives.
Also, no cronjobs t
It turns out this is not as consistently reproducible as I thought.
The issue happened for at least three consecutive reboots (including
one complete power-off) before I sent this bug, but when I later went
to test if unplugging/reconnecting the USB device after boot made any
difference, I discover
Synopsis: umount says device busy after having used openrsync
Category: user
Environment:
System : OpenBSD 6.5
Details : OpenBSD 6.5-current (GENERIC.MP) #158: Tue Jul 30
15:25:51 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/am
July 29 amd64 snap. I had just tested something in a vm (not very
common for me) and did "halt -p" in the guest. Immediately afterwards
I hit this:
uvm_fault(0xfd84031d4ef0, 0x8, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at filt_bpfrdetach+0x43: movq0x8(%rax),%rax
>From ps
Looks like it can be related to my commit from May:
https://github.com/openbsd/src/commit/b50d0c1cf040666aed872208cd6f6ba609197b11#diff-7922ad1d2f6422aa72d4bacd1bf41909
I'll try to take a look. The steps to reproduce would be handy.
as the first aid I would give a try to apply a reverse pat
On Wed, Jul 31, 2019 at 10:12:02AM -0500, myportslist20190...@nym.hush.com
wrote:
> Synopsis: umount says device busy after having used openrsync
I have seen this behavior in combination with unveil(2) and chroot(2).
Could you test if the same diff helps for your problem?
bluhm
Index: kern/
On Wed, Jul 31, 2019 at 08:22:55PM +0200, Alexandr Nedvedicky wrote:
> Looks like it can be related to my commit from May:
>
>
> https://github.com/openbsd/src/commit/b50d0c1cf040666aed872208cd6f6ba609197b11#diff-7922ad1d2f6422aa72d4bacd1bf41909
>
> I'll try to take a look. The steps to repr
On Sun, Jul 28, 2019 at 11:52:52AM +0200, Alexandre Ratchov wrote:
> On Sat, Jul 27, 2019 at 08:47:58PM -0600, Samuel Larkin wrote:
>
> I verified that cranking the max number of channels can't cause
> regressions and just committed the change.
I tested the changes and it is working. I wasn't abl
On Tue, Jul 30, 2019 at 03:58:48PM +0200, Mark Kettenis wrote:
> > Date: Tue, 30 Jul 2019 15:13:21 +0200
> > From: Raimo Niskanen
> >
> > I have now tried with a few FreeBSD derivatives: GhostBSD, TrueOS and
> > Project Trident, and they all manage to start X on the machine.
> > / Raimo Niskanen
