All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tj Hariharan <tj.physicist@gmail.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: kernel stuck at trying to change CPU resolution.
Date: Sat, 18 Jul 2009 15:42:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907181529310.11571@localhost.localdomain> (raw)
In-Reply-To: <20090717153742.d9144d91.akpm@linux-foundation.org>

On Fri, 17 Jul 2009, Andrew Morton wrote:
> On Fri, 26 Jun 2009 07:16:53 -0400
> Tj Hariharan <tj.physicist@gmail.com> wrote:
> 
> > 
> > Hi, I have a Pentium-M 1.86GHZ processor Laptop. Standard DELL Latitude
> > D610. I ran the 2.6.31-rc1 kernel (updated tree as of 10 minutes ago).
> > The kernel gets stuck at the message saying "Switching to High
> > resolution mode on CPU0" after about 10 minutes it goes to the next
> > step, but then continues to get stuck. There is no log, as presumable
> > this is happening before the kernel fully initialises the harddrive and
> > passes control to user mode. I am running a non modular kernel with no
> > major changes made to my configuration since 2.6.27. I have never had
> > any issues thus far. Since I am using a laptop I am unable to access the
> > sysrq key (which in my case is not prnt screen, but Fn+PrintScreen, and
> > Fn key is not read by kernel at all, even after full boot and under
> > normal conditions). Thank you for your time. I have also attached my
> > config file. 

Tj, does the kernel boot when you add "nohz=off highres=off" to the
kernel command line ?

Another thing worth a try is to add "hpet=disable" to the kernel command
line. HPET code is the major change in the timers area since 2.6.27.

Thanks,

	tglx

      parent reply	other threads:[~2009-07-18 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 11:16 kernel stuck at trying to change CPU resolution Tj Hariharan
2009-07-17 22:37 ` Andrew Morton
2009-07-18  1:00   ` Carlos R. Mafra
2009-07-18 13:42   ` Thomas Gleixner [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=alpine.LFD.2.00.0907181529310.11571@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj.physicist@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.