Mailing List Archive

Troubles starting OpenAFS client in XEN
I compiled OpenAFS module for my xenU 2.4.28 kernel.
The module loads fine, however starting afsd (the OpenAFS client daemon)
causes a system crash with the following output. After that I have to
restart the domain to get access to console again.
Is this a known bug? Does anybody run OpenAFS in Xen domain
successfully? If yes, what are the steps to succeed?
Thank you.

lukas

Failed to execute MMU updates.
invalid operand: 0000
CPU: 0
EIP: 0819:[<c01b4288>] Tainted: P
EFLAGS: 00010286
eax: 00000022 ebx: c02b2c00 ecx: cf06e000 edx: fbff9000
esi: 00000000 edi: 0010b000 ebp: 0010b000 esp: cf06fad0
ds: 0821 es: 0821 ss: 0821
Process afsd (pid: 326, stackpage=cf06f000)<1>
Stack: c02600c0 c129509c c136342c c011fe34 c1363428 48de4163 0010b000
00400000
c031bd08 d050b000 d050a000 c031bd08 00001000 d050a000 00001000
d04e39e0
c01200cc d0800000 00001000 000001f2 00000163 00000000 00000004
000003ff
Call Trace: [<c011fe34>] [<d04e39e0>] [<c01200cc>] [<d04e39f7>]
[<c021c49a>]
[<d04a00b7>] [<d04e3465>] [<d04fea7c>] [<d05081dc>] [<d04e3639>]
[<d04e39e0>]
[<d04e3610>] [<d04e37a2>] [<d04b0a92>] [<d04d1e02>] [<d0508a20>]
[<d04e7a7b>]
[<d04e7a56>] [<d04e7f06>] [<d04e8a19>] [<c012323b>] [<c0121791>]
[<c0117754>]
[<c0118208>] [<c01b37c8>] [<d04e8c5f>] [<c01aa6e3>] [<c0113778>]
[<c01abf1f>]

general protection fault: 0000
CPU: 0
EIP: 0819:[<d04e4e40>] Tainted: P
EFLAGS: 00010246
eax: fbff9000 ebx: 00000000 ecx: cf05e000 edx: c027c81c
esi: cf06bc3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
ds: 0821 es: 0821 ss: 0821
Process keventd (pid: 329, stackpage=cf05f000)<1>
Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf06bc3c d04e7ad0
c136e000
Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]

general protection fault: 0000
CPU: 0
EIP: 0819:[<d04e4e40>] Tainted: P
EFLAGS: 00010246
eax: fbff9000 ebx: 00000013 ecx: cf05e000 edx: c027c81c
esi: cf069c3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
ds: 0821 es: 0821 ss: 0821
Process keventd (pid: 330, stackpage=cf05f000)<1>
Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf069c3c d04e7ad0
c136e000
Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]
Re: Troubles starting OpenAFS client in XEN [ In reply to ]
Can you stick the vmlinuz / System.map on the web somewhere so that these
crash dumps can be analysed?

What release of Xen are you running?

Cheers,
Mark

On Monday 31 January 2005 14:06, Lukas Kubin wrote:
> I compiled OpenAFS module for my xenU 2.4.28 kernel.
> The module loads fine, however starting afsd (the OpenAFS client daemon)
> causes a system crash with the following output. After that I have to
> restart the domain to get access to console again.
> Is this a known bug? Does anybody run OpenAFS in Xen domain
> successfully? If yes, what are the steps to succeed?
> Thank you.
>
> lukas
>
> Failed to execute MMU updates.
> invalid operand: 0000
> CPU: 0
> EIP: 0819:[<c01b4288>] Tainted: P
> EFLAGS: 00010286
> eax: 00000022 ebx: c02b2c00 ecx: cf06e000 edx: fbff9000
> esi: 00000000 edi: 0010b000 ebp: 0010b000 esp: cf06fad0
> ds: 0821 es: 0821 ss: 0821
> Process afsd (pid: 326, stackpage=cf06f000)<1>
> Stack: c02600c0 c129509c c136342c c011fe34 c1363428 48de4163 0010b000
> 00400000
> c031bd08 d050b000 d050a000 c031bd08 00001000 d050a000 00001000
> d04e39e0
> c01200cc d0800000 00001000 000001f2 00000163 00000000 00000004
> 000003ff
> Call Trace: [<c011fe34>] [<d04e39e0>] [<c01200cc>] [<d04e39f7>]
> [<c021c49a>]
> [<d04a00b7>] [<d04e3465>] [<d04fea7c>] [<d05081dc>] [<d04e3639>]
> [<d04e39e0>]
> [<d04e3610>] [<d04e37a2>] [<d04b0a92>] [<d04d1e02>] [<d0508a20>]
> [<d04e7a7b>]
> [<d04e7a56>] [<d04e7f06>] [<d04e8a19>] [<c012323b>] [<c0121791>]
> [<c0117754>]
> [<c0118208>] [<c01b37c8>] [<d04e8c5f>] [<c01aa6e3>] [<c0113778>]
> [<c01abf1f>]
>
> general protection fault: 0000
> CPU: 0
> EIP: 0819:[<d04e4e40>] Tainted: P
> EFLAGS: 00010246
> eax: fbff9000 ebx: 00000000 ecx: cf05e000 edx: c027c81c
> esi: cf06bc3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
> ds: 0821 es: 0821 ss: 0821
> Process keventd (pid: 329, stackpage=cf05f000)<1>
> Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf06bc3c d04e7ad0
> c136e000
> Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]
>
> general protection fault: 0000
> CPU: 0
> EIP: 0819:[<d04e4e40>] Tainted: P
> EFLAGS: 00010246
> eax: fbff9000 ebx: 00000013 ecx: cf05e000 edx: c027c81c
> esi: cf069c3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
> ds: 0821 es: 0821 ss: 0821
> Process keventd (pid: 330, stackpage=cf05f000)<1>
> Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf069c3c d04e7ad0
> c136e000
> Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Re: Troubles starting OpenAFS client in XEN [ In reply to ]
I'm running Xen 2.0.3.
My vmlinuz and System.map are at:

