From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39 Date: Tue, 7 Jun 2011 15:19:49 -0400 Message-ID: <20110607191949.GB2075@dumpdata.com> References: <20110504202318.GC2117@dumpdata.com> <4DC1CB36.3020309@sce.pridelands.org> <20110504221627.GA8422@dumpdata.com> <4DC1DFE9.3080604@sce.pridelands.org> <20110505183408.GA10142@dumpdata.com> <4DC30D24.7040005@sce.pridelands.org> <20110505210629.GB18972@dumpdata.com> <4DED15B3.7080701@sce.pridelands.org> <20110606191725.GZ32595@reaktio.net> <4DED478E.5070607@sce.pridelands.org> 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: <4DED478E.5070607@sce.pridelands.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Scott Garron Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Jeremy Fitzhardinge List-Id: xen-devel@lists.xenproject.org On Mon, Jun 06, 2011 at 05:33:02PM -0400, Scott Garron wrote: > On 06/06/2011 03:17 PM, Pasi K=E4rkk=E4inen wrote: > >Did you try konrad/xen.git xen/stable-2.6.39.x branch? >=20 > I hadn't until you suggested it and did just now. That one crashe= s > in a different spot. The full serial output is here: >=20 > http://www.pridelands.org/~simba/xen-debug/hailstorm-fullserial20110606= .txt > [ 2.026893] [] ? retint_restore_args+0x5/0x6 ... > [ 2.026902] [] ? acpi_os_execute_deferred+0x2c/0x= 31 > [ 2.026910] [] ? acpi_os_write_port+0xe/0x2b > [ 2.026922] [] ? acpi_hw_write_port+0x3e/0x94 > [ 2.026931] [] ? pvclock_clocksource_read+0x48/0x= b1 > [ 2.026939] [] page_fault+0x25/0x30 > [ 2.026947] [] ? acpi_os_execute_deferred+0x2c/0x= 31 That looks very similar to some previous bugs where the ACPI DSDT was trying to write to the IOAPIC to set pins or such. Hmm, the way we "fixed" it was looking at the disassembled DSDT and removing the offending write. You can look in the archive for ACPI DSDT and look for emails from Jan Beulich - he found the culprit. But this might be also something else. Did you try to boot with 'acpi=3Do= ff' just to see if ti gets past this. It might hang on something else with that option sadly :-(