14.2-RELEASE Kernel Panic

S

smdb01us

Howdy,

I have a Beelink with Intel N100 with 14.2-RELEASE (amd64) installed. It had been running with no issues as my home FW for about 3 weeks. I woke up this morning with the machine was not responding to pings. I connected a monitor and found that the machine had been rebooting all night with a kernel panic (attached screenshot).

I was planning on re-installing FreeBSD but wanted to see if perhaps this was a bug and if there is any information that could be gathered to fix it that I can provide. If it is a file/driver corruption, will just reinstall.

Thoughts?
 

Attachments

  • IMG_1184.jpg
    IMG_1184.jpg
    2 MB · Views: 498
The panic comes from ZFS code. The ultimate cause might be a hardware malfunction, software bug or even both.

You can try capturing a kernel core dump in case it will help the developers. If you have a swap partition that you can use as a dump device, you can set dumpdev=/dev/da7p8 from the loader prompt. The kernel should automatically dump to the specified dump device and then you can either copy the dump device's contents to a file with dd(1) (this is the easier way; the post-processing can be done by developers) or try to use savecore(8) when booted from rescue media (this requires more skill). If you can afford the disk space, saving a perfect copy of the whole zpool could also help developers.

After you optionally save a core dump, you should inspect your zpool and the ZFS filesystems on it. Look at log files for clues on when the problem occurred and what preceded it.

In a bug report you should also describe your ZFS configuration including what features you use (e.g. encryption).
 
Thank you JordanG, I can confirm it is from the ZFS code as I as soon as I try to mount the zroot, I get a kernel panic in both single user (from USB installer) or even when running the installer, when it tries to overwrite the existing internal drive setup. I just changed from ZFS to UFS during install and the installation is proceeding...
 
Are you sure you are running 14.2-RELEASE?

Stack Backtrace comes from debugging which is only enabled by default on -CURRENT
 
Phishfry said:
Are you sure you are running 14.2-RELEASE?

Stack Backtrace comes from debugging which is only enabled by default on -CURRENT
Click to expand...
Yes, absolutely. Not sure how backtrace was enabled on -RELEASE, I don’t recall messing with that at all.
 
Phishfry said:
I could be wrong....
Click to expand...
Or, I could… but I only have one media to install and used it to reinstalled it:

system:~ % freebsd-version
14.2-RELEASE

system:~ % uname -a
FreeBSD system 14.2-RELEASE FreeBSD 14.2-RELEASE releng/14.2-n269506-c8918d6c7412 GENERIC amd64
 
You must log in or register to reply here.
Back
Top