From: Thomas Gleixner <tglx@linutronix.de>
To: Diego Woitasen <diego@woitasen.com.ar>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Venkatesch Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: BUG: High resolution timer/dynticks bug
Date: Sun, 9 Mar 2008 20:42:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0803092039140.3099@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080309190002.GB15058@motherbox.xtech.com.ar>
On Sun, 9 Mar 2008, Diego Woitasen wrote:
> On Sun, Mar 09, 2008 at 04:42:05PM +0100, Thomas Gleixner wrote:
> > On Sat, 8 Mar 2008, Diego Woitasen wrote:
> > > >
> > > > Is the problem reproducible when you add "hpet=disable" to the kernel
> > > > command line ?
> > >
> > > No, with hpet=disable works fine.
> >
> > Can you please try "processor.max_cstate=2" on the kernel command line ?
> >
> > Also please provide a full boot log and the output of lspci -vvv
> >
> > Thanks,
> >
> > tglx
>
> I tried. Same results, freezes after few minutes.
>
> ----------------dmesg:
> Unknown boot option `processor.max_cstate=2': ignoring
Hmm. That probably does not work when the ACPI processor stuff is
compiled as module. Can you please compile that in via
CONFIG_ACPI_PROCESSOR=y ?
Thanks,
tglx
next prev parent reply other threads:[~2008-03-09 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 1:07 BUG: High resolution timer/dynticks bug Diego Woitasen
2008-03-04 11:09 ` Pavel Machek
2008-03-04 11:14 ` Jiri Kosina
2008-03-04 15:06 ` Pavel Machek
2008-03-04 23:00 ` Diego Woitasen
2008-03-05 8:27 ` Pavel Machek
2008-03-06 22:50 ` Diego Woitasen
2008-03-07 10:33 ` Thomas Gleixner
2008-03-09 1:30 ` Diego Woitasen
2008-03-09 15:42 ` Thomas Gleixner
2008-03-09 19:00 ` Diego Woitasen
2008-03-09 19:42 ` Thomas Gleixner [this message]
2008-03-09 21:57 ` Diego Woitasen
2008-03-05 23:21 ` Ed Tomlinson
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=alpine.LFD.1.00.0803092039140.3099@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=diego@woitasen.com.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=venkatesh.pallipadi@intel.com \
/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