[elrepo] Announcement: EL5 updated kmod-nvidia release [version 260.19.12]

Akemi Yagi amyagi at gmail.com
Sat Oct 16 18:35:12 EDT 2010


On Sat, Oct 16, 2010 at 2:51 PM, Phil Perry <phil at elrepo.org> wrote:
> On 16/10/10 22:03, Akemi Yagi wrote:

>> The installation went fine and it seemed as if everything was a-ok. But ...
>>
>> You probably remember that I encountered a problem with an earlier
>> version of kmod-nvidia in testing (2010-09-10).  The problem was that
>> starting a kvm guest caused segfault.
>
> That version was our first internal build of the 260.x beta release.
>
>> I have the same issue with the current test nvidia driver:
>>
>> kernel: qemu-kvm[4524]: segfault at 000000394a40da11 rip
>> 00002b6c82c8883f rsp 0000000043e4be80 error 7
>>
>> When I went back to 256.53-1, all was fine again. I really don't know
>> how to debug this problem, so decided to post to the mailing lists.
>> Anyone else seeing this?
>
> So this looks to be an issue specific to the 260.x series driver.

Yes, that seems to be the case.

> To start with it would be nice to confirm that it's not an issue that we
> have introduced - i.e, it's not a packaging issue. To that end, could
> you test an install with the nvidia installer just to check you get the
> same results. Assuming you do then I guess the next step would be to
> file a bug report with nvidia.

Will do the test but sometime next week. I want to do it on my laptop
running RHEL5 which is 17 miles away now.

> This thread has useful information on how to file a bug report with nvidia:
>
> http://www.nvnews.net/vbulletin/showthread.php?t=46678
>
> We don't currently package the nvidia bug reporting script
> nvidia-bug-report.sh - perhaps we should? Although I guess nvidia would
> probably prefer bug reports from native unpackaged installs.

They always request the output from that script. Let's use theirs.

Akemi



More information about the elrepo mailing list