Date: Thu, 25 Jan 2024 15:34:54 +0800 From: Zhenlei Huang <zlei@FreeBSD.org> To: void <void@f-m.fm> Cc: freebsd-current@freebsd.org Subject: Re: loading vmm.ko crashes main-n267684-e4b646ce1610 Message-ID: <36DAFC0F-EDB2-49D9-94D5-60CBEEB360EC@FreeBSD.org> In-Reply-To: <8db9d82d-37a8-472a-adbf-4565748adac4@app.fastmail.com> References: <8db9d82d-37a8-472a-adbf-4565748adac4@app.fastmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On Jan 24, 2024, at 8:47 AM, void <void@f-m.fm> wrote: > > Hello, > > Loading vmm either via vmm_load=YES in /boot/loader.conf or > manually via kldload vmm crashes the system to db> prompt > as shown in the link below: > > http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png > > Thing is, access is via a html5 console with no up/down scrolling > or buffer. Nothing can be entered into the db> prompt. There's plenty > more information when it crashes, but the output scrolls off the top. > > The main-n267684 is running a modified GENERIC-NODEBUG > kernel and has debugging turned off in /etc/src.conf > (it has WITHOUT_ASSERT_DEBUG= and WITHOUT_DEBUG_FILES= and > WITH_MALLOC_PRODUCTION=) > > Apart from turning these on again and rebuilding GENERIC, what other things > need to be set to get a usable coredump when this happens? You may want to configure the dump device before get the coredump. See https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain <https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain>; . > > /var/crash has nothing in it. > > thanks in advance for any assistance > -- > Best regards, Zhenlei [-- Attachment #2 --] <html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 24, 2024, at 8:47 AM, void <<a href="mailto:void@f-m.fm" class="">void@f-m.fm</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello,<br class=""><br class="">Loading vmm either via vmm_load=YES in /boot/loader.conf or<br class="">manually via kldload vmm crashes the system to db> prompt<br class="">as shown in the link below:<br class=""><br class=""><a href="http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png" class="">http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png</a><br class=""><br class="">Thing is, access is via a html5 console with no up/down scrolling<br class="">or buffer. Nothing can be entered into the db> prompt. There's plenty<br class="">more information when it crashes, but the output scrolls off the top.<br class=""><br class="">The main-n267684 is running a modified GENERIC-NODEBUG<br class="">kernel and has debugging turned off in /etc/src.conf <br class="">(it has WITHOUT_ASSERT_DEBUG= and WITHOUT_DEBUG_FILES= and <br class="">WITH_MALLOC_PRODUCTION=)<br class=""><br class="">Apart from turning these on again and rebuilding GENERIC, what other things<br class="">need to be set to get a usable coredump when this happens?<br class=""></div></div></blockquote><div><br class=""></div><div>You may want to configure the dump device before get the coredump.</div><div>See <a href="https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain" class="">https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain</a> .</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">/var/crash has nothing in it.<br class=""><br class="">thanks in advance for any assistance<br class="">-- <br class=""><br class=""></div></div></blockquote></div><br class=""><div class=""> <div>Best regards,</div><div>Zhenlei</div> </div> <br class=""></body></html>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36DAFC0F-EDB2-49D9-94D5-60CBEEB360EC>