This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] file corruption!!!

On 18 Jul 2004, at 17:22, Chris Andrews wrote:

I've checked in a fix. It should work fine with LVM and loop
devices again.

All seems well with that fix, with domain 0 using LVs, and exporting them to other domains. I'll give the machine some load and see what happens.

So, I've got the following results. The machine has an aacraid controller, which reports no errors. My test, such as it is, is to rebuild the 'festival' package -- simply because that's what I was doing when I first saw corruption.

2.4.26 plus the device-mapper patch and the VFS-locking patch - stable.
Xen, 2.4.26 domain0 plus device-mapper, VFS-locking, domain 0 only - stable.
Xen, 2.4.26 domain0 etc, and a 2.6.7-xenU guest - stable.
Xen, 2.4.26 domain0 and a 2.4.26-xenU guest - corruption in dom0, and an oops.

The oops below happened shortly after I started the 2.4 guest, and killed the machine. I'll run memtest86 as soon as I've got it built with serial support and hooked into grub...


Unable to handle kernel paging request at virtual address 258b0619
Oops: 0000
CPU:    0
EIP:    0819:[<c0124f32>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00213202
eax: 258b0601   ebx: 00000001   ecx: 258b0601   edx: 00000000
esi: c66bdaa0   edi: c1a31034   ebp: c66bdaa0   esp: c767dbd8
ds: 0821   es: 0821   ss: 0821
Process find (pid: 2877, stackpage=c767d000)<1>
Stack: c0261d6c 00000000 c66bdaa0 c75eb220 c0261da3 c66bdaa0 c66bdaa0 c0261ed9 c66bdaa0 00000000 00000030 952163ff c0288163 c66bdaa0 c66bdaa0 00000000 c66bdaa0 c1189800 00000000 c02ac920 00000001 952163cf c02766a0 007de526 Call Trace: [<c0261d6c>] [<c0261da3>] [<c0261ed9>] [<c0288163>] [<c02ac920>] [<c02766a0>] [<c028feb2>] [<c0290353>] [<c02af7e0>] [<c027667e>] [<c02af7e0>] [<c02766a0>] [<c0276859>] [<c026e85a>] [<c02b04b7>] [<c026e506>] [<c02766a0>] [<c026e85a>] [<c02766a0>] [<c027646e>] [<c02766a0>] [<c02667d7>] [<c0266935>] [<c0266a93>] [<c010ddba>] [<c01b07ee>] [<c01b4ffd>] [<c01aefab>] [<c01bf403>] [<c01be83d>] [<c01bf23f>] [<c01c0ab7>] [<c01bef3b>] [<c01bc5fa>] [<c01c0920>]
   [<c012c273>] [<c01aee97>] [<c01a0833>]
 <0>Kernel panic: Aiee, killing interrupt handler!
Warning (Oops_read): Code line not seen, dumping what data is available

>>EIP; c0124f32 <__free_pages+2/20>   <=====

>>eax; 258b0601 <__start___xen_guest+258ad3b2/c00fcdb1>
>>ecx; 258b0601 <__start___xen_guest+258ad3b2/c00fcdb1>

Trace; c0261d6c <skb_release_data+7c/a0>
Trace; c0261da3 <kfree_skbmem+13/30>
Trace; c0261ed9 <__kfree_skb+119/190>
Trace; c0288163 <tcp_rcv_established+483/850>
Trace; c02ac920 <br_handle_frame_finish+0/170>
Trace; c02766a0 <ip_rcv_finish+0/210>
Trace; c028feb2 <tcp_v4_do_rcv+122/130>
Trace; c0290353 <tcp_v4_rcv+493/5d0>
Trace; c02af7e0 <br_nf_pre_routing_finish+0/280>
Trace; c027667e <ip_local_deliver_finish+14e/170>
Trace; c02af7e0 <br_nf_pre_routing_finish+0/280>
Trace; c02766a0 <ip_rcv_finish+0/210>
Trace; c0276859 <ip_rcv_finish+1b9/210>
Trace; c026e85a <nf_hook_slow+7a/190>
Trace; c02b04b7 <ipv4_sabotage_in+27/30>
Trace; c026e506 <nf_iterate+76/b0>
Trace; c02766a0 <ip_rcv_finish+0/210>
Trace; c026e85a <nf_hook_slow+7a/190>
Trace; c02766a0 <ip_rcv_finish+0/210>
Trace; c027646e <ip_rcv+19e/260>
Trace; c02766a0 <ip_rcv_finish+0/210>
Trace; c02667d7 <netif_receive_skb+137/210>
Trace; c0266935 <process_backlog+85/160>
Trace; c0266a93 <net_rx_action+83/160>
Trace; c010ddba <do_softirq+da/f0>
Trace; c01b07ee <do_IRQ+9e/a0>
Trace; c01b4ffd <evtchn_do_upcall+ad/110>
Trace; c01aefab <hypervisor_callback+33/49>
Trace; c01bf403 <opost_block+b3/180>
Trace; c01be83d <tty_default_put_char+2d/40>
Trace; c01bf23f <opost+9f/1b0>
Trace; c01c0ab7 <write_chan+197/220>
Trace; c01bef3b <do_tty_write+db/134>
Trace; c01bc5fa <tty_write+13a/170>
Trace; c01c0920 <write_chan+0/220>
Trace; c012c273 <sys_write+a3/140>
Trace; c01aee97 <system_call+2f/33>
Trace; c01a0833 <nlmsvc_decode_notify+23/70>

1 warning and 1 error issued.  Results may not be reliable.

This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>