public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lenar Lõhmus" <lenar@vision.ee>
To: Lars <terraformers@gmx.net>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied
Date: Thu, 10 Jun 2004 17:51:23 +0300	[thread overview]
Message-ID: <40C8756B.6050501@vision.ee> (raw)
In-Reply-To: <ca9nid$bnc$1@sea.gmane.org>

Lars wrote:

>hi
>
>thanks for answering!
>
>rc2 worked completely stable with c1 disconnect halt enabled and low
>cpu temp.
>  
>
I've kind of opposite here. with rc2-mm2 boot message says that fixup is 
applied. "athcool stat" says 'c1 bit disabled'.
Everything stable. When I enable that bit with "athcool on" the system 
will lock up solid after an hour or so.

With 2.6.1-rc1-mm1 I could enable that bit manually and everything was 
still stable afterwards ...

Lenar


      parent reply	other threads:[~2004-06-10 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 12:18 2.6.7-rc3: nforce2, no C1 disconnect fixup applied Lars
2004-06-10 12:59 ` Bartlomiej Zolnierkiewicz
2004-06-10 13:26   ` Lars
2004-06-10 13:58     ` Bartlomiej Zolnierkiewicz
2004-06-10 21:36       ` Lars
2004-06-10 21:56         ` Bartlomiej Zolnierkiewicz
2004-06-10 22:00           ` Craig Bradney
2004-06-10 22:26             ` Bartlomiej Zolnierkiewicz
2004-06-10 22:32               ` Craig Bradney
2004-06-10 22:53                 ` Bartlomiej Zolnierkiewicz
2004-06-10 22:19           ` Lars
2004-06-10 22:35             ` Bartlomiej Zolnierkiewicz
2004-06-10 23:01               ` Lars
2004-06-10 23:23                 ` Bartlomiej Zolnierkiewicz
2004-06-10 23:38                   ` Lars
2004-06-10 14:51     ` Lenar Lõhmus [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=40C8756B.6050501@vision.ee \
    --to=lenar@vision.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terraformers@gmx.net \
    /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