Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt

I just committed a band-aid for this. Please try.

Thanks,
Kip

On Fri, Aug 22, 2008 at 4:12 PM, Brad Pitney <pitney.brad_at_googlemail.com> wrote:
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2008 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>        The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 8.0-CURRENT #0: Fri Aug 22 21:33:48 UTC 2008
>    root_at_test:/usr/obj/usr/src/sys/XEN
> WARNING: WITNESS option enabled, expect reduced performance.
> Xen reported: 1799.493 MHz processor.
> Timecounter "ixen" frequency 1000000000 Hz quality 0
> CPU: AMD Sempron(tm) Processor 3000+ (1799.49-MHz 686-class CPU)
>  Origin = "AuthenticAMD"  Id = 0x20fc2  Stepping = 2
>  Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
>  Features2=0x1<SSE3>
>  AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
>  AMD Features2=0x1<LAHF>
> real memory  = 268435456 (256 MB)
> avail memory = 255016960 (243 MB)
> kbd0 at kbdmux0
> xc0: <Xen Console> on motherboard
> Timecounters tick every 10.000 msec
> [XEN] Initialising virtual ethernet driver.
> xs_single device xs_talkv read_reply event=1 itype=1 htype=1 len=16
> xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt
> cpuid = 0
> KDB: enter: panic
> [thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
> db> bt
> Tracing pid 0 tid 100000 td 0xc03ae260
> kdb_enter(c0340f2d,c0340f2d,c033d73c,c059ab40,0,...) at kdb_enter+0x3a
> panic(c033d73c,c03ae260,c16a102c,c1721200,81,...) at panic+0x12c
> intr_event_handle(c1721200,c059aba8,c03ae304,c0692000,0,...) at
> intr_event_handle+0xb5
> intr_execute_handlers(c16a102c,c059aba8,0,3,c16a102c,...) at
> intr_execute_handlers+0x4f
> evtchn_do_upcall(c059aba8) at evtchn_do_upcall+0xad
> Xhypervisor_callback(c16dc0c8,10,2,0,c059acac,...) at Xhypervisor_callback+0x35
> xs_init(c0363c1f,c00e1c49,c051fb00,8,c0363bba,...) at xs_init+0x350
> xs_init(c1681480,0,c0363bba,115,1,...) at xs_init+0x8c7
> xs_init(1,c059acfc,c1681480,b,c036fdac,...) at xs_init+0xc53
> xs_resume(c059acfc,c0381ca0,0,c036fdac,fffffff,...) at xs_resume+0xf0
> xenbus_directory(0,c03431d8,c166b030,c059ad34,c166b020,...) at
> xenbus_directory+0x39
> xenbus_probe_devices(c039ff80,c033f859,86,c039ff80,c036fdac,...) at
> xenbus_probe_devices+0x8c
> xenbus_probe_devices(0,800,800,59f000,0,...) at xenbus_probe_devices+0x15c
> mi_startup(59f000,0,0,0,0,...) at mi_startup+0x96
> btext() at btext+0x95
>
> this is on a NetBSD/Xen dom0 AMD64 current/4.99.72 with Xen 3.3.0,
> which is the latest in pkgsrc, there is no 3.2 :(
>
> the domain is paused, and ready to supply any more info, etc.
>
> --
> Best regards,
>  Brad
>