On Tue, May 04, 2021 at 07:07:03PM +, kyo wrote:
> Background - I was trying to troubleshoot a networking problem. I had put my
> wg(4) interface on rdomain 2 and was NAT-ing certain packets from iwm(4) to
> it.
> When the crash happened, I was running a ping and a tcpdump on the wireguard
>
On Tue, May 04, 2021 at 05:01:35PM +0200, Florian Obser wrote:
> On 2021-05-04 16:50 +02, Sebastien Marie wrote:
> > On Tue, May 04, 2021 at 02:15:05PM +0200, Alexandr Nedvedicky wrote:
> >> Hello Sebastien,
> >>
> >> thank you for additional info about previously working kernel.
> >>
> >> it
Hi again,
Someone let me know attaching my dmesg is very helpful to
anyone investigating a bug that happened on my hardware
so I'm attaching it here!
`--`
`ed25519指紋` `ce2e1e8d1842d1b0d5aeacecbb384c9c3ae41b43`
‐‐‐ Original Message ‐‐‐
2021年5月4日 火曜日 15:07に、kyo は書きました:
> Hi,
>
> I'm not
> Date: Mon, 3 May 2021 23:06:58 +0200
> From: "Peter N. M. Hansteen"
> Cc: bugs@openbsd.org
> Content-Type: multipart/mixed; boundary="xA/hR9rv41MU9mZo"
> Content-Disposition: inline
>
>
> [1:text/plain Hide]
>
> Hi Mark,
>
> On Mon, May 03, 2021 at 07:00:44PM +0200, Mark Kettenis wrote:
> >
Unfortunately, booting up only worked as long as I didn't power down.
Now that I did, the boot process stops where the warning was issued before.
...
scsibus3 at softraid0: 256 targets
softraid0: sd2 was not shutdown properly
sd2 at scsibus3 targ 1 lun 0:
sd2: 122103MB, 512 bytes/sector,
On 2021-05-04 16:50 +02, Sebastien Marie wrote:
> On Tue, May 04, 2021 at 02:15:05PM +0200, Alexandr Nedvedicky wrote:
>> Hello Sebastien,
>>
>> thank you for additional info about previously working kernel.
>>
>> it looks like your older kernel, which works, might be running without
>> my
On Tue, May 04, 2021 at 02:15:05PM +0200, Alexandr Nedvedicky wrote:
> Hello Sebastien,
>
> thank you for additional info about previously working kernel.
>
> it looks like your older kernel, which works, might be running without
> my commit
>
> revision 1.1116
> date: 2021/04/27
Thanks for the quick help. I built a kernel with your fix.
The system is booting up with a warning, now.
...
scsibus3 at softraid0: 256 targets
sd2 at scsibus3 targ 1 lun 0:
sd2: 122103MB, 512 bytes/sector, 250067198 sectors
root on sd2a (da12fadb67cf7a4d.a) swap on sd2b dump on sd2b
drm :
Den tis 4 maj 2021 kl 15:34 skrev :
> Dear OpenBSD developers,
> I tried to run OpenBSD 6.9 on an Intel NUC 11 (NUC11TNKv7). Install runs
> fine except Network Interface iwx0: could not read firmware iwx-quz-...
> iwx0: failed to load init firmware
> iwx0: aquiring device failed
> After sucessful
Dear OpenBSD developers,
I tried to run OpenBSD 6.9 on an Intel NUC 11 (NUC11TNKv7). Install runs
fine except Network Interface iwx0: could not read firmware iwx-quz-...
iwx0: failed to load init firmware
iwx0: aquiring device failed
After sucessful istall the screen goes blank while booting
Hello Sebastien,
thank you for additional info about previously working kernel.
it looks like your older kernel, which works, might be running without
my commit
revision 1.1116
date: 2021/04/27 09:38:29; author: sashan; state: Exp;\
lines: +14 -6; commitid: 3W1fRTkLb3ZlUanF;
On 2021/05/03 21:51, Jon Fineman wrote:
> For cpan/cpanm I had gotten the same base64 error.
>
> After moving those two directories and rebooting I was able to run pkg_add
> and now cpanm. However cpan now gets the below error:
> desktop(~)$: cpan
> Encode.c: loadable library and perl binaries
On Tue, May 04, 2021 at 11:47:55AM +0200, Alexandr Nedvedicky wrote:
> Hello Sebastien,
>
> On Tue, May 04, 2021 at 11:08:19AM +0200, Sebastien Marie wrote:
> > Hi,
> >
> > Currently, I am regulary (~1 per day) get panic on an amd64 host (OpenBSD
> > 6.9-current (GENERIC.MP) #492: Sat May 1
On Tue, May 04, 2021 at 10:27:05AM +0200, Matthias Pressfreund wrote:
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
> 2021
>
>
There are two issues in there:
one is using cpan and not breaking stuff, for which I don't know the
solution, which is probably what afresh suggests.
On the other hand, we have base perl looking under /usr/local which is not
bad per se.
But base tools need to be restricted a bit, most probably
Hello Sebastien,
On Tue, May 04, 2021 at 11:08:19AM +0200, Sebastien Marie wrote:
> Hi,
>
> Currently, I am regulary (~1 per day) get panic on an amd64 host (OpenBSD
> 6.9-current (GENERIC.MP) #492: Sat May 1 17:37:28 MDT 2021).
>
> panic: kernel diagnostic assertion "refcnt != ~0" failed:
Hi,
Currently, I am regulary (~1 per day) get panic on an amd64 host (OpenBSD
6.9-current (GENERIC.MP) #492: Sat May 1 17:37:28 MDT 2021).
panic: kernel diagnostic assertion "refcnt != ~0" failed: file
"/usr/src/sys/kern/kern_synch.c", line 826
Starting stack trace...
panic(81dfbc8e)
>Environment:
System : OpenBSD 6.9
Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
18 matches
Mail list logo