On Wed, May 01, 2024 at 03:13:15PM GMT, Alexander Klimov wrote:
> Oh, I didn't init them first with bioctl.
Init and assemble/attach is the same command.
> And I neither even involved two devices.
> I, literally,
>
> - created one fresh RAID partition with disklabel -E
> - ran ./bioctl -c 1 -l
On Tue, Apr 30, 2024 at 12:03:04PM GMT, Alexander Klimov wrote:
> Hello everyone!
>
> Actually I was working on a way to create a degraded RAID.
> As the ioctl create RAID syscall takes a list of dev_t,
> I tried NODEV for Not yet Online DEVice. ;-)
> I expected the kernel to complain. But
On Mon, Apr 29, 2024 at 12:58:25PM GMT, bo...@plexuscomp.com wrote:
> >Synopsis:sysupgrade to latest snap results in bootloop, had to replace
> >boot.bin
> >Category:system aarch64
> >Environment:
> System : OpenBSD 7.5
> Details : OpenBSD 7.5-current (GENERIC.MP)
On Sun, Mar 31, 2024 at 06:18:22PM +0200, Mark Kettenis wrote:
> > Date: Sun, 31 Mar 2024 13:23:41 +
> > From: Klemens Nanni
> >
> > Default snapshot install works with the intial UEFI/u-boot from macOS/Asahi.
> >
> > After manual fw_update(8) via urndi
Default snapshot install works with the intial UEFI/u-boot from macOS/Asahi.
After manual fw_update(8) via urndis(4) tethering to install apple-boot-1.2
and cold reboot, it still boots the initial UEFI/u-boot and works.
Once I run sysupgrade(8), after the upgrade the boot firmware is switched to
On Fri, Feb 09, 2024 at 05:00:44PM -0500, Dave Voutila wrote:
> Turns out I had a bug in my packet injection logic. Locked addr forces
> use of the copy mode (i.e. not the zero-copy mode) and my logic was
> thinking the packet being read was an "injected" packet from the dhcp
> intercept. I don't
On Fri, Feb 09, 2024 at 10:02:29AM -0500, Dave Voutila wrote:
> Try this diff. There was an issue in the order of closing disk fds. I
> also noticed we're not closing the sockets when closing the data fds, so
> that's added into virtio_dev_closefds().
>
> With this i can boot a guest that uses a
On Fri, Feb 09, 2024 at 10:20:12AM +, Klemens Nanni wrote:
> This terminates the VM immediately after startup:
>
> # cat /tmp/vm.conf
> vm foo {
> disable
> disk /tmp/linux.qcow2
> interface
> }
Backing thi
kern.version=OpenBSD 7.4-current (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST
2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
This boots fine:
# cat /tmp/vm.conf
vm foo {
disable
disk /tmp/linux.qcow2
}
kern.version=OpenBSD 7.4-current (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST
2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
'locked addr' in `switch' block yields
vm/foo/vionet0: vionet_rx_copy: invalid injected packet object
Minimal reproducer from my
On Sun, Feb 04, 2024 at 01:58:17PM +0100, Peter J. Philipp wrote:
> Hi,
>
> I just reinstalled a host and noticed the following two conditions:
>
> 1. BOOTRISCV64.EFI does not get installed on the outer (non-sr0) partition i.
> in the installer. This means I cannot boot without booting
On Mon, Jan 15, 2024 at 05:23:06PM +0100, Florian Obser wrote:
> Obviously this doesn't work with your fritz.box because it just messes
> around with DNS.
>
> [1] We made one kind of split horizon DNS work. There are many others. I
> have ideas but I'm not particularly motivated since
> - it's
On Sat, Jan 13, 2024 at 05:48:43PM +0100, Florian Obser wrote:
> I think we need to improve debug logging a bit, but I'm pretty sure you
> are hitting
>
> } else
> checked_resolver->state = DEAD; /* we know the root exists */
>
> on line 1588 in resolver.c. I.e. your
On Sat, Jan 13, 2024 at 04:29:55PM +0100, Florian Obser wrote:
> On 2024-01-13 01:13 UTC, Klemens Nanni wrote:
> > The last unwind.conf(5) EXAMPLE does not work for me unless I remove all
> > three of "DoT", "oDoT-forwarder" and "forwarder"
The last unwind.conf(5) EXAMPLE does not work for me unless I remove all
three of "DoT", "oDoT-forwarder" and "forwarder" from preferences; moving
them to the end or "autoconf" to the front does not work.
Behind a standard german VDSL2 FRITZ!Box CPE reachable as "fritz.box":
$ unwind -n
On Sat, Dec 09, 2023 at 10:16:46PM +0100, Alexandre Ratchov wrote:
> On Sat, Dec 09, 2023 at 03:45:44PM +0000, Klemens Nanni wrote:
> >
> > However, detach USB during explicit playback to it, e.g.
> > $ AUDIODEVICE=snd/1 ncspot
> > crashes sndiod(8) rather than pla
Sound defaults to external USB for me as per
https://www.openbsd.org/faq/faq13.html#usbaudio
$ dmesg | grep uaudio0
uaudio0 at uhub3 port 1 configuration 1 interface 3 "Creative
Technology Ltd Creative BT-W4" rev 2.00/28.38 addr 5
uaudio0: class v1, full-speed, sync,
On Fri, Dec 01, 2023 at 06:54:48AM +, Miod Vallat wrote:
> > It always chokes on fp->fsisig4.
>
> Well, that's what you get from reading 512 bytes and casting the buffer
> to a 1024 byte struct.
>
> The following diff ought to solve this.
Makes sense, works for me, thanks.
OK kn
>
>
-current amd64 sometimes dumps core when creating a FAT32 image.
Minimal reproducer below; other FS types, sizes or files are stable,
FAT32 seems to be the culprit. I don't have time to look into this.
$ cd /usr/src/*bin/makefs
$ make DEBUG=-g
$ mkdir empty/
$
On Sat, Nov 11, 2023 at 06:00:13PM +0100, Alexandr Nedvedicky wrote:
> I think there is a glitch in pfctl(8). It fails to traverse
> to anchors when it is asked to show tables. however table
> is there if you search for it using hints:
Yes, that's a pfctl(8) bug, it's '-a' defines
Default -current relayd(8) installs pf(4) rules with wrong table names.
Minimal reproducer:
# cat /etc/relayd.conf
table { openbsd.org }
redirect "myRedirect" {
listen on ::1 port 80
forward to check icmp
}
# relayd -d &
This is a purely vio(4) specific XXXSMP bug, 7.1 (perhaps earlier) has it
already.
There are multiple possible crashes, with IPv4 alone as well.
The one reported seems most likely to trigger.
On my Intel T14 gen 3 with Alderlake GPU, brightness keys except when
going from the second darkest (1) to the darkest level/display off (0).
BrightnessDown/F5 from 1 to 0 goes to 0 and back to 1 after <1s.
Second press equally goes to 0 and back to 1.
Third press goes to 0 and stays there.
When
02.08.2023 07:11, Jonathan Gray пишет:
> The fix is to not reset the end of list marker when
> assigning a page.
This alone without the xorg.conf snippet is stable, no hangs or glitches
in Xfce or 0.A.D., which so far instanstly triggered corruptions.
Thanks a lot!
FWIW, OK kn
>
> Index:
acts and promptly hang in the menu).
I'll run this xorg.conf snippet and report back in a while,
thanks a lot.
>
> Thanks,
>
> On Wed, 26 Jul 2023 14:53:42 +
> Klemens Nanni wrote:
> > startxfce4 in ~/.xsession leaves the screen black immediately after
> > login
startxfce4 in ~/.xsession leaves the screen black immediately after
login from xenodm on an Intel T14g3 with latest snap and packages,
sometimes it hangs completely and needs a hard reset, but this time
I could switch to ttyC0 and use DDB:
uvm_fault(0x825b0130, 0x820a8014, 0, 1)
On Tue, Aug 23, 2022 at 10:15:22AM +0200, Stefan Sperling wrote:
> I found one of my amd64 systems running -current, built on 12th of
> August, has crashed as follows.
>
> I am not sure if this is still relevant; please excuse the noise if
> this has already been found and fixed.
>
> kernel:
On Wed, Jun 28, 2023 at 06:17:46PM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
> the fix below solves the locking issue. however pf_close_all_trans() still
> breaks the test case. it fails to retrieve all rules. it looks like pfctl(8)
> currently opens transaction for every ruleset/anchor it's
On Wed, Jun 28, 2023 at 05:46:36PM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
> it looks like we need to use goto fail instead of return.
> this is the diff I'm testing now.
>
> 8<---8<---8<--8<
> diff --git a/sys/net/pf_ioctl.c
On Wed, Jun 28, 2023 at 02:38:00PM +0200, Alexander Bluhm wrote:
> Hi,
>
> Since Jun 26 regress tests panic the kernel.
>
> panic: rw_enter: pfioctl_rw locking against myself
> Stopped at db_enter+0x14: popq%rbp
> TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
> * 19846
Snapshots with 'disable inteldrm' to reduce corruption/hangs on a
Intel T14 gen 3 always print the following on shutdown/reboot:
syncing disks... done
wsdisplay_switch2: not switching
rebooting...
Unmodified bsd.mp does not show this.
It is always a single
On Mon, Apr 24, 2023 at 11:53:25PM +1000, Jonathan Gray wrote:
> On Mon, Apr 24, 2023 at 01:49:32PM +0100, Stuart Henderson wrote:
> > Running picom (with no special config or command line flags) on intel
> > T14 gen 3 fairly easily triggers a crash in drm. If it doesn't fail the
> > first time,
On Wed, Apr 26, 2023 at 10:40:59AM +, Klemens Nanni wrote:
> Default install on softraid with default daemons and config.
> Was just typing looking at a picture in telegram-desktop and typing,
> neomutt and ssh in xterm, nothing else going on.
If I move the mouse over certain
Default install on softraid with default daemons and config.
Was just typing looking at a picture in telegram-desktop and typing,
neomutt and ssh in xterm, nothing else going on.
typed from photo:
uvm_fault(0x82632a80, 0x8376c014, 0, 1) -> e
WARNING: SPL NOT LOWERED ON
On Wed, Apr 26, 2023 at 08:43:36AM +0100, Stuart Henderson wrote:
> On 2023/04/25 19:40, Klemens Nanni wrote:
> > Speakers work fine, 'aucat -o rec.wav' produces non-zero data,
> > but 'aucat -i rec.wav' keeps quiet ('mpv song73.ogg' plays).
> >
> > https://www
Speakers work fine, 'aucat -o rec.wav' produces non-zero data,
but 'aucat -i rec.wav' keeps quiet ('mpv song73.ogg' plays).
https://www.openbsd.org/faq/faq13.html#enablerec did not help me,
there is nothing muted and I did not find a knob to tweak to make it work.
$ sysctl -n kern.audio.record
1
On Mon, Apr 24, 2023 at 04:58:08PM +0100, Stuart Henderson wrote:
> On 2023/04/24 15:50, Klemens Nanni wrote:
> > cpu0: 12th Gen Intel(R) Core(TM) i7-1270P, 2095.31 MHz, 06-9a-03
>
> ah you got one of the warm CPU versions then :)
what does that mean?
Saw this in /var/log/messages on a clean -current GENERIC.MP with WITNESS
and kern.witness.watch=2
Rebooted, zzz and ZZZ a few times, but can't reproduce it so far.
Apr 24 16:16:45 atar /bsd: OpenBSD 7.3-current (GENERIC.MP) #2: Mon Apr
24 13:46:43 WEST 2023
...
root on
Was testing dv's latest BTI fix for unhibernate.
Fresh boot into -current bsd.mp, run top in xterm, ZZZ, unhibernate,
ssh somewhere to say unhibernate is working, then I got the panic.
System was locked up, had to hard reset.
Typed from photo:
OpenBSD/amd64 (atar.my.domain) (ttyC0)
login:
On Thu, Apr 13, 2023 at 04:43:39PM +, Mikolaj Kucharski wrote:
> I have an amd64 based cheap laptop, which has extremly slow I/O and even
> slower I/O in the installer. The result is, that fsck during upgrade,
> triggered via sysupgrade -s, takes ages. Basically makes upgrade
> non-usable.
Paul should follow up with more details soon, but I'm relaying our findings
with his debug output as this may be important for release:
- happens with all of bsd.{rd,sp,mp}
- nothing to do with softraid
- nvme disks are fine
- any ahci disk is super slow, 'ktrace disklabel sd1':
19830 disklabel
12/18/22 19:37, Andreas Bartelt пишет:
Hi,
after upgrading to a recent snapshot from today, I've noticed that an
(additionally configured) loopback interface (i.e., lo1) doesn't get
created anymore from my preexisting (and previously working)
/etc/hostname.lo1 configuration.
I've verified
On Tue, Dec 06, 2022 at 11:33:06PM +0300, Vitaliy Makkoveev wrote:
> On Tue, Dec 06, 2022 at 07:56:13PM +0100, Paul de Weerd wrote:
> > I was playing with the USB NIC that's in my (USB-C) monitor. As soon
> > as I do traffic over the interface, I get a kernel panic:
> >
> > panic: kernel
On Tue, Nov 15, 2022 at 06:50:50PM +0100, Stefan Sperling wrote:
> On Tue, Nov 15, 2022 at 03:07:05PM +0100, Leah Neukirchen wrote:
> >
> > I hit the same issue on a 7.2-RELEASE system, which was idle and had
> > roughly 3 weeks of uptime.
> >
> > Stopped at rt_ifa_del+0x39: movb 0x1b6(%rax),%bl
On Sun, Nov 20, 2022 at 02:15:24AM +0100, Alexandr Nedvedicky wrote:
> Hello Olivier,
>
> thank your for reporting a bug. Patch is always welcomed,
> though I think there is a better way to fix it.
>
> I was able to reproduce the bug. After adding a 64 groups to
> interface vio0 I was getting
On Sun, Nov 20, 2022 at 10:25:47AM +0100, Sebastien Marie wrote:
> On Mon, Nov 14, 2022 at 01:04:45PM +, Koakuma wrote:
> > On 7.2-current/sparc64, `fork-exit` regression test fails with these errors:
> >
> > run-fork1-heap
> > # allocate 400 MB of heap memory
> > ulimit -p 500 -n
On Mon, Nov 14, 2022 at 10:40:37PM +0100, Kirill Miazine wrote:
> The most recent snapshot gives non-recoverable failure in name
> resolution upon boot starting with configuration which I had not
> touched:
>
> starting network
> route: fe80::: non-recoverable failure in name resolution
> route:
On Sun, Nov 13, 2022 at 12:46:26PM +0100, Peter J. Philipp wrote:
> appended are the screenshots of the Hyper-v, bug report follows in the
> forwarded message. Please treat this as low priority, I can do work with
> IPv4 on this. Also one thing I forgot to mention was that I had 2 hyper-v's
>
On Sun, Sep 18, 2022 at 12:13:34PM +0200, Martin Pieuchot wrote:
> The rockpro64 no longer boots in multi-user on -current. It hangs after
> displaying the following lines:
>
> rkiis0 at mainbus0
> rkiis1 at mainbus0
>
> The 8/09 snapshot works, the next one from 11/09 doesn't.
Smells like a
On Fri, Sep 16, 2022 at 05:59:20PM -0700, Michael Truog wrote:
> Hi,
>
> I was attempting to have a RAID 5 softraid0 setup on a sparc64 machine (boot
> log output below) but ran into problems when attempting to create a single
> partition with the size 5.5TB (RAID 5 with 4 x 2TB hard drives). I
On Sun, Sep 04, 2022 at 08:53:45AM +0200, Stefan Sperling wrote:
> On Sat, Aug 27, 2022 at 11:32:24PM +0300, Vitaliy Makkoveev wrote:
> > > On 27 Aug 2022, at 22:03, Alexander Bluhm wrote:
> > >
> > > On Sat, Aug 27, 2022 at 03:14:15AM +0300, Vitaliy Makkoveev wrote:
> > >>> On 27 Aug 2022, at
On Tue Aug 9, 2022 at 2:12 AM +04, Theo de Raadt wrote:
> Klemens Nanni wrote:
>
> > > GENERIC.MP builds and boots fine with both enabled, but I have no
> > > hardware to run-test these drivers.
> > >
> > > Can anyone test this on real hardware or do
On Fri, Aug 05, 2022 at 07:46:41PM -0700, Michael Truog wrote:
> On 7/31/22 00:00, Klemens Nanni wrote:
> > On Sat, Jul 30, 2022 at 06:58:21PM -0700, Michael Truog wrote:
> > > I previously sent an email regarding the Areca ARC-1880 on sparc64.
> > > I also have an Areca
On Mon, Aug 08, 2022 at 08:32:54PM +, Klemens Nanni wrote:
> On Sat, Aug 06, 2022 at 10:16:57PM -0700, Michael Truog wrote:
> > Hi,
> >
> > I believe I found a common hardware RAID PCIe card that is not detected as a
> > mfi device on sparc64. There are differe
On Sat, Aug 06, 2022 at 10:16:57PM -0700, Michael Truog wrote:
> Hi,
>
> I believe I found a common hardware RAID PCIe card that is not detected as a
> mfi device on sparc64. There are different names for this PCIe card when
> they are sold with a cheaper card being called a "LSI SAS 9261-8i
>
On Sat, Jul 30, 2022 at 06:58:21PM -0700, Michael Truog wrote:
> I previously sent an email regarding the Areca ARC-1880 on sparc64.
> I also have an Areca ARC-1222i 8 Port PCIe RAID card which
This one is indeed listed as supported card.
> I tried with the 7.1 stable release ISO on a SPARC
On Sat, Jul 30, 2022 at 05:35:25PM -0700, Michael Truog wrote:
> The http://www.openbsd.org/sparc64.html info and the arc manpage
> claims support for the Areca ARC-1880i 8 Port PCIe RAID card.
sparc64.html just links to https://man.openbsd.org/spar64/arc.4 which
lists two 1880 cards, but neither
On Wed, Feb 16, 2022 at 11:39:19PM +0100, Mark Kettenis wrote:
> > Date: Wed, 16 Feb 2022 21:13:03 +
> > From: Klemens Nanni
> >
> > Unmodified -current with WITNESS enabled booting into X on my X230:
> >
> > wsdisplay0: screen 1-5 added (std, vt1
Unmodified -current with WITNESS enabled booting into X on my X230:
wsdisplay0: screen 1-5 added (std, vt100 emulation)
witness: acquiring duplicate lock of same type: ">vmobjlock"
1st uobjlk
2nd uobjlk
Starting stack trace...
witness_checkorder(fd83b625f9b0,9,0) at witness_checkorder+0x8ac
I have been using the following headset for a few weeks just fine with
`sndiod_flags=-f rsnd/0 -F rsnd/1' on my X230:
kern.version=OpenBSD 7.0-current (GENERIC.MP) #188: Mon Dec 20 22:32:56 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
uaudio0 at uhub0 port 2
On Mon, Nov 22, 2021 at 09:30:13AM +0100, Claudio Jeker wrote:
> > Index: sbin/ifconfig/ifconfig.c
> > ===
> > RCS file: /cvs/src/sbin/ifconfig/ifconfig.c,v
> > retrieving revision 1.450
> > diff -u -p -r1.450 ifconfig.c
> > ---
On Mon, Nov 22, 2021 at 08:17:47AM +0100, Peter J. Philipp wrote:
> On Mon, Nov 22, 2021 at 12:30:19AM +0000, Klemens Nanni wrote:
> > On Sun, Nov 21, 2021 at 11:18:29AM +0100, p...@delphinusdns.org wrote:
> > > >Synopsis:session uptime is wrong
> >
On Sun, Nov 21, 2021 at 11:18:29AM +0100, p...@delphinusdns.org wrote:
> >Synopsis:session uptime is wrong
> >Category:system
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC.MP) #698: Thu Sep 30 21:07:33 MDT
> 2021
>
>
ng? I'm out of my comfort zone here.
> Klemens Nanni wrote:
>
> > Just upgraded a standard test install in vmm(4) to the latest snap and
> > noticed new and garbled output:
> >
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > intr_establish: pic pic0 pin
On Sat, Sep 05, 2020 at 03:18:21AM +0200, Klemens Nanni wrote:
> Latest mpv on snapshots on my X250 dumps core whenever I quit playing
> with `q' or `Q'; I have no mpv config and this happens regardless of
> any values for the vm.malloc_conf and hw.smt sysctls:
>
> $ sysctl
Just upgraded a standard test install in vmm(4) to the latest snap and
noticed new and garbled output:
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
intr_establish: pic pic0 pin 6: can't share type 3 with 2
com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo
...
On Tue, Nov 09, 2021 at 09:45:23AM +0100, Marcus MERIGHI wrote:
> >Synopsis:shell script started by rcctl stops immediately
> >Category:user
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #80: Mon Nov 8 08:34:04
> MST 2021
>
On Tue, Nov 09, 2021 at 12:31:24AM +1000, Paul W. Rankin wrote:
> On 2021-11-08 23:36, Klemens Nanni wrote:
> > On Mon, Nov 08, 2021 at 05:40:24PM +1000, Paul W. Rankin wrote:
> > > On 2021-11-04 04:31, Klemens Nanni wrote:
> > > >
> > > > FWI
On Mon, Nov 08, 2021 at 05:40:24PM +1000, Paul W. Rankin wrote:
> On 2021-11-04 04:31, Klemens Nanni wrote:
> >
> > FWIW, my Raspberry Pi 4b boots fine with both
> > OpenBSD 7.0-current (GENERIC.MP) #1372: Mon Nov 1 22:52:56 MDT 2021
> > OpenBSD 7.0-current (GENERIC.
On Fri, Nov 05, 2021 at 09:32:52AM +0100, Paul de Weerd wrote:
> I recently got an RPi4 for a project at home and had the same error.
>
> On Tue, Nov 02, 2021 at 02:09:29PM +, Klemens Nanni wrote:
> | After reading through openbsd-arm after sthen's suggestion I only tried
> |
On Wed, Nov 03, 2021 at 06:30:55PM -0400, Josh Rickmar wrote:
> I'm not familiar enough with mdoc to determine if this is a manpage
> bug or a rendering bug, but mandoc -Thtml doesn't nicely render the
> command aliases in tmux, but instead moves the terminating ) outside
> of the div so it
OpenBSD 7.0-current (GENERIC.MP) #1373: Tue Nov 2 17:32:41 MDT 2021
reproducibly panics on my Pinebook Pro:
...
"battery" at mainbus0 not configured
panic: uvm_fault failed: ff800075669c esr 964f far
ff8000cb0188
Stopped at panic+0x160:cmp
On Tue, Nov 02, 2021 at 01:36:14PM +, Klemens Nanni wrote:
> On Sun, Oct 24, 2021 at 02:06:56PM +0000, Klemens Nanni wrote:
> > On Sun, Oct 24, 2021 at 08:04:26AM -0600, Theo de Raadt wrote:
> > > Theo Buehler wrote:
> > >
> > > > On Sun, Oct 24, 2021 a
On Tue, Nov 02, 2021 at 11:44:25AM +0100, Mark Kettenis wrote:
> > Date: Tue, 2 Nov 2021 00:05:49 +
> > From: Klemens Nanni
> >
> > On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote:
> > > On 2021/11/01 22:33, Klemens Nanni wrote:
> >
On Sun, Oct 24, 2021 at 02:06:56PM +, Klemens Nanni wrote:
> On Sun, Oct 24, 2021 at 08:04:26AM -0600, Theo de Raadt wrote:
> > Theo Buehler wrote:
> >
> > > On Sun, Oct 24, 2021 at 12:37:47PM +, Klemens Nanni wrote:
> > > > On Thu, Oct 21, 2021 at 1
On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote:
> On 2021/11/01 22:33, Klemens Nanni wrote:
> 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot
> should work.
>
> > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600)
>
> Not sure the
Neither RAMDISK nor GENERIC.MP from snapshots boot on my Raspberry 4
Model B unless I disable xhci(4).
I flashed miniroot70.img to an SD card, booted from it, did a default
install to it and booted the new system from it.
Both times, `boot /bsd -c' and "disable xhci" were needed to bypass the
On Wed, Oct 27, 2021 at 04:22:27PM +0100, Andrew Grillet wrote:
> Thanks ...
>
> Oracle Advanced Lights Out Manager CMT v1.7.9
> Sun-Fire-T2000 System Firmware 6.7.10 2010/07/14 16:35
> Host flash versions:
>OBP 4.30.4.b 2010/07/09 13:48
>Hypervisor 1.7.3.c 2010/07/09 15:14
>POST
On Tue, Sep 14, 2021 at 05:52:08PM -0400, James Hastings wrote:
> >Synopsis:run(4): connecting to WEP network. panic: null node
> >Category:kernel
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-beta (GENERIC.MP) #206: Thu Sep 9 09:24:02
> MDT 2021
>
On Thu, Oct 28, 2021 at 04:02:33AM +0900, Roc Vallès wrote:
> Yes, it does. It gets an IPv4 address with the check removed.
Fixed, thanks for the report.
(moving Cc to bugs@)
On Wed, Oct 27, 2021 at 02:33:55PM +0100, Andrew Grillet wrote:
> I reported this problem in 2019, and was asked to provide data for
> diagnosis.
> Unfortunately, I was not able to do so at the time.
Thanks for coming back to this.
Please provide boot logs, specifically
On Sun, Oct 24, 2021 at 02:18:39PM +0200, Florian Obser wrote:
> On 2021-10-24 13:53 +09, Roc Vallès wrote:
> > Sysupgraded my 6.9 personal server to 7.0 tonight. Only IPv6 came up
> > (which I have a custom dhcp setup for, as required by my host).
> >
> > On the daemon log, this shows up:
> >
On Mon, Oct 25, 2021 at 05:18:48PM +0200, Kristof Provost wrote:
> On 25 Oct 2021, at 17:06, Alexandr Nedvedicky wrote:
> > Hello,
> >
> > On Fri, Oct 22, 2021 at 02:47:07PM +0200, Kristof Provost wrote:
> >> On 21 Oct 2021, at 20:33, Alexandr Nedvedicky wrote:
> >>> Hello,
> >>>
> I’ve had a
On Mon, Oct 25, 2021 at 10:17:27AM -0400, Dave Voutila wrote:
>
> "Todd C. Miller" writes:
>
> > On Sun, 24 Oct 2021 20:45:47 -0400, Dave Voutila wrote:
> >
> >> We end up freeing some strings and unlinking the temp file. You can
> >> easily see this without a debugger by checking /tmp before
On Sun, Oct 24, 2021 at 03:35:49PM -0500, Tim Chase wrote:
> On 2021-10-24 15:05, Edgar Pettijohn wrote:
> > On 10/24/21 10:11 AM, Klemens Nanni wrote:
> >> I fat fingered commands and it crashed. Here is a reproducer
> >> (files do not have to exist):
> >>
&g
I fat fingered commands and it crashed. Here is a reproducer
(files do not have to exist):
$ vi foo
:e
:e bar
:q!
vi(12918) in free(): write after free 0xea559a2d980
Abort trap (core
dumped)
In
On Sun, Oct 24, 2021 at 08:04:26AM -0600, Theo de Raadt wrote:
> Theo Buehler wrote:
>
> > On Sun, Oct 24, 2021 at 12:37:47PM +0000, Klemens Nanni wrote:
> > > On Thu, Oct 21, 2021 at 10:29:02AM +, Klemens Nanni wrote:
> > > > On Thu, Oct 21, 2021 at 04:0
On Thu, Oct 21, 2021 at 10:29:02AM +, Klemens Nanni wrote:
> On Thu, Oct 21, 2021 at 04:06:53AM -0600, Theo de Raadt wrote:
> > Can people handle typing these passwords blindly? I suspect yes.
> >
> > Then this seems like a reasonable solution.
>
> Other systems d
On Thu, Oct 21, 2021 at 04:06:53AM -0600, Theo de Raadt wrote:
> Can people handle typing these passwords blindly? I suspect yes.
>
> Then this seems like a reasonable solution.
Other systems do the redacted typing thing, so you see instead of
what you actually typed; I think we're used
On Sun, Oct 17, 2021 at 01:29:23PM +, Klemens Nanni wrote:
> On Sun, Oct 17, 2021 at 11:33:48AM +0300, Pasi-Pekka Karppinen wrote:
> > When doing a fresh install and you are at the point where you are
> > configuring a wireless network, the installer is asking you to provide
On Sun, Oct 17, 2021 at 11:33:48AM +0300, Pasi-Pekka Karppinen wrote:
> When doing a fresh install and you are at the point where you are configuring
> a wireless network, the installer is asking you to provide a WPA/WPA2
> security passphrase for the wireless network - if your WPA/WPA2
On Thu, Apr 08, 2021 at 08:09:29AM +0100, Stuart Henderson wrote:
> I committed this a couple of weeks ago.
I'm glad it's just me looking at the wrong file's CVS log...
good morning :)
On Wed, Apr 07, 2021 at 11:16:44PM +, Uwe Werler wrote:
> >Synopsis:no default route added when dhcp option 121 set
> >Category:system
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #12: Tue Apr 6 15:41:46 GMT 2021
>
On Mon, Mar 22, 2021 at 12:42:27AM +1100, Matt Dunwoodie wrote:
> On Sat, 20 Mar 2021 11:48:52 +
> Stuart Henderson wrote:
>
> > oh, let's cc Matt on this too.
> >
> > On 2021/03/20 11:17, Martin Pieuchot wrote:
> > > On 19/03/21(Fri) 20:15, Stuart Henderson wrote:
> > > > Not a great
Pinebook Pro running a -CURRENT kernel with patches on recent snapshots
paniced upon
$ doas ifconfig bwfm0 down
$ doas ifconfig bwfm0 up
$ doas ifconfig bwfm0 down
$ doas ifconfig bwfm0 up
Changes from GENERIC.MP include omission of unused drivers such as
On Mon, Mar 08, 2021 at 04:50:53PM -0500, Josh Rickmar wrote:
> >Synopsis:vmm/vmd fails to boot bsd.rd
> >Category:vmm
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9-beta (GENERIC.MP) #385: Mon Mar 8 12:57:12
> MST 2021
>
>
On Fri, Jan 08, 2021 at 11:58:25AM -0700, Alex Long wrote:
> Okay. So going forward, vmt(4) is being deprecated in favor of the new
> open-vm-tools port?
The package can do everything the driver does and more, but it also
requires pkg_add and rcctl to work opposed to just a default base
On Thu, Jan 07, 2021 at 09:45:31PM +0100, Klemens Nanni wrote:
> A quick look at upstream seems to indicate that they still use
> `info-set guestinfo.ip %s', but there's also much more in the
> open-vm-tools code I didn't look at (yet):
>
> https://github.com/vmware/open-vm-tools/b
On Wed, Jan 06, 2021 at 11:46:04PM -0700, Alex Long wrote:
> Software in use:
> ESXi / vCenter 7.0U1
> OpenBSD 6.8
I'm not using Packer or OpenBSD on ESXi, but I just installed the latest
snapshot on ESXi/vCenter 7.0U1 to see.
> It seems like the vmt module is populating the legacy
I use unwind on my notebook where one particular domain must always go
through one particular resolver; this resolver should should not be
used for anything else.
Hence I overwrite the default preference list (output of
`unwind -vnf/dev/null') by removing `oDoT-forwarder' and `forwarder'
such
1 - 100 of 200 matches
Mail list logo
