Re: Giving developers clue how many testers verified certain kernel version

Adrian Bunk
2005-07-23T03:56:50Z

On Fri, Jul 22, 2005 at 09:15:14PM -0500, Alejandro Bonilla wrote:
> Lee Revell wrote:
>
> >On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
> >
> >>I will get flames for this, but my laptop boots faster and sometimes
> >>responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
> >>for me. IBM T42.
> >
> >Sorry dude, but there's just no way that any automated process can catch
> >these.
> >
> I'm not looking for an automated process for this. But for all in
> general, when moving from 2.6.11 to 2.6.12 or from any version to
> another. (At least in the same kernel branch)
>...

You send:
- a problem description X
- tell that the last working kernel was Y
- tell that it is broken in kernel Z

The probability of any kernel developer being interested in your problem
increases:
- the better the description X is
- the nearer versions Y and Z are together
- the more recent version Y is

Ideally, you are able to say that patch A in the latest -mm kernel
broke it.

It's perfectly OK to send a description X that says:
- with version Y and the following workload B, everything is working
perfectly
- with version Z and the same workload B, XMMS is stuttering

If any kernel developer is interested in your bug report, he will tell
you which data might be interesting for debugging the problem.

The problem is that debugging a problem often requires knowledge about
possible causes and changes between versions Y and Z in this area. Even
a kernel developer who perfectly knows one part of the kernel might not
be able to debug a problem in a completely different area of the kernel.

> .Alejandro

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed