crash 10 min after start dom0

[Pavel Mlčoch]

Binary package hint: linux-source-2.6.22

Oct 19 15:30:38 ubuntu kernel: [ 3905.899995] ------------[ cut here ]------------
Oct 19 15:30:38 ubuntu kernel: [ 3905.900124] kernel BUG at /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/arch/i386/mm/hypervisor.c:60!
Oct 19 15:30:38 ubuntu kernel: [ 3905.900249] invalid opcode: 0000 [#1]
Oct 19 15:30:38 ubuntu kernel: [ 3905.900348] SMP
Oct 19 15:30:38 ubuntu kernel: [ 3905.900604] Modules linked in: snd_rtctimer binfmt_misc rfcomm l2cap bridge nfsd exportfs lockd sunrpc i915 drm ppdev button ac battery ipv6 af_packet sbp2 lp arc4 ecb blkcipher ieee80211_crypt_wep snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq pcmcia snd_timer snd_seq_device ipw3945 joydev snd soundcore ieee80211 ieee80211_crypt hci_usb intel_agp bluetooth snd_page_alloc parport_pc parport pcspkr yenta_socket shpchp pci_hotplug tpm_infineon tpm tpm_bios agpgart psmouse rsrc_nonstatic pcmcia_core serio_raw evdev ext3 jbd mbcache sg sr_mod cdrom sd_mod ata_generic tg3 ohci1394 ieee1394 ata_piix libata scsi_mod ehci_hcd uhci_hcd usbcore dm_mirror dm_snapshot dm_mod thermal processor fan fuse apparmor commoncap
Oct 19 15:30:38 ubuntu kernel: [ 3905.908009] CPU: 0
Oct 19 15:30:38 ubuntu kernel: [ 3905.908010] EIP: 0061:[xen_l2_entry_update+148/160] Not tainted VLI
Oct 19 15:30:38 ubuntu kernel: [ 3905.908013] EFLAGS: 00010282 (2.6.22-14-xen #1)
Oct 19 15:30:38 ubuntu kernel: [ 3905.908313] EIP is at xen_l2_entry_update+0x94/0xa0
Oct 19 15:30:38 ubuntu kernel: [ 3905.908414] eax: ffffffea ebx: ea091e0c ecx: 00000001 edx: 00000000
Oct 19 15:30:38 ubuntu kernel: [ 3905.908519] esi: 00007ff0 edi: 00000000 ebp: e56d38c0 esp: ea091e04
Oct 19 15:30:38 ubuntu kernel: [ 3905.908623] ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0069
Oct 19 15:30:38 ubuntu kernel: [ 3905.908727] Process bash (pid: 11957, ti=ea090000 task=e532a000 task.ti=ea090000)
Oct 19 15:30:38 ubuntu kernel: [ 3905.908832] Stack: 31f59067 00000000 546abdf0 00000000 31f59067 00000000 00000000 31f59067
Oct 19 15:30:38 ubuntu kernel: [ 3905.909675] 00000000 c01615ec ea0aadf0 e56d38c0 4c959000 00000000 00000000 00000000
Oct 19 15:30:38 ubuntu kernel: [ 3905.910515] 00000000 e56d38c0 c016580e f57f6920 ea0aadf8 c28a0a6c 7c72f025 00000000
Oct 19 15:30:38 ubuntu kernel: [ 3905.911356] Call Trace:
Oct 19 15:30:38 ubuntu kernel: [ 3905.911565] [__pte_alloc+588/816] __pte_alloc+0x24c/0x330
Oct 19 15:30:38 ubuntu kernel: [ 3905.911764] [__handle_mm_fault+5278/6784] __handle_mm_fault+0x149e/0x1a80
Oct 19 15:30:38 ubuntu kernel: [ 3905.911999] [check_pgt_cache+27/32] check_pgt_cache+0x1b/0x20
Oct 19 15:30:38 ubuntu kernel: [ 3905.912189] [unmap_region+207/288] unmap_region+0xcf/0x120
Oct 19 15:30:38 ubuntu kernel: [ 3905.912405] [do_page_fault+0/3568] do_page_fault+0x0/0xdf0
Oct 19 15:30:38 ubuntu kernel: [ 3905.912603] [do_page_fault+766/3568] do_page_fault+0x2fe/0xdf0
Oct 19 15:30:38 ubuntu kernel: [ 3905.912836] [do_page_fault+0/3568] do_page_fault+0x0/0xdf0
Oct 19 15:30:38 ubuntu kernel: [ 3905.913024] [error_code+53/64] error_code+0x35/0x40
Oct 19 15:30:38 ubuntu kernel: [ 3905.913238] =======================
Oct 19 15:30:38 ubuntu kernel: [ 3905.913339] Code: 89 74 24 08 be f0 7f 00 00 89 54 24 14 31 d2 89 44 24 10 e8 af 81 fe ff 85 c0 78 0f 83 c4 18 5b 5e 5f c3 39 c2 72 9b 0f 0b eb fe <0f> 0b eb fe 90 8d b4 26 00 00 00 00 56 89 c2 53 83 ec 0c c1 ea
Oct 19 15:30:38 ubuntu kernel: [ 3905.918785] EIP: [xen_l2_entry_update+148/160] xen_l2_entry_update+0x94/0xa0 SS:ESP 0069:ea091e04

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It would be helpful to know which specific kernel version you noticed this with. You can check via 'cat /proc/version_signature'. It would be even more helpful if you were to test the Hardy version of the kernel so we can get this resolved in the actively developed kernel. Thanks in advance.

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.