[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-users] xen-unstable amd64 troubles
Hi Ian,
I did a somehow complex network setup. I'm using a bridged setup with one
domU as firewall-host, connected to an 'internal'-bridge. The internal
domUs mount some network-filesystems exported from dom0. The machines
didn't do any work at all when crashing, they just idled. I waited for the
panic to come back. ;-)
I checked with xm dmesg if the gnttab_transfer messages came back. Once
they did, the two external domains had been crashed (the ones, connected to
xenbr0, the bridge connected to the real network).
Thanks for your help,
Thomas
--On 11. November 2005 10:29:08 +0000 Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
wrote:
Thomas. What were you doing on the machine at the time? Was there a lot
of inter-domain or domain-to-external networking activity going on?
Which domain did the crash messsage come from?
Please post the diff of your config vs our -xen0 config.
Thanks,
Ian
please excuse my late reply, but I had a lot of work to do
last night. I tried the latest changeset again this morning,
but got the same problems again.
xm info
system : Linux
host : atbroy64
release : 2.6.12.6-xen0-br14
version : #2 Fri Nov 11 08:34:18 GMT 2005
machine : x86_64
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2002
hw_caps : 078bfbff:e1d3fbff:00000000:00000010
memory : 1534
free_memory : 224
xen_major : 3
xen_minor : 0
xen_extra : -devel
xen_caps : xen-3.0-x86_64
xen_params : virt_start=0xffff800000000000
xen_changeset : Thu Nov 10 18:43:56 2005 +0100
7745:b9e8654c3f10
cc_compiler : gcc version 3.4.4 (Gentoo 3.4.4-r1)
cc_compile_by : root
cc_compile_date : Fri Nov 11 08:41:18 GMT 2005
I customized the kernel to accomplish my hardware needs.
The machine got 1500MB of mem, Dom0 got 512 from these, the
other 3 DomUs got 256.
I'm almost sure, that my kernel-config is right for my machine.
Thanks in advance,
Thomas
--On 10. November 2005 16:49:03 +0000 Ian Pratt
<m+Ian.Pratt@xxxxxxxxxxxx>
wrote:
>
> Please can you try figuring out how to repro.
>
> Also, in bug reports please aditionally state:
> * your changeset number (please always make sure you're using the
> latest)
> * whether you have modified the kernel config in any way
> * how much memory your machine has, how much each of the
domains have
>
> I think this issue may already be on bugzilla. Would like to get it
> nailed, but we need more info to repro.
>
> Thanks,
> Ian
>
>
>> I'm using xen-unstable with all the latest changesets and some
>> domains on it on a amd64 machine.
>> Today my domains crashed with the following output:
>>
>> Unable to handle kernel paging request at ffff88000e928700 RIP:
>> <ffffffff803988ca>{netif_poll+1354}
>> PGD 788067 PUD 789067 PMD 7fe067 PTE 0
>> Oops: 0002 [1]
>> CPU 0
>> Pid: 0, comm: swapper Not tainted 2.6.12.6-xenU-br14
>> RIP: e030:[<ffffffff803988ca>] <ffffffff803988ca>{netif_poll+1354}
>> RSP: e02b:ffffffff806d3d98 EFLAGS: 00010212
>> RAX: ffff88000e928700 RBX: ffff88000e909940 RCX: ffff88000e928058
>> RDX: ffff88000e928700 RSI: ffff88000e9091c0 RDI: ffff88000e909940
>> RBP: ffff88000e909940 R08: 0000000000feffff R09: 0000000000000017
>> R10: ffff88000f312250 R11: 0000000000000001 R12: ffff8800016d4360
>> R13: ffff88000167c550 R14: 00000000000000c0 R15: 0000000000000000
>> FS: 0000000000505ae0(0000) GS:ffffffff806c0080(0000)
>> knlGS:ffffffff80600400
>> CS: e033 DS: 0000 ES: 0000
>> Process swapper (pid: 0, threadinfo ffffffff806d2000, task
>> ffffffff8057d500)
>> Stack: 0000000180117076 0000000200000040 0000000000000002
>> 001e7cab001e7cab
>> ffffffff806d3e2c ffff8800016d4000 ffffffff806d3dc8
>> ffffffff806d3dc8
>> ffff880000000000 ffff8800016d4000 Call
>> Trace:<ffffffff803ea348>{net_rx_action+152}
>> <ffffffff801325ab>{__do_softirq+107}
>> <ffffffff8013264d>{do_softirq+61}
<ffffffff80114ea9>{do_IRQ+57}
>> <ffffffff8010d948>{evtchn_do_upcall+136}
>> <ffffffff80112029>{do_hypervisor_callback+17}
>> <ffffffff8010fa53>{xen_idle+83}
<ffffffff8010fa53>{xen_idle+83}
>> <ffffffff8010fa8f>{cpu_idle+31}
>> <ffffffff806d46ea>{start_kernel+490}
>> <ffffffff806d4169>{_sinittext+361}
>>
>> Code: c7 00 01 00 00 00 48 8b 83 10 01 00 00 c7 40 04 00
00 00 00 RIP
>> <ffffffff803988ca>{netif_poll+1354} RSP <ffffffff806d3d98>
>> CR2: ffff88000e928700
>> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>>
>> xm dmesg tells me:
>>
>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times
to switch
>> input to Xen).
>> (XEN) gnttab_transfer: invalid pfn for mfn=4f27e001
>> (XEN) gnttab_transfer: invalid pfn for mfn=3f7df001
>> (XEN) gnttab_transfer: invalid pfn for mfn=3f03b001
>> (XEN) gnttab_transfer: invalid pfn for mfn=516ca001
>> (XEN) gnttab_transfer: invalid pfn for mfn=4f306001
>> (XEN) gnttab_transfer: invalid pfn for mfn=50cf0001
>> (XEN) gnttab_transfer: invalid pfn for mfn=52305001
>> (XEN) gnttab_transfer: invalid pfn for mfn=510ce001
>> (XEN) gnttab_transfer: invalid pfn for mfn=3efc1001
>> (XEN) gnttab_transfer: invalid pfn for mfn=3efc2001
>> (XEN) gnttab_transfer: invalid pfn for mfn=3efc3001
>> (XEN) gnttab_transfer: invalid pfn for mfn=4e74c001
>> (XEN) gnttab_transfer: invalid pfn for mfn=4e74d001
>> (XEN) gnttab_transfer: invalid pfn for mfn=4e74e001
>>
>> except from that there's nothing unusual in any logs/debug-outputs.
>>
>> Could anyone please explain to me, what could be done here?
--
-- So Long, and Thanks for all the Fish
- Douglas Adams, Hitchhikers Guide to the Galaxy --
--
-- So Long, and Thanks for all the Fish
- Douglas Adams, Hitchhikers Guide to the Galaxy --
Attachment:
config-diff
Description: Binary data
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
