tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Differences between NetBSD 3.0 and 4.0 [was: with regard to the filesystem] + how to reproduce



Hi,

Here are simple reproduce instructions for AMD64:

cd /usr/src/sys/lkm
make depend
make all
make install
modload -o pf.t  /usr/lkm/pf.o

Leads to:

panic: kernel debugging assertion "end <= VM_MAX_KERNEL_ADDRESS" failed: 
file "../../../../uvm/uvm_km.c", line 496
Stopped in pid 5993.1 (modload) at      netbsd:cpu_Debugger+0x5:        leave

db> print end
ffffffff80b6b408

Conclusion: Modules do not work at all on AMD64.

Next: How to fix.

--HPS

> Hi,
>
> I compiled a NetBSD 4.0 GENERIC kernel with DEBUG + DIAGNOSTICS and got the
> following when I tried to load my module. Without DEBUG + DIAGNOSTICS my
> module loaded fine.
>
> ...
> root on wd0a dumps on wd0b
> mountroot: trying lfs...
> mountroot: trying ffs...
> root file system type: ffs
> init: copying out path `/sbin/init' 11
> wsdisplay0: screen 1 added (80x25, vt100 emulation)
> wsdisplay0: screen 2 added (80x25, vt100 emulation)
> wsdisplay0: screen 3 added (80x25, vt100 emulation)
> wsdisplay0: screen 4 added (80x25, vt100 emulation)
> panic: kernel debugging assertion "end <= VM_MAX_KERNEL_ADDRESS" failed:
> file ".
> ./../../../uvm/uvm_km.c", line 496
> uvm_fault(0xffff800048569160, 0x0, 1) -> e
> uvm_fault(0xffff800048569160, 0x0, 1) -> e
> db> bt
> cpu_Debugger() at netbsd:cpu_Debugger+0x5
> panic() at netbsd:panic+0x1fc
> __assert() at netbsd:__assert+0x21
> uvm_km_check_empty() at netbsd:uvm_km_check_empty+0x110
> uvm_map() at netbsd:uvm_map+0x152
> uvm_km_alloc() at netbsd:uvm_km_alloc+0xa9
> lkmioctl() at netbsd:lkmioctl+0x539
> VOP_IOCTL() at netbsd:VOP_IOCTL+0x32
> vn_ioctl() at netbsd:vn_ioctl+0x76
> sys_ioctl() at netbsd:sys_ioctl+0x197
> syscall_plain() at netbsd:syscall_plain+0x112
> uvm_fault(0xffff800048569160, 0x0, 1) -> e
> kernel: page fault trap, code=0
> Faulted in DDB; continuing...
> db>
>
> How can this be fixed and what is the cause of the problem ?
>
> I am using NetBSD 4.0 Release on AMD64 .
>
> I need to have all issues with my ISDN4BSD module on NetBSD 4.0 resolved by
> the end of April else FreeBSD will be used.
>
> --HPS


Home | Main Index | Thread Index | Old Index