From: Peter Zijlstra <peterz@infradead.org>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [2.6.27] early exception - lockdep related?
Date: Thu, 04 Sep 2008 16:25:31 +0200 [thread overview]
Message-ID: <1220538332.8609.233.camel@twins> (raw)
In-Reply-To: <68676e00809031221v6486d4cdmc1ac7487acd01190@mail.gmail.com>
On Wed, 2008-09-03 at 21:21 +0200, Luca Tettamanti wrote:
> On Wed, Sep 3, 2008 at 10:28 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
> > 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.
>
> Config is attached.
>
> I tried netconsole, but got not output. No luck with qemu either :S
>
> QEMU from SVN reports that:
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000000a0000
>
> KVM goes a bit further but dies due to an exception while the kernel
> is still executing in real mode.
Sadly your config just boots, albeit not to userspace due to missing
drivers.
root@twins:/mnt/build/linux-2.6# git-describe
v2.6.27-rc5-6-gbef69ea
root@twins:/mnt/build/linux-2.6# /mnt/md0/cross/bin/x86_64-linux-gcc --version
x86_64-linux-gcc (GCC) 4.3.1 20080510 (prerelease)
next prev parent reply other threads:[~2008-09-04 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:06 Luca Tettamanti
2008-09-03 6:52 ` Peter Zijlstra
2008-09-03 8:28 ` Luca Tettamanti
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 [this message]
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=1220538332.8609.233.camel@twins \
--to=peterz@infradead.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
Powered by JetHome