linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ira K. Weiny" <iweiny@kdat.csc.calpoly.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Kernal crashes
Date: Fri, 6 Aug 1999 11:07:42 -0700 (PDT)	[thread overview]
Message-ID: <199908061807.LAA11714@kdat.csc.calpoly.edu> (raw)


I have used 2.1.24 kernal with a MkLinux/LinuxPPC mixture
system.  It's a long story but it worked.

I have just upgraded to R5 of the LinuxPPC distribution
(linuxppc.com) which has the 2.2.6 kernal.

I used my same scripts to connect with ppp to my ISP.  But the new pppd and
chat programs.

I have now expierenced serveral kernal crashes when running Netscape, and
once with rlogin.  The last of which destroyed my file system and now I
can't even log in.  Very disapointing.  I have emailed the linuxppc-user
list concerning this issue and apparently others have the same problem but
no one knows how to fix it.

I know the kernal goes down because I can not even telnet to the box.  Well
maybe telnetd just went down, but I can't even get a getty to shut the
machine down and that is why the file system is hosed.

Is there something different between the kernals concering serial support?
And if so what can I do about it?

I sent something to the linuxppc-user list but the only response I got back
was "I just don't use Netscape"  Well the problem happened with rlogin and I
don't see any reason Netscape (a user program) could mess up the kernal.  If
just Netscape were crashing that would be a different issue.

Can anybody help me with this.

Thanks
Ira Weiny
iweiny@acm.org


[[ 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.   ]]

                 reply	other threads:[~1999-08-06 18:07 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=199908061807.LAA11714@kdat.csc.calpoly.edu \
    --to=iweiny@kdat.csc.calpoly.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 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).