public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, adaplas@pol.net
Subject: Re: Radeon FB troubles with recent kernels
Date: Mon, 14 Feb 2005 22:06:01 -0800	[thread overview]
Message-ID: <20050215060601.GS15058@waste.org> (raw)
In-Reply-To: <1108429654.12739.60.camel@gaston>

On Tue, Feb 15, 2005 at 12:07:34PM +1100, Benjamin Herrenschmidt wrote:
> 
> > Nope. No printk outputs from _set_par, _write_mode, or _engine_init.
> > 
> > Just to clarify: the gdm stop is done from tty1 while gdm is running
> > on tty7, so I don't think it's a matter of mode switch logic.
> 
> Ohhh, this is a known bug then. When you kill X while it's not on the
> front VT, it will crap on the engine. This has always been the case, I
> suppose that if you didn't notice it before, it 's because you are
> lucky :)

I think I noticed it in the course of testing recent fbdev and console
code changes..

> > Also, I'm still seeing the LCD blooming + hang on starting radeonfb.
> > It's something like 1 in 10 boots rather than every boot now though.
> 
> Does it actually hangs ? That's weird... looks like a chip crash. Can
> you check if that happens with radeonfb.default_dynclk=-1 on the kernel
> command line ?

Hard to say, it's rather a pain to reproduce. I can add that to my
default boot and if it shows up again, I'll let you know.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2005-02-15  6:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 20:39 Radeon FB troubles with recent kernels Matt Mackall
2005-02-14 22:38 ` Benjamin Herrenschmidt
2005-02-14 23:08   ` Benjamin Herrenschmidt
2005-02-15  0:02     ` Antonino A. Daplas
2005-02-15  0:20     ` Matt Mackall
2005-02-15  1:07       ` Benjamin Herrenschmidt
2005-02-15  6:06         ` Matt Mackall [this message]
     [not found] <3xVku-kH-15@gated-at.bofh.it>
2005-02-15  3:14 ` Vincent C Jones
2005-02-15 12:46   ` Benjamin Herrenschmidt
2005-02-15 12:50   ` Benjamin Herrenschmidt
     [not found] <3y1SR-5K6-1@gated-at.bofh.it>
     [not found] ` <3yatk-4mE-29@gated-at.bofh.it>
2005-02-15 15:07   ` Vincent C Jones
2005-02-15 22:02     ` Benjamin Herrenschmidt
2005-02-16  1:53       ` Vincent C Jones
2005-02-16  2:41         ` Benjamin Herrenschmidt
2005-02-16 14:39           ` Vincent C Jones
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16 10:08 tvrtko.ursulin

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=20050215060601.GS15058@waste.org \
    --to=mpm@selenic.com \
    --cc=adaplas@pol.net \
    --cc=benh@kernel.crashing.org \
    --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