From: "young dave" <hidave.darkstar@gmail.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Fwd: PROBLEM: 2.6.20-1 not working on ibook g4 (BUG/Oops)
Date: Tue, 13 Mar 2007 01:54:53 +0000 [thread overview]
Message-ID: <a8e1da0703121854h161ddf2fib0235cd392b5977b@mail.gmail.com> (raw)
In-Reply-To: <a8e1da0703121849y202b7e3clb39afca72731762d@mail.gmail.com>
---------- Forwarded message ----------
Hi,
I have tested on my mac mini g4.
The 2.6.21-rc2 will cause oops like the above post.
And for the new 2.6.21-rc3-git7 , the kernel load ok, penguin pixmap
appears, but then it stopped, there's no error messages also.
Regards
dave
2007/3/7, Benjamin Herrenschmidt <benh@kernel.crashing.org>:
> On Wed, 2007-03-07 at 17:53 +1300, Paul Collins wrote:
> > David Woodhouse <dwmw2@infradead.org> writes:
> >
> > > On Tue, 2007-03-06 at 14:53 +1300, Paul Collins wrote:
> > >> In case it's of interest, 2.6.20 has been running fine on my
> > >> PowerBook5,4.
> > >
> > > How much memory? What if you boot with mem=512M or mem=256M?
> >
> > 1GB. Also works fine when booted with those options.
>
> Can you try 2.6.21-rc3 ? We just fixed a nasty bug causing memory
> corruption.
>
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2007-03-13 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703051414.15802.frafore@tiscali.it>
2007-03-06 1:18 ` PROBLEM: 2.6.20-1 not working on ibook g4 (BUG/Oops) David Woodhouse
2007-03-06 1:53 ` Paul Collins
2007-03-06 10:35 ` David Woodhouse
2007-03-07 4:53 ` Paul Collins
2007-03-07 11:04 ` Benjamin Herrenschmidt
[not found] ` <a8e1da0703121849y202b7e3clb39afca72731762d@mail.gmail.com>
2007-03-13 1:54 ` young dave [this message]
[not found] ` <1173769125.24454.58.camel@localhost.localdomain>
2007-03-15 1:27 ` young dave
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=a8e1da0703121854h161ddf2fib0235cd392b5977b@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).