LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Adrian Bunk <bunk@stusta.de>,
	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: Mon, 29 Jan 2007 17:30:28 -0500	[thread overview]
Message-ID: <45BE7584.8040808@redhat.com> (raw)
In-Reply-To: <200701252311.46858.pluto@agmk.net>

Paweł Sikora wrote:
> On Thursday 25 of January 2007 05:50:45 Len Brown wrote:
>   
>> 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.
>>     
>
> with debug options enabled oops looks better:
> http://minus.ds14.agh.edu.pl/~pluto/2.6.20rc5-oops-01.jpg
>
>   

In __rmqueue() (mm/page_alloc.c line 619:

static struct page *__rmqueue(struct zone *zone, unsigned int order)
{
        struct free_area * area;
        unsigned int current_order;
        struct page *page;

        for (current_order = order; current_order < MAX_ORDER;
++current_order) {
                area = zone->free_area + current_order;
                if (list_empty(&area->free_list))
                        continue;

                page = list_entry(area->free_list.next, struct page, lru);
                list_del(&page->lru);   <=====================
                rmv_page_order(page);
                area->nr_free--;

page->lru is NULL




      reply	other threads:[~2007-01-29 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 22:46 Paweł Sikora
2007-01-24 22:52 ` Adrian Bunk
2007-01-25  4:50   ` Len Brown
2007-01-25 20:54     ` Paweł Sikora
2007-01-26 21:57       ` Paweł Sikora
2007-01-25 22:11     ` Paweł Sikora
2007-01-29 22:30       ` Chuck Ebbert [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=45BE7584.8040808@redhat.com \
    --to=cebbert@redhat.com \
    --cc=bunk@stusta.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pluto@agmk.net \
    --subject='Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).' \
    /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

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).