Re: kernel BUG at lib/kernel_lock.c:83! - 2.6.19-1.2895.fc6

On Tue January 30 2007 02:16, Albert Graham wrote:
Alan wrote:
But only Nvidia have the source code to both parts so they can actually
debug it. Nobody else can. It's simply the way things work currently.

*Exactly! yet another useless comment.*

Guys, Nvidia have closed source drivers which will NEVER be open

not until market dictates never say never :-)

sourced, they're a milti-billions $ company, so you can shout all you
like, things are never going to change, however, at least they actively
maintain (with good will) closed source drivers which is a lot more than
most other hardware companies do.

I couldn't give a nats chuff what nvidia do with their milty-billions $ they
certainly don't spend it on linux driver devel go look at tests done at
phoronix.net compare what these cards can do in M$ to Linux.

In my post I was hoping you guys would "see past" the fact that the
kernel was tainted and just look at the "actual message", maybe someone
else was seeing the same thing?, but instead every bloody one of you
jumped on the NVidia bandwagon , well whoppee! you're all great! for
pointing this out, well done.

One thing to say here, You don't seem to get that a tainted kernel adds a
massive layer of unpredictability to all but nvidia. (not sure they know) :-)

I had no reason to create a bugzilla report because, firstly I could not
reproduce it and actually don't know what caused it, however the link I
provided in my was interested because it appears to be the same bug
which "should" have been fixed 3 years ago. Also, I wanted to create a
reference point in time and content so if someone at a later date

I followed the link u posted and I have to say your bug has nothing to do with
what the original poster was reporting at lkml. Just coincidence you both
hung out at the same place. :-) The poster was also given a successfull
patch later problem solved.

started seeing this problem some of the info I provided would be somehow
useful however that penny never dropped for the tainted among us. - I
assume you goes use google right?

Like I said in my second post, if you can't be constructive why bother
telling me how to suck eggs!

"constructive comment " if I'm getting upto 5 lock-ups a day I'm going to be
banging hell out of someones bugzilla until answers start commin out. tainted
kernels are completely useless around here along with that phony bug report
you posted but you knew that anyway. :-)


...dex
Thanks For Comming ...








___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Houston, we have a problem: big file copying, USB, external disks
    ... The bug you link to ... It is also unclear how the users determine that a given transfer rate is ... kernel) that works better it should be relatively easy to make some ... Leann Ogasawara actually already told people to report in separate ...
    (Linux-Kernel)
  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... Noone knows how many thousand bug reports have never reached lkml ... filing or get back to terminate the report. ... But I would like kernel people to become less egocentric ... Send _one_ email to lkml and you'll get forever spam to this address. ...
    (Linux-Kernel)
  • Backport hr-tick fix into .25/.26
    ... Since the introduction of 2.6.25-rc1 kernel I've been experiencing screen blanking during boot up. ... I've reported this issue before, and Rafael Wysocki opened a bug report. ... I know of one other person that ran into what seems to be the same bug. ... I did a git bisect and found both the commit that introduced the bug and also the one that fixed it. ...
    (Linux-Kernel)
  • Bug: Asus CUR-DLS and 2.6
    ... I'm writing to report and interesting occurance that I fully believe is a bug ... In March I purchased a used Asus CUR-DLS motherboard with two socket 370 PIII ... I believe my initial kernel was ... Well, I have more free time now, and I've narrowed down the bug I think. ...
    (Linux-Kernel)
  • Re: [patch] Real-Time Preemption, -RT-2.6.11-rc3-V0.7.38-01
    ... Great work on the -RT kernel! ... Here's a status report from my Athlon box ... Latencytest (measured with RTC instead of latencytest LKM, ... BUG: sleeping function called from invalid context ksoftirqd/0at ...
    (Linux-Kernel)