[elrepo] kmod-atl1e update

Sun Oct 31 09:12:30 EDT 2010

Hi

I'm not sure whether the problem is my end or yours - but I have checked all
my spam folders without success.
I note that there seems to be a new kmod-atl1e being offered by yum from
elrepo - but I haven't received a notice of this update on this mailing
list. Usually we get notices before updates appear.

Richard.

On Mon, Oct 18, 2010 at 12:00 AM, <elrepo-request at lists.elrepo.org> wrote:

> Send elrepo mailing list submissions to
>        elrepo at lists.elrepo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.elrepo.org/mailman/listinfo/elrepo
> or, via email, send a message with subject or body 'help' to
>        elrepo-request at lists.elrepo.org
>
> You can reach the person managing the list at
>        elrepo-owner at lists.elrepo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of elrepo digest..."
>
>
> Today's Topics:
>
>   1. Re: Announcement: EL5 updated kmod-nvidia release [version
>      260.19.12] (Akemi Yagi)
>   2. Re: Announcement: EL5 updated kmod-nvidia release [version
>      260.19.12] (Phil Perry)
>   3. Re: Announcement: EL5 updated kmod-nvidia release [version
>      260.19.12] (Akemi Yagi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 16 Oct 2010 14:03:25 -0700
> From: Akemi Yagi <toracat at elrepo.org>
> Subject: Re: [elrepo] Announcement: EL5 updated kmod-nvidia release
>        [version        260.19.12]
> To: EL Repo General Mailing List <elrepo at lists.elrepo.org>,     EL Repo
>        Developer Mailing List <elrepo-devel at lists.elrepo.org>
> Message-ID:
>        <AANLkTi=sPRUrjGykshA0uK0jZz_gODoQMD3zgjE+s=Pr at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sat, Oct 16, 2010 at 2:19 AM, Phil Perry <phil at elrepo.org> wrote:
> > Announcing the release of updated kmod-nvidia packages in the EL5
> > elrepo-testing repository:
> >
> > http://elrepo.org/tiki/kmod-nvidia
> >
> > x86
> > kmod-nvidia-260.19.12-1.el5.elrepo.i686.rpm
> > kmod-nvidia-PAE-260.19.12-1.el5.elrepo.i686.rpm
> > nvidia-x11-drv-260.19.12-1.el5.elrepo.i386.rpm
> >
> > x86-64
> > kmod-nvidia-260.19.12-1.el5.elrepo.x86_64.rpm
> > nvidia-x11-drv-260.19.12-1.el5.elrepo.x86_64.rpm
> > nvidia-x11-drv-32bit-260.19.12-1.el5.elrepo.x86_64.rpm
>
> Phil,
>
> 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.
>
> 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?
>
> Akemi
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 16 Oct 2010 22:51:01 +0100
> From: Phil Perry <phil at elrepo.org>
> Subject: Re: [elrepo] Announcement: EL5 updated kmod-nvidia release
>        [version 260.19.12]
> To: EL Repo General Mailing List <elrepo at lists.elrepo.org>
> Message-ID: <4CBA1E45.5060405 at elrepo.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 16/10/10 22:03, Akemi Yagi wrote:
> >
> > Phil,
> >
> > 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.
>
> 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.
>
> 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.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 16 Oct 2010 15:35:12 -0700
> From: Akemi Yagi <amyagi at gmail.com>
> Subject: Re: [elrepo] Announcement: EL5 updated kmod-nvidia release
>        [version        260.19.12]
> To: EL Repo General Mailing List <elrepo at lists.elrepo.org>,     EL Repo
>        Developer Mailing List <elrepo-devel at lists.elrepo.org>
> Message-ID:
>        <AANLkTimWWrj4yAoT3QQV5MVfW9-i-=e1M73koj5uj8Zk at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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
>
>
> ------------------------------
>
> _______________________________________________
> elrepo mailing list
> elrepo at lists.elrepo.org
> http://lists.elrepo.org/mailman/listinfo/elrepo
>
>
> End of elrepo Digest, Vol 16, Issue 7
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20101031/eadafbc0/attachment.html>