All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Weippert <weiti@security.tds.de>
To: Daniel Drake <dsd@gentoo.org>
Cc: akpm@osdl.org, cpufreq@lists.linux.org.uk, discuss@x86-64.org,
	linux-kernel@vger.kernel.org, davej@codemonkey.org.uk
Subject: Re: Bad page state on AMD Opteron Dual System with kernel 2.6.13-rc6-git13
Date: Mon, 29 Aug 2005 07:24:55 +0200	[thread overview]
Message-ID: <20050829052454.GA8172@pbkg4> (raw)
In-Reply-To: <43110363.7020808@gentoo.org>

On Sun, Aug 28, 2005 at 01:20:51AM +0100, Daniel Drake wrote:
> Hi,
> 
> Tim Weippert wrote:
> >i have read some postings concerning the following Kernel Messages:
> >
> >Aug 26 18:04:01 montdsnsu3 kernel: grep[11619] general protection
> >rip:2aaaaaaaed43 rsp:7fffff9c0740 error:0
> >Aug 26 18:08:02 montdsnsu3 kernel: ping[14867] general protection
> >rip:2aaaaaaaed43 rsp:7fffffdbf300 error:0
> >Aug 26 18:08:03 montdsnsu3 kernel: grep[14987] general protection
> >rip:2aaaaaaaed43 rsp:7fffffdbfce0 error:0
> >Aug 26 18:08:03 montdsnsu3 kernel: grep[15041] general protection
> >rip:2aaaaaaaed43 rsp:7fffff9bf550 error:0
> >
> >And the Bad Page State Messages:
> >
> >Bad page state at prep_new_page (in process 'sh', page ffff8100011a69c8)
> >flags:0x0100000000000014 mapping:0000000000000000 mapcount:-3 count:0
> >Backtrace:
> >
> >Call Trace:<ffffffff8015a653>{bad_page+99}
> ><ffffffff8015aa31>{prep_new_page+65}
> >       <ffffffff8015b1e2>{buffered_rmqueue+306}
> ><ffffffff8015b425>{__alloc_pages+261}
> >       <ffffffff8015b7c5>{get_zeroed_page+37}
> ><ffffffff801691b7>{__pmd_alloc+55}
> >       <ffffffff8016614e>{copy_page_range+462}
> ><ffffffff80131da4>{copy_mm+820}
> >       <ffffffff80132cba>{copy_process+2282}
> ><ffffffff80133407>{do_fork+215}
> >       <ffffffff8010db7a>{system_call+126}
> ><ffffffff8010deeb>{ptregscall_common+103}
> >       
> >Trying to fix it up, but a reboot is needed
> 
> Seems to be an identical problem as was filed here:
> 
> 	http://bugs.gentoo.org/show_bug.cgi?id=103497
> 
> This bug report seems to suggest that the ondemand scaling governor may be 
> at fault. Does your setup use this too?
> 
> (CC'ing some extra people to make sure problem is known)
> 

As this is an Server, i don't even use cpufreq on this machine. So it
think this isn't the same problem ...

Kind regards, 

    weiti

p.s: Please CC me, cause i am not subscribed on lkml.

-- 

Interpunktion und Orthographie dieser Email ist frei erfunden.
Eine Übereinstimmung mit aktuellen oder ehemaligen Regeln
wäre rein zufällig und ist nicht beabsichtigt.

Tim Weippert <weiti@topf-sicret.org>
http://www.topf-sicret.org/

WARNING: multiple messages have this Message-ID (diff)
From: Tim Weippert <weiti@security.tds.de>
To: Daniel Drake <dsd@gentoo.org>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk,
	davej@codemonkey.org.uk, akpm@osdl.org, discuss@x86-64.org
Subject: Re: Bad page state on AMD Opteron Dual System with kernel 2.6.13-rc6-git13
Date: Mon, 29 Aug 2005 07:24:55 +0200	[thread overview]
Message-ID: <20050829052454.GA8172@pbkg4> (raw)
In-Reply-To: <43110363.7020808@gentoo.org>

On Sun, Aug 28, 2005 at 01:20:51AM +0100, Daniel Drake wrote:
> Hi,
> 
> Tim Weippert wrote:
> >i have read some postings concerning the following Kernel Messages:
> >
> >Aug 26 18:04:01 montdsnsu3 kernel: grep[11619] general protection
> >rip:2aaaaaaaed43 rsp:7fffff9c0740 error:0
> >Aug 26 18:08:02 montdsnsu3 kernel: ping[14867] general protection
> >rip:2aaaaaaaed43 rsp:7fffffdbf300 error:0
> >Aug 26 18:08:03 montdsnsu3 kernel: grep[14987] general protection
> >rip:2aaaaaaaed43 rsp:7fffffdbfce0 error:0
> >Aug 26 18:08:03 montdsnsu3 kernel: grep[15041] general protection
> >rip:2aaaaaaaed43 rsp:7fffff9bf550 error:0
> >
> >And the Bad Page State Messages:
> >
> >Bad page state at prep_new_page (in process 'sh', page ffff8100011a69c8)
> >flags:0x0100000000000014 mapping:0000000000000000 mapcount:-3 count:0
> >Backtrace:
> >
> >Call Trace:<ffffffff8015a653>{bad_page+99}
> ><ffffffff8015aa31>{prep_new_page+65}
> >       <ffffffff8015b1e2>{buffered_rmqueue+306}
> ><ffffffff8015b425>{__alloc_pages+261}
> >       <ffffffff8015b7c5>{get_zeroed_page+37}
> ><ffffffff801691b7>{__pmd_alloc+55}
> >       <ffffffff8016614e>{copy_page_range+462}
> ><ffffffff80131da4>{copy_mm+820}
> >       <ffffffff80132cba>{copy_process+2282}
> ><ffffffff80133407>{do_fork+215}
> >       <ffffffff8010db7a>{system_call+126}
> ><ffffffff8010deeb>{ptregscall_common+103}
> >       
> >Trying to fix it up, but a reboot is needed
> 
> Seems to be an identical problem as was filed here:
> 
> 	http://bugs.gentoo.org/show_bug.cgi?id=103497
> 
> This bug report seems to suggest that the ondemand scaling governor may be 
> at fault. Does your setup use this too?
> 
> (CC'ing some extra people to make sure problem is known)
> 

As this is an Server, i don't even use cpufreq on this machine. So it
think this isn't the same problem ...

Kind regards, 

    weiti

p.s: Please CC me, cause i am not subscribed on lkml.

-- 

Interpunktion und Orthographie dieser Email ist frei erfunden.
Eine Übereinstimmung mit aktuellen oder ehemaligen Regeln
wäre rein zufällig und ist nicht beabsichtigt.

Tim Weippert <weiti@topf-sicret.org>
http://www.topf-sicret.org/

  reply	other threads:[~2005-08-29  5:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 16:53 Bad page state on AMD Opteron Dual System with kernel 2.6.13-rc6-git13 Tim Weippert
2005-08-28  0:20 ` Daniel Drake
2005-08-28  0:20   ` Daniel Drake
2005-08-29  5:24   ` Tim Weippert [this message]
2005-08-29  5:24     ` Tim Weippert
2005-08-29 10:28     ` Tim Weippert
2005-08-29 10:28       ` Tim Weippert
2005-08-29 20:04       ` Bongani Hlope
2005-08-30  7:36         ` Tim Weippert
     [not found]       ` <Pine.LNX.4.61.0508291401470.13709@goblin.wat.veritas.com>
     [not found]         ` <20050829142318.GB7604@pbkg4>
     [not found]           ` <20050830072759.GA4150@pbkg4>
     [not found]             ` <Pine.LNX.4.61.0508301035410.6339@goblin.wat.veritas.com>
2005-08-30 12:35               ` Tim Weippert
2005-09-02  9:58                 ` Tim Weippert
2005-08-29 10:49     ` Daniel Drake
2005-08-29 10:49       ` Daniel Drake

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=20050829052454.GA8172@pbkg4 \
    --to=weiti@security.tds.de \
    --cc=akpm@osdl.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=discuss@x86-64.org \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.