On Sat, 22 Jan 2022, Martin Husemann wrote:
Date: Sat, 22 Jan 2022 08:36:22 +
From: Martin Husemann
To: Christos Zoulas
Cc: current-users@netbsd.org
Subject: [Extern] Re: netbsd-9.99.93 crash
On Mon, Jan 10, 2022 at 10:18:02PM -, Christos Zoulas wrote:
In article ,
<
etbsd-9.99.93 crash
On Mon, Jan 10, 2022 at 10:18:02PM -, Christos Zoulas wrote:
In article ,
<6b...@6bone.informatik.uni-leipzig.de> wrote:
Does that help?
Regards
Uwe
I have the same issue and I can reproduce this on demand. I have disabled
IPv6 on this router.
Has this been fi
On Mon, Jan 10, 2022 at 10:18:02PM -, Christos Zoulas wrote:
> In article
> ,
> <6b...@6bone.informatik.uni-leipzig.de> wrote:
> >Does that help?
> >
> >Regards
> >Uwe
>
> I have the same issue and I can reproduce this on demand. I have disabled
> IPv6 on this router.
Has this been fixed? I
In article ,
<6b...@6bone.informatik.uni-leipzig.de> wrote:
>Does that help?
>
>Regards
>Uwe
I have the same issue and I can reproduce this on demand. I have disabled
IPv6 on this router.
christos
ect: [Extern] Re: netbsd-9.99.93 crash
You need to identify what the "last lockecd" location is, something
like:
gdb netbsd.gdb # or just netbsd, if you do not have a netbsd.gdb
gdb> list *(0x80ea0a90)
(I never can remember the equivalent addr2line flags fo
You need to identify what the "last lockecd" location is, something
like:
gdb netbsd.gdb # or just netbsd, if you do not have a netbsd.gdb
gdb> list *(0x80ea0a90)
(I never can remember the equivalent addr2line flags for this, probably:
addr2line -a 0x80ea0a90 -e n
Hi there,
when starting the network the kernel crashes.
Does anyone have an idea what the problem could be?
Thank you for your efforts
Regards
Uwe
dmesg -M netbsd.14.core -N netbsd.14
...
[28.382481] boot device: sd0
[28.382481] root on sd0a dumps on sd0b
[28.382481] dump_misc_in
