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

[Brian Marete <bgmarete@gmail.com>]

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@gmail.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@tiscali.co.uk> wrote:
>> On Thu, 8 Oct 2009, Brian Marete wrote:
>>> On Thu, Oct 8, 2009 at 3:10 AM, Brian Marete <bgmarete@gmail.com> wrote:
>>> > On Thu, Oct 8, 2009 at 2:34 AM, Brian Marete <bgmarete@gmail.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