Subject: Todays uvm changes causes panic (at least) on i386
To: None <current-users@netbsd.org, port-i386@netbsd.org>
From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
List: current-users
Date: 11/01/2003 17:34:52
Hi!

Freshly compiled kernels for my dual i386 machine (with and w/o
MULTIPROCESSOR) panic. The MULTIPROCESSOR one stops with the following
messages:

[...]
cpu0: apic clock running at 268 MHz
cpu0: 8 page colors
cpu1 at mainbus0: apid 1 (application processor)
panic: kernel diagnostic assertion "tmp->next->start == tmp->end + tmp->ownspace" failed: file "../../../../uvm/uvm_map.c", line 1456
Stopped in pid 0.1 (swapper) at netbsd:cpu_Debugger+0x4:        leave
db{0}> t
cpu_Debugger(c0421902,c0527b74,7,1,40) at netbsd:cpu_Debugger+0x4
panic(c0461a60,c040c85a,c0449740,c0415f49,5b0) at netbsd:panic+0x133
__assert(c040c85a,c0415f49,5b0,c0449740,c06b3b80) at netbsd:__assert+0x2e
uvm_map_findspace(c04853c0,e422d000,4000,c0527ca8,c0485320) at netbsd:uvm_map_findspace+0x364
uvm_map(c04853c0,c0527ca8,4000,c0485320,ffffffff) at netbsd:uvm_map+0x146
uvm_km_alloc1(c04853c0,4000,0,5,0) at netbsd:uvm_km_alloc1+0x6c
cpu_set_tss_gates(c176a800,1,0,c0298b62,c040e16b) at netbsd:cpu_set_tss_gates+0xf3
cpu_attach(c1761f80,c1768180,c0527dc0,c0466154,1) at netbsd:cpu_attach+0x152
config_attach(c1761f80,c0466154,c0527dc0,c031a680,c040f987) at netbsd:config_attach+0x283
mpacpi_config_cpu(e42170e0,c1761f80,c0527df8,c1761f80,0) at netbsd:mpacpi_config_cpu+0x5f
acpi_madt_walk(c031a970,c1761f80,c0527e18,c03cae11,c1761f80) at netbsd:acpi_madt_walk+0x2f
mpacpi_scan_apics(c1761f80,c166afa0,c166afac,2,0) at netbsd:mpacpi_scan_apics+0x71
mainbus_attach(0,c1761f80,0,e42050a8,c0465e7c) at netbsd:mainbus_attach+0x259
config_attach(0,c0465e7c,0,0,c0466620) at netbsd:config_attach+0x283
config_rootfound(c040c558,0,c0527f58,c02910a1,c04130aa) at netbsd:config_rootfound+0x46
cpu_configure(c04130aa,c0413f7a,c046d220,c0466620,c04b0a60) at netbsd:cpu_configure+0x2e
configure(c04b0a60,1,0,bfeff000,0) at netbsd:configure+0x41
main(0,0,0,0,0) at netbsd:main+0x322
db{0}>

W/o MULTIPROCESSER it lasts a little bit longer.

[...]
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
Sat Nov  1 17:01:34 GMT 2003
swapctl: adding /dev/wd0b as swap device at priority 0
Starting file system checks:
/dev/rwd0a: file system is clean; not checking
/dev/rwd0e: file system is clean; not checking
panic: kernel diagnostic assertion "tmp->next->start == tmp->end + tmp->ownspace" failed: file "../../../../uvm/uvm_map.c", line 1456
Stopped in pid 29.1 (fsck_msdos) at     netbsd:cpu_Debugger+0x4:        leave
db> t
cpu_Debugger(c040a9f6,e53a2ce8,ffffffff,0,c18f8000) at netbsd:cpu_Debugger+0x4
panic(c044a4c0,c03f5b18,c0432740,c03ff214,5b0) at netbsd:panic+0x12e
__assert(c03f5b18,c03ff214,5b0,c0432740,1727) at netbsd:__assert+0x2e
uvm_map_findspace(e4d2c370,bdbf0000,6000,e53a2eb0,0) at netbsd:uvm_map_findspace+0x2ac
uvm_map(e4d2c370,e53a2eb0,6000,0,ffffffff) at netbsd:uvm_map+0x1c8
uvm_mmap(e4d2c370,e53a2eb0,6000,3,7) at netbsd:uvm_mmap+0x159
sys_mmap(e4d2f908,e53a2f64,e53a2f5c,e4d5cd04,0) at netbsd:sys_mmap+0x253
syscall_plain(e53a2fa8,1f,1f,1f,1f) at netbsd:syscall_plain+0x85
db>

Anything else I sh/could test?

Markus.