All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SANGOI DINO LEONARDO <dino.leonardo.sangoi@allianz.it>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Len Brown <len.brown@intel.com>,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.24-rc1 and 2.6.24.rc2 hangs while running udev on my laptop
Date: Fri, 9 Nov 2007 13:10:52 +0100	[thread overview]
Message-ID: <20071109121052.GA30799@alberich.amd.com> (raw)
In-Reply-To: <20071109020321.b26b293f.akpm@linux-foundation.org>

> On Fri, 9 Nov 2007 09:47:02 +0100  SANGOI DINO LEONARDO <dino.leonardo.sangoi@allianz.it> wrote:
> > Hi,
> >  
> > My laptop (an HP nx6125) doesn't boot with kernels 2.6.24-rc1 and
> > 2.6.24.rc2. 
> > It works fine with 2.6.23 and older.
> > 
> > I seen this bug first while running fedora rawhide, so you can find hardware
> > 
> > info and boot logs at https://bugzilla.redhat.com/show_bug.cgi?id=312201.
> > 
> > I did a git bisect, and got this:
> > 
> > $ git bisect bad
> > 4f86d3a8e297205780cca027e974fd5f81064780 is first bad commit
> > commit 4f86d3a8e297205780cca027e974fd5f81064780
> > Author: Len Brown <len.brown@intel.com>
> > Date:   Wed Oct 3 18:58:00 2007 -0400
> > 
> >     cpuidle: consolidate 2.6.22 cpuidle branch into one patch

    ... snip ...

> > Config is taken from Fedora kernel. CONFIG_CPU_IDLE is set to y (tell me if
> > full config is needed).
> > 
> > If I use 'nolapic' parameter, kernel 2.6.24-rc1 boots fine. 
> > Setting CONFIG_CPU_IDLE=n also gives me a working kernel.

I am just thinking aloud ...

Boot log in the bugzilla shows:

  CPU0: AMD Turion(tm) 64 Mobile ML-34 stepping 02

So it seems that the hardware just dislikes CONFIG_CPU_IDLE.

I haven't dealt with that cpuidle stuff in the past.
Now I am wondering with which platforms that code was verified.
And yes, I know the code was in -mm for a while.
But maybe the test coverage on AMD platforms was not that high?

What about making CONFIG_CPU_IDLE dependent on EXPERIMENTAL for
the time being and remove EXPERIMENTAL when some more testing has
been done?


Regards,

Andreas

-- 
Operating | AMD Saxony Limited Liability Company & Co. KG,
  System  | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 Research | Register Court Dresden: HRA 4896, General Partner authorized
  Center  | to represent: AMD Saxony LLC (Wilmington, Delaware, US)
  (OSRC)  | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy




  reply	other threads:[~2007-11-09 12:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09  8:47 2.6.24-rc1 and 2.6.24.rc2 hangs while running udev on my laptop SANGOI DINO LEONARDO
2007-11-09 10:03 ` Andrew Morton
2007-11-09 12:10   ` Andreas Herrmann [this message]
2007-11-09 18:10   ` Pallipadi, Venkatesh
2007-11-09 18:10     ` Pallipadi, Venkatesh
     [not found]   ` <B5B0CFF685D7DF46A05CF1678CFB42ED20E0093D@orsmsx423.amr.corp.intel.com>
2007-11-10  0:52     ` Venki Pallipadi

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=20071109121052.GA30799@alberich.amd.com \
    --to=andreas.herrmann3@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=dino.leonardo.sangoi@allianz.it \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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 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.