Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging."

[Dave Airlie <airlied@gmail.com>]

>>
>> 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.
>

Okay I've booted this on the rv370 + rv380 machines I have, I've no old Athlon's
though so I'm trying to get RHTS to give me access to one or two internally,

Another question, that came to mind, what is there any monitors plugged in?
or a KVM or something? if yes can you try without and if no can you try with?

Also can you add CONFIG_FRAMEBUFFER_CONSOLE as well since I
don't think we test often without it.

Dave.