From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Guido Hecken" Subject: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 12:02:55 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0138247105==" Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0138247105== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBD1B6.E4ECFE8D" Content-class: urn:content-classes:message This is a multi-part message in MIME format. ------_=_NextPart_001_01CBD1B6.E4ECFE8D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Same problem here, what is the actual state of this bug? Is there any workaround for "older" kernels like mine (2.6.32-5-xen-amd64) on debian-squeeze? BTW if I start the server with the same kernel (without xen) the problem does not exist. =20 Since Giam gave us a lot of relevant informations on this bug, I don't know which details=20 I could post here to help further on this. =20 regards, Guido =20 ------_=_NextPart_001_01CBD1B6.E4ECFE8D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Same problem = here,

what is the actual state of this = bug?

Is there any workaround for = “older” kernels like mine (2.6.32-5-xen-amd64) on = debian-squeeze?

BTW if I start the server with the same = kernel (without xen) the problem does not exist.

Since Giam gave us a lot of relevant = informations on this bug, I don’t know which details =

I could post here to help further on = this.

regards,

Guido

------_=_NextPart_001_01CBD1B6.E4ECFE8D-- --===============0138247105== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0138247105==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 14:58:04 +0200 Message-ID: <20110221125804.GA5345@reaktio.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guido Hecken Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Feb 21, 2011 at 12:02:55PM +0100, Guido Hecken wrote: > Same problem here, > > what is the actual state of this bug? > > Is there any workaround for "older" kernels like mine (2.6.32-5-xen-amd64) > on debian-squeeze? > > BTW if I start the server with the same kernel (without xen) the problem > does not exist. > > > > Since Giam gave us a lot of relevant informations on this bug, I don't > know which details > > I could post here to help further on this. > What do you do to reproduce this bug? Can you post the full stacktrace/BUG log ? -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Guido Hecken" Subject: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 14:58:53 +0100 Message-ID: References: <20110221125804.GA5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Pasi, thanks for the quick response. As mentioned in previous posts, creating and afterwards deleting = snapshots crashes the system. I can do the following commands only twice, max. three times, before the = server crashes. lvcreate -s -L 10G some_vg/some_lv -n snap_some_vg_some_lv lvremove /dev/some_vg/some_lv -f Also tried this: sync; sleep 10; lvcreate -s -L 10G some_vg/some_lv -n = snap_some_vg_some_lv; sync; sleep 10; lvremove /dev/some_vg/some_lv -f Result: -------------------------------------------------------------------------= -------------------------- Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840309] ------------[ cut here ]------------ Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840323] invalid opcode: 0000 [#2] SMP Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840329] last sysfs file: = /sys/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sdb/= sdb1/alignment_offset Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840488] Stack: Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840512] Call Trace: Message from syslogd@svd-xen at Feb 21 14:32:33 ... kernel:[22916.840549] Code: ec 28 89 3c 24 48 89 f7 e8 a2 fd ff ff 48 = 89 e7 48 89 44 24 08 be 01 00 00 00 31 d2 41 ba f0 7f 00 00 e8 b0 cc ff = ff 85 c0 74 04 <0f> 0b eb fe 48 83 c4 28 c3 55 49 89 ca 48 89 d5 40 = 88 f1 48 89 -------------------------------------------------------------------------= -------------------------- /sys/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sdb/= sdb1/alignment_offset The above line is amazing, since the disk sdb isn't involved at all. The LVM stuff resides on sda. Here the whole thing from syslog: -------------------------------------------------------------------------= ------------------------- Feb 21 14:44:33 svd-xen kernel: [23636.279456] CPU 4: Feb 21 14:44:33 svd-xen kernel: [23636.279458] Modules linked in: = xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack = xt_physdev ip6table_filter ip6_tables iptable_filter ip_tables = ebtable_nat ebtables x_tables bridge stp parport_pc ppdev lp parport = cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative = xen_evtchn xenfs fuse bonding ext2 loop evdev i2c_i801 psmouse i2c_core = pcspkr serio_raw ioatdma button processor acpi_processor ext3 jbd = mbcache dm_snapshot dm_mod sg sr_mod cdrom sd_mod crc_t10dif usbhid hid = uhci_hcd ahci ehci_hcd libata usbcore nls_base aacraid scsi_mod thermal = igb dca thermal_sys [last unloaded: scsi_wait_scan] Feb 21 14:44:33 svd-xen kernel: [23636.279508] Pid: 6881, comm: = udisks-dm-expor Tainted: G D 2.6.32-5-xen-amd64 #1 X8DT3 Feb 21 14:44:33 svd-xen kernel: [23636.279510] RIP: = e030:[] [] _spin_lock+0x18/0x1b Feb 21 14:44:33 svd-xen kernel: [23636.279516] RSP: = e02b:ffff88059ad21b10 EFLAGS: 00000297 Feb 21 14:44:33 svd-xen kernel: [23636.279518] RAX: 0000000000000027 = RBX: ffff88059ad21b28 RCX: ffff88059ad21b68 Feb 21 14:44:33 svd-xen kernel: [23636.279520] RDX: 0000000000000026 = RSI: 0000000000000200 RDI: ffff8805dc0db180 Feb 21 14:44:33 svd-xen kernel: [23636.279522] RBP: 0000000000000200 = R08: 0000000000000008 R09: ffffffff814eb870 Feb 21 14:44:33 svd-xen kernel: [23636.279524] R10: 000000000000000b = R11: 00000000000186a0 R12: ffff8805dc0db100 Feb 21 14:44:33 svd-xen kernel: [23636.279526] R13: 000000000000c580 = R14: ffff88059ad21b28 R15: ffffffff814eb830 Feb 21 14:44:33 svd-xen kernel: [23636.279531] FS: = 00007feca22657a0(0000) GS:ffff88001c6c2000(0000) knlGS:0000000000000000 Feb 21 14:44:33 svd-xen kernel: [23636.279533] CS: e033 DS: 0000 ES: = 0000 CR0: 000000008005003b Feb 21 14:44:33 svd-xen kernel: [23636.279535] CR2: 00007feca1c043c0 = CR3: 0000000001001000 CR4: 0000000000002660 Feb 21 14:44:33 svd-xen kernel: [23636.279537] DR0: 0000000000000000 = DR1: 0000000000000000 DR2: 0000000000000000 Feb 21 14:44:33 svd-xen kernel: [23636.279539] DR3: 0000000000000000 = DR6: 00000000ffff0ff0 DR7: 0000000000000400 Feb 21 14:44:33 svd-xen kernel: [23636.279541] Call Trace: Feb 21 14:44:33 svd-xen kernel: [23636.279545] [] ? = xen_exit_mmap+0xf8/0x136 Feb 21 14:44:33 svd-xen kernel: [23636.279548] [] ? = exit_mmap+0x5a/0x148 Feb 21 14:44:33 svd-xen kernel: [23636.279551] [] ? = mmput+0x3c/0xdf Feb 21 14:44:33 svd-xen kernel: [23636.279554] [] ? = exit_mm+0x102/0x10d Feb 21 14:44:33 svd-xen kernel: [23636.279557] [] ? = _spin_lock_irq+0x7/0x22 Feb 21 14:44:33 svd-xen kernel: [23636.279560] [] ? = do_exit+0x1f8/0x6c6 Feb 21 14:44:33 svd-xen kernel: [23636.279564] [] ? = check_events+0x12/0x20 Feb 21 14:44:33 svd-xen kernel: [23636.279567] [] ? = oops_end+0xaf/0xb4 Feb 21 14:44:33 svd-xen kernel: [23636.279570] [] ? = do_invalid_op+0x8b/0x95 Feb 21 14:44:33 svd-xen kernel: [23636.279573] [] ? = pin_pagetable_pfn+0x2d/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279576] [] ? = __alloc_pages_nodemask+0x11c/0x5f5 Feb 21 14:44:33 svd-xen kernel: [23636.279579] [] ? = invalid_op+0x1b/0x20 Feb 21 14:44:33 svd-xen kernel: [23636.279582] [] ? = pin_pagetable_pfn+0x2d/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279585] [] ? = pin_pagetable_pfn+0x29/0x36 Feb 21 14:44:33 svd-xen kernel: [23636.279588] [] ? = __pte_alloc+0x6b/0xc6 Feb 21 14:44:33 svd-xen kernel: [23636.279591] [] ? = pmd_alloc+0x28/0x5b Feb 21 14:44:33 svd-xen kernel: [23636.279594] [] ? = handle_mm_fault+0xce/0x80f Feb 21 14:44:33 svd-xen kernel: [23636.279597] [] ? = pvclock_clocksource_read+0x3a/0x8b Feb 21 14:44:33 svd-xen kernel: [23636.279600] [] ? = do_page_fault+0x2e0/0x2fc Feb 21 14:44:33 svd-xen kernel: [23636.279603] [] ? = page_fault+0x25/0x30 -------------------------------------------------------------------------= ------------------------- Please tell me, if you need more informations. Sorry for posting with wrong subject line "(Xen-dev]" instead of = [Xen-devel]. Should I post it again to [Xen-devel]? regards, Guido -----Urspr=FCngliche Nachricht----- Von: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi]=20 Gesendet: Montag, 21. Februar 2011 13:58 An: Guido Hecken Cc: xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at = arch/x86/xen/mmu.c:1860! On Mon, Feb 21, 2011 at 12:02:55PM +0100, Guido Hecken wrote: > Same problem here, >=20 > what is the actual state of this bug? >=20 > Is there any workaround for "older" kernels like mine = (2.6.32-5-xen-amd64) > on debian-squeeze? >=20 > BTW if I start the server with the same kernel (without xen) the = problem > does not exist. >=20 >=20 >=20 > Since Giam gave us a lot of relevant informations on this bug, I = don't > know which details >=20 > I could post here to help further on this. >=20 What do you do to reproduce this bug?=20 Can you post the full stacktrace/BUG log ? -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 11:15:39 -0500 Message-ID: <20110221161539.GA5041@dumpdata.com> References: <20110221125804.GA5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guido Hecken Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > Pasi, > thanks for the quick response. > > As mentioned in previous posts, creating and afterwards deleting snapshots crashes the system. > I can do the following commands only twice, max. three times, before the server crashes. You need these two patches: b2464c422fb44275deeb5770b668351860f68e0e "x86: hold mm->page_table_lock while doing vmalloc_sync" a8bf92faf72dba6e0dd2130256cb81c3e68f672b "vmalloc: eagerly clear ptes on vunmap". From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 18:28:17 +0200 Message-ID: <20110221162817.GH5345@reaktio.net> References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110221161539.GA5041@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, Guido Hecken List-Id: xen-devel@lists.xenproject.org On Mon, Feb 21, 2011 at 11:15:39AM -0500, Konrad Rzeszutek Wilk wrote: > On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > > Pasi, > > thanks for the quick response. > > > > As mentioned in previous posts, creating and afterwards deleting snapshots crashes the system. > > I can do the following commands only twice, max. three times, before the server crashes. > > You need these two patches: > > b2464c422fb44275deeb5770b668351860f68e0e > "x86: hold mm->page_table_lock while doing vmalloc_sync" > a8bf92faf72dba6e0dd2130256cb81c3e68f672b > "vmalloc: eagerly clear ptes on vunmap". > Sounds like someone should open a bugreport to debian to add these patches to their kernel. Those patches have been in xen/stable-2.6.32.x branch for around 5 months.. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Guido Hecken" Subject: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 17:55:41 +0100 Message-ID: References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Konrad, thanks for the fast response and your hint. I suppose, I 'll have to recompile the debian standard kernel to = integrate these patches or did I miss something? If so, this drives me back to a non-standard system which I can't update = by normal system-tools without taking special care. Is there any other way to integrate these patches? regards, Guido -----Urspr=FCngliche Nachricht----- Von: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 Gesendet: Montag, 21. Februar 2011 17:16 An: Guido Hecken Cc: Pasi K=E4rkk=E4inen; xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at = arch/x86/xen/mmu.c:1860! On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > Pasi, > thanks for the quick response. >=20 > As mentioned in previous posts, creating and afterwards deleting = snapshots crashes the system. > I can do the following commands only twice, max. three times, before = the server crashes. You need these two patches: b2464c422fb44275deeb5770b668351860f68e0e "x86: hold mm->page_table_lock while doing vmalloc_sync" a8bf92faf72dba6e0dd2130256cb81c3e68f672b "vmalloc: eagerly clear ptes on vunmap". From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 16:56:30 +0000 Message-ID: <1298307390.16356.8054.camel@zakaz.uk.xensource.com> References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> <20110221162817.GH5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20110221162817.GH5345@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Cc: Guido, "xen-devel@lists.xensource.com" , Hecken , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, 2011-02-21 at 16:28 +0000, Pasi K=C3=A4rkk=C3=A4inen wrote: > On Mon, Feb 21, 2011 at 11:15:39AM -0500, Konrad Rzeszutek Wilk wrote: > > On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > > > Pasi, > > > thanks for the quick response. > > >=20 > > > As mentioned in previous posts, creating and afterwards deleting snap= shots crashes the system. > > > I can do the following commands only twice, max. three times, before = the server crashes. > >=20 > > You need these two patches: > >=20 > > b2464c422fb44275deeb5770b668351860f68e0e > > "x86: hold mm->page_table_lock while doing vmalloc_sync" > > a8bf92faf72dba6e0dd2130256cb81c3e68f672b > > "vmalloc: eagerly clear ptes on vunmap". > > >=20 > Sounds like someone should open a bugreport to debian=20 > to add these patches to their kernel. Yes please. Even if I remember I'll need a bug report to justify the change for a stable update. > Those patches have been in xen/stable-2.6.32.x branch for around 5 months= .. 5 months ago is post the xen.git snapshot used in Squeeze unfortunately so it missed out. Ian. > -- Pasi >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --=20 Ian Campbell Current Noise: Ludicra - Stagnant Pond I never said all Democrats were saloonkeepers; what I said was all saloonkeepers were Democrats. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 16:59:27 +0000 Message-ID: <1298307567.16356.8061.camel@zakaz.uk.xensource.com> References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guido Hecken Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, 2011-02-21 at 16:55 +0000, Guido Hecken wrote: > Konrad, >=20 > thanks for the fast response and your hint. > I suppose, I 'll have to recompile the debian standard kernel to integrat= e these patches or did I miss something? > If so, this drives me back to a non-standard system which I can't update = by normal system-tools without taking special care. > Is there any other way to integrate these patches? Only by reporting the issue to Debian and waiting for them to release an update. There is nothing this list can do to update an existing kernel binary for you. Ian. >=20 > regards, > Guido >=20 > -----Urspr=C3=BCngliche Nachricht----- > Von: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 > Gesendet: Montag, 21. Februar 2011 17:16 > An: Guido Hecken > Cc: Pasi K=C3=A4rkk=C3=A4inen; xen-devel@lists.xensource.com > Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! >=20 > On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > > Pasi, > > thanks for the quick response. > >=20 > > As mentioned in previous posts, creating and afterwards deleting snapsh= ots crashes the system. > > I can do the following commands only twice, max. three times, before th= e server crashes. >=20 > You need these two patches: >=20 > b2464c422fb44275deeb5770b668351860f68e0e > "x86: hold mm->page_table_lock while doing vmalloc_sync" > a8bf92faf72dba6e0dd2130256cb81c3e68f672b > "vmalloc: eagerly clear ptes on vunmap". >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --=20 Ian Campbell Current Noise: Ludicra - Stagnant Pond What's page one, a preemptive strike? -- Professor Freund, Communication, Ramapo State College From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 19:00:43 +0200 Message-ID: <20110221170043.GI5345@reaktio.net> References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guido Hecken Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, Feb 21, 2011 at 05:55:41PM +0100, Guido Hecken wrote: > Konrad, >=20 > thanks for the fast response and your hint. > I suppose, I 'll have to recompile the debian standard kernel to integr= ate these patches or did I miss something? > If so, this drives me back to a non-standard system which I can't updat= e by normal system-tools without taking special care. > Is there any other way to integrate these patches? >=20 That's why Debian needs to integrate those patches to their kernel. They've been in xen/stable-2.6.32.x branch for around 5 months already. -- Pasi > regards, > Guido >=20 > -----Urspr=FCngliche Nachricht----- > Von: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 > Gesendet: Montag, 21. Februar 2011 17:16 > An: Guido Hecken > Cc: Pasi K=E4rkk=E4inen; xen-devel@lists.xensource.com > Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:186= 0! >=20 > On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > > Pasi, > > thanks for the quick response. > >=20 > > As mentioned in previous posts, creating and afterwards deleting snap= shots crashes the system. > > I can do the following commands only twice, max. three times, before = the server crashes. >=20 > You need these two patches: >=20 > b2464c422fb44275deeb5770b668351860f68e0e > "x86: hold mm->page_table_lock while doing vmalloc_sync" > a8bf92faf72dba6e0dd2130256cb81c3e68f672b > "vmalloc: eagerly clear ptes on vunmap". >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Guido Hecken" Subject: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Mon, 21 Feb 2011 20:44:49 +0100 Message-ID: References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> <20110221170043.GI5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I have opened a bug report at debian.org on this problem. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D614400 Thanks for your time regards, Guido -----Urspr=FCngliche Nachricht----- Von: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi]=20 Gesendet: Montag, 21. Februar 2011 18:01 An: Guido Hecken Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at = arch/x86/xen/mmu.c:1860! On Mon, Feb 21, 2011 at 05:55:41PM +0100, Guido Hecken wrote: > Konrad, >=20 > thanks for the fast response and your hint. > I suppose, I 'll have to recompile the debian standard kernel to = integrate these patches or did I miss something? > If so, this drives me back to a non-standard system which I can't = update by normal system-tools without taking special care. > Is there any other way to integrate these patches? >=20 That's why Debian needs to integrate those patches to their kernel. They've been in xen/stable-2.6.32.x branch for around 5 months already. -- Pasi > regards, > Guido >=20 > -----Urspr=FCngliche Nachricht----- > Von: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 > Gesendet: Montag, 21. Februar 2011 17:16 > An: Guido Hecken > Cc: Pasi K=E4rkk=E4inen; xen-devel@lists.xensource.com > Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at = arch/x86/xen/mmu.c:1860! >=20 > On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: > > Pasi, > > thanks for the quick response. > >=20 > > As mentioned in previous posts, creating and afterwards deleting = snapshots crashes the system. > > I can do the following commands only twice, max. three times, before = the server crashes. >=20 > You need these two patches: >=20 > b2464c422fb44275deeb5770b668351860f68e0e > "x86: hold mm->page_table_lock while doing vmalloc_sync" > a8bf92faf72dba6e0dd2130256cb81c3e68f672b > "vmalloc: eagerly clear ptes on vunmap". >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fajar A. Nugraha" Subject: Re: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Wed, 23 Feb 2011 15:30:52 +0700 Message-ID: References: <20110221125804.GA5345@reaktio.net> <20110221161539.GA5041@dumpdata.com> <20110221162817.GH5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20110221162817.GH5345@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Guido Hecken Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, Feb 21, 2011 at 11:28 PM, Pasi K=E4rkk=E4inen wrote: > On Mon, Feb 21, 2011 at 11:15:39AM -0500, Konrad Rzeszutek Wilk wrote: >> On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: >> > Pasi, >> > thanks for the quick response. >> > >> > As mentioned in previous posts, creating and afterwards deleting snaps= hots crashes the system. >> > I can do the following commands only twice, max. three times, before t= he server crashes. >> >> You need these two patches: >> >> b2464c422fb44275deeb5770b668351860f68e0e >> "x86: hold mm->page_table_lock while doing vmalloc_sync" >> a8bf92faf72dba6e0dd2130256cb81c3e68f672b >> "vmalloc: eagerly clear ptes on vunmap". >> > > Sounds like someone should open a bugreport to debian > to add these patches to their kernel. > > Those patches have been in xen/stable-2.6.32.x branch for around 5 months= .. It might not be those patches that fixed the bug. I was testing latest xen/stable-2.6.32.x (currently at 2.6.32.27, definitely has those patches) with zvol when I got the bug, which manifests itself when starting 4 domUs at boot using xendomains service. So I tried xen/next-2.6.32 (which was just updated to 2.6.32.28), works fine so far. So to Guido, if you have time, please try using both xen/stable-2.6.32.x and xen/next-2.6.32 to verify which version can solve your problem. Regarding your concern about non-standard systems, "make-kpkg" might help (http://newbiedoc.sourceforge.net/system/kernel-pkg.html). --=20 Fajar From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Guido Hecken" Subject: [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860! Date: Wed, 23 Feb 2011 11:31:51 +0100 Message-ID: References: <20110221125804.GA5345@reaktio.net><20110221161539.GA5041@dumpdata.com><20110221162817.GH5345@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Fajar A. Nugraha" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Fajar, thanks for your comments on this. Here some explanatory notes concerning the case: I thought it would be a good idea to have the base for production = xen-servers on a stable distribution with presumable stable packages = installed, instead of compiling my own. In the past I used to compile the needed xen dom0 kernel on top of = Centos 5.x or Fedora but stumbled on not to be compliant to distribution = specific update methods anymore. Especially compiling new xen kernels on top of the old 2.6.18 kernel in = Centos 5.x was a pain. So I switched to Debian Squeeze which has the = reputation to be the distribution with the most actual xen packages = integrated. Another reason for choosing a presumable stable distribution was the = long time support (LTS) one would get... I will have a closer look on your provided link and hopefully, it will = lead to a stable system with newest and stable xen-kernel, which leaves = other installed packages still uptadeable through distribution specific = methods. regards, Guido -----Urspr=FCngliche Nachricht----- Von: Fajar A. Nugraha [mailto:list@fajar.net]=20 Gesendet: Mittwoch, 23. Februar 2011 09:31 An: Guido Hecken Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com; Pasi = K=E4rkk=E4inen Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at = arch/x86/xen/mmu.c:1860! On Mon, Feb 21, 2011 at 11:28 PM, Pasi K=E4rkk=E4inen = wrote: > On Mon, Feb 21, 2011 at 11:15:39AM -0500, Konrad Rzeszutek Wilk wrote: >> On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote: >> > Pasi, >> > thanks for the quick response. >> > >> > As mentioned in previous posts, creating and afterwards deleting = snapshots crashes the system. >> > I can do the following commands only twice, max. three times, = before the server crashes. >> >> You need these two patches: >> >> b2464c422fb44275deeb5770b668351860f68e0e >> "x86: hold mm->page_table_lock while doing vmalloc_sync" >> a8bf92faf72dba6e0dd2130256cb81c3e68f672b >> "vmalloc: eagerly clear ptes on vunmap". >> > > Sounds like someone should open a bugreport to debian > to add these patches to their kernel. > > Those patches have been in xen/stable-2.6.32.x branch for around 5 = months.. It might not be those patches that fixed the bug. I was testing latest xen/stable-2.6.32.x (currently at 2.6.32.27, definitely has those patches) with zvol when I got the bug, which manifests itself when starting 4 domUs at boot using xendomains service. So I tried xen/next-2.6.32 (which was just updated to 2.6.32.28), works fine so far. So to Guido, if you have time, please try using both xen/stable-2.6.32.x and xen/next-2.6.32 to verify which version can solve your problem. Regarding your concern about non-standard systems, "make-kpkg" might help (http://newbiedoc.sourceforge.net/system/kernel-pkg.html). --=20 Fajar