From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: pv_ops dom0 USB fixed Date: Mon, 15 Dec 2008 12:20:05 -0800 Message-ID: <4946BBF5.30508@goop.org> References: <4940210C.1060401@goop.org> <4942D0F9.7080903@goop.org> <4942E6FD.6080601@goop.org> <1e16a9ed0812131102s79d231depef1466fda8e2b897@mail.gmail.com> <1e16a9ed0812131753m3412e3ffgd9028185c90c2c40@mail.gmail.com> <1229334549.25349.82.camel@zakaz.uk.xensource.com> <1e16a9ed0812151015v50867776l100c1830380f8411@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1e16a9ed0812151015v50867776l100c1830380f8411@mail.gmail.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: deshantm@gmail.com Cc: Xen-devel , Andrew Lyon , Aviv Grafi , Ian Campbell List-Id: xen-devel@lists.xenproject.org Todd Deshane wrote: >> That's because your initramfs only contains modules for >> 2.6.27-7-generic but your Xen kernel is 2.6.28-rc8-tip so the ramdisk >> fails to load the modules it needs. >> > > Yeah, I figured that out this morning as well (Sorry for the silly mistake > and noise previously). > > I have 3 new logs though, that may give some more information > into the detection of the USB disk as well as others. > > Still not booting, but it looks like it *should* work. > > The first shows that it clearly detects the usb disk, but as > sda{1}, which makes some sense since it doesn't detect > the other two SCSI disks. Also it detects it late... > > So, I then changed the root to sda1 and added a rootdelay > option (twice I tried to add rootdelay, the second one I > put up to 90 seconds even. > > I don't know if they shed any light or if there is something > obvious that I could do to fix the situation. So I've been getting things going on my test box here. What I've observed: When I set the SATA controller to either "Legacy" mode or "Native / IDE" mode in the BIOS, it works fine. When I set it to AHCI, I see the same timeouts on IDENTIFY, but the DVD drive is detected properly. USB seems to be working fine. If I plug in a memory stick, I can mount the filesystem and read things from it. In these logs, it looks like you've overlooked the patch I added on Friday (vmap-allow-unflush-tlb.patch), and your udevd processes have been caught up in a deadlock which is preventing them from doing their thing. I suspect that's the root cause of your problems. J