linux-um archives
 help / color / mirror / Atom feed
From: Peter <peter.repliesignored@rimuhosting.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: 2.6.9-bb1, 2.4.27-bs1, SKAS3/2.6-V7 released
Date: Wed, 10 Nov 2004 12:12:28 +1300	[thread overview]
Message-ID: <41914EDC.7000206@rimuhosting.com> (raw)
In-Reply-To: <200411091935.03983.blaisorblade_spam@yahoo.it>

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

  reply	other threads:[~2004-11-09 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05  2:59 [uml-devel] __wrap_malloc compile error without CONFIG_MODE_TT Peter
2004-11-05 19:42 ` Blaisorblade
2004-11-09  2:17   ` [uml-devel] Re: 2.6.9-bb1, 2.4.27-bs1, SKAS3/2.6-V7 released Peter
2004-11-09 18:35     ` Blaisorblade
2004-11-09 23:12       ` Peter [this message]
2004-11-10  8:43       ` stian
  -- strict thread matches above, loose matches on Subject: below --
2004-11-04 18:32 [uml-devel] " Blaisorblade
2004-11-08 12:28 ` [uml-devel] " Nuutti Kotivuori
2004-11-09 11:41   ` Blaisorblade
2004-11-09 18:06 ` Bodo Stroesser
2004-11-09 18:50   ` Blaisorblade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41914EDC.7000206@rimuhosting.com \
    --to=peter.repliesignored@rimuhosting.com \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox