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 15:33:29 +0100 [thread overview]
Message-ID: <20101201143329.GB18074@a1.tnic> (raw)
In-Reply-To: <1291209888.12511.11.camel@Tobias-Karnat>
On Wed, Dec 01, 2010 at 02:24:48PM +0100, Tobias Karnat wrote:
> > What does that mean? Are you using an official kernel version or
> > something you cooked up?
>
> I'm using the official 2.6.36.1 kernel.
> The problem happens with the modules from the kernel 2.6.36.1
>
> But as a workaround for now,
> I'm using the edac modules from 2.6.35 compiled for 2.6.36.1
> I'm just saying that the problem only occurs on kernel >= 2.6.36
Hmm, I can't reproduce it here.
> > Please try to catch the whole oops. I can see rIP but it'd be much more
> > helpful to see the calltrace and the whole register dump which are cut
> > off at the bottom of your pic.
>
> Yes, here you go:
>
> http://i55.tinypic.com/igyhpt.jpg
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.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2010-12-01 14:33 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 [this message]
2010-12-01 17:46 ` Tobias Karnat
2010-12-01 19:35 ` Borislav Petkov
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=20101201143329.GB18074@a1.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®