public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joseph Fannin <jfannin@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Sean Neakums <sneakums@zork.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Fw: Re: 2.6.11-rc2-mm2
Date: Tue, 01 Feb 2005 10:18:33 +1100	[thread overview]
Message-ID: <1107213513.5963.26.camel@gaston> (raw)
In-Reply-To: <20050131112106.GA3494@samarkand.rivenstone.net>

On Mon, 2005-01-31 at 06:21 -0500, Joseph Fannin wrote:

>     I'm getting a blank screen with radeonfb on two boxes here as
> well. One is a beige g3, the other is i386; both have PCI Radeon 7000s
> with radeonfb non-modular. 
> 
>     On the PC I could see the earliest kernel messages in VGA text
> mode before radeonfb took over and the screen went blank -- no
> penguin, and the logo is enabled.  Booting with radeonfb:off seemed to
> work except for the module problem in -rc2-mm2:
> 
>     On the ppc box I tried both -rc2-mm1 and -rc2-mm2.  Both hung and
> then rebooted after 3 minutes, so it seems to be panicing somewhere.
> I backed the massive-radeonfb patch out of -mm2 and radeonfb worked,
> so I got as far as the module thing again.
> 
>     So yeah, it's possible that there's something in -mm1 that panics
> my ppc, and radeonfb is just making a blank screen, but it seems more
> likely that radeonfb is panicing.  I tried to get netconsole working
> on both machines, but it didn't work out for unrelated reasons.
> 
>     Hopefully I'll have more time to poke at this tomorrow; maybe this
> is helpful somehow.

Hrm... indeed, there seem to be a problem, though I can't tell for sure
what's up now, it just works on all the configs I had a chance to test
on. Can you try to boot your G3 with serial console so you can see the
panic message if any ?

Ben.



  reply	other threads:[~2005-01-31 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050129163117.1626d404.akpm@osdl.org>
2005-01-31  7:11 ` Fw: Re: 2.6.11-rc2-mm2 Benjamin Herrenschmidt
2005-01-31  7:22   ` Andrew Morton
2005-01-31  9:23   ` Sean Neakums
2005-01-31 23:16     ` Benjamin Herrenschmidt
2005-01-31 11:21   ` Joseph Fannin
2005-01-31 23:18     ` Benjamin Herrenschmidt [this message]
2005-02-02  3:42       ` Joseph Fannin
2005-02-02  3:45         ` Benjamin Herrenschmidt
     [not found] <20050130130131.030c1ef1.akpm@osdl.org>
     [not found] ` <200501301831.25095.dtor_core@ameritech.net>
2005-01-31 19:08   ` Paul Blazejowski
2005-01-31 19:27     ` Vojtech Pavlik
2005-02-04 14:57     ` Vojtech Pavlik

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=1107213513.5963.26.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=jfannin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sneakums@zork.net \
    /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