From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: Continuing problems booting
Date: Sun, 22 Feb 2009 22:27:56 -0800
Message-ID: <49A241EC.3050300@goop.org>
References: <alpine.GSO.2.00.0902201239010.757@algedi.dur.ac.uk>
	<alpine.GSO.2.00.0902201554500.757@algedi.dur.ac.uk>
	<alpine.LFD.2.00.0902211225540.14632@vega4.dur.ac.uk>
	<49A0F68D.9070306@goop.org>
	<alpine.LFD.2.00.0902220922040.4149@vega1.dur.ac.uk>
	<alpine.LFD.2.00.0902221449410.17196@vega3.dur.ac.uk>
	<49A187B8.7000902@goop.org>
	<alpine.LFD.2.00.0902222257230.4472@vega4.dur.ac.uk>
	<49A1DD80.1080903@goop.org>
	<alpine.LFD.2.00.0902222359090.4472@vega4.dur.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <alpine.LFD.2.00.0902222359090.4472@vega4.dur.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

M A Young wrote:
> On Sun, 22 Feb 2009, Jeremy Fitzhardinge wrote:
>
>> That's a pity; I was hoping those problems would be behind us...  Do 
>> you have any log messages relating to them?
>
> ata is still timimg out, and the devices don't work. Some errors from 
> a kvm boot are
> ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14
> ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15
> ata2.00: ATAPI: QEMU DVD-ROM, 0.9.1, max UDMA/100
> ata2.00: configured for MWDMA2
> Clocksource tsc unstable (delta = -2149391501 ns)
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
> ata2.00: configured for MWDMA2
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
> ata2.00: limiting speed to MWDMA2:PIO3
> ata2.00: configured for MWDMA2
>
> ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
> ata2.00: disabled
> ata2: soft resetting link
> ata2: EH complete

This is under qemu/kvm?

Can you include the complete boot output, and compare a native boot of 
the dom0 kernel too?

> I haven't yet seen the NULL pointer dereferences in x86_64, but for 
> i686 boot they would just be part of the ordinary system startup, 
> which I think in that case might have got far enough to try to fire 
> off an X boot screen (the kernel was from before the last couple of 
> days of drm related fixes were applied).

Hm, I don't see what would be causing them, regardless.

    J