mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tobias Karnat <tobias.karnat@googlemail.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: edac_core: crashes on shutdown
Date: Wed, 1 Dec 2010 20:35:08 +0100	[thread overview]
Message-ID: <20101201193508.GA4916@liondog.tnic> (raw)
In-Reply-To: <1291225614.8646.4.camel@Tobias-Karnat>

On Wed, Dec 01, 2010 at 06:46:54PM +0100, Tobias Karnat wrote:
> Am Mittwoch, den 01.12.2010, 15:33 +0100 schrieb Borislav Petkov:
> > Unfortunately, this is still incomplete because it is missing the Code: tag and
> > the end trace tag which looks like this
> > 
> > ---[ end trace ... ]---
> > 
> > and this is most probably so because we're halting and cannot print out
> > all the oops. Two things you can do:
> > 
> > 1. Connect the machine to another machine over serial- or netconsole.
> > Google for instructions how.
> > 
> > 2. If you can't do 1. you can try enabling CONFIG_BOOT_PRINTK_DELAY and
> > boot the kernel with 'boot_delay=10', for example, so that a 10ms delay
> > is inserted after each printk line. This might let us see more on the
> > console before halt and catch the whole oops.
> > 
> > Thanks.
> 
> Yes, boot_delay=10 has helped and I also removed the nvidia driver:
> 
> http://oi56.tinypic.com/eas0pg.jpg

Hmm, I see two backtraces now. I'm still not sure whether the first
one is actually the first one that happens since it is cut off at the
beginning.

If it is the first one, it should contain something like

[ ... ] Pid: ... , comm: ... Not tainted <kernel version> <DMI system name>

the important part being the "Not tainted" string. Can you check that
please?

Also, can you disable the EDAC subsystem in Kconfig and retry?
I'm trying to rule out some other issue since the backtraces are
inconclusive wrt EDAC.

Thanks.

-- 
Regards/Gruss,
    Boris.

  reply	other threads:[~2010-12-02  6:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 11:01 Tobias Karnat
2010-12-01 12:39 ` Borislav Petkov
2010-12-01 13:24   ` Tobias Karnat
2010-12-01 14:33     ` Borislav Petkov
2010-12-01 17:46       ` Tobias Karnat
2010-12-01 19:35         ` Borislav Petkov [this message]
2010-12-02  9:03           ` Tobias Karnat
2010-12-02 14:51             ` Florian Mickler
2010-12-02 14:52               ` Florian Mickler
2010-12-02 15:21             ` Borislav Petkov
2010-12-02 16:21               ` Tobias Karnat
2010-12-02 17:02                 ` Florian Mickler
2010-12-02 17:07                   ` Borislav Petkov
2010-12-02 17:06                 ` Borislav Petkov
2010-12-02 18:05                   ` Tobias Karnat
2010-12-02 18:37                     ` Borislav Petkov
2010-12-02 22:34                       ` Tobias Karnat
2010-12-03 11:58                         ` Borislav Petkov
2010-12-03 21:23                       ` Doug Thompson
2010-12-02 18:14                   ` Florian Mickler
2010-12-02 18:51                     ` Borislav Petkov
2010-12-02 19:54                       ` Florian Mickler

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=20101201193508.GA4916@liondog.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias.karnat@googlemail.com \
    /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

all inboxes | Powered by JetHome®