From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Lars <terraformers@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied
Date: Thu, 10 Jun 2004 15:58:54 +0200 [thread overview]
Message-ID: <200406101558.54240.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <ca9nid$bnc$1@sea.gmane.org>
On Thursday 10 of June 2004 15:26, Lars wrote:
> hi
Hi,
> thanks for answering!
>
> rc2 worked completely stable with c1 disconnect halt enabled and low
> cpu temp.
> rc3 has no C1 enabled after booting, so the cpu temp rises, but its
> stable.
> when enabling the c1 disconnect halt after this with something like
> "setpci -v -H1 -s 0:0.0 6F=$(printf %x $((0x$(setpci -H1 -s 0:0.0 6F) |
> 0x10)))"
> (from
> http://www.tldp.org/HOWTO/Athlon-Powersaving-HOWTO/approaches.html#commandl
>ine) the cpu is getting cool again but the system locks up frequently.
> so it would be great to have the fixup re-enabled at boottime.
> maybe a switch to force the fixup on boards without c1 disconnect
> bios-settings would do it ?
We can't do that, some older boards hang if C1 disconnect is used.
However you can enable fixup and then C1 Halt Disconnect yourself. :-)
setpci -v -H1 -s 0:0.0 6C.L=$(printf %x $((0x$(setpci -H1 -s 0:0.0 6C.L) & 0x9F01FF01)))
- to enable fixup first
setpci -v -H1 -s 0:0.0 6F=$(printf %x $((0x$(setpci -H1 -s 0:0.0 6F) | 0x10)))
- to enable C1 Halt Disconnect
[ this is untested as I don't have nForce2 board ]
> thanks,
> lars
>
> Bartlomiej Zolnierkiewicz wrote:
> > Do you get lockups with -rc3 and not with -rc2?
next prev parent reply other threads:[~2004-06-10 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 12:18 Lars
2004-06-10 12:59 ` Bartlomiej Zolnierkiewicz
2004-06-10 13:26 ` Lars
2004-06-10 13:58 ` Bartlomiej Zolnierkiewicz [this message]
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
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=200406101558.54240.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--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
all inboxes | Powered by JetHome®