From: Steven Barnhart <sbarn03@softhome.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: *****SPAM***** Re: 2.5.54-mm3
Date: 05 Jan 2003 11:42:27 -0500 [thread overview]
Message-ID: <1041784953.10746.1.camel@sbarn.net> (raw)
In-Reply-To: <3E17D826.1378BE4E@digeo.com>
On Sun, 2003-01-05 at 02:00, Andrew Morton wrote:
> Are you sure you selected the right CPU type?
Yes, and before I messed with it it had my cpu right in /proc (Intel
Celeron 1.06GHz)
>
> Did you enable "Load all symbols for debugging/kksymoops" in the
> kernel hacking menu?
Yes. I am always the one getting weird problems :)
--
Steven
sbarn03@softhome.net
GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5 2230 BB92 6D64 D516 0A94
prev parent reply other threads:[~2003-01-05 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 2:20 2.5.54-mm3 Steven Barnhart
[not found] ` <3E17D826.1378BE4E@digeo.com>
2003-01-05 16:42 ` Steven Barnhart [this message]
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=1041784953.10746.1.camel@sbarn.net \
--to=sbarn03@softhome.net \
--cc=akpm@digeo.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