linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: sedat.dilek@gmail.com, Andre Przywara <andre.przywara@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: linux-next: Tree for Sept 6 (does not boot on AMD64)
Date: Thu, 6 Sep 2012 22:08:34 +0200	[thread overview]
Message-ID: <201209062208.34545.rjw@sisk.pl> (raw)
In-Reply-To: <CA+icZUUQiPv=iwwC43f6kuU_ikDDKeRC5=QYN4R9OzccmpAEeA@mail.gmail.com>

On Thursday, September 06, 2012, Sedat Dilek wrote:
> On Thu, Sep 6, 2012 at 1:48 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > On Thu, Sep 6, 2012 at 9:23 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >> Hi all,
> >>
> >> Changes since 20120905:
> >>
> >> New tree: arm64
> >>
> >> The powerpc tree gained a build failure for which I reverted 3 commits.
> >>
> >> The net-next tree lost its build failure.
> >>
> >> The trivial tree gained a conflict against the powerpc tree.
> >>
> >> The spi-mb tree gained a build failure so I used the version from
> >> next-20120905.
> >>
> >> The driver-core tree gained a build failure (form an interaction with the
> >> workqueues tree) for which I applied a merge fix patch.
> >>
> >> The tty tree gained a build failure for which I applied a patch.
> >>
> >> The staging tree lost its build failure.
> >>
> >> The arm-soc tree gained a conflict against the usb tree.
> >>
> >> ----------------------------------------------------------------------------
> >>
> >
> > Hi,
> >
> > Unfortunately, today's linux-next does not boot here on Ubuntu/precise AMD64.
> > My yesterday's next-20120905 is fine.
> >
> > I throw out all my additional patches an rebuild again as "-2", but
> > this linux-image does not boot.
> > It's in very early stage.
> > I removed "quiet" etc. from kernel-command-line, but this reveals not much more.
> >
> > From the attached kernel-config.diff:
> > Dunno why the 2nd is disabled now and try to turn off the 1st one in a
> > "-3" build.
> >
> > +CONFIG_X86_ACPI_CPUFREQ_CPB=y
> > -CONFIG_USB_LIBUSUAL=y
> >
> 
> [ CC Rafael (cpufreq sub-maintainer) ]

Well, this is related to the AMD cpufreq patchset I've just added to
linux-next.  I'll drop it for now until the issue is resolved.

> I hacked to turn off CONFIG_X86_ACPI_CPUFREQ_CPB, but this is not the
> root cause.
> Not sure why this setting is default YES, Rafael?
> 
> To switch from upstart to systemd does not help.

Andre, care to have a look at this?

Rafael

  reply	other threads:[~2012-09-06 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 11:48 linux-next: Tree for Sept 6 (does not boot on AMD64) Sedat Dilek
2012-09-06 13:35 ` Sedat Dilek
2012-09-06 20:08   ` Rafael J. Wysocki [this message]
2012-09-06 20:30     ` Sedat Dilek
2012-09-06 20:50       ` Andre Przywara
2012-09-06 20:53         ` Sedat Dilek
2012-09-06 21:17           ` Rafael J. Wysocki
2012-09-06 21:15             ` Sedat Dilek
2012-09-06 21:24               ` Rafael J. Wysocki

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=201209062208.34545.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=andre.przywara@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=trenn@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).