Repository navigation
Sometimes a kernel panic occurs #42
Description
Activity
Thanks for the detailed report. This panic is happening inside Apple's own tmpfs kernel extension (
com.apple.filesystems.tmpfs), which TmpDisk hands off to via the systemmount_tmpfstool. Once the volume is mounted, the kext is entirely out of TmpDisk's control, so unfortunately there's nothing I can patch on my end to prevent it.The best place for this is a Feedback Assistant report to Apple with the full panic/JetsamEvent log attached, since it's their kext.
As a workaround, you can avoid the tmpfs path completely by creating an APFS or HFS+ RAM disk instead (that's the default) — those use
hdiutil/diskutilrather than the tmpfs kext, so they don't go through the code that's panicking.I'll leave this open for visibility in case others run into it.
There seems to be some bugs in the macos tmpfs kernel extension
The following are some brief log information
bug_type: 210 (JetsamEvent)
panicString:
panic(cpu 4 caller 0xfffffe0030ed7e74): "tmpfs_alloc_vp: type 0xfffffe1b400a5540 0" @tmpfs_subr.c:686backtrace:
Panicked task 0xfffffe29ae08f990: 51149 pages, 21 threads: pid 3391: Finderkext:
com.apple.filesystems.tmpfs(1.0)If you need the full JetsamEvent and panic-full log information, let me know and I'll send it via email.