From: "roland" <for_spam@gmx.de>
To: Gerd Knorr <kraxel@bytesex.org>, Henrik Nordstrom <hno@marasystems.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
uml-user <user-mode-linux-user@lists.sourceforge.net>
Subject: Re: [uml-devel] Re: Workaround for bug #851759 - SuSE YAST in textmode does not work
Date: Thu, 11 Dec 2003 22:59:13 +0100 [thread overview]
Message-ID: <044301c3c032$0789b930$2000000a@schlepptopp> (raw)
In-Reply-To: 20031211120056.GA5347@bytesex.org
mhhh,
that result is different to the results i posted.
what uml on what host are you using?
regards
roland
----- Original Message -----
From: "Gerd Knorr" <kraxel@bytesex.org>
To: "Henrik Nordstrom" <hno@marasystems.com>
Cc: "roland" <for_spam@gmx.de>; <user-mode-linux-devel@lists.sourceforge.net>; "uml-user"
<user-mode-linux-user@lists.sourceforge.net>
Sent: Thursday, December 11, 2003 1:00 PM
Subject: Re: [uml-devel] Re: Workaround for bug #851759 - SuSE YAST in textmode does not work
> On Wed, Dec 10, 2003 at 10:14:07PM +0100, Henrik Nordstrom wrote:
> > On Mon, 8 Dec 2003, Gerd Knorr wrote:
> >
> > > IMHO this one is a UML kernel bug.
> >
> > The hang certainly can be considered a UML bug.
> >
> > I think the same hang should be seen on any SIGSEGV due to incorrect X86
> > I/O operations. Can you try these two simple programs to try to isolate
> > the error?
>
> > /* test1.c */
>
> > /* test2.c */
>
> Both test do hang (until doing something else in another terminal).
> test1 does *not* print a "Segmentation fault" message as it should
> (and does outside a uml machine).
>
> > The test as such will however (if not hanging) give a false positive if
> > UML is running within vmware and can be questioned unless complemented
> > with a UML test.
>
> The test seems to work correctly. Probably it tries to access a "magic"
> i/o port which is used for communication between vmware and guest os,
> but I don't know for sure.
>
> Gerd
>
> --
> You have a new virus in /var/mail/kraxel
>
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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
next prev parent reply other threads:[~2003-12-11 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 0:33 [uml-devel] Workaround for bug #851759 - SuSE YAST in textmode does not work roland
2003-12-08 0:34 ` Matt Ayres
2003-12-08 9:40 ` Henrik Nordstrom
2003-12-08 9:44 ` Henrik Nordstrom
2003-12-08 20:32 ` [uml-user] " roland
2003-12-08 9:59 ` [uml-devel] " Gerd Knorr
2003-12-08 22:30 ` [uml-devel] Re: [uml-user] " roland
2003-12-09 9:06 ` Gerd Knorr
2003-12-10 21:14 ` [uml-devel] " Henrik Nordstrom
2003-12-10 23:52 ` roland
2003-12-11 12:00 ` Gerd Knorr
2003-12-11 12:58 ` Henrik Nordstrom
2003-12-11 14:06 ` Gerd Knorr
2003-12-11 21:59 ` roland [this message]
2003-12-12 8:58 ` Gerd Knorr
2003-12-12 11:31 ` Henrik Nordstrom
2003-12-12 11:55 ` Gerd Knorr
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='044301c3c032$0789b930$2000000a@schlepptopp' \
--to=for_spam@gmx.de \
--cc=hno@marasystems.com \
--cc=kraxel@bytesex.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.