Re: Dedicated kernel bug database

[Stephen Wille Padnos <stephen.willepadnos@verizon.net>]

John Bradford wrote:

> [snip]
>
>Interesting - so the first stage in reporting a bug would be to select
>the latest 2.4 and 2.5 kernels that you've noticed it in, and get a
>list of known bugs fixed in those versions.  Also, if you'd selected
>the maintainer, (from an automatically generated list from the
>MAINTAINERS file), it could just search *their* changes in the changelog.
>
It's often difficult to pick a maintainer for a bug - it may not be the 
fault of a single subsystem.  As an example, I recently had a problem 
getting USB and network to function (on kernels 2.5.5x).  I noticed that 
toggling Local APIC would also toggle which of the two devices worked. 
 Disabling ACPI allows both deviecs to function regardless of local APIC.

So, where is the problem?
1) Network driver?  It doesn't work with ACPI and both Local APIC and 
IO-APIC.
2) USB driver?  It doesn't work with ACPI and no UP APIC.
3) APIC?  Causes weird problems with various drivers when ACPI is turned on.
4) ACPI?  Causes weird problems with various drivers when APIC is toggled.

(this exact bug was in Bugzilla, though I hadn't checked there before 
mailing lkml ;)

I'm not exactly a neophyte to the kernel, and I would have to do a lot 
more digging to find the right maintainer to send this to.  Also, the 
person(s) to whom the bug is reported will depend on how much debugging 
work I do, and in what order I do it.

I'm not trying to discourage you - just raising a potential gotcha.

- Steve