Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay.
From: Ross Dickson
Date: Fri Feb 13 2004 - 09:42:17 EST
- Next message: Daniel Blueman: "Re: File system performance, hardware performance, ext3, 3ware RAID1, etc."
- Previous message: Jamie Lokier: "Re: bug, or is it? - SCHED_RR and futex related"
- In reply to: Prakash K. Cheemplavam: "Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead of apic ack delay."
- Next in thread: cheuche+lkml: "Nforce2, APIC, CPU Disconnect and setup_boot_APIC_clock()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Friday 13 February 2004 21:17, Prakash K. Cheemplavam wrote:
> Hi,
>
> I am just testing this patch with latest 2.6.3-rc2-mm1. It works in that
> sense, that my machine doesn't lock up of APIC issue. (If it locks up -
> hasn't done yet - then because of something else, I am currently
> discssing it in another thread...)
>
> But it doesn't work in the sense of cooling my machine down. Though
> athcool reports disconnect is activated it behaves like it is not, ie,
> turning disconnect off makes no difference in temperatures. Your old
> tack patch in conjunction with 2.6.2-rc1 (linus) works like a charm, ie
> no lock-ups and less temp.
>
Thanks Prakash for testing it and spotting thermal problem.
Here are some temperatures from my machine read from the bios on reboot.
I gave it minimal activity for the minutes prior to reboot.
Win98, 47C
XPHome, 42C
Patched Linux 2.4.24 (1000Hz), 40C
Patched Linux 2.6.3-rc1-mm1, 53C OUCH!
Sorry, I will have to go through my latest patch and see why the temp differs
so much between 2.4 and 2.6. I currently use patched 2.4.24 with Suse 8.2 for
convenience. When it stopped the lockups on 2.6 I thought the 2.6 was
working the same way.
Daniel - I think you patched your 2.6 too. I assume it is also hot?
> Any idea? I haven't taken out the apic_tack line, but I have added the
> idle=... line. Should that be a problem? I mean the apic_tack should
> safely be ignored, isn't it? Since I swap kernels quite often, I am too
> lazy to edit the boot line every time...
Correct, apic_tack will be ignored if the apic.c is not patched with my apic
ack delay patch.
Ross.
>
> Prakash
>
>
>
-
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/
- Next message: Daniel Blueman: "Re: File system performance, hardware performance, ext3, 3ware RAID1, etc."
- Previous message: Jamie Lokier: "Re: bug, or is it? - SCHED_RR and futex related"
- In reply to: Prakash K. Cheemplavam: "Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead of apic ack delay."
- Next in thread: cheuche+lkml: "Nforce2, APIC, CPU Disconnect and setup_boot_APIC_clock()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]