From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Drake <dsd@laptop.org>
Cc: Borislav Petkov <bp@alien8.de>,
jbaron@redhat.com, Andres Salomon <dilinger@queued.net>,
Chris Ball <cjb@laptop.org>,
linux-kernel@vger.kernel.org
Subject: Re: Dynamic nop selection breaks boot on Geode LX
Date: Mon, 04 Oct 2010 14:06:00 -0400 [thread overview]
Message-ID: <1286215560.6750.64.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <AANLkTikhJ6sE=CZ9HytG0p9DN9A0D+kqYB-sP8EfBN85@mail.gmail.com>
On Sun, 2010-10-03 at 17:32 +0100, Daniel Drake wrote:
> On 3 October 2010 06:50, Borislav Petkov <bp@alien8.de> wrote:
> > maybe because the Geode doesn't have both the
> > P6_NOP5 and the NOP with 4 0x66 prefixes:
> > http://kerneltrap.org/mailarchive/linux-kernel/2010/8/27/4612336
> >
> > and for some reason the trap can't find the fixup address. You say
> > "hangs" so you don't even get an "invalid opcode" OOPS?
>
> The XO doesn't have standard VGA, so it is difficult to debug such
> early crashes. This is crashing so early that kernel messages don't
> even start to get sent over serial.
>
> To debug these things, I checkpoint the code with various calls which
> send individual characters over serial:
>
> static void log_serial(char c)
> {
> while ((inb(0x3fd) & 0x20) == 0) ;
> outb(c, 0x3f8);
> while ((inb(0x3fd) & 0x40) == 0) ;
> }
Did you try earlyprintk? That is, on the kernel command line add:
earlyprintk=ttyS0,115200
or whatever the tty and baud rate is. This will start printing out the
serial right at kernel startup. Even before printk is configured.
-- Steve
>
> So, I'm not really sure if/how it crashed or oops'd. However, I can
> confirm that panic() does not get reached, since I put a character log
> in there and it doesn't get sent. Let me know if you want me to put
> character logging in other places.
>
> I applied your two patches by hand and it doesn't solve the issue,
> because the init_amd_k6() code is called long after
> arch_init_ideal_nop5()
>
next prev parent reply other threads:[~2010-10-04 18:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 19:16 Daniel Drake
2010-10-03 5:50 ` Borislav Petkov
2010-10-03 9:26 ` Borislav Petkov
2010-10-03 14:47 ` Borislav Petkov
2010-10-03 16:32 ` Daniel Drake
2010-10-03 17:12 ` Borislav Petkov
2010-10-04 18:06 ` Steven Rostedt [this message]
2010-10-04 15:46 ` Jason Baron
2010-10-04 16:49 ` Daniel Drake
2010-10-04 20:31 ` Steven Rostedt
2010-10-04 20:39 ` Jason Baron
2010-10-04 22:11 ` Steven Rostedt
2010-10-04 21:51 ` H. Peter Anvin
2010-10-04 22:15 ` Steven Rostedt
2010-10-04 22:22 ` H. Peter Anvin
2010-10-04 22:27 ` Nick Lowe
[not found] ` <AANLkTikCkwF+yd4kdad8Bcz-6YX+STiy1wgrFfJxsfRg@mail.gmail.com>
2010-10-04 22:32 ` H. Peter Anvin
2010-10-26 20:08 ` Daniel Drake
2010-10-26 20:12 ` Jason Baron
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=1286215560.6750.64.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=cjb@laptop.org \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=jbaron@redhat.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
all inboxes | Powered by JetHome®