[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#425373: linux-image-2.6.18-3-xen-686: Xen kernel opps



On Mon, May 21, 2007 at 12:52:04PM +1000, Anand Kumria wrote:
> Package: linux-image-2.6.18-3-xen-686
> Version: 2.6.18-7
> Severity: normal
> 
> Hi,
> 
> BUG: unable to handle kernel paging request at virtual address c79d00d9
>  printing eip:
> c79d00d9
> *pde = ma 03f59067 pa 00f59067
> *pte = ma 00000000 pa fffff000
> Oops: 0000 [#1]
> SMP 
> Modules linked in: xt_tcpudp xt_physdev bridge iptable_filter ip_tables
> x_tables button ac battery ipv6 loop rtc parport_pc parport evdev
> snd_cmipci gameport snd_pcm snd_page_alloc snd_opl3_lib shpchp snd_timer
> snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd pci_hotplug
> soundcore i2c_sis630 i2c_core serial_core sis_agp agpgart floppy pcspkr
> ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic
> ide_cd cdrom ide_disk sis5513 generic ide_core ohci_hcd usbcore sis900
> mii thermal processor fan
> CPU:    0
> EIP:    0061:[<c79d00d9>]    Not tainted VLI
> EFLAGS: 00010286   (2.6.18-3-xen-686 #1) 
> EIP is at 0xc79d00d9
> eax: 00000000   ebx: c4c200c0   ecx: 00000002   edx: c13a7a98
> esi: 00000000   edi: c13a0084   ebp: c33a644c   esp: c4c25f98
> ds: 007b   es: 007b   ss: 0069
> Process loop101 (pid: 9468, ti=c4c24000 task=c0e53000 task.ti=c4c24000)
> Stack: 00001000 00000001 c5f50aa0 00000000 c79d25dc 00000000 00000000
> a4001000 
>        00000000 00000001 c13a7984 c1019d80 00001000 00001000 a4001000
> 00000000 
>        c79d227b 00000000 00000000 00000000 c0102941 c13a7984 00000000
> 00000000 
> Call Trace:
>  [<c79d25dc>] do_lo_send_aops+0x0/0x20f [loop]
>  [<c79d227b>] loop_thread+0x0/0x361 [loop]
>  [<c0102941>] kernel_thread_helper+0x5/0xb
> Code:  Bad EIP value.
> EIP: [<c79d00d9>] 0xc79d00d9 SS:ESP 0069:c4c25f98
> 
> The BUG initially occurred in one of the DomUs and when it had locked up,
> I destroyed it and attempted to create it again. That failed and I found
> this on Dom0s dmesg output.

Was this a one-time error and can the issue be reproduced? If you're
running Lenny in the mean time, did the error reappear?

Cheers,
        Moritz



Reply to: