Ingo Molnar once said (http://lwn.net/Articles/251784):
|  We must not ignore people who tell us that "there is something wrong
| going on here", just because they are unable to analyze it themselves.
| Very often where we end up saying "we don't know what's going on here"
| it's likely _our_ fault. We also must not hide behind "please do these
| 10 easy steps and 2 kernel recompiles and 10 reboots, only takes half
| a day, and come back to us once you have the detailed debug data"
| requests.

  To help address this, Alan Rocker and I wrote an article about how
to do a good report of a kernel crash or hang, based on a course
we gave for a well-known board supplier, on diagnosing and reporting
bugs in their Linux drivers.

  We're nervous about the last few steps, submitting bugs to the 
kernel community, so we'd like people who care about the quality 
of bug reports to review us. Viciously. With lots of thrown
brickbats. We'd really prefer to have it right before publishing (;-)) 

  Everyone interested, drop me a line.

--dave (currently contracting at Sun in Toronto) c-b
-- 
David Collier-Brown            | Always do right. This will gratify
Sun Microsystems, Toronto      | some people and astonish the rest
davecb@sun.com                 |                      -- Mark Twain
(905) 943-1983, cell: (647) 833-9377, (800) 555-9786 x56583
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/