[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1174667371.5863.396.camel@queen.suse.de>
Date: Fri, 23 Mar 2007 17:29:30 +0100
From: Thomas Renninger <trenn@...e.de>
To: Jean Delvare <khali@...ux-fr.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Len Brown <len.brown@...el.com>
Subject: Re: Xorg fails to start on 2.6.21-rc4-git7
On Fri, 2007-03-23 at 17:19 +0100, Jean Delvare wrote:
> Hi all,
>
> 2.6.21-rc4-git7 doesn't work on my laptop, git6 was OK. Symptop: the
> machine freezes as Xorg is started. A bisection led me there:
>
> 25496caec111481161e7f06bbfa12a533c43cc6f is first bad commit
> commit 25496caec111481161e7f06bbfa12a533c43cc6f
> Author: Thomas Renninger <trenn@...e.de>
> Date: Tue Feb 27 12:13:00 2007 -0500
>
> ACPI: Only use IPI on known broken machines (AMD, Dothan/BaniasPentium M)
>
> Use IPI for blacklisted CPUs, add parameter IPI vs LAPIC
>
> Currently, Linux disables lapic timer for all machines with C2 and higher
> C-state support.
>
> According to Intel only specific Intel models (Banias/Dothan) are broken
> in respect of not waking up from C2 with lapic.
>
> However, I am not sure about the naming of the parameter and how it
> could/should get integrated into the dyntick part
> (CONFIG_GENERIC_CLOCKEVENTS). There, a more fine grained check (TSC
> still running?, ..) is needed? Does this make sense (always use
> CLOCK_EVT_NOTIFY_BROADCAST_ON, but use OFF if forced by use_ipi=0:
> clockevents_notify(use_ipi ? CLOCK_EVT_NOTIFY_BROADCAST_ON :
> CLOCK_EVT_NOTIFY_BROADCAST_OFF, &pr->id);
>
> Signed-off-by: Thomas Renninger <trenn@...e.de>
> Signed-off-by: Len Brown <len.brown@...el.com>
>
> :040000 040000 f089eab6ed1e602029c532d828e7d7a2e46e51af d639f8aa8676fee0bf0b868fe20151712f3a530c M drivers
>
> My laptop's CPU is:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 11
> model name : Intel(R) Pentium(R) III Mobile CPU 866MHz
> stepping : 1
> cpu MHz : 864.500
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
> bogomips : 1724.04
> clflush size : 32
>
> Thomas, Len, any idea? I can help with testing as needed.
This one has already been found, got reverted and gets fixed by Ingo
Molnar, Thomas Gleissner and Len.
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists