From: David Riley <happyoscar42@usa.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: kernel.org kernels and unreliability
Date: Thu, 09 Mar 2000 16:47:17 +0000 [thread overview]
Message-ID: <38C7D58F.C8970B7E@usa.net> (raw)
Has anyone else noticed unreliable memory problems using kernel.org's
2.3.x kernels? Especially while compiling, random things start
happening (more specifically, I get random page faults, signal 11
terminations of cc1 and bits of code are randomly dropped which reappear
when I restart compiling), but I have also noticed that any large files
that I download over ftp (and probably other protocols) have pieces
dropped from them. At first I blamed this on the ethernet card on the
other end (I have an FTP server running on a K6-2 linux box that says
"eth0: tx interrupt but no status"), but MacOS downloads perfectly from
it, and it has no problem receiving. I would use paul's kernel source,
but my PPP connenction runs behind a firewall which blocks out almost
every port (which includes Quake*, rsync, and sometimes even http when
the operators screw up) and I woun't get my DSL line until June. ;-( I
know I could use the tarballs of Paul's kernel source, but it's easy to
download a small patch every update than a 10-12 MB tarball over a PPP link.
If it makes a difference, I'm running on a 7300 (604e, hammerhead memory
controller) and this has been happening since kernel 2.3.42 (when I
upgraded from vger-2.3.18) and includes kernel 2.3.50 which hardly works
on i386 (it breaks , among other things, xfs, so I can't run X) as well.
--
"Your mouse has been moved. Windows 95 must be restarted for change to
take effect."
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-03-09 16:47 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=38C7D58F.C8970B7E@usa.net \
--to=happyoscar42@usa.net \
--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).