The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@telia.com>
To: Lawrence Walton <lawrence@the-penguin.otak.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: oops 2.6.11 and 2.6.12-rc6
Date: Tue, 07 Jun 2005 23:27:06 +0200	[thread overview]
Message-ID: <1118179626.956.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20050607194852.GA3638@the-penguin.otak.com>

Please always do reply-to-all around here, might get missed otherwise

> > > I have a production server that has not booted any kernel I've tried sense
> > > 2.6.10.
> > > I captured this oops by *hand* this morning when trying to boot 2.6.12-rc6.
> > > 
> > > I've included the decoded oops, lspci -vvv, .config and ver_linux information.
> > > 
> > > Unlike most cases this is a prodution machine and I have limited time to test patches. :(
> > > 
> > 
> > Unfortunately the oops text you sent cannot be used for debugging.
> > Please send the oops that 2.6.12-rc6 produces to the list (ksymoops is
> > not necessary on 2.6.x kernels and should not be used!). 
> > Depending on how early the oops happens you can definately use
> > Documentation/serial-console.txt and maybe the somewhat simpler
> > Documentation/networking/netconsole.txt
> > 
> > Please send the non-ksymoopsed oops you wrote off the screen when
> > booting 2.6.12-rc6
> > 
> > Thanks
> > 
> Here is the bare oops.
> 
> 

It appears you have disabled General setup => Configure standard kernel
=> Load all symbols

Please don't do that without a good reason, makes debugging more
difficult. How much memory is it in the box? Can you put the System.map
somewhere so I can resolve the addresses?

And you said this happened at booting right? hmmpf


      reply	other threads:[~2005-06-07 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 18:23 oops 2.6.11 and 2.6.12-rc6 Lawrence Walton
2005-06-07 19:33 ` Alexander Nyberg
2005-06-07 19:48   ` Lawrence Walton
2005-06-07 21:27     ` Alexander Nyberg [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=1118179626.956.19.camel@localhost.localdomain \
    --to=alexn@telia.com \
    --cc=lawrence@the-penguin.otak.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