RE: port-amd64/32816

[Paul Goyette <paul%whooppee.com@localhost>]

The following reply was made to PR port-amd64/32816; it has been noted by GNATS.

From: Paul Goyette <paul%whooppee.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: RE: port-amd64/32816
Date: Thu, 27 Nov 2008 06:48:28 -0800 (PST)

 As reported oncurrent-users, here's another instance of this bug, with a 
 different back-trace.  In this case, kernel was apparently trying to 
 unmap a module.
 
 ---------- Forwarded message ----------
 Date: Wed, 26 Nov 2008 19:45:41 -0800 (PST)
 From: Paul Goyette <paul%whooppee.com@localhost>
 To: current-users%netbsd.org@localhost
 Subject: Module problem on amd64
 
 I've built a amd64 kernel without any file systems or compat code in the 
kernel 
 itself;  all of those options lines are commented out in the config file.
 
 I've installed the new kernel and the 5.99.03/modules and the new /boot (from 
 /usr/mdec/boot).
 
 Shortly after booting, while the various /etc/rc.d/ stuff is still going on, 
 the system panics.  Unfortunately, it seems to happen just as soon as xdm 
takes 
 over the console/display.
 
 So, I rebooted in single-user mode, and of course I needed to run fsck on my 
 root partition.  During the fsck, I got the following panic:
 
 panic: kernel diagnostic assertion "end <= VM_MAX_KERNEL_ADDRESS" failed: file 
 "/build/netbsd-local/src/sys/uvm/uvm_km.c", line 473
 fatal breakpoint trap in supervisor mode
 trap type 1 code 0 rip ffffffff80151565 cs 8 rflags 246 cr2 f0cbc9 cpl 0 rsp 
 ffff80004bedaa90
 Stopped in pid 0.8 (system) at netbsd:breakpoint+0x5:   leave
 0x1
 
 A backtrace produces
 
 breakpoint()+0x5
 panic()+0x260
 __kernassert()+0x2d
 uvm_km_pgremove_intrsafe()+0x198
 uvm_km_free()+0xb5
 kobj_unload()+0x58
 module_do_unload()+0xcd
 module_thread()+0xe9
 
 The config file and dmesg output available on request.