From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Ehrhardt Date: Thu, 20 Mar 2008 11:08:12 +0000 Subject: Re: [kvm-ppc-devel] guest panic fixed Message-Id: <47E2459C.6040702@linux.vnet.ibm.com> List-Id: References: <1205969120.11366.67.camel@basalt> In-Reply-To: <1205969120.11366.67.camel@basalt> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: kvm-ppc@vger.kernel.org Hollis Blanchard wrote: > Thanks to some excellent debugging by Christian, we found the cause of > our annoying guest panics. We had not implemented exception priorities > (my bad), so a userspace ITLB miss was being delivered immediately after > entry to the decrementer interrupt vector. Patch follows, > http://penguinppc.org/~hollisb/kvm/ updated. >=20 > NFS root with virtio-net still doesn't work for me, but it doesn't > crash. :) >=20 my network works fine (at least initially) see the attached log: Sending DHCP requests .., OK IP-Config: Got DHCP answer from 192.168.1.2, my address is 192.168.1.10 IP-Config: Complete: device=3Deth0, addr=192.168.1.10, mask%5.255.255.0, gw=192.168.1.2, host=192.168.1.10, domain=3Dlocal-devnet, nis-domain=3D(none), bootserver=192.168.1.2, rootserver=192.168.1.2, rootpathLooking up por= t of RPC 100003/2 on 192.168.1.2 Looking up port of RPC 100005/1 on 192.168.1.2 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 116k init modprobe: FATAL: Could not load /lib/modules/2.6.25-rc3-dirty/modules.dep: = No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.25-rc3-dirty/modules.dep: = No such file or directory INIT: version 2.85 booting nfs: server 192.168.1.2 not responding, still trying nfs: server 192.168.1.2 not responding, still trying nfs: server 192.168.1.2 not responding, still trying INFO: task rc.sysinit:679 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. After that I run into those lockup's for init:1 and rc.sysinit:679.=20 The network is working fine for a while and then that I get these nfs timeo= uts you see above. I think thats the track I will continue - find out whats wrong there e.g. v= irtio mangles the packets, too high latency, lost virtio interrupts, ... wh= atever. @Hollis let me know if I can help you with your nfs root setup somehow? --=20 Gr=FCsse / regards,=20 Christian Ehrhardt IBM Linux Technology Center, Open Virtualization ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-ppc-devel mailing list kvm-ppc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel