linux-kernel - Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <45BE7584.8040808@redhat.com>
Date:	Mon, 29 Jan 2007 17:30:28 -0500
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Paweł Sikora <pluto@...k.net>
CC:	linux-kernel@...r.kernel.org, Len Brown <lenb@...nel.org>,
	Adrian Bunk <bunk@...sta.de>, linux-acpi@...r.kernel.org,
	cpufreq@...ts.linux.org.uk
Subject: Re: 2.6.20rc5 k8/acpi regression ( 2.6.17.13 works fine ).

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



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/