From: Dave A. <ai...@gm...> - 2010-02-04 21:14:44
|
On Fri, Feb 5, 2010 at 6:46 AM, Ingo Molnar <mi...@el...> wrote: > > * Dave Airlie <ai...@gm...> wrote: > >> On Wed, Feb 3, 2010 at 1:44 AM, Ingo Molnar <mi...@el...> wrote: >> > >> > * Dave Airlie <ai...@li...> wrote: >> > >> >> > It's the moving of radeom KMS out of staging after -rc6 that causes it, >> >> > because it brought it into the scope of my testing: >> >> > >> >> > ?f71d018: drm/radeon/kms: move radeon KMS on/off switch out of staging. >> >> > >> >> > So at least on this box it's clearly not ready for mainline enablement >> >> > yet. I've attached the revert patch further below. >> >> >> >> Its not enabled by default so reverting this doesn't make much sense. >> > >> > I boot allyesconfig kernels regularly, which testing method works fine >> > with another 2000+ upstream drivers. (including the dozens of drivers >> > which match to active hardware components on that box) >> >> Okay this was something I wondered about, since these are *not* >> allyesconfig .configs, I've generated some and CONFIG_FB_RADEON is always >> on here, and you seem to not have that enabled (not that enabling it is a >> good idea it is in fact a really bad idea). > > These were random configs - the size doesnt match an allyesconfig, those are > way bigger. My above comment related to the first crash, and to my argument > that all other drivers are fine during bootup - and there's a lot of them. > >> So do you have something you are running after allyesconfig to fix things? >> or have you just got a config that is close enough to allyesconfig. >> >> I'm building kernels with your .config now and boot testing them on the >> full range of hardware I have/ > > Thanks. Is there something i can enable to get a better log for you to find > out where (and why) it's hanging? It's still early during bootup so the box > is not particularly debuggable - so i'm not sure i can get a task list dump, > etc., unfortunately. > Do you have NMI watchdog enabled? (does it work that early) a backtrace of where it hangs would be nice, Also a dmesg from booting with drm.debug=15 might help narrow it down also. Dave. > Ingo > |