Re: hung bootup with "drm/radeon/kms: move radeon KMS on/off switch out of staging."

[Jesse Barnes <jbarnes@virtuousgeek.org>]

On Thu, 4 Feb 2010 20:32:32 +0100
Ingo Molnar <mingo@elte.hu> wrote:
> Nobody has reacted to my related boot hang bugreport yet - and it's
> detailed and fully reproducible (so i can test any proposed fixes as
> well in short order). I.e. my limited testing has triggered two
> separate bugs in the same driver - and this will show up in -rc7.
> 
> It might be all OK and no-one else will see trouble. Or past patterns
> might repeat themselves and i might simply be an early bird for
> trouble to come.
> 
> My (oft repeated) point is that adding new sub-features to existing
> drivers is not what we do in late -rc's: there's simply not enough
> time to shake out bugs/regressions in them.
> 
> We introduce new functionality to existing drivers in the merge
> window - in the two weeks following a stable kernel's release.

This is the .config issue right?  It doesn't sound like the bug is new,
you're just seeing now it because of the way you run tests.  It
shouldn't affect any more or fewer users than it did before, and
reverting the "move radeon KMS out of staging" won't fix the bug at all
or prevent anyone from seeing it.  People using KMS will still use KMS
and people without it won't, because no one actually uses allyes
configs, and the option defaults to N anyway.

> In late -rc's we only try to fix regressions. Sometimes we make
> exceptions for pragmatic reasons, but then we are straightforward
> about those reasons and try to warn users about our zeal to help them
> with cool, new, not-to-be-missed GPU functionality ;-)

Agree, I just don't think this is a regression or an exception.

-- 
Jesse Barnes, Intel Open Source Technology Center