linux-kernel - Re: BUG: bad page state in process (In version 2.6.31.2)

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>] [day] [month] [year] [list]

Message-ID: <6dd519ae0911200657l752437f5i7c97669328a2b381@mail.gmail.com>
Date:	Fri, 20 Nov 2009 17:57:27 +0300
From:	Brian Marete <bgmarete@...il.com>
To:	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: BUG: bad page state in process (In version 2.6.31.2)

Since upgrading to 2.6.31.5 (and now running 2.6.31.6), I have not
been able to replicate this bug, whether with the proprietary modules
loaded or not.

Thanks!

On Thu, Oct 8, 2009 at 12:28 PM, Brian Marete <bgmarete@...il.com> wrote:
> Ok. Will do without having the nvidia module loaded and report on the
> results. Also, I run a full pass of memtest86 and no problems were
> discovered.
>
> Thanks!
>
> On 10/8/09, Hugh Dickins <hugh.dickins@...cali.co.uk> wrote:
>> On Thu, 8 Oct 2009, Brian Marete wrote:
>>> On Thu, Oct 8, 2009 at 3:10 AM, Brian Marete <bgmarete@...il.com> wrote:
>>> > On Thu, Oct 8, 2009 at 2:34 AM, Brian Marete <bgmarete@...il.com> wrote:
>>> >>
>>> >> Just found the BUG back-trace pasted below in my kernel logs.
>>>
>>> Rebooted the machine and the same BUG manifests. See the trace below:
>>>
>>> (Also, run memtest86 just in case I have bad memory.)
>>>
>>> [  726.890990] BUG: Bad page state in process tracker-indexer  pfn:77541
>>> [  726.890997] page:c47eb820 flags:80000000 count:0 mapcount:0
>>> mapping:00000001 index:0
>>
>>                  ^ for some reason that page->mapping got a 1 in it.
>>
>>> [  726.891002] Pid: 9758, comm: tracker-indexer Tainted: P
>>> 2.6.31.2 #1
>>
>>                    but you're using a Proprietary module   ^
>>
>> It's great that you can reproduce this case easily, but please try
>> without Proprietary modules loaded - they're often the origin, and
>> we're unable to debug them.
>>
>> Thanks,
>> Hugh
>>
>
>
> --
> B. Gitonga Marete
> Tel: +254-722-151-590
>



-- 
B. Gitonga Marete
Tel: +254-722-151-590
--
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/