hello,
On 2024-05-16 16:14, Claudio Jeker wrote:
> On Thu, May 16, 2024 at 10:00:20AM -0400, Johan Huldtgren wrote:
> > hello,
>
> Removed a lot of text to keep this under control.
>
> > > > > >> > Relevant configs:
> > > >
hello,
On 2024-05-16 15:06, Claudio Jeker wrote:
> On Thu, May 16, 2024 at 08:52:24AM -0400, Johan Huldtgren wrote:
> > hello,
> >
> > On 2024-05-16 8:14, Dave Voutila wrote:
> > >
> > > Johan Huldtgren writes:
> > >
> > > > he
hello,
On 2024-05-16 8:14, Dave Voutila wrote:
>
> Johan Huldtgren writes:
>
> > hello,
> >
> > On 2024-05-15 17:31, Dave Voutila wrote:
> >>
> >> Johan Huldtgren writes:
> >>
> >> >> Synopsis: vmm g
hello,
On 2024-05-15 17:31, Dave Voutila wrote:
>
> Johan Huldtgren writes:
>
> >> Synopsis: vmm guest does not get IP after upgrade to 7.5
> >> Category: vmd
> >> Environment:
> > System : OpenBSD 7.5
> > Details : OpenBSD 7.
> Synopsis: vmm guest does not get IP after upgrade to 7.5
> Category: vmd
> Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
hello,
On 2024-01-19 13:21, Stuart Henderson wrote:
> On 2024/01/19 13:15, Stuart Henderson wrote:
> > On 2024/01/19 13:27, Radek wrote:
> > > I'm not using any USB keyboard but I need USB port to manage APC UPS
> > > connected by USB cable (apcupsd).
> >
> > Yes exactly.
>
> ...actually,
On 2024-01-11 10:29, Alexandre Ratchov wrote:
> On Wed, Jan 10, 2024 at 09:26:45AM -0700, David Rinehart wrote:
> > I have notice the same. To resolve, I installed / configured autofs
> > and have not had any issues since. No heavy load on the machine,
> > though.
>
> Thank you for confirming
hello,
On 2023-12-08 15:09, Vitaliy Makkoveev wrote:
> On Thu, Dec 07, 2023 at 11:58:31PM -0500, Johan Huldtgren wrote:
> > hello,
> >
> [skip]
> >
> > Would this apply against 7.4 or only -current? Machine is currently
> > running 7.4+syspat
hello,
On 2023-12-07 18:14, Vitaliy Makkoveev wrote:
> On Thu, Nov 30, 2023 at 04:51:06PM +0300, Vitaliy Makkoveev wrote:
> > On Thu, Nov 30, 2023 at 08:44:19AM +0100, Alexandr Nedvedicky wrote:
> > > Hello Johan,
> > >
> > > On Wed, Nov 29, 2023 at 11:
hello,
On 2023-11-30 8:44, Alexandr Nedvedicky wrote:
> Hello Johan,
>
> On Wed, Nov 29, 2023 at 11:24:59PM -0500, Johan Huldtgren wrote:
> >
> > so my machine paniced today, but the panic this time is completely
> > different.
> > I don't know if it's
hello,
On 2023-11-04 15:26, Alexandr Nedvedicky wrote:
> Hello Johan,
>
> On Sat, Nov 04, 2023 at 10:01:06AM -0400, Johan Huldtgren wrote:
> > hello,
> >
> > On 2023-11-03 19:10, Alexandr Nedvedicky wrote:
> > > Hello Johan,
> > >
> > >
hello,
On 2023-11-04 15:26, Alexandr Nedvedicky wrote:
> Hello Johan,
>
> On Sat, Nov 04, 2023 at 10:01:06AM -0400, Johan Huldtgren wrote:
> > hello,
> >
> > On 2023-11-03 19:10, Alexandr Nedvedicky wrote:
> > > Hello Johan,
> > >
> > >
On 2022-05-21 15:33, Johan Huldtgren wrote:
> On 2022/05/21 14:23, Mark Kettenis wrote:
> >> Date: Sat, 21 May 2022 13:13:19 -0400
> >> From: Johan Huldtgren
> >>
> >> On 2022/05/21 12:43, Mark Kettenis wrote:
> >>>> Date: Sat, 2
On 2022-05-24 5:44, anoduck wrote:
> To: bugs@openbsd.org
> Subject: froze after upgrade
> From: anod...@protonmail.com
> Cc:
> Reply-To: anod...@protonmail.com
>
> >Synopsis:After upgrading to 7.1 from 7.0, system immediately froze after
> >disk checks were successfully completed.
>
On 2022/05/21 14:23, Mark Kettenis wrote:
>> Date: Sat, 21 May 2022 13:13:19 -0400
>> From: Johan Huldtgren
>>
>> On 2022/05/21 12:43, Mark Kettenis wrote:
>>>> Date: Sat, 21 May 2022 12:36:03 -0400
>>>> From: Johan Huldtgren
>>>>
&g
On 2022/05/21 12:43, Mark Kettenis wrote:
>> Date: Sat, 21 May 2022 12:36:03 -0400
>> From: Johan Huldtgren
>>
>> hello,
>>
>> On 2022/05/21 12:08, Mark Kettenis wrote:
>>>> Date: Sat, 21 May 2022 10:31:37 -0400
>>>> From: Johan Huldtgr
hello,
On 2022/05/21 12:08, Mark Kettenis wrote:
>> Date: Sat, 21 May 2022 10:31:37 -0400
>> From: Johan Huldtgren
>>
>> hello,
>>
>> Details below, but commenting out 'ttyflags -a' from /etc/rc lets
>> this host boot. I wrote much of this e-mail while
think it's relevant I did this
upgrade
by doing sysupgrade -nr
On 2022/05/21 05:04, Sebastien Marie wrote:
> On Sat, May 21, 2022 at 04:35:25AM -0400, Johan Huldtgren wrote:
>> hello,
>>
>> I tried to update my server from 7.0 to 7.1 tonight but after the upgrade
>> booting
hello,
I tried to update my server from 7.0 to 7.1 tonight but after the upgrade
booting 7.1 it just
hangs after having mounted the filesystems. After leaving it for a long time
and it never
proceeds past that. This is an MP system but using the SP kernel has the same
result. I tried
booting
On 2020-12-12 23:30, Alexander Bluhm wrote:
> On Fri, Dec 11, 2020 at 03:14:52PM -0500, Johan Huldtgren wrote:
> > init: single user shell terminated, restarting
> > init: single user shell terminated, restarting
>
> The problem is that libc setjmp tries to save the MXCSR
On 2020-12-11 15:14, Johan Huldtgren wrote:
> hello,
>
> i recently tried to upgrade one of my i386 boxes from an older 6.8 snap (~end
> of
> October timeframe) to the latest one (Dec 10th). First I used sysupgrade and
> when it gets to the part where it would normally print
hello,
i recently tried to upgrade one of my i386 boxes from an older 6.8 snap (~end of
October timeframe) to the latest one (Dec 10th). First I used sysupgrade and
when it gets to the part where it would normally print "Install, Upgrade, Shell"
it simply started rolling:
init: single user shell
hello,
You are using 802.1x, which means wpa_supplicant from the ports
tree is involved. I never use 802.1x myself, but I supose you'll
need to manually kick wpa_supplicant somehow to regain a connection
when the AP changes channel.
noted.
Until proper 802.1x support arrives in the base
hello,
i recently got a Thinkpad X1 Carbon gen6. I'm seeing something with
regard to wireless that strike me as at least slightly unexpected.
I enabled debug on the interface but did not recompile my kernel with
IWM_DEBUG, if that will help let me know.
tl;dr
1) If the AP changes channel iwm0
On 2018-03-01 17:00, Alexander Bluhm wrote:
On Tue, Feb 27, 2018 at 11:15:22AM -0300, Johan Huldtgren wrote:
Patch does not change anything, it panics as soon as I've connected
and
I try to ping something on the inside. I couldn't find any logging for
this, I assume it would be in messages
On 2018-02-25 22:48, Johan Huldtgren wrote:
On 2018-02-25 21:54, Alexander Bluhm wrote:
On Sat, Feb 24, 2018 at 04:20:50PM -0500, Johan Huldtgren wrote:
trying to connect to my gateway today I found the following
panic. This is 100% reproducible anytime I connect via
openvpn and then generate
On 2018-02-25 21:54, Alexander Bluhm wrote:
On Sat, Feb 24, 2018 at 04:20:50PM -0500, Johan Huldtgren wrote:
trying to connect to my gateway today I found the following
panic. This is 100% reproducible anytime I connect via
openvpn and then generate traffic. This first happened on
the Feb 7th
hello,
trying to connect to my gateway today I found the following
panic. This is 100% reproducible anytime I connect via
openvpn and then generate traffic. This first happened on
the Feb 7th snap, I updated and it happens on the latest
snap as well.
For completeness sake, here is first all the
For the archives I can confirm that this has been fixed, presumably
by this commit
http://marc.info/?l=openbsd-cvs=150217645202029=2
thanks,
.jh
On 2017/07/28 23:38, Johan Huldtgren wrote:
> hello,
>
> I have a host which has multiple vlan(4) configured. When I go to upgrade
> wit
hello,
I have a host which has multiple vlan(4) configured. When I go to upgrade
with the latest bsd.rd (and several prior) after I enter which mirror to
fetch the sources from it simply hangs and nothing happens. If I ctrl-c
out and do an 'ifconfig' only one vlan (not the one I need to reach
>Synopsis: system will most of the time hang on boot after entry point line
>Category: system
>Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-beta (GENERIC.MP) #1: Sat Mar 25 08:33:54 MDT
2017
Ah, this machine doesn't have an APIC table so acpimadt doesn't
attach and cpu0's cpu_acpi_proc_id is thus the default 0 when acpicpu0,
which has proc_id == 1, tried to attach.
It looks like we need to make sure cpus are attached before acpicpu is
attached. I'm not sure how to do that, so
Synopsis: Boot fails on i386 -current
Category: kernel
Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0 (GENERIC) #1911: Mon Jul 25 17:31:41 MDT 2016
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
On 2/13/16 22:16, Kenneth R Westerback wrote:
Oops. And here is a version w/o an errant line deletion.
Ken
Index: softraid.c
===
RCS file: /cvs/src/sys/dev/softraid.c,v
retrieving revision 1.365
diff -u -p -r1.365
On 2/13/16 19:31, Jonathan Gray wrote:
On Sat, Feb 13, 2016 at 11:37:17AM +0100, Stefan Sperling wrote:
On Sat, Feb 13, 2016 at 03:42:16PM +1100, Jonathan Gray wrote:
On Fri, Feb 12, 2016 at 11:07:35AM -0500, Johan Huldtgren wrote:
uvm_fault(0x8193f240, 0x38, 0, 1) -> e
kernel: p
On 2/13/16 22:16, Kenneth R Westerback wrote:
On 02/13, Johan Huldtgren wrote:
On 2/13/16 19:31, Jonathan Gray wrote:
On Sat, Feb 13, 2016 at 11:37:17AM +0100, Stefan Sperling wrote:
On Sat, Feb 13, 2016 at 03:42:16PM +1100, Jonathan Gray wrote:
On Fri, Feb 12, 2016 at 11:07:35AM -0500
hello,
a bit over a week ago one of my remote boxes stopped responding, once
I got out there I noticed it had panicked, it doesn't have a serial
console so I grabbed some pictures and tried to bring it back alive.
The box came back but my softraid never recovered, this is all
documented in this
Thanks for the report. We're currently doing major changes to the network
stack at l2k15 and are happy to hear about any problem reports.
In this particular case we think this is already fixed so please try a
later snapshot. There should be on from Sept 11 that should have that
fixed.
I can
hello,
I have a setup with two carp nodes, I was replacing one of these with
new hardware (old was i386, new is amd64) and installed latest snapshot
and then copied over all the relevant files from the old node, changing
things which differed (vr -> em). I shut the old host down, and booted
the
39 matches
Mail list logo
