From: Matt Clay <mattclay@hevanet.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Allen Chan <alydar@users.sourceforge.net>,
user-mode-linux-devel@lists.sourceforge.net,
260111@bugs.debian.org
Subject: Re: [uml-devel] Re: Bug#260111: user-mode-linux: upgrade hangs at "NET4: Linux TCP/IP 1.0 for NET4.0 "
Date: Sat, 31 Jul 2004 00:59:20 -0700 [thread overview]
Message-ID: <410B5158.3050004@hevanet.com> (raw)
In-Reply-To: <200407301849.i6UInpUE003226@ccure.user-mode-linux.org>
Jeff Dike wrote:
>
>>Works for me. What still bothers me is that turning on debugging
>>symbols was "fixing" it for me as well.
>
> Yeah, this definitely needs more investigation.
Looking at the code for generic_console_write I noticed the return codes
for tcgetattr and tcsetattr are not being checked. After I added checks
for the return codes, I found out that both calls to tcsetattr always
return a non-zero status, which, according to the man pages, indicates a
failure. I have no idea if that is important or not.
This happens with or without the patch you supplied.
BTW: I also noticed that commenting out the second call to tcsetattr
makes the problem go away as well.
- Matt
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
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:[~2004-07-31 8:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 7:15 [uml-devel] Re: Bug#260111: user-mode-linux: upgrade hangs at "NET4: Linux TCP/IP 1.0 for NET4.0 " Allen Chan
2004-07-28 17:22 ` Jeff Dike
2004-07-29 18:30 ` Allen Chan
2004-07-30 2:34 ` Allen Chan
2004-07-30 17:23 ` Jeff Dike
2004-07-30 17:19 ` Matt Clay
2004-07-30 17:43 ` Allen Chan
2004-07-30 18:49 ` Jeff Dike
2004-07-30 21:44 ` Allen Chan
2004-07-31 5:08 ` Jeff Dike
2004-07-31 7:59 ` Matt Clay [this message]
2004-08-01 3:28 ` Matt Clay
2004-08-01 3:46 ` Matt Clay
2004-08-01 15:52 ` Jeff Dike
2004-08-01 20:10 ` Matt Clay
2004-08-02 5:15 ` Allen Chan
2004-08-02 7:33 ` Matt Clay
2004-08-02 8:14 ` Matt Clay
2004-08-02 19:19 ` Jeff Dike
2004-08-03 6:06 ` Matt Clay
2004-07-30 23:51 ` Daniel Heemann
2004-07-31 0:30 ` Nicholas Lee
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=410B5158.3050004@hevanet.com \
--to=mattclay@hevanet.com \
--cc=260111@bugs.debian.org \
--cc=alydar@users.sourceforge.net \
--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 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.