From: "D. Bahi" <dbahi@enterasys.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] No Bug Here: [Was: Expected SIGSTOP persists in 2.4.26-3um ]
Date: Wed, 18 Aug 2004 22:23:36 -0400 [thread overview]
Message-ID: <41240F28.1080709@enterasys.com> (raw)
In-Reply-To: <200408182346.i7INkMek003723@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
no sir. the versions were correct. and the reboot-patch was applied
to the 2.4.24-1um kernel - this i originally reported as fixed, but
in later runs it showed up again... sigh.
the errors reported were those versions w/patches mentioned + all
our mods. more recent testing with just kernel.org + UML leads
to believe this is something we're inducing... so should not be
reported against what everyone else is playing with.
Jeff Dike wrote:
> dbahi@enterasys.com said:
>
>>I withdraw this error report against 2.4.26-3um against any plain
>>vanilla UML kernel for that matter.
>
>
> Is it possible you were mistaken about the versions, or whether the
> reboot-signals patch was present?
>
> Jeff
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2004-08-19 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 15:43 [uml-devel] Expected SIGSTOP persists in 2.4.26-3um D. Bahi
2004-08-18 20:22 ` [uml-devel] No Bug Here: [Was: Expected SIGSTOP persists in 2.4.26-3um ] D. Bahi
2004-08-18 23:46 ` Jeff Dike
2004-08-19 2:23 ` D. Bahi [this message]
2004-08-19 3:53 ` 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=41240F28.1080709@enterasys.com \
--to=dbahi@enterasys.com \
--cc=jdike@addtoit.com \
--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