All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jussi Laako <jlaako@pp.htv.fi>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Christian Bornträger" <linux-kernel@borntraeger.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Athlon possible fixes
Date: Sat, 12 May 2001 12:51:21 +0300	[thread overview]
Message-ID: <3AFD0799.A297066E@pp.htv.fi> (raw)
In-Reply-To: <E14yJR6-0001ec-00@the-village.bc.nu>

[-- Attachment #1: Type: text/plain, Size: 452 bytes --]

Alan Cox wrote:
> 
> > So only working kernel (without noautotune) on that A7V133 machine is
> > RedHat's 2.4.2-2 shipped with RedHat 7.1... But that's not good either
> > because the system has large reiserfs volume and 2.4.2-2 has some
> I wish I knew why the Red Hat one worked 8)

Here's my kernel config if anyone has any idea what's wrong...

-- 
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
Available at PGP keyservers

[-- Attachment #2: kernel2.cfg --]
[-- Type: application/x-ns-proxy-autoconfig, Size: 16439 bytes --]

  reply	other threads:[~2001-05-12  9:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05  7:35 Athlon possible fixes Alan Cox
2001-05-05 16:26 ` Rogier Wolff
2001-05-05 16:42   ` Kurt Roeckx
2001-05-05 22:44   ` Seth Goldberg
2001-05-06 16:44     ` Jussi Laako
2001-05-06 17:41       ` Zilvinas Valinskas
2001-05-06 18:16       ` Christian Bornträger
2001-05-06 19:23         ` Marek Pętlicki
2001-05-07 18:54         ` Jussi Laako
2001-05-11 20:09         ` Jussi Laako
2001-05-11 20:22           ` Alan Cox
2001-05-12  9:51             ` Jussi Laako [this message]
2001-05-06  2:23 ` Chris Wedgwood
2001-05-06 12:51   ` Alan Cox
2001-05-06 13:00     ` Chris Wedgwood
2001-05-11  4:02     ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2001-05-12 18:31 Ishikawa
2001-05-12 23:02 ` Alan Cox

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=3AFD0799.A297066E@pp.htv.fi \
    --to=jlaako@pp.htv.fi \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@borntraeger.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.