Re: Libata, bug 5700.

[Pekka Enberg]

On 1/28/06, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
> Maybe think about if there's more information you can supply to make it
> easier for the developers to diagnose (this is the most common reason
> bugs aren't looked at, just plain not enough info to even begin thinking
> about it)... or look at the code yourself, or try to find where this
> behavior started, or .. or ...

The simplest thing you can do on your own is to see if you can find an
older kernel that doesn't have that problem. And if you do find a
working kernel, you can use git bisect to find out the exact changeset
that broke it. See the following URL for details:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt

                               Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/