[RFC] debug kernel for Lucid/Maverick/Mainline?

[Andy Whitcroft]

On Wed, Jun 02, 2010 at 05:17:11PM -0500, Manoj Iyer wrote:

> I propose we build a kernel with certain XX_DEBUG turned on for Lucid, 
> Maverick and Mainline. The benefits of having it are:
> 
> * we can point people at this debug kernel give them instructions on how 
> to control debug prints though sysfs and get more data that might help 
> debug problems. Certainly in the case where debugging kernel across 
> suspend/resume etc.

Which debug options do you have in mind?

> * We could use this kernel in our alpha/beta compatibility testing ISO, we 
> could collect more debug information for each test. For example turn on 
> debug before suspend and turn off after resume, if suspend/resume had 
> issues, took long times etc we might be able to gather bit more 
> information as to why.

One issue we introduce here is that by turning on the DEBUG_XX options
which we are saying are not suitable for production use we change the
kernel we are testing away from that which we want to work, we are not
testing the same beast any more which effectivly lowers the quality of
the results as a test of the original kernel.

> * I think mainline kernel builds should have config debug turned on by 
> default, since this is "try & test this" kernel, what is the harm in 
> having a slightly bloated kernel?

Possibly, again which options are you itching to have.

-apw