From: "Luca Tettamanti" <kronos.it@gmail.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [2.6.27] early exception - lockdep related?
Date: Wed, 3 Sep 2008 10:28:25 +0200 [thread overview]
Message-ID: <68676e00809030128o45820023n6f270847e14af2a3@mail.gmail.com> (raw)
In-Reply-To: <1220424721.8609.74.camel@twins>
On Wed, Sep 3, 2008 at 8:52 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, 2008-09-02 at 23:06 +0200, Luca Tettamanti wrote:
>> Hello,
>> I'm seeing an early exception (0e) - which seems related to lockdep - at
>> boot with many 2.6.27 kernels and I'm having troubles to track it down.
>
> Does it print one of these nice stack traces?
Of course not ;-) It dies before dumping the stack trace (or at least
it doesn't make to the console - that machine has a serial port, but
my notebook does not... I've ordered a usb-to-serial adapter).
>> The strange thing is that it comes and goes with different kernel
>> versions
>
> What kernel version did you generate the below with - and what config.
-rc2 is working, after that it's intermittent. The last kernel that I
tried is -git from a couple of days ago.
>> , but a "bad" kernel consistently fails across reboots. It also
>> seems to be sensitive to the configuration (attached)
>
> you seem to have forgotten that attachment.
Ops, will send as soon as I get home.
Luca
next prev parent reply other threads:[~2008-09-03 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:06 [2.6.27] early exception - lockdep related? Luca Tettamanti
2008-09-03 6:52 ` Peter Zijlstra
2008-09-03 8:28 ` Luca Tettamanti [this message]
2008-09-03 8:37 ` Peter Zijlstra
2008-09-03 8:54 ` Luca Tettamanti
2008-09-03 9:01 ` Peter Zijlstra
2008-09-03 9:03 ` Peter Zijlstra
2008-09-03 19:21 ` Luca Tettamanti
2008-09-04 14:25 ` Peter Zijlstra
2008-09-04 20:51 ` Luca Tettamanti
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=68676e00809030128o45820023n6f270847e14af2a3@mail.gmail.com \
--to=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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