Re: 5.99.15 domU panic

[Sarton O'Brien <bsd-xen%roguewrt.org@localhost>]

On 4/08/2009 8:07 PM, Martti Kuparinen wrote:
> Hi,
>
> A fresh domU fails like this. Any ideas?
>
>
> NetBSD 5.99.15 (XEN3PAE_DOMU) #0: Tue Aug 4 11:48:02 EEST 2009
> total memory = 256 MB
> avail memory = 245 MB
> mainbus0 (root)
> hypervisor0 at mainbus0: Xen version 3.3
> vcpu0 at hypervisor0: Intel 686-class, 2992MHz, id 0x1067a
> panic: xpq_flush_cache
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c0129ef4 cs 9 eflags 246 cr2 0 ilevel 8
> Stopped in pid 0.1 (system) at netbsd:breakpoint+0x4: popl %ebp
> db> xenconscn_getc(): not console
>
>
> Reverting back to 5.99.14 kernel works fine (with 5.99.15 userland)...

I'm seeing the same (posted as: domu panics on boot, dom0 reboots on 
destroy), though I've reverted to a working 5.99.15 kernel. Are you 
having an issue when destroying a domu? Dom0 details and panic below ...

NetBSD gogeta.internal 5.99.15 NetBSD 5.99.15 (XEN3_DOM0) #2: Tue Aug  4 
14:48:28 EST 2009 
root%spike.internal@localhost:/usr/obj/sys/arch/amd64/compile/XEN3_DOM0 amd64


On 4/08/2009 3:57 PM, Sarton O'Brien wrote:
> Just updated (hour or so ago) kernels and rebooted. When a domu is
> launched I'm seeing this:
>
> NetBSD 5.99.15 (XEN3_DOMU) #2: Tue Aug  4 14:33:54 EST 2009
> root%spike.internal@localhost:/usr/obj/sys/arch/amd64/compile/XEN3_DOMU
> total memory = 256 MB
> avail memory = 239 MB
> mainbus0 (root)
> hypervisor0 at mainbus0: Xen version 3.3
> vcpu0 at hypervisor0: Intel 686-class, 2793MHz, id 0xf44
> panic: xpq_flush_cache
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 rip ffffffff8012aa5d cs e030 rflags 246 cr2  0 cpl 8
> rsp ffffffff807dcbb0
> Stopped in pid 0.1 (system) at  netbsd:breakpoint+0x5:  leave
> breakpoint() at netbsd:breakpoint+0x5
> panic() at netbsd:panic+0x269
> xen_set_ldt() at netbsd:xen_set_ldt
> cpu_init() at netbsd:cpu_init+0x32
> cpu_attach_common() at netbsd:cpu_attach_common+0x13b
> config_attach_loc() at netbsd:config_attach_loc+0x160
> hypervisor_attach() at netbsd:hypervisor_attach+0x76
> config_attach_loc() at netbsd:config_attach_loc+0x160
> mainbus_attach() at netbsd:mainbus_attach+0x4a
> config_attach_loc() at netbsd:config_attach_loc+0x160
> cpu_configure() at netbsd:cpu_configure+0x1c
> main() at netbsd:main+0x1a0
> ds          0x2b4
> es          0xcbc0
> fs          0xe000
> gs          0xe329
> rdi         0x8
> rsi         0xd
> rbp         0xffffffff807dcbb0
> rbx         0xffffffff807dcbc0
> rdx         0
> rcx         0x1
> --db_more--xenconscn_getc(): not console
>
> Reverting only the domu to:
>
> NetBSD symbiote.internal 5.99.15 NetBSD 5.99.15 (XEN3_DOMU) #1: Thu Jul
> 30 14:41:07 EST 2009
> root%spike.internal@localhost:/usr/obj/sys/arch/amd64/compile/XEN3_DOMU amd64
>
> Works fine.
>
> When I destroy the domu the server reboots. This part was happening
> before the update though (I only noticed just before updating so figured
> I'd check it after the update). I don't have console access atm so can't
> check what's going on with dom0 as yet.