linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Molina <tmolina@cablespeed.com>
To: linux-kernel@vger.kernel.org
Cc: tmolina@cablespeed.com
Subject: Re: Presario oops on 2.6.0-test1
Date: Mon, 28 Jul 2003 03:40:11 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307280338390.821-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0307250518230.822-100000@lap>

On Fri, 25 Jul 2003, Thomas Molina wrote:

> > It gives me Unable to handle kernel paging request at virtual address
> > c035800
> > *pde = 00102027
> > *pte = 00358000
> >
> > Oops: 0000[#1]
> > CPU:    0
> > EIP:    0060:[<C014CE95>]    Not tainted
> > EFLAGS: 00010002
> > EIP is at store_stackinfo+0x85/0xc0
> 
> 
> I have an update to this.  I went back and tested various kernel 
> revisions.  The above panic started happening in 2.5.74-bk1.  This appears 
> to be where the store_stackinfo function was added, protected by 
> CONFIG_DEBUG_PAGEALLOC.  Sure enough, building a 2.6.0-test1 with the same 
> configuration minus page allocation debugging produces a kernel which 
> boots without the above panic.  However, now I get the following oops, 
> which at least makes it into the message log.  This oops happens during 
> bootup, followed a minute or two later by a followon oops which I am 
> unable to capture.  The oops does not happen with every boot 
> unfortunately.

This behaviour continues with 2.6.0-test2.  This has been filed in 
Bugzilla as bug number 973.


      reply	other threads:[~2003-07-29  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20  7:05 Presario oops on 2.6.0-test1 Thomas Molina
2003-07-25 11:41 ` Thomas Molina
2003-07-28  9:40   ` Thomas Molina [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=Pine.LNX.4.44.0307280338390.821-100000@localhost.localdomain \
    --to=tmolina@cablespeed.com \
    --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 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).