Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied

[Bartlomiej Zolnierkiewicz]

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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/