From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brice Figureau <brice@tincell.com>
Cc: "Linuxppc-Dev@Lists. " "Linuxppc. Org"
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: ibook2r2 & strange freeze.
Date: 26 Apr 2003 12:33:50 +0200 [thread overview]
Message-ID: <1051353230.10342.31.camel@gaston> (raw)
In-Reply-To: <B575F872-7771-11D7-BD12-0003939D5F18@tincell.com>
> After several hours of kernel compiling (my ibook is not that fast
> ;-)), I found that the latest working patch is -ben8.
> The first non working is then -ben9.
Great, many thanks. That will help.
Can you try now to put drivers/video/radeonfb.c from -ben8 into
-ben9 (and then -ben10 if it works) and tell me if that helps ?
> I can crash ben9 almost reproductibly and xmon is triggered if that can
> help you (I didn't understand how to use the System.map with xmon to
> decipher the stack trace, but I might send xmon output and my
> System.map).
> Note this might not be the same crash as ben10, because xmon is not
> fired with this kernel, although it seems to crash at the early
> beginning of rc.sysinit (I'm almost sure this is something about the
> fonts).
The system.map thing might not help (if the crash is random), but
basically, you just need to copy System.map next to vmlinux (in
/boot typically) and edit yaboot.conf to add a line
sysmap=/boot/System.map
after the image=... line (and re-run ybin to install the new yaboot.conf)
With this, xmon will know about symbols. Then, you can use the "t"
command in xmon to get a backtrace.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-26 10:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 15:27 ibook2r2 & strange freeze Brice Figureau
2003-04-25 17:43 ` Benjamin Herrenschmidt
2003-04-25 17:50 ` Benjamin Herrenschmidt
2003-04-25 20:05 ` Brice Figureau
2003-04-25 23:00 ` Brice Figureau
2003-04-26 10:33 ` Benjamin Herrenschmidt [this message]
2003-04-26 20:22 ` Brice Figureau
2003-04-26 20:35 ` Benjamin Herrenschmidt
2003-04-26 20:51 ` Brice Figureau
2003-04-26 21:01 ` Benjamin Herrenschmidt
2003-04-26 22:08 ` Brice Figureau
2003-04-26 22:13 ` Benjamin Herrenschmidt
2003-04-26 22:32 ` Brice Figureau
2003-04-26 22:40 ` Benjamin Herrenschmidt
2003-04-26 22:51 ` Brice Figureau
2003-04-26 23:14 ` Benjamin Herrenschmidt
2003-04-27 12:39 ` Brice Figureau
2003-04-25 20:12 ` Remco Treffkorn
2003-04-25 22:55 ` Brice Figureau
2003-04-26 7:08 ` Mich Lanners
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=1051353230.10342.31.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=brice@tincell.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).