Date: Tue, 28 Feb 2023 22:19:58 -0500 From: Richard Hurt <rnhurt@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-stable@freebsd.org Subject: Re: OPNSense (FreeBSD 13.1-p6) kernel panic Message-ID: <CAAFV=K3K79-5cvUn2CSKtG15Adrz6SbWtzxYcDh0y3nD1E2bNA@mail.gmail.com> In-Reply-To: <82564799-2ab9-f19f-0fa8-a069325c0e7a@grosbein.net> References: <CAAFV=K1c_emsV-jnefpfr%2BYTSgVggAiuQ85kqyNyGLroEKmXog@mail.gmail.com> <82564799-2ab9-f19f-0fa8-a069325c0e7a@grosbein.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Yes, that was exactly the problem. Sorry for wasting everyone's time. -- Richard On Tue, Feb 28, 2023 at 9:29 AM Eugene Grosbein <eugen@grosbein.net> wrote: > 28.02.2023 19:25, Richard Hurt wrote: > > > After a recent OPNSense update my HD activity light was staying on and > the CPU meter on the OPNSense dashboard was reading 100%. After looking > for anything obvious and turning off all the services I could, the CPU was > still pegged and the HD light was still on constantly. So I rebooted the > machine; it never came back online. > > > > After I attached a monitor to the machine I saw that it had a kernel > panic. While unusual I didn't think too much of it however rebooting the > machine didn't resolve the issue. So, I removed all the cards, memory, > etc. to see if I could get a clean boot. Nothing helped and I continued to > get a kernel panic. > > > > I thought it might be a corrupted hard drive or something so I > disconnected the drive and booted off a USB thumb drive with a fresh copy > of OPNSense v23.1 installed on it. The system booted just fine and ran the > live version. So I turned the machine off, reconnected the drive, rebooted > and installed v23.1 on the HD. The install worked perfectly and the > machine rebooted. Once again, I got the kernel panic. > > > > My next thought was that maybe the HD was "bad". I replaced the HD and > again installed a fresh copy of v23.1. Again, the kernel panic showed up. > Arrggghhh! > > > > I'm running Memtest86 v6.10 right now and it has passed 4 times, so I > don't think it's memory related. I've replaced the HD so that's (probably) > not the problem. It seems to work fine when booting from the USB flash > drive (it's just slooooow) so the CPU seems to be OK. > > > > After the kernel panic the machine is locked up completely. Nothing > works. The keyboard doesn't do anything, the capslock key doesn't, light > up and the floppy drive light is stuck on. > > > > I've not been able to get a text output of the panic but here is a > screenshot I took from my phone: https://imgur.com/a/aaXwkVK I posted > about this first on the OPNSense forum ( > https://forum.opnsense.org/index.php?topic=32728.msg158386#msg158386) but > they said that this mailing list was probably the better option. > > > > Equipment: > > * Acer Aspire AST180-UA380B > > * AMD Athlon 3800+ > > * 3GB RAM > > * 1TB SATA drive > > > > Thanx > > Richard > > The problem seems to be known and specific to OPNSense that change some > default FreeBSD settings > unconditionally, no matter if hardware's compatible with non-default > setting or not: > > https://github.com/opnsense/core/issues/3177 > > > > [-- Attachment #2 --] <div dir="ltr">Yes, that was exactly the problem. Sorry for wasting everyone's time.<br clear="all"><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br></div><div>--</div><div>Richard<br></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 28, 2023 at 9:29 AM Eugene Grosbein <<a href="mailto:eugen@grosbein.net">eugen@grosbein.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">28.02.2023 19:25, Richard Hurt wrote:<br> <br> > After a recent OPNSense update my HD activity light was staying on and the CPU meter on the OPNSense dashboard was reading 100%. After looking for anything obvious and turning off all the services I could, the CPU was still pegged and the HD light was still on constantly. So I rebooted the machine; it never came back online.<br> > <br> > After I attached a monitor to the machine I saw that it had a kernel panic. While unusual I didn't think too much of it however rebooting the machine didn't resolve the issue. So, I removed all the cards, memory, etc. to see if I could get a clean boot. Nothing helped and I continued to get a kernel panic.<br> > <br> > I thought it might be a corrupted hard drive or something so I disconnected the drive and booted off a USB thumb drive with a fresh copy of OPNSense v23.1 installed on it. The system booted just fine and ran the live version. So I turned the machine off, reconnected the drive, rebooted and installed v23.1 on the HD. The install worked perfectly and the machine rebooted. Once again, I got the kernel panic.<br> > <br> > My next thought was that maybe the HD was "bad". I replaced the HD and again installed a fresh copy of v23.1. Again, the kernel panic showed up. Arrggghhh! <br> > <br> > I'm running Memtest86 v6.10 right now and it has passed 4 times, so I don't think it's memory related. I've replaced the HD so that's (probably) not the problem. It seems to work fine when booting from the USB flash drive (it's just slooooow) so the CPU seems to be OK. <br> > <br> > After the kernel panic the machine is locked up completely. Nothing works. The keyboard doesn't do anything, the capslock key doesn't, light up and the floppy drive light is stuck on.<br> > <br> > I've not been able to get a text output of the panic but here is a screenshot I took from my phone: <a href="https://imgur.com/a/aaXwkVK" rel="noreferrer" target="_blank">https://imgur.com/a/aaXwkVK</a> I posted about this first on the OPNSense forum (<a href="https://forum.opnsense.org/index.php?topic=32728.msg158386#msg158386" rel="noreferrer" target="_blank">https://forum.opnsense.org/index.php?topic=32728.msg158386#msg158386</a>) but they said that this mailing list was probably the better option.<br> > <br> > Equipment:<br> > * Acer Aspire AST180-UA380B<br> > * AMD Athlon 3800+<br> > * 3GB RAM<br> > * 1TB SATA drive<br> > <br> > Thanx<br> > Richard<br> <br> The problem seems to be known and specific to OPNSense that change some default FreeBSD settings<br> unconditionally, no matter if hardware's compatible with non-default setting or not:<br> <br> <a href="https://github.com/opnsense/core/issues/3177" rel="noreferrer" target="_blank">https://github.com/opnsense/core/issues/3177</a><br>; <br> <br> <br> </blockquote></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAFV=K3K79-5cvUn2CSKtG15Adrz6SbWtzxYcDh0y3nD1E2bNA>