kernel panic #2

tscholak opened this Issue Mar 23, 2012 · 5 comments


None yet

2 participants


Hi nigoro, thx for this astonishing work.

I went through your fbsd 9 amd64 zfs guide without problems, but see myself now confronted with a kernel panic at boottime. I'm using vmware fusion 4.1.1 on a mac. (I have also tried virtualbox 4.1.10 to no success.) The kernel output reads as follows:

nfslock: pseudo-device
mem: <memory


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x70
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff80b48d95
stack pointer = 0x28:0xffffffff81628bb0
frame pointer = 0x28:0xffffffff81628c00
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
trap number = 12
panic: page fault
cupid = 0
KDB: stack backtrace:
#0 0xffffffff808a0bce at kdb_backtrace+0x5e
#1 0xffffffff8086acd7 at panic+0x147
#2 0xffffffff80b61a0f at trap_fatal+0x29f
#3 0xffffffff80b61e7c at trap_pfault+0x31c
#4 0xffffffff80b6225e at trap+0x3ce
#5 0xffffffff80b4aa8f at calltrap+0x8
#6 0xffffffff80b4809f at nexus_acpi_attach+0x7f
#7 0xffffffff8089b934 at device_attach+0xa4
#8 0xffffffff8089c748 at bus_generic_new_pass+0xf8
#9 0xffffffff8089852e at bus_set_pass+0x7e
#10 0xffffffff80b4a09a at configure+0xa
#11 0xffffffff8081f7e5 at mi_startup+0xa5
#12 0xffffffff802b8bac at btext+0x2c

Uptime = 1s
Automatic reboot in 15 seconds - press a key on the console to abort

This happens when ACPI is enabled. When I turn it off, the boot fails at a later stage, after loading zfs:

procfs registered
FS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 5
ZFS storage pool version 28
panic: No usable event timer found!
cpuid = 0
KDB stack backtrace:
#0 0xffffffff808a0bce at kdb_backtrace+0x5e
#1 0xffffffff8086acd7 at panic+0x147
#2 0xffffffff80b9e35d at cpu_initclocks_bsp+0x3fd
#3 0xffffffff80820cd0 at initclocks+0x20
#4 0xffffffff8081f7e5 at mi_startup+0xa5
#5 0xffffffff802b8bac at btext+0x2c

Uptime: 1s
Automated reboot in 15 seconds - press a key on the console to abort

Btw, the vanilla GENERIC kernel on the freebsd 9 release image loads without problems. Is there some way I can copy this kernel to my boot partition and use it instead of the one I compiled using your guide?

The problem seems to be quite similar to these stories, I'm not sure though:

Do you have any idea what's going on?

nigoro commented Mar 23, 2012

hi tscholak, thank you for your interest in my overlay.

I don't have a Mac. I'll check this problem with VMware (Windows ver) so.
However, I can not check immediately...

Please use the vanilla kernel until this issue is resolved.

My patch for freebsd-sources*.ebuild might be incorrect.
may be solved by compiling the kernel with gcc-4.3.

sample howto)

  1. emerge -C freebsd-sources
  2. rm -rf /usr/src/sys-9.0-r0
  3. USE="symlink" emerge -a sys-freebsd/freebsd-sources::gentoo
  4. emerge '<gcc-4.4'
  5. gcc-config -l
    [1] x86_64-gentoo-freebsd8.2-4.3.4
    [2] x86_64-gentoo-freebsd8.2-4.4.5 *
  6. gcc-config 1
  7. source /etc/profile
  8. gcc -v
    gcc version 4.3.4 (Gentoo 4.3.4 p1.3, pie-10.1.5)
  9. Compiling and installing the kernel !
  10. gcc-config -l
    [1] x86_64-gentoo-freebsd8.2-4.3.4 *
    [2] x86_64-gentoo-freebsd8.2-4.4.5
  11. gcc-config 2
  12. source /etc/profile

Thanks in advance.


Thank you, now fun can begin


me again: should I remove 'zfs volinit' and 'zfs volfini' from /etc/init.d/zvol? These commands seem to be no longer available.

nigoro commented Mar 24, 2012

I'm glad to hear your kernel has booted.

In the version containing ZFS v28 (ex. FreeBSD 9.0/8.3), it's unnecessary.
Please remove them.
In addition, it's a bug common G/FBSD.
Would you make a report about zvol to the official Gentoo Bugzilla ?


Thanks in advance.

nigoro commented May 16, 2012

This problem has been fixed officially.

@nigoro nigoro closed this May 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment