-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-01-03 at 20:35 -0600, M Harris wrote:
If the module comes with the kernel supplied by suse, then it is an integral part of the kernel supplied by suse, and the kernel is this the culprit. It is not a third party module installed by the user. I think you might be missing my point | question. Ok, we report the bug to
On Thursday 03 January 2008 20:23, Carlos E. R. wrote: the suse kernel people (third party, since they don't own the kernel) and they fix their module, or the module owner fixes the module), and then the "suse kernel" is fixed. OK, don't the suse kernel people want to know which module is failing before a bug report is submitted as a "kernel" problem?
If you have the expertise, do so. If not, simply report the Oops or panic to suse people and they can help the reporter get the data needed, and then perhaps they can solve it or report upstream. As to suse being third party... not completely. They have a good number of kernel developer/contributors on their staff. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHgB24tTMYHG2NR9URAmKUAKCVA02JqZW6ldlUO5PTEodh6CdZywCeLPJE gWDjK2HKR2rS8O45DG1G2GA= =/sN6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org