pkgx: Kernel panic when installing.

I’ve had my second kernel panic while installing something with Tea. I can’t imagine why Tea would do this. But it’s happened twice now so I’m going to create this issue. Here’s the text from Discord for the first panic (on November 4th).

My M1 panicked while I was installing go. The process that crashed was kernel_task. Here are the parts from the panic log that might be remotely interesting.

"build" : "macOS 12.6 (21G115)",
"product" : "MacBookAir10,1",
"kernel" : "Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101",
"date" : "2022-11-04 22:17:42.18 -0600",
"panicString" : "panic(cpu 1 caller 0xfffffe002816b53c): watchdog timeout: no checkins from watchdogd in 94 seconds (895 total checkins since monitoring last enabled)

Panicked task 0xfffffe201c754678: 0 pages, 479 threads: pid 0: kernel_task

last started kext at 386692668936: com.apple.filesystems.smbfs\t4.0 (addr 0xfffffe00276366c0, size 65195)

last 2 processes

"procname":"tea"
"procname":"bsdtar"

The second panic happened today. I ran tea +python.org~3.10 pip. Neither python nor pip was installed when I ran it. The panic log looked very similar to the first. Besides memory addresses, the first real difference started at last started kext.

last started kext at 3141788048810: com.apple.UVCService\t1 (addr 0xfffffe0021a60450, size 1772)
last stopped kext at 888788618382: com.apple.filesystems.msdosfs\t1.10 (addr 0xfffffe0021b1a7d0, size 5926)

The last process is bsdtar again. Could that be causing a kernel panic?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (14 by maintainers)

Most upvoted comments

It has not happened again, but I haven’t really installed much with tea in a while. I’ll close this issue, but here’s what I’ll do. I just wrote a shell script that is running a while loop that uninstalls and reinstalls tea and every tea package. I’ll let it run all weekend, and heck, why not all next week too? If tea is causing kernel panics, this should expose it.