Re: [Xen-users] BUG after create snapshot in a script - Xen 4.01-2.6.32-5-xen-amd64

[Rémi BERNIER <R.BERNIER@xxxxxxxxxxx>]

Hi Guido,

I use it only to install the package
linux-image and linux-base on a test server for the moment.

Regards,
Rémi




Hi Remi,
great to hear it's working for you.
Did you leave the proposed-updates active on your server or did you use
it only once to install the linux-image packet and made it inactive afterwards?
I'm a bit unassured using them on a production server.

Regards
Guido


Von: Rémi BERNIER [mailto:R.BERNIER@xxxxxxxxxxx] 
Gesendet: Mittwoch, 11. Mai 2011 11:52
An: Guido Hecken
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx; xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Betreff: RE: [Xen-users] BUG after create snapshot in a script - Xen 4.01
-2.6.32-5-xen-amd64


Thanks Guido for your answer. 

I haven't seen this report.... oups.. 
I have add the "squeeze-proposed-updates" in the sources.list
and i have update the package linux-image-2.6.32-5-xen-amd64 - 2.6.32-31
to 2.6.32-34 
All of my test script works fine now. No bug with the lvcreate and lvremove..

Regards, 
Remi


Hi,

have the same bug here!
It should be fixed as:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614400

I'm not 100% shure but the fix should be available under proposed updates
for squeeze.
You can activate them under /etc/apt/sources.list
Add something like this to include "proposed updates"
# deb http://ftp-stud.hs-esslingen.de/debian squeeze-proposed-updates main
non-free contrib
I didn't try it in production environment until now and don't know which
impacts it might have to "mix" different deb sources.

Regards
Guido 

________________________________________
Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]
Im Auftrag von Rémi BERNIER
Gesendet: Dienstag, 10. Mai 2011 14:07
An: Xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: [Xen-users] BUG after create snapshot in a script - Xen 4.01 -2.6.32-5-xen-amd64


Hello list, 

I have met a Bug in the debian squeeze with the kernel 2.6.32-5-xen-amd64
and Xen 4.0.1 
I have try with two differents environement, but i have the same result...
I haven't this bug when i use just the kernel  2.6.32-5-xen-amd64
without the hypervisor Xen 4.0.1 and on the debian lenny with the kernel
2.6.26-2-xen-amd64 + Xen 3.2.1. 
When i run a script who create a snapshot of a LV, i have this Bug error:

Just after the "lvcreate -s -n Snap -L 1G /dev/data/svsqueeze"
in the script 