http://uit.opf.slu.cz/Members/kubin/download/vmlinuz-2.4.28-xenU
http://uit.opf.slu.cz/Members/kubin/download/System.map-2.4.28-xenU

Thank you.

lukas

Mark Williamson wrote:
> Can you stick the vmlinuz / System.map on the web somewhere so that these
> crash dumps can be analysed?
>
> What release of Xen are you running?
>
> Cheers,
> Mark
>
> On Monday 31 January 2005 14:06, Lukas Kubin wrote:
>
>>I compiled OpenAFS module for my xenU 2.4.28 kernel.
>>The module loads fine, however starting afsd (the OpenAFS client daemon)
>>causes a system crash with the following output. After that I have to
>>restart the domain to get access to console again.
>>Is this a known bug? Does anybody run OpenAFS in Xen domain
>>successfully? If yes, what are the steps to succeed?
>>Thank you.
>>
>>lukas
>>
>>Failed to execute MMU updates.
>>invalid operand: 0000
>>CPU: 0
>>EIP: 0819:[<c01b4288>] Tainted: P
>>EFLAGS: 00010286
>>eax: 00000022 ebx: c02b2c00 ecx: cf06e000 edx: fbff9000
>>esi: 00000000 edi: 0010b000 ebp: 0010b000 esp: cf06fad0
>>ds: 0821 es: 0821 ss: 0821
>>Process afsd (pid: 326, stackpage=cf06f000)<1>
>>Stack: c02600c0 c129509c c136342c c011fe34 c1363428 48de4163 0010b000
>>00400000
>> c031bd08 d050b000 d050a000 c031bd08 00001000 d050a000 00001000
>>d04e39e0
>> c01200cc d0800000 00001000 000001f2 00000163 00000000 00000004
>>000003ff
>>Call Trace: [<c011fe34>] [<d04e39e0>] [<c01200cc>] [<d04e39f7>]
>>[<c021c49a>]
>> [<d04a00b7>] [<d04e3465>] [<d04fea7c>] [<d05081dc>] [<d04e3639>]
>>[<d04e39e0>]
>> [<d04e3610>] [<d04e37a2>] [<d04b0a92>] [<d04d1e02>] [<d0508a20>]
>>[<d04e7a7b>]
>> [<d04e7a56>] [<d04e7f06>] [<d04e8a19>] [<c012323b>] [<c0121791>]
>>[<c0117754>]
>> [<c0118208>] [<c01b37c8>] [<d04e8c5f>] [<c01aa6e3>] [<c0113778>]
>>[<c01abf1f>]
>>
>> general protection fault: 0000
>>CPU: 0
>>EIP: 0819:[<d04e4e40>] Tainted: P
>>EFLAGS: 00010246
>>eax: fbff9000 ebx: 00000000 ecx: cf05e000 edx: c027c81c
>>esi: cf06bc3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
>>ds: 0821 es: 0821 ss: 0821
>>Process keventd (pid: 329, stackpage=cf05f000)<1>
>>Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf06bc3c d04e7ad0
>>c136e000
>>Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]
>>
>> general protection fault: 0000
>>CPU: 0
>>EIP: 0819:[<d04e4e40>] Tainted: P
>>EFLAGS: 00010246
>>eax: fbff9000 ebx: 00000013 ecx: cf05e000 edx: c027c81c
>>esi: cf069c3c edi: 00000000 ebp: c136e000 esp: cf05ffe0
>>ds: 0821 es: 0821 ss: 0821
>>Process keventd (pid: 330, stackpage=cf05f000)<1>
>>Stack: d04e7ae8 c136ff40 00004111 c136ff40 c01aa43e cf069c3c d04e7ad0
>>c136e000
>>Call Trace: [<d04e7ae8>] [<c01aa43e>] [<d04e7ad0>]