Bug 280642

Summary:

13.4-BETA1: Panic while installing packages in VirtualBox

Product:

Base System

Reporter:

Jason W. Bacon <jwb>

Component:

kern

Assignee:

freebsd-virtualization (Nobody) <virtualization>

Status:

Open ---

Severity:

Affects Some People

CC:

markj

Priority:

---

Keywords:

crash

Version:

Unspecified

Hardware:

amd64

OS:

Any

Attachments:

Description	Flags
Manually generated core.txt.0	none

Description Jason W. Bacon freebsd_committer

2024-08-06 00:10:02 UTC

Installed 13.4-BETA1 under VirtualBox, FreeBSD 14.0 host fully up-to-date as of Aug 4.

Ran desktop-installer and was waiting for the many pkg installs to run, when suddenly the VM rebooted.  Got the following from /var/crash:

Dump header from device: /dev/ada0p3
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 225968128
  Blocksize: 512
  Compression: none
  Dumptime: 2024-08-05 18:52:10 -0500
  Hostname: freebsd13.local
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 13.4-BETA1 releng/13.4-n258208-e192230d0de8 GENERIC
  Panic String: sleeping thread
  Dump Parity: 3764632698
  Bounds: 0
  Dump Status: good

After removing the corrupted pkg database (local.sqlite) and starting over, desktop-installer completed without incident.  I will continue to run the VM and follow up if any more problems occur.

Comment 1 Mark Johnston freebsd_committer

2024-08-09 17:42:57 UTC

Please provide at least the core.txt from this crash so that we can see the backtrace.

Comment 2 Jason W. Bacon freebsd_committer

2024-08-10 12:58:53 UTC

(In reply to Mark Johnston from comment #1)

core.txt simply states that no gdb was found.  As I'm unable to attach a tarball of /var/crash, I placed a copy at https://acadix.biz/Debug/crash.txz.

Comment 3 Jason W. Bacon freebsd_committer

2024-08-10 13:13:29 UTC

Created attachment 252655 [details]
Manually generated core.txt.0

Following the developer's handbook, I manually ran crashinfo after installing gdb to regenerate the core.txt.0 file attached here.

Comment 4 Mark Johnston freebsd_committer

2024-08-10 15:50:57 UTC

This looks to be a bug in the virtualbox kernel module.  After a bit of time looking, I can't really tell which lock it's referring to.  I pushed commit aea9dba46b81abc5c0fd4c42d3ac762d3bc1de37 to help address that, but that doesn't help here of course.

Comment 5 Jason W. Bacon freebsd_committer

2024-08-10 16:54:30 UTC

(In reply to Mark Johnston from comment #4)

I repeated the installation from scratch with the exact same VM config, and did not reproduce the problem.

Since it's intermittent, and probably VirtualBox-specific, I wouldn't give it a high priority.