Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Mar 2022 18:38:41 +0200
From:      Ze Dupsys <zedupsys@gmail.com>
To:        =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
Cc:        freebsd-xen@freebsd.org, buhrow@nfbcal.org
Subject:   Re: ZFS + FreeBSD XEN dom0 panic
Message-ID:  <088c8222-063a-1db5-da83-a5a0168d66c6@gmail.com>
In-Reply-To: <YjybrgeORadwBmjP@Air-de-Roger>
References:  <Yi8IvnqWUoWBIsLB@Air-de-Roger> <ca88a8c8-3b4e-fbde-18a7-d4e5f61e8b2c@gmail.com> <YjSkIZmV%2Bt8Q3AEn@Air-de-Roger> <b5fc1a74-6a52-e237-4a69-2b3f8d4974bd@gmail.com> <YjheCAFXykUZz/pz@Air-de-Roger> <d1d8f552-15a3-3d4f-1143-2e1cae7904ee@gmail.com> <YjipQwBQ/JTo4S6G@Air-de-Roger> <Yji8NZePmovLFhk2@Air-de-Roger> <YjxuPF80Z8z0V58t@Air-de-Roger> <abcdae23-eea9-93c3-04da-61b7f79a99e9@gmail.com> <YjybrgeORadwBmjP@Air-de-Roger>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2022.03.24. 18:26, Roger Pau Monné wrote:
> 
> This seems to be a fairly common trace for your panics:
> 
> #0 0xffffffff80c74605 at kdb_backtrace+0x65
> #1 0xffffffff80c26611 at vpanic+0x181
> #2 0xffffffff80c26483 at panic+0x43
> #3 0xffffffff810c1b97 at trap+0xba7
> #4 0xffffffff810c1bef at trap+0xbff
> #5 0xffffffff810c1243 at trap+0x253
> #6 0xffffffff81098c58 at calltrap+0x8
> #7 0xffffffff80c7f251 at rman_is_region_manager+0x241
> #8 0xffffffff80c36e71 at sbuf_new_for_sysctl+0x101
> #9 0xffffffff80c362bc at kernel_sysctl+0x3ec
> #10 0xffffffff80c36933 at userland_sysctl+0x173
> #11 0xffffffff80c3677f at sys___sysctl+0x5f
> #12 0xffffffff810c249c at amd64_syscall+0x10c
> #13 0xffffffff8109956b at Xfast_syscall+0xfb
> 
> Could you give me the output of executing the following on dom0:
> 
> $ addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c7f251
> $ addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c36e71
> $ addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c362bc
> $ addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c36933
> $ addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c3677f

Yes, i'd say that with current stress test the panic message always 
contains rman_is_region_manager in mid.

  addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c7f251
/usr/src/sys/kern/subr_rman.c:0

  addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c36e71
/usr/src/sys/kern/kern_sysctl.c:185

addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c362bc
/usr/src/sys/kern/kern_sysctl.c:2305

addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c36933
/usr/src/sys/kern/kern_sysctl.c:2462

addr2line -e /usr/lib/debug/boot/kernel/kernel.debug 0xffffffff80c3677f
/usr/src/sys/kern/kern_sysctl.c:2335

At the moment: uname -a
FreeBSD lab-01.localnet 13.1-STABLE FreeBSD 13.1-STABLE #27 
stable/13-812638797-dirty: Tue Mar 22 19:45:17 EET 2022 
root@lab-01.localnet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

Thanks.







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?088c8222-063a-1db5-da83-a5a0168d66c6>