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: 25 Apr 2003 19:43:12 +0200 [thread overview]
Message-ID: <1051292592.2104.9.camel@gaston> (raw)
In-Reply-To: <1051284468.2467.179.camel@localhost.localdomain>
> By unstable I mean that the computer completely freeze during boot time,
> around the time rc.sysinit is launched. Unfortunately I'm rather new to
> linux kernel so I don't know how to provide more information on the
> crash (maybe should I configure the kernel with xmon ?).
> In a divide&conquer approach I found that the part of rc.sysinit which
> 'uploads' the console font to the font layer was triggering the crash.
Can you try 2 things and let me know if one of them helps ?
- Compile without CPUFREQ support
- Use video=radeon:noaccel on the command line to disable acceleration
on console
> I then re-installed from scratch everything (because I thought there
> could have been a fs corruption somewhere which had corrupted the
> fonts), but no chance it crashed again.
>
> I then commented-out this part of rc.sysinit and then I could boot up to
> the login prompt.
>
> But the kernel was still unstable, and still froze at completely random
> time (mounting a cdrom, vi'ing some text files, rsyncing a kernel,
> compiling the kernel).
>
> I decided to have a look to the latest devel kernel (namely
> 2.4.21-pre7-ben0 and 2.4.21-rc1-ben0) but no chance again, when booted
> with video=radeonfb (or with nothing) they're oopsing during the boot (I
> can provide more information if needed). With video=ofonly, everything
> went smooth.
>
> As I wasn't sure the crash came from my compiled kernel, I also tried
> pre-built kernel from penguinppc.org (the following dmesg output has
> been taken from this kernel). This kernel was relatively stable with my
> modified rc.sysinit, but failed with the original rc.sysinit.
>
> So, what should I do to have a stable kernel with radeonfb ?
That's interesting. I need to investigate...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-25 17:43 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 [this message]
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
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=1051292592.2104.9.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).