From: pi <pi_ichat@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel v2.4.3 segfault on any network send
Date: Tue, 3 Apr 2001 17:51:53 -0600 [thread overview]
Message-ID: <a05010402b6f00bdebe5b@[204.134.47.72]> (raw)
Please cc me the messages, i'm not subscribed...
Hey,
I just upgraded to kernel 2.4.3 on a k6 (233 mhz) with the processor
type set accordingly, all the proper drivers compiled in and I get
this big disgusting error message (my friend said that means i f***ed
up) Sorry I don't have it, but I'll try to get it, because i'd have
to write it down... I can't telnet-and-copy/paste for obvious reasons.
If I boot to kernel 2.4.2, it won't do that, so I know that lynx
isn't the problem (and ftp has it too).
Pi
PS:
The SysRq key is a little funky in all kernels since 2.4.0... it
doesn't accept help with the letter H, i have to hit the spacebar,
and the log levels only change with the number pad...
Pi
--
use begin;
begin::signature;
Anthony "3.14159" Martinez
AIM name - LittleManTheGeek
---PERL-SIGNATURE---
#! /usr/bin/perl -w
while () {
my $sig1;
my $sig2;
my $name;
$sig1="What we have here is a failure to deallocate";
$sig2="This file provides programmers with information
proving that it was really a hardware problem";
$name="Anthony \"3.14159 iMacTinez\" Martinez"
}
=pod
ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL
YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR
BASE ARE BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE
ARE BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US! ALL YOUR BASE ARE
BELONG TO US! ALL YOUR BASE ARE BELONG TO US!
Pi
=cut
reply other threads:[~2001-04-03 23:53 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='a05010402b6f00bdebe5b@[204.134.47.72]' \
--to=pi_ichat@bigfoot.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®