May 10 12:39:29 asusf3ja kernel: [   55.006801] BUG: unable to handle
kernel paging request at ffff88000f0cc010 
May 10 12:39:29 asusf3ja kernel: [   55.006921] IP: [<ffffffff8100e428>]
xen_set_pmd+0x15/0x2c 
May 10 12:39:29 asusf3ja kernel: [   55.007000] PGD 1002067 PUD 1006067
PMD 6a067 PTE 801000000f0cc065 
May 10 12:39:29 asusf3ja kernel: [   55.007162] Oops: 0003 [#1] SMP
May 10 12:39:29 asusf3ja kernel: [   55.007261] last sysfs file: /sys/devices/virtual/block/dm-0/dm/suspended
May 10 12:39:29 asusf3ja kernel: [   55.007308] CPU 1 
May 10 12:39:29 asusf3ja kernel: [   55.007374] Modules linked in:
dm_snapshot sco bridge stp bnep rfcomm l2cap bluetooth parport_pc ppdev
cpufreq_userspace cpufreq_stats cpufreq_powersave lp cpufreq_conservative
parport xen_evtchn xenfs uinput fuse loop firewire_sbp2 snd_hda_codec_si3054
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep arc4 snd_pcm
radeon ecb joydev snd_timer ttm drm_kms_helper stkwebcam i2c_i801 snd soundcore
iwl3945 drm i2c_algo_bit videodev v4l1_compat v4l2_compat_ioctl32 iwlcore
snd_page_alloc i2c_core psmouse pcspkr evdev rng_core asus_laptop mac80211
serio_raw cfg80211 rfkill battery ac button video output processor acpi_processor
ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic
uhci_hcd sdhci_pci sdhci ehci_hcd ata_piix thermal firewire_ohci libata
mmc_core led_class thermal_sys ricoh_mmc firewire_core crc_itu_t r8169
mii usbcore nls_base scsi_mod [last unloaded: scsi_wait_scan] 
May 10 12:39:29 asusf3ja kernel: [   55.009039] Pid: 1907, comm: dmsetup_env
Not tainted 2.6.32-5-xen-amd64 #1 F3JA 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RIP: e030:[<ffffffff8100e428>]
 [<ffffffff8100e428>] xen_set_pmd+0x15/0x2c 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RSP: e02b:ffff88000264db18
 EFLAGS: 00010246 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RAX: 0000000000000000
RBX: ffff88000f0cc010 RCX: ffff880000000000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RDX: ffffea0000000000
RSI: 0000000001d4a000 RDI: ffff88000f0cc010 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RBP: 0000000000000000
R08: 0000000001d4a000 R09: ffff88000fc03c00 
May 10 12:39:29 asusf3ja kernel: [   55.009039] R10: 0000000000000000
R11: ffff880002710760 R12: 000000000061c000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] R13: 0000000000400000
R14: ffff88000f0cc010 R15: ffff88000f396000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] FS:  00007f7138d0b700(0000)
GS:ffff880003356000(0000) knlGS:0000000000000000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] CS:  e033 DS:
0000 ES: 0000 CR0: 000000008005003b 
May 10 12:39:29 asusf3ja kernel: [   55.009039] CR2: ffff88000f0cc010
CR3: 000000000eda9000 CR4: 0000000000002660 
May 10 12:39:29 asusf3ja kernel: [   55.009039] DR0: 0000000000000000
DR1: 0000000000000000 DR2: 0000000000000000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] DR3: 0000000000000000
DR6: 00000000ffff0ff0 DR7: 0000000000000400 
May 10 12:39:29 asusf3ja kernel: [   55.009039] Process dmsetup_env
(pid: 1907, threadinfo ffff88000264c000, task ffff8800025fc6a0) 
May 10 12:39:29 asusf3ja kernel: [   55.009039] Stack: 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  ffff880000000000
0000000000600000 0000000000400000 ffffffff810cfae2 
May 10 12:39:29 asusf3ja kernel: [   55.009039] <0> ffff88000264dfd8
000000000edb1067 0000000003192ad3 0000000000000000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] <0> 0000000000000000
000000000061bfff 000000000061bfff 0000000001c00000 
May 10 12:39:29 asusf3ja kernel: [   55.009039] Call Trace: 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810cfae2>]
? free_pgd_range+0x226/0x3bf 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810cfd17>]
? free_pgtables+0x9c/0xbd 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810d14f9>]
? exit_mmap+0xef/0x148 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff8104cc7d>]
? mmput+0x3c/0xdf 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810f470e>]
? flush_old_exec+0x460/0x54c 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff81127468>]
? load_elf_binary+0x0/0x1954 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff81127805>]
? load_elf_binary+0x39d/0x1954 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810cc7ce>]
? follow_page+0x2ad/0x303 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810ce392>]
? __get_user_pages+0x3ea/0x47b 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810f5203>]
? get_arg_page+0x61/0x110 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff81127468>]
? load_elf_binary+0x0/0x1954 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810f3ede>]
? search_binary_handler+0xb4/0x245 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff810f56df>]
? do_execve+0x1e4/0x2c3 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff81010500>]
? sys_execve+0x35/0x4c 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  [<ffffffff81011f9a>]
? stub_execve+0x6a/0xc0 
May 10 12:39:29 asusf3ja kernel: [   55.009039] Code: fb ff ff e8
d2 f4 01 00 bf 01 00 00 00 e8 c9 ea ff ff 59 5e 5b c3 55 48 89 f5 53 48
89 fb 48 83 ec 08 e8 6e e3 ff ff 84 c0 75 08 <48> 89 2b 41 59 5b
5d c3 41 58 48 89 df 48 89 ee 5b 5d e9 7e ff 
May 10 12:39:29 asusf3ja kernel: [   55.009039] RIP  [<ffffffff8100e428>]
xen_set_pmd+0x15/0x2c 
May 10 12:39:29 asusf3ja kernel: [   55.009039]  RSP <ffff88000264db18>
May 10 12:39:29 asusf3ja kernel: [   55.009039] CR2: ffff88000f0cc010
May 10 12:39:29 asusf3ja kernel: [   55.009039] ---[ end trace eb86c0dbc5e972a3
]--- 


Anyone have met this problem ? 
Thanks in advance for your answer. 
Regards, 
Rémi 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users