On Tue, Apr 12, 2022 at 06:44:09AM +0200, Sebastien Marie wrote:
On Mon, Apr 11, 2022 at 10:35:37PM +0300, Andrew Krasavin wrote:
Unfortunately, I didn't have a chance to get to my home computer last
week and provide you with the information you need. My apologies.
It isn't a problem. but I will be still interested by result on your computer,
as it could help to figure the problem.
Of course. I wouldn't think of refusing to give you information. I
would be glad if I could do something to help you find the cause of
the problem. Feel free to ask me for any information you need about
it.
I successfully built the latest current snapshot with your diff and
booted with the new kernel. The panic was reproduced in the same way
as on previous times.
This time, with your permission, I will post photos. If necessary,
I can reprint what would be desirable to translate into text (please
let me know if such a thing is needed).
trace:
http://46.23.91.227:8098/trace0.jpg
http://46.23.91.227:8098/trace1.jpg
Scrollback in the ddb console did not work for me for some reason.
However, the 'dmesg' command seemed to show everything we needed:
http://46.23.91.227:8098/console0.jpg
http://46.23.91.227:8098/console1.jpg
http://46.23.91.227:8098/console2.jpg
http://46.23.91.227:8098/console3.jpg
http://46.23.91.227:8098/console4.jpg
http://46.23.91.227:8098/console5.jpg
http://46.23.91.227:8098/console6.jpg
But just in case, here is also the output of the 'show vnode'
command itself:
http://46.23.91.227:8098/show_vnode0.jpg
http://46.23.91.227:8098/show_vnode1.jpg
http://46.23.91.227:8098/show_vnode2.jpg
http://46.23.91.227:8098/show_vnode3.jpg
show mount:
http://46.23.91.227:8098/show_mount.jpg
show uvm:
http://46.23.91.227:8098/show_uvm.jpg
After I rebooted into OS from ddb and got distracted by some
personal stuff, qbittorrent continued rechecking from where it
stopped during the panic (about half of 27Gb). I was searching for
something in firefox at the time.
Very soon I saw the kernel panic again, now with a slightly different
content. I'm not sure if these things are related, but just in case,
I'll leave the data from the console for this panic as well:
http://46.23.91.227:8098/second_panic0.jpg
http://46.23.91.227:8098/second_panic_bcstats.jpg
http://46.23.91.227:8098/second_panic_precpu0.jpg
http://46.23.91.227:8098/second_panic_precpu1.jpg
http://46.23.91.227:8098/second_panic_uvm.jpg
(I suspect I should open a separate bug report for this problem?)
--
Wbr, Andrew Krasavin
