From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1CRfAF-0004lX-FV for user-mode-linux-devel@lists.sourceforge.net; Tue, 09 Nov 2004 15:12:39 -0800 Received: from rimuhosting.com ([69.90.33.248]) by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.41) id 1CRfAC-0006vc-UR for user-mode-linux-devel@lists.sourceforge.net; Tue, 09 Nov 2004 15:12:39 -0800 Message-ID: <41914EDC.7000206@rimuhosting.com> From: Peter MIME-Version: 1.0 Subject: Re: [uml-devel] Re: 2.6.9-bb1, 2.4.27-bs1, SKAS3/2.6-V7 released References: <418AEC78.2010502@rimuhosting.com> <200411052042.22095.blaisorblade_spam@yahoo.it> <419028BF.3090308@rimuhosting.com> <200411091935.03983.blaisorblade_spam@yahoo.it> In-Reply-To: <200411091935.03983.blaisorblade_spam@yahoo.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: user-mode-linux-devel-admin@lists.sourceforge.net Errors-To: user-mode-linux-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: The user-mode Linux development list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 10 Nov 2004 12:12:28 +1300 To: Blaisorblade Cc: user-mode-linux-devel@lists.sourceforge.net There was no oops in /var/log/messages for that 'stuck' process. A server reboot managed to get rid of that stuck process OK. The host server is now up and running with a 2.6.8.1-skas3-v7 kernel. and the VPS survived 50 restarts ok. Cheers, Peter Blaisorblade wrote: > On Tuesday 09 November 2004 03:17, Peter wrote: > >>Hi. Host is 2.6.9-skas3-v7. Guest is linux.2.4.27-bs1. I restarted a >>UML guest 24 times ok. After that I got these two processes that won't >>die. > > >>xxxxd 30282 0.0 0.1 132344 3988 ? D 01:21 0:00 >>/home/umlusers/xxxxd.net/linux umid=leventd.net con=null con0=fd: >>xxxxd 30284 0.0 0.1 132344 3988 ? T 01:21 0:00 \_ >>/home/umlusers/xxxxd.net/linux umid=xxxxd.net con=null con0 > > > I.e. 24 restarts and only two dead processes, right? It means that the fix > "normally" works. But those two processes are hanged for another host kernel > bug, and this time a very bad one! > > The first process is in "D" state. > > If it stays that way, it will never die - and it also means you have had a > kernel Oops or something like that - search /var/log/messages on the host and > you'll find some text about that, which you should post (search "Oops" and > you should find it). Btw, this is a host kernel bug, so you should probably > also report it to LKML (post it here also, to get some more answers). > > Also, could you post "ps -ef" output about this processes, if they are still > alive? If not, the Oops text should be enough. ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel