Re: NetBSD 5.1_RC3 Xen problem: user-triggered panic when using a Xen kernel

kernel: page fault trap, code=0

Stopped in pid 840.1 (dd) at netbsd:pmap_kenter_pa+0x173: movq 0(%rax),%rsi

pmap_kenter_pa() at netbsd:pmap_kenter_pa+0x173

ubc_alloc() at netbsd:ubc_alloc+0x25d

ubc_uiomove at netbsd:ubc_uiomove+0xba

ffs_write() at netbsd:ffs_write+0x5c2

VOP_WRITE() at netbsd:VOP_WRITE+0x2d

vn_write() at netbsd:vn_write+0xce

dofilewrite() at netbsd:dofilewrite+0x7f

sys_write() at netbsd:sys_write+0x72

syscall() at netbsd:syscall+0xb4

rdi 0xffffa0004e080000

rbp 0xffffa0004e99c900

rax 0xffffffff81400000

r8 0xffffffff80baea80 cpu_info_primary

r9 0xffffa00006130140

r10 0xffffa00007e0e990

r11 0xffffa004e99c920

r14 0xffffa0004ece8050

r15 0xffffa0004e080000

rip 0xffffffff804fb4c3 pmap_kenter_pa+0x173

rsp 0xffffa0004e99c8d0

triggers a repeated re-occurrence of the following

Stopped in pid 840.1 (dd) at netbsd:pmap_kenter_pa+0x173: movq 0(%rax),%rsi

pmap_kenter_pa() at netbsd:pmap_kenter_pa+0x173

uvm_km_alloc_poolpage_cache() at netbsd:uvm_km_alloc_poolpage_cache+0xb8

pool_grow() at netbsd:pool_grow+0x36

pool_catchup() at netbsd:pool_catchup+0x25

pool_get() at netbsd:pool_get+0x3cc

pool_cache_get_slow() at netbsd:pool_cache_et_slow+0x1c8

pool_cache_get_paddr() at netbsd:pool_cache_get_paddr+0x188

m_get at netbsd:m_get+0x25

m_copym0() at netbsd:m_copym0+0x1e4

bridge_input() at netbsd:bridge_input+0x1cd

ether_input at netbsd:ether_input+0x123

wm_intr at netbsd_intr+0x3f6

Xresume_xenev6() at netbsd:Xresume_xenev6+0x55

Xspllower() at netbsd:Xspllower+0xe

trap() at netbsd:trap+0x345

fatal page fault in supervisor mode

trap type 6 code 0 rip ffffffff804f58bb cs e030 rflags 10247 cr2 ffffa0004e0800b8 cpl 8 rsp ffffa0004e99bb80

kernel: page fault trap, code=0

Faulted in DDB; continuting...

pmap_kenter_pa() at netbsd:pmap_kenter_pa+0x173

uvm_km_alloc_poolpage_cache() at netbsd:uvm_km_alloc_poolpage_cache+0xb8

pool_grow() at netbsd:pool_grow+0x36

no dump is ever created. This is only interruptible with a power-off.

On Thu, Jul 22, 2010 at 4:11 AM, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:

On Mon, Jul 12, 2010 at 11:26:31AM -0600, Steven Senator wrote:
> Hello,
> I am in the process of collecting sufficient information to submit a proper
> bug report, but I have found a repeatable panic when using the Xen kernel
> distributed with NetBSD 5.1 RC3. This problem does not occur when using the
> distributed NetBSD 5.1_RC3 kernel.
>
> To reproduce:
> A. Boot Xen dom0 kernel
> I have tried with varying amounts of dom0_mem, up to 8GB, without
> effect. No other Xen domU need be running.
> B. run dd if=/dev/zero of=<some-file> bs=1048576 count=8192
> This command will cause a panic at an arbitrary point in file
> creation, within a few (3-5) minutes.

this is strange, I always create my domU virtual disks this way (with a
1m block size). What is the exact panic (with stack trace if possible) ?

--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--