Panic in recent 7.2-Stable
Dmitrij Tejblum
tejblum at yandex-team.ru
Sun Sep 6 10:11:43 UTC 2009
Thierry Herbelot wrote:
> Hello,
>
> I'm having a panic with the latest kernel build of my -Stable file server
> (sources cvsupped around yesterday evening, CEST). The panic happens soon
> after entering multi-user :
>
> panic: vm_phys_paddr_to_vm_page: paddr 0xf0000 is not in any segment
> KDB: enter: panic
> [thread pid 1005 tid 100154 ]
> Stopped at kdb_enter_why+0x3a: movl $0,kdb_why
> db> where
> Tracing pid 1005 tid 100154 td 0x8ecad480
> kdb_enter_why(80ba731f,80ba731f,80bc1ad6,fb301a94,fb301a94,...) at
> kdb_enter_why+0x3a
> panic(80bc1ad6,f0000,0,8ecad480,0,...) at panic+0xd1
> vm_phys_paddr_to_vm_page(f0000,f0000,fb301ad8,1,80a36a78,...) at
> vm_phys_paddr_to_vm_page+0x4d
> dev_pager_getpages(92b8d980,fb301c04,1,0,fb301bcc,...) at
> dev_pager_getpages+0xe1
> vm_fault(89267bfc,33d90000,1,0,89b0b50c,...) at vm_fault+0x1020
> trap_pfault(202,7,8583b900,80cd9800,89b0eb00,...) at trap_pfault+0x15b
> trap(fb301d38) at trap+0x247
>
Similar panic here. I believe, the panic introduced in SVN revision 196838.
For us, the panic is caused by the `dmidecode' program. The dmidecode
program mmap /dev/mem at offset 0xf0000 and reads on...
More information about the freebsd-stable
mailing list