From: puetzk6715@uni.edu
To: linuxppc-dev@lists.linuxppc.org
Subject: Bug in G3 serial - stty causes total lockup
Date: Fri, 26 Feb 1999 10:13:38 -0600 (CST) [thread overview]
Message-ID: <Pine.PMDF.3.96.990226100814.539037820C-100000@uni.edu> (raw)
I just moved my printer from a Localtalk network to my Linux box. I then
BootX'ed into Linux (1.0.2b4 and Pauls 2.2.1) to try the HP 660C
instructions from the FAQ-o-Matic. However, attempting to use stty raw
57600 -echo crtscts < /dev/ttyS1 completely locked up the machine. I
rebooted (OF-boot), and all worked fine. Went back to MacOS, BootX'ed (I
wanted to see if this was the problem), and... it locked up again.
I finally turned off LocalTalk on the MacOS (which I was going to do
anyway now that the printer is directly connected) and now stty works
reliably after BootX. However, I don't like Linux to crash, even in
uunrealistic situations (like changing the speed on a port MacOS thought
was LocalTalk). Anyone want to look at this? I'm afreaid of the
kernel-code...
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-02-26 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.PMDF.3.96.990226100814.539037820C-100000@uni.edu \
--to=puetzk6715@uni.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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.