From: Thomas Renninger <trenn@suse.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Len Brown <len.brown@intel.com>
Subject: Re: Xorg fails to start on 2.6.21-rc4-git7
Date: Fri, 23 Mar 2007 17:29:30 +0100 [thread overview]
Message-ID: <1174667371.5863.396.camel@queen.suse.de> (raw)
In-Reply-To: <20070323171919.7260a5b6.khali@linux-fr.org>
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@suse.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@suse.de>
> Signed-off-by: Len Brown <len.brown@intel.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
prev parent reply other threads:[~2007-03-23 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 16:19 Jean Delvare
2007-03-23 16:24 ` Jiri Kosina
2007-03-23 16:29 ` Thomas Renninger [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=1174667371.5863.396.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome