From owner-freebsd-xen@FreeBSD.ORG Sun Jan 2 11:12:48 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 614A4106566B; Sun, 2 Jan 2011 11:12:48 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 37DB18FC12; Sun, 2 Jan 2011 11:12:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p02BCmqp073145; Sun, 2 Jan 2011 11:12:48 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p02BCmpJ073141; Sun, 2 Jan 2011 11:12:48 GMT (envelope-from cperciva) Date: Sun, 2 Jan 2011 11:12:48 GMT Message-Id: <201101021112.p02BCmpJ073141@freefall.freebsd.org> To: cperciva@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 11:12:48 -0000 Synopsis: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: cperciva Responsible-Changed-When: Sun Jan 2 11:12:29 UTC 2011 Responsible-Changed-Why: Assign Xen clock bug to freebsd-xen list. http://www.freebsd.org/cgi/query-pr.cgi?pr=153620 From owner-freebsd-xen@FreeBSD.ORG Sun Jan 2 11:20:11 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A3F7106566B for ; Sun, 2 Jan 2011 11:20:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 395A08FC1C for ; Sun, 2 Jan 2011 11:20:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p02BKBDh075030 for ; Sun, 2 Jan 2011 11:20:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p02BKBM6075029; Sun, 2 Jan 2011 11:20:11 GMT (envelope-from gnats) Date: Sun, 2 Jan 2011 11:20:11 GMT Message-Id: <201101021120.p02BKBM6075029@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Colin Percival Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Colin Percival List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 11:20:11 -0000 The following reply was made to PR kern/153620; it has been noted by GNATS. From: Colin Percival To: bug-followup@FreeBSD.org, fbsd-9.0-aws-ec2-1293964000@holmberg.to Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Date: Sun, 02 Jan 2011 03:16:52 -0800 This is interesting -- I thought I had squashed all the clock drift bugs. Can you tell me: 1. Did the clock run ahead, or behind? 2. Can you reproduce this? 3. Did the clock _drift_, or _jump_? The 2200 seconds mentioned is almost exactly the 2^41 ns period of the Xen timecounter, so if the clock jumped it's probably safe to guess that it's involved somehow... -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Sun Jan 2 12:20:12 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB580106566C for ; Sun, 2 Jan 2011 12:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BF9CC8FC19 for ; Sun, 2 Jan 2011 12:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p02CKCF2041382 for ; Sun, 2 Jan 2011 12:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p02CKCg1041380; Sun, 2 Jan 2011 12:20:12 GMT (envelope-from gnats) Date: Sun, 2 Jan 2011 12:20:12 GMT Message-Id: <201101021220.p02CKCg1041380@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Greg Holmberg Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Greg Holmberg List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 12:20:13 -0000 The following reply was made to PR kern/153620; it has been noted by GNATS. From: Greg Holmberg To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Date: Sun, 2 Jan 2011 12:51:33 +0100 On Sun, Jan 02, 2011 at 03:16:52AM -0800, Colin Percival wrote: > > Can you tell me: > 1. Did the clock run ahead, or behind? The NTP adjustment is a positive number (see below). Does this mean the clock is running slow? > 2. Can you reproduce this? > Yes. In the existing AMI, I just reset the clock again. Since I filed the PR, it had drifted "offset 0.124360 sec". While writing this email, it has drifted another "offset 0.009534 sec". I will let it go without correction for a while now. > 3. Did the clock _drift_, or _jump_? > Good question. Based on a handful of invocations of ntpdate, I would say that it drifts. The offset is different each time. ... Regards, Greg From owner-freebsd-xen@FreeBSD.ORG Mon Jan 3 11:07:18 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F0DE10656C4 for ; Mon, 3 Jan 2011 11:07:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F1A308FC2C for ; Mon, 3 Jan 2011 11:07:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p03B7H2L046688 for ; Mon, 3 Jan 2011 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p03B7HMq046686 for freebsd-xen@FreeBSD.org; Mon, 3 Jan 2011 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Jan 2011 11:07:17 GMT Message-Id: <201101031107.p03B7HMq046686@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 11:07:18 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS p kern/153511 xen [xen] [panic] kernel panic when xen disk is detached o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after p kern/141328 xen [xen] [panic] gstat exit causes kernel panic from unma p kern/140313 xen [xen] [panic] FreeBSD8 RC2 as PV domU crashes during c f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config 16 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 01:50:12 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5896F1065670 for ; Tue, 4 Jan 2011 01:50:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2CE5A8FC0C for ; Tue, 4 Jan 2011 01:50:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p041oCDQ003522 for ; Tue, 4 Jan 2011 01:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p041oCaQ003521; Tue, 4 Jan 2011 01:50:12 GMT (envelope-from gnats) Date: Tue, 4 Jan 2011 01:50:12 GMT Message-Id: <201101040150.p041oCaQ003521@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Greg Holmberg Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Greg Holmberg List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 01:50:12 -0000 The following reply was made to PR kern/153620; it has been noted by GNATS. From: Greg Holmberg To: FreeBSD PR kern/153620 Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Date: Tue, 4 Jan 2011 02:10:29 +0100 > On Sun, Jan 02, 2011 at 03:16:52AM -0800, Colin Percival wrote: > > 3. Did the clock _drift_, or _jump_? > I started a new VM (ami-5b82b72f) using the latest available 2011-01-01 code. The problem -- the system clock losing 2200 seconds -- is still present. Last night, the clock in the new AMI seems to have lost 2200 seconds twice in a 14 hour idle period. The system clock seemed to be stopped before login. It started incrementing smoothly again when I logged in to check on the system in the morning. The system clock itself only managed to advance 14 minutes (837 seconds) overnight. After subtracting the accumulated drift from the previous evening's work, we see that the offset with a nearby NTP server at the moment I logged in was 4398.107077. This value is very close to 2 * (2^41) / 1e9. system clock NTP source ... 20110103-141513UTC 0.437444 # drift is gradual, linear 20110103-141613UTC 0.438124 # clock is running slow 20110103-141713UTC 0.438786 20110103-141813UTC 0.439584 20110103-141914UTC 0.440247 20110103-142014UTC 0.440957 20110103-142114UTC 0.441663 20110103-142214UTC 0.442313 20110103-142314UTC 0.443064 20110103-143711UTC 4398.550141 <--- 4398.107077 second difference 20110103-143811UTC 4398.550755 between slow clock and NTP src ... I have noticed that it only seems to happen when there are no active login sessions. I have seen a large jump in system time happen with a monitor script backgrounded from a single login shell, sometime after logout. I have seen it happen when the script runs in the foreground of a window in GNU screen. I have not been able to provoke it during an interactive login session. Maybe I just need to be more creative. Best regards, Greg Holmberg From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 11:11:38 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D7D4106564A; Tue, 4 Jan 2011 11:11:38 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 148238FC15; Tue, 4 Jan 2011 11:11:38 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p04BBbVx049263; Tue, 4 Jan 2011 11:11:37 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p04BBbGQ049259; Tue, 4 Jan 2011 11:11:37 GMT (envelope-from cperciva) Date: Tue, 4 Jan 2011 11:11:37 GMT Message-Id: <201101041111.p04BBbGQ049259@freefall.freebsd.org> To: cperciva@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/153672: i386/XEN panics under heavy fork load X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 11:11:38 -0000 Synopsis: i386/XEN panics under heavy fork load Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: cperciva Responsible-Changed-When: Tue Jan 4 11:11:24 UTC 2011 Responsible-Changed-Why: Assign Xen bug to freebsd-xen list. http://www.freebsd.org/cgi/query-pr.cgi?pr=153672 From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 11:40:12 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE4361065675 for ; Tue, 4 Jan 2011 11:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD44F8FC17 for ; Tue, 4 Jan 2011 11:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p04BeCJh074590 for ; Tue, 4 Jan 2011 11:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p04BeCXx074589; Tue, 4 Jan 2011 11:40:12 GMT (envelope-from gnats) Date: Tue, 4 Jan 2011 11:40:12 GMT Message-Id: <201101041140.p04BeCXx074589@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Colin Percival Cc: Subject: Re: kern/153620: [xen] Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Colin Percival List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 11:40:13 -0000 The following reply was made to PR kern/153620; it has been noted by GNATS. From: Colin Percival To: bug-followup@FreeBSD.org, fbsd-9.0-aws-ec2-1293964000@holmberg.to Cc: Subject: Re: kern/153620: [xen] Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Date: Tue, 04 Jan 2011 03:32:21 -0800 Ok, I think I see what's happening here: Under some conditions it seems that the clock stops running. If there are no interrupts from any source, the FreeBSD instance never gets scheduled; and the clock loses time in multiples of the timecounter period (2^41 ns) if it doesn't tick for that long. The reason this doesn't show up with an interactive login session open is that ssh generates enough network traffic to wake the kernel periodically; this is also provides a workaround for this bug: Send a ping to the instance once every 30 minutes. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 15:28:45 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A444106566C; Tue, 4 Jan 2011 15:28:45 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 20FF58FC1A; Tue, 4 Jan 2011 15:28:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p04FSj9N018672; Tue, 4 Jan 2011 15:28:45 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p04FSi9p018668; Tue, 4 Jan 2011 15:28:45 GMT (envelope-from cperciva) Date: Tue, 4 Jan 2011 15:28:45 GMT Message-Id: <201101041528.p04FSi9p018668@freefall.freebsd.org> To: cperciva@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/153674: i386/XEN idle thread shows wrong percentages X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 15:28:45 -0000 Synopsis: i386/XEN idle thread shows wrong percentages Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: cperciva Responsible-Changed-When: Tue Jan 4 15:28:29 UTC 2011 Responsible-Changed-Why: Assign Xen bug to freebsd-xen list. http://www.freebsd.org/cgi/query-pr.cgi?pr=153674 From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 15:40:10 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7DD7106564A for ; Tue, 4 Jan 2011 15:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BD3B28FC14 for ; Tue, 4 Jan 2011 15:40:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p04FeAgA029837 for ; Tue, 4 Jan 2011 15:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p04FeAiw029834; Tue, 4 Jan 2011 15:40:10 GMT (envelope-from gnats) Date: Tue, 4 Jan 2011 15:40:10 GMT Message-Id: <201101041540.p04FeAiw029834@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Colin Percival Cc: Subject: Re: kern/153674: i386/XEN idle thread shows wrong percentages X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Colin Percival List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 15:40:11 -0000 The following reply was made to PR kern/153674; it has been noted by GNATS. From: Colin Percival To: bug-followup@FreeBSD.org, flo@freebsd.org Cc: Subject: Re: kern/153674: i386/XEN idle thread shows wrong percentages Date: Tue, 04 Jan 2011 07:31:16 -0800 FWIW, this sounds to me like the kernel scheduler is getting confused in its accounting; possibly due to "stolen" time (when the hypervisor is off running other instances) and possibly related to the clock-interrupts-getting-lost bug (kern/153620). -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Tue Jan 4 16:00:29 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEFAC10656D8 for ; Tue, 4 Jan 2011 16:00:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 042CA8FC17 for ; Tue, 4 Jan 2011 16:00:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p04G0OAL049425 for ; Tue, 4 Jan 2011 16:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p04G0OeE049424; Tue, 4 Jan 2011 16:00:24 GMT (envelope-from gnats) Date: Tue, 4 Jan 2011 16:00:24 GMT Message-Id: <201101041600.p04G0OeE049424@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/153672: commit references a PR X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2011 16:00:29 -0000 The following reply was made to PR kern/153672; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153672: commit references a PR Date: Tue, 4 Jan 2011 15:55:21 +0000 (UTC) Author: cperciva Date: Tue Jan 4 15:55:15 2011 New Revision: 216960 URL: http://svn.freebsd.org/changeset/base/216960 Log: Add hamfisted locking to the Xen/PV pmap code: Only allow one thread to be in {pmap_pinit, pmap_copy, pmap_release} at a time. This reduces the rate of panics when running 'make index' from ~0.6/hour to ~0.02/hour (p < 10^-30). At a later date this locking will be removed, and for this reason, it is wrapped in #ifdef HAMFISTED_LOCKING; this temporary hack is being put in place with the intention of shipping somewhat-stable Xen bits in FreeBSD 8.2-RELEASE. PR: kern/153672 MFC after: 3 days Modified: head/sys/i386/xen/pmap.c Modified: head/sys/i386/xen/pmap.c ============================================================================== --- head/sys/i386/xen/pmap.c Tue Jan 4 15:53:38 2011 (r216959) +++ head/sys/i386/xen/pmap.c Tue Jan 4 15:55:15 2011 (r216960) @@ -202,6 +202,11 @@ __FBSDID("$FreeBSD$"); #define pmap_pte_set_prot(pte, v) ((*(int *)pte &= ~PG_PROT), (*(int *)pte |= (v))) +#define HAMFISTED_LOCKING +#ifdef HAMFISTED_LOCKING +static struct mtx createdelete_lock; +#endif + struct pmap kernel_pmap_store; LIST_HEAD(pmaplist, pmap); static struct pmaplist allpmaps; @@ -502,6 +507,10 @@ pmap_bootstrap(vm_paddr_t firstaddr) /* Turn on PG_G on kernel page(s) */ pmap_set_pg(); #endif + +#ifdef HAMFISTED_LOCKING + mtx_init(&createdelete_lock, "pmap create/delete", NULL, MTX_DEF); +#endif } /* @@ -1462,6 +1471,10 @@ pmap_pinit(pmap_t pmap) static int color; int i; +#ifdef HAMFISTED_LOCKING + mtx_lock(&createdelete_lock); +#endif + PMAP_LOCK_INIT(pmap); /* @@ -1473,6 +1486,9 @@ pmap_pinit(pmap_t pmap) NBPTD); if (pmap->pm_pdir == NULL) { PMAP_LOCK_DESTROY(pmap); +#ifdef HAMFISTED_LOCKING + mtx_unlock(&createdelete_lock); +#endif return (0); } #ifdef PAE @@ -1545,6 +1561,9 @@ pmap_pinit(pmap_t pmap) TAILQ_INIT(&pmap->pm_pvchunk); bzero(&pmap->pm_stats, sizeof pmap->pm_stats); +#ifdef HAMFISTED_LOCKING + mtx_unlock(&createdelete_lock); +#endif return (1); } @@ -1776,6 +1795,10 @@ pmap_release(pmap_t pmap) pmap->pm_stats.resident_count)); PT_UPDATES_FLUSH(); +#ifdef HAMFISTED_LOCKING + mtx_lock(&createdelete_lock); +#endif + pmap_lazyfix(pmap); mtx_lock_spin(&allpmaps_lock); LIST_REMOVE(pmap, pm_list); @@ -1811,6 +1834,10 @@ pmap_release(pmap_t pmap) pmap_qremove((vm_offset_t)pmap->pm_pdpt, 1); #endif PMAP_LOCK_DESTROY(pmap); + +#ifdef HAMFISTED_LOCKING + mtx_unlock(&createdelete_lock); +#endif } static int @@ -3136,6 +3163,10 @@ pmap_copy(pmap_t dst_pmap, pmap_t src_pm CTR5(KTR_PMAP, "pmap_copy: dst_pmap=%p src_pmap=%p dst_addr=0x%x len=%d src_addr=0x%x", dst_pmap, src_pmap, dst_addr, len, src_addr); +#ifdef HAMFISTED_LOCKING + mtx_lock(&createdelete_lock); +#endif + vm_page_lock_queues(); if (dst_pmap < src_pmap) { PMAP_LOCK(dst_pmap); @@ -3225,6 +3256,10 @@ pmap_copy(pmap_t dst_pmap, pmap_t src_pm vm_page_unlock_queues(); PMAP_UNLOCK(src_pmap); PMAP_UNLOCK(dst_pmap); + +#ifdef HAMFISTED_LOCKING + mtx_unlock(&createdelete_lock); +#endif } static __inline void _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Wed Jan 5 16:40:10 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB16510656A3 for ; Wed, 5 Jan 2011 16:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C933D8FC12 for ; Wed, 5 Jan 2011 16:40:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p05GeAfi083717 for ; Wed, 5 Jan 2011 16:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p05GeAHX083716; Wed, 5 Jan 2011 16:40:10 GMT (envelope-from gnats) Date: Wed, 5 Jan 2011 16:40:10 GMT Message-Id: <201101051640.p05GeAHX083716@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Greg Holmberg Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Greg Holmberg List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2011 16:40:10 -0000 The following reply was made to PR kern/153620; it has been noted by GNATS. From: Greg Holmberg To: FreeBSD PR kern/153620 Cc: Subject: Re: kern/153620: Xen guest system clock drifts in AWS EC2 (FreeBSD 9.0-CURRENT i386 T1-micro) Date: Wed, 5 Jan 2011 17:32:53 +0100 The latest AMI (FreeBSD 9.0-CURRENT @ 2011-01-04) still drops time in chunks. It loses time in multiples of 2200 seconds while idle. The clock in the latest AMIs and older AMIs also drifts. Without some kind of external correction, it runs slightly slower, losing time at a rate of a little less than one second every 24 hours. In the 2011-01-01 and 2011-01-04 AMIs, a single ping from a remote host once every thirty minutes keeps an otherwise idle VM awake enough to prevent any time from being lost in chunks. In the latest AMIs and older AMIs, no amount of system activity or interrupts seems to prevent, aggravate, or change the rate of gradual clock drift. Regards, Greg Holmberg From owner-freebsd-xen@FreeBSD.ORG Thu Jan 6 23:00:22 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07065106566B for ; Thu, 6 Jan 2011 23:00:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CFFF28FC19 for ; Thu, 6 Jan 2011 23:00:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06N0LY1064581 for ; Thu, 6 Jan 2011 23:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06N0LtI064556; Thu, 6 Jan 2011 23:00:21 GMT (envelope-from gnats) Date: Thu, 6 Jan 2011 23:00:21 GMT Message-Id: <201101062300.p06N0LtI064556@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/140313: commit references a PR X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 23:00:22 -0000 The following reply was made to PR kern/140313; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/140313: commit references a PR Date: Thu, 6 Jan 2011 22:52:59 +0000 (UTC) Author: cperciva Date: Thu Jan 6 22:52:52 2011 New Revision: 217080 URL: http://svn.freebsd.org/changeset/base/217080 Log: MFS r217051: Fix panic when mlock(2) is used on i386/XEN. PR: kern/140313 Approved by: re (rwatson) Modified: releng/8.2/sys/i386/xen/pmap.c Directory Properties: releng/8.2/sys/ (props changed) releng/8.2/sys/amd64/include/xen/ (props changed) releng/8.2/sys/cddl/contrib/opensolaris/ (props changed) releng/8.2/sys/contrib/dev/acpica/ (props changed) releng/8.2/sys/contrib/pf/ (props changed) Modified: releng/8.2/sys/i386/xen/pmap.c ============================================================================== --- releng/8.2/sys/i386/xen/pmap.c Thu Jan 6 22:26:00 2011 (r217079) +++ releng/8.2/sys/i386/xen/pmap.c Thu Jan 6 22:52:52 2011 (r217080) @@ -1070,7 +1070,9 @@ pmap_pte_release(pt_entry_t *pte) if ((pt_entry_t *)((vm_offset_t)pte & ~PAGE_MASK) == PADDR2) { CTR1(KTR_PMAP, "pmap_pte_release: pte=0x%jx", *PMAP2); + vm_page_lock_queues(); PT_SET_VA(PMAP2, 0, TRUE); + vm_page_unlock_queues(); mtx_unlock(&PMAP2mutex); } } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Thu Jan 6 23:00:26 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8305810656B6 for ; Thu, 6 Jan 2011 23:00:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 57D378FC08 for ; Thu, 6 Jan 2011 23:00:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06N0Qm1065276 for ; Thu, 6 Jan 2011 23:00:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06N0Q4f065258; Thu, 6 Jan 2011 23:00:26 GMT (envelope-from gnats) Date: Thu, 6 Jan 2011 23:00:26 GMT Message-Id: <201101062300.p06N0Q4f065258@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/141328: commit references a PR X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 23:00:26 -0000 The following reply was made to PR kern/141328; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/141328: commit references a PR Date: Thu, 6 Jan 2011 22:54:00 +0000 (UTC) Author: cperciva Date: Thu Jan 6 22:53:55 2011 New Revision: 217081 URL: http://svn.freebsd.org/changeset/base/217081 Log: MFS r217052: Fix a panic when gstat exits or when 'mdconfig -l' is run, on i386/XEN. PR: kern/141328 Approved by: re (rwatson) Modified: releng/8.2/sys/i386/xen/pmap.c Directory Properties: releng/8.2/sys/ (props changed) releng/8.2/sys/amd64/include/xen/ (props changed) releng/8.2/sys/cddl/contrib/opensolaris/ (props changed) releng/8.2/sys/contrib/dev/acpica/ (props changed) releng/8.2/sys/contrib/pf/ (props changed) Modified: releng/8.2/sys/i386/xen/pmap.c ============================================================================== --- releng/8.2/sys/i386/xen/pmap.c Thu Jan 6 22:52:52 2011 (r217080) +++ releng/8.2/sys/i386/xen/pmap.c Thu Jan 6 22:53:55 2011 (r217081) @@ -2293,19 +2293,8 @@ pmap_remove_pte(pmap_t pmap, pt_entry_t if (oldpte & PG_G) pmap_invalidate_page(kernel_pmap, va); pmap->pm_stats.resident_count -= 1; - /* - * XXX This is not strictly correctly, but somewhere along the line - * we are losing the managed bit on some pages. It is unclear to me - * why, but I think the most likely explanation is that xen's writable - * page table implementation doesn't respect the unused bits. - */ - if ((oldpte & PG_MANAGED) || ((oldpte & PG_V) && (va < VM_MAXUSER_ADDRESS)) - ) { + if (oldpte & PG_MANAGED) { m = PHYS_TO_VM_PAGE(xpmap_mtop(oldpte) & PG_FRAME); - - if (!(oldpte & PG_MANAGED)) - printf("va=0x%x is unmanaged :-( pte=0x%llx\n", va, oldpte); - if (oldpte & PG_M) { KASSERT((oldpte & PG_RW), ("pmap_remove_pte: modified page not writable: va: %#x, pte: %#jx", @@ -2315,9 +2304,7 @@ pmap_remove_pte(pmap_t pmap, pt_entry_t if (oldpte & PG_A) vm_page_flag_set(m, PG_REFERENCED); pmap_remove_entry(pmap, m, va); - } else if ((va < VM_MAXUSER_ADDRESS) && (oldpte & PG_V)) - printf("va=0x%x is unmanaged :-( pte=0x%llx\n", va, oldpte); - + } return (pmap_unuse_pt(pmap, va, free)); } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Thu Jan 6 23:02:49 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45C2B1065670; Thu, 6 Jan 2011 23:02:49 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1B5188FC1B; Thu, 6 Jan 2011 23:02:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06N2md9076090; Thu, 6 Jan 2011 23:02:48 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06N2mEH076086; Thu, 6 Jan 2011 23:02:48 GMT (envelope-from cperciva) Date: Thu, 6 Jan 2011 23:02:48 GMT Message-Id: <201101062302.p06N2mEH076086@freefall.freebsd.org> To: mister.olli@googlemail.com, cperciva@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/140313: [xen] [panic] FreeBSD8 RC2 as PV domU crashes during configure of security/libgcrypt X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 23:02:49 -0000 Synopsis: [xen] [panic] FreeBSD8 RC2 as PV domU crashes during configure of security/libgcrypt State-Changed-From-To: patched->closed State-Changed-By: cperciva State-Changed-When: Thu Jan 6 23:02:19 UTC 2011 State-Changed-Why: Fixed in HEAD, 8-STABLE, and 8.2-RC2. http://www.freebsd.org/cgi/query-pr.cgi?pr=140313 From owner-freebsd-xen@FreeBSD.ORG Thu Jan 6 23:03:11 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFE351065674; Thu, 6 Jan 2011 23:03:11 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C6BC18FC0A; Thu, 6 Jan 2011 23:03:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06N3Bp3076192; Thu, 6 Jan 2011 23:03:11 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06N3Bnj076187; Thu, 6 Jan 2011 23:03:11 GMT (envelope-from cperciva) Date: Thu, 6 Jan 2011 23:03:11 GMT Message-Id: <201101062303.p06N3Bnj076187@freefall.freebsd.org> To: tom@hur.st, cperciva@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/141328: [xen] [panic] gstat exit causes kernel panic from unmanaged virtual address X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 23:03:12 -0000 Synopsis: [xen] [panic] gstat exit causes kernel panic from unmanaged virtual address State-Changed-From-To: patched->closed State-Changed-By: cperciva State-Changed-When: Thu Jan 6 23:02:54 UTC 2011 State-Changed-Why: Fixed in HEAD, 8-STABLE, and 8.2-RC2. http://www.freebsd.org/cgi/query-pr.cgi?pr=141328 From owner-freebsd-xen@FreeBSD.ORG Thu Jan 6 23:03:37 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ED651065672; Thu, 6 Jan 2011 23:03:37 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E91048FC15; Thu, 6 Jan 2011 23:03:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p06N3abk076289; Thu, 6 Jan 2011 23:03:36 GMT (envelope-from cperciva@freefall.freebsd.org) Received: (from cperciva@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p06N3a2V076282; Thu, 6 Jan 2011 23:03:36 GMT (envelope-from cperciva) Date: Thu, 6 Jan 2011 23:03:36 GMT Message-Id: <201101062303.p06N3a2V076282@freefall.freebsd.org> To: cperciva@freebsd.org, cperciva@FreeBSD.org, freebsd-xen@FreeBSD.org From: cperciva@FreeBSD.org Cc: Subject: Re: kern/153511: [xen] [panic] kernel panic when xen disk is detached X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 23:03:37 -0000 Synopsis: [xen] [panic] kernel panic when xen disk is detached State-Changed-From-To: patched->closed State-Changed-By: cperciva State-Changed-When: Thu Jan 6 23:03:21 UTC 2011 State-Changed-Why: Fixed in HEAD, 8-STABLE, and 8.2-RC2. http://www.freebsd.org/cgi/query-pr.cgi?pr=153511 From owner-freebsd-xen@FreeBSD.ORG Sat Jan 8 12:57:29 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B66A1065694; Sat, 8 Jan 2011 12:57:29 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 518CE8FC1C; Sat, 8 Jan 2011 12:57:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p08CvTjd049391; Sat, 8 Jan 2011 12:57:29 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p08CvT5t049387; Sat, 8 Jan 2011 12:57:29 GMT (envelope-from bz) Date: Sat, 8 Jan 2011 12:57:29 GMT Message-Id: <201101081257.p08CvT5t049387@freefall.freebsd.org> To: bz@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org From: bz@FreeBSD.org Cc: Subject: Re: kern/153789: REGRESSION: FreeBSD 8.2-RC1 crashes under Solaris/Xen while FreeBSD 8.1-p2 does not. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2011 12:57:29 -0000 Synopsis: REGRESSION: FreeBSD 8.2-RC1 crashes under Solaris/Xen while FreeBSD 8.1-p2 does not. Responsible-Changed-From-To: freebsd-bugs->freebsd-xen Responsible-Changed-By: bz Responsible-Changed-When: Sat Jan 8 12:56:35 UTC 2011 Responsible-Changed-Why: Assign Xen bug to freebsd-xen list. http://www.freebsd.org/cgi/query-pr.cgi?pr=153789 From owner-freebsd-xen@FreeBSD.ORG Sat Jan 8 13:30:19 2011 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B977C106573C for ; Sat, 8 Jan 2011 13:30:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A7E468FC1D for ; Sat, 8 Jan 2011 13:30:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p08DUJw0083557 for ; Sat, 8 Jan 2011 13:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p08DUJKu083548; Sat, 8 Jan 2011 13:30:19 GMT (envelope-from gnats) Date: Sat, 8 Jan 2011 13:30:19 GMT Message-Id: <201101081330.p08DUJKu083548@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Colin Percival Cc: Subject: Re: kern/153789: REGRESSION: FreeBSD 8.2-RC1 crashes under Solaris/Xen while FreeBSD 8.1-p2 does not. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Colin Percival List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2011 13:30:19 -0000 The following reply was made to PR kern/153789; it has been noted by GNATS. From: Colin Percival To: bug-followup@FreeBSD.org, gadm@avalon-island.ru Cc: Subject: Re: kern/153789: REGRESSION: FreeBSD 8.2-RC1 crashes under Solaris/Xen while FreeBSD 8.1-p2 does not. Date: Sat, 08 Jan 2011 05:27:49 -0800 > pmap_init(): address is out of range You sure about that message? I can't find it anywhere in the source tree. Is it possible that the message was "pmap_init(): page table page is out of range" instead? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid