From: Ira K Weiny <iweiny@falcon.csc.calpoly.edu>
To: lambert@jeol.com, linuxppc-user@lists.linuxppc.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Communicator Crashes X II
Date: Sun, 29 Aug 1999 22:07:53 -0700 (PDT) [thread overview]
Message-ID: <199908300507.WAA11832@falcon.csc.calpoly.edu> (raw)
Well I may have some more news about this problem...
Fisrt I just locked up using lynx!!! Box rebooted after? 1min? Again proves
this is not Netscape, nor a font issue etc.
I had 2 hard crashes one right after the other. The first after having set up
my printer on my other serial port. One thing I did during this was to unplug
my Pilot cradle and plug in my Printer. The two crashes occured shortly after
that. Could this be a problem with the serial code/our hardware. (PS I know
that you are not supposed to hot swap the serial ports. I just have gotten
into bad habbits over the years. ;-)
I don't know about others but my 8500 has been moved from dorm room to home and
around more times that I can think. I have plug/unpluged the serial port more
time that I can think. A couple of us have said they use Cable modems and I am
going to DSL as soon as Pac Bell can get out here to hook me up. This tends to
rule out the networking code...
So what about the serial ports. I am thinking the problem may lie there. Does
anyone else have thoughts/info which might support this theory.
Thanks
Ira Weiny
BTW I am trying to get 2.2.10 compiled so I can start messing with the code.
Have not gotten it to boot yet... ;-( Was just trying to get some OF info off
the web when this problem acted up...
[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-08-30 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 5:07 Ira K Weiny [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-30 13:16 Communicator Crashes X II Kevin Puetz
1999-08-30 16:20 ` Takashi Oe
1999-08-30 16:23 ` Geert Uytterhoeven
1999-08-31 1:48 ` Paul Mackerras
1999-09-08 18:45 ` Jerry Quinn
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=199908300507.WAA11832@falcon.csc.calpoly.edu \
--to=iweiny@falcon.csc.calpoly.edu \
--cc=lambert@jeol.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).