All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-acpi@vger.kernel.org, "Paweł Sikora" <pluto@agmk.net>,
	linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).
Date: Wed, 24 Jan 2007 23:50:45 -0500	[thread overview]
Message-ID: <200701242350.45276.lenb@kernel.org> (raw)
In-Reply-To: <20070124225238.GT17836@stusta.de>

On Wednesday 24 January 2007 17:52, Adrian Bunk wrote:
> On Wed, Jan 24, 2007 at 11:46:44PM +0100, Paweł Sikora wrote:

> > for 2.6.20rc5 i get an acpi related oops during x86-64 boot:
> > http://minus.ds14.agh.edu.pl/~pluto/2.6.20rc5-acpi-oops.jpg
> > disabling the "amd-k8 cool'n'quiet" option in bios helps.
> > moreover, it works fine for 2.6.17.13, so it looks like
> > a recent regression. i can provide more details if you need.
> 
> thanks for your report.
> 
> Can you narrow down a bit when it started?
> Is 2.6.19 OK?
> Is 2.6.18 OK?

Is the stack trace always the same?  It doesn't make much sense to me.

if AMD cool & quiet is enabled in the BIOS, but CONFIG_CPU_FREQ=n
in the kernel, do you see the same problem?

thanks,
-Len

WARNING: multiple messages have this Message-ID (diff)
From: Len Brown <lenb@kernel.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-acpi@vger.kernel.org, "Paweł Sikora" <pluto@agmk.net>,
	linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).
Date: Wed, 24 Jan 2007 23:50:45 -0500	[thread overview]
Message-ID: <200701242350.45276.lenb@kernel.org> (raw)
In-Reply-To: <20070124225238.GT17836@stusta.de>

On Wednesday 24 January 2007 17:52, Adrian Bunk wrote:
> On Wed, Jan 24, 2007 at 11:46:44PM +0100, Paweł Sikora wrote:

> > for 2.6.20rc5 i get an acpi related oops during x86-64 boot:
> > http://minus.ds14.agh.edu.pl/~pluto/2.6.20rc5-acpi-oops.jpg
> > disabling the "amd-k8 cool'n'quiet" option in bios helps.
> > moreover, it works fine for 2.6.17.13, so it looks like
> > a recent regression. i can provide more details if you need.
> 
> thanks for your report.
> 
> Can you narrow down a bit when it started?
> Is 2.6.19 OK?
> Is 2.6.18 OK?

Is the stack trace always the same?  It doesn't make much sense to me.

if AMD cool & quiet is enabled in the BIOS, but CONFIG_CPU_FREQ=n
in the kernel, do you see the same problem?

thanks,
-Len

WARNING: multiple messages have this Message-ID (diff)
From: Len Brown <lenb@kernel.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Paweł Sikora" <pluto@agmk.net>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	cpufreq@lists.linux.org.uk
Subject: Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).
Date: Wed, 24 Jan 2007 23:50:45 -0500	[thread overview]
Message-ID: <200701242350.45276.lenb@kernel.org> (raw)
In-Reply-To: <20070124225238.GT17836@stusta.de>

On Wednesday 24 January 2007 17:52, Adrian Bunk wrote:
> On Wed, Jan 24, 2007 at 11:46:44PM +0100, Paweł Sikora wrote:

> > for 2.6.20rc5 i get an acpi related oops during x86-64 boot:
> > http://minus.ds14.agh.edu.pl/~pluto/2.6.20rc5-acpi-oops.jpg
> > disabling the "amd-k8 cool'n'quiet" option in bios helps.
> > moreover, it works fine for 2.6.17.13, so it looks like
> > a recent regression. i can provide more details if you need.
> 
> thanks for your report.
> 
> Can you narrow down a bit when it started?
> Is 2.6.19 OK?
> Is 2.6.18 OK?

Is the stack trace always the same?  It doesn't make much sense to me.

if AMD cool & quiet is enabled in the BIOS, but CONFIG_CPU_FREQ=n
in the kernel, do you see the same problem?

thanks,
-Len

  reply	other threads:[~2007-01-25  4:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 22:46 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ) Paweł Sikora
2007-01-24 22:52 ` Adrian Bunk
2007-01-24 22:52   ` Adrian Bunk
2007-01-25  4:50   ` Len Brown [this message]
2007-01-25  4:50     ` Len Brown
2007-01-25  4:50     ` Len Brown
2007-01-25 20:54     ` Paweł Sikora
2007-01-25 20:54       ` Paweł Sikora
2007-01-26 21:57       ` Paweł Sikora
2007-01-25 22:11     ` Paweł Sikora
2007-01-25 22:11       ` Paweł Sikora
2007-01-25 22:11       ` Paweł Sikora
2007-01-29 22:30       ` Chuck Ebbert
2007-01-29 22:30         ` Chuck Ebbert
2007-01-29 22:30         ` Chuck Ebbert

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=200701242350.45276.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=bunk@stusta.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pluto@agmk.net \
    /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.