Messages in this thread | | | Date | Mon, 14 Feb 2005 22:06:01 -0800 | From | Matt Mackall <> | Subject | Re: Radeon FB troubles with recent kernels |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |