Mailinglist Archive: opensuse (2348 mails)

< Previous Next >
Re: [opensuse] Novell Bugzilla - At it Again - Bugs Apparently Dismissed Without Sufficient Investigation
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 04 Apr 2008 11:20:22 -0500
  • Message-id: <47F65546.6000101@xxxxxxxxxxxxxxxxxx>
Dave Howorth wrote:
David C. Rankin wrote:
Yes, I think there is a misunderstanding. The problem *IS NOT* the
nvidia kernel module it self, it works fine. What I suspect the problem
*IS*, is the way the system handles the memory mapping, etc. *after* the
module is loaded. Forget that the module involved is nvidia. It could
just as well be called "The bunch of 1's and 0's, this many of them,
that goes here when loaded" for purposes of this discussion.

Well, if you can reproduce the problem with another module to which you
have the source then I'm sure they will investigate. You could always
take a small module and add an array containing whatever pattern of 1s
and 0s you think is important :)

What I _am_ saying is that on my Tyan board with its chipset/bios
combination, and multicore AMD processors, the software (another
module/kernel/pick you favorite part), is in fatal conflict with the
driver and that for debugging purposes, there needs to be sufficient
investigation to either rule in or rule out the problem.

Agreed. The issue is who should do that investigation. You seem to
believe that it should be Novell/kernel developers. I - and others
AFAICT - believe it should be nvidia. And they're unlikely to do it
unless you report it to them.

Cheers, Dave

Good point. However, in the past with the ATI drivers, the way it worked was that I would report it to Novell and then "we" me working with the Novell developers would get the ATI people involved and then work the issue with all interested parties in the loop until it was either (1) fully understood; or (2) fixed. (You know, the logical way it should work). See:

https://bugzilla.novell.com/show_bug.cgi?id=338930
https://bugzilla.novell.com/show_bug.cgi?id=338947
https://bugzilla.novell.com/show_bug.cgi?id=340459
https://bugzilla.novell.com/show_bug.cgi?id=344135

However, in this instance, the Novell response was "don't bother us" with your issue, go away? WTF? That is the wrong answer even if it isn't a Novell issue.

When Novell leads people to the nvidia driver, designs and offers its own "1-click" install for the driver through YAST, and promotes the fact that the driver install is a simple matter with its distro, then Novell certainly has a vested interest in at least being interested or part of the solution in cases where it doesn't work. Especially if it has the potential to affect a category of bios/chipset combinations.

I have found it makes far more sense to have Novell in the loop when addressing a problem affecting openSuSE that just beating on vendors doors saying this doesn't work with SuSE. In either regard, I would hope to see the developers take more of an interest in seeing problems fixed than simply acknowledging the issue and saying "not my problem, go away" and certainly not to summarily dismiss a potential software issue by saying "the software says it isn't broken - so it isn't - now go away."

We'll see what kind of response we get from Nvidia.

--
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >