From: "D. Bahi" <dbahi@enterasys.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] Re: Expedted SIGSTOP, got status = <blah> (UML 2.4.24-1um)
Date: Fri, 06 Aug 2004 18:48:29 -0400 [thread overview]
Message-ID: <41140ABD.7020806@enterasys.com> (raw)
In-Reply-To: <200408062246.i76Mk9QW004489@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
reboot-signals is only listed in the 2.6 series patches;
i didn't think to try it.
hey, THANKS! _it applies_ and almost solves the problem completely!!!
of my 20 simultaneous UMLs only one failed to launch:
Checking for the skas3 patch in the host...found
is all it does - and it just sits there....
also on reboot - do you expect the deactivate_all_fds to fail?
umount: /dev: device is busy
Please stand by while rebooting the system.
Restarting system.
deactivate_all_fds failed, errno = 9
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
Jeff Dike wrote:
> dbahi@enterasys.com said:
>
>>ok - i have skas hosts - and i'm tired of this occasional hang.
>
>
> Have you tried the reboot-signals patch?
>
> Jeff
>
--
There are two kinds of people in this world: Those that enter a room and
turn the television set on, and those that enter a room and turn the
television set off. -- Raymond Shaw, The Manchurian Candidate (1962).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2004-08-06 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <410806FE.1000209@enterasys.com>
2004-08-06 19:16 ` [uml-devel] Re: Expedted SIGSTOP, got status = <blah> (UML 2.4.24-1um) D. Bahi
2004-08-06 22:46 ` Jeff Dike
2004-08-06 22:48 ` D. Bahi [this message]
2004-08-07 0:59 ` Jeff Dike
2004-08-07 0:15 ` D. Bahi
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=41140ABD.7020806@enterasys.com \
--to=dbahi@enterasys.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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