From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: SATA detect fails on ICH7 chipset / DellPoweredgeSC430 Date: Wed, 31 Aug 2005 15:01:38 +0100 Message-ID: <623652d50508310701368681d2@mail.gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline 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, Ian Pratt List-Id: xen-devel@lists.xenproject.org On 31/08/05, Ian Pratt wrote: > Please can you try searching for bios updates etc. I have an almost > identical pre-release Dell machine that Xen works fine on. A00 came installed and is the latest. =20 > Please can you post the ouput of 'lspci -v'. My sata controller is a rev > 03, prog-if 8f, 'Unknown device 5656' This one is different, but like you said sata failing seems to be a symptom and not the cause: 0000:00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controllers cc=3DIDE (rev 01) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Dell: Unknown device 01ae Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 20 I/O ports at fe00 [size=3D8] I/O ports at fe10 [size=3D4] I/O ports at fe20 [size=3D8] I/O ports at fe30 [size=3D4] I/O ports at fea0 [size=3D16] Memory at 40000000 (32-bit, non-prefetchable) [size=3D1K] Capabilities: [70] Power Management version 2 I just noticed the hypervisor leaves a message on the screen: (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen). (XEN) (file=3D.../xen-unstable/xen/include/asm/mm.h, line=3D201) Error pfn 6000: rd=3Dffbfb080, od=3D00000000, caf=3D00000000, taf=3D0000000c (XEN) Domain 0 shutdown: rebooting machine Thats with dom0_mem=3D98304. The pfn number changes: 128MB reports Error pfn 8000, 512MB reports pfn 20000. I guess the next step is to run it under a debugger and try to get a back trace from that error?