kernel error in SL 6.9

Hi I am getting kernel errors in several SL 6 machines after yum update: kernel: gam_server[2941]: segfault at 58f5f7aa ip 0040a2b9 sp 7ffe56238e80 error 4 in gam_server[40+16000] What is a gam_server? Should I be worried by this? Cheers Bill Maidment

Re: Licensing and EULA

On Tue, Apr 18, 2017 at 6:58 AM, Cankaya, Yilmaz wrote: > Dear All, > > > > We are as Airbus DS CyberSecurity running projects with the aim of > introducing some cyber security products mainly for defence and ICS > industry. > > > > We want to use Linux OS in our

Re: CUDA Setup Failing

Eric my last experiments were with it on version 6.so.. check if you have the original driver installed correctly not the RPM version of it. On Apr 18, 2017 19:30, "Lofgren, Eric" wrote: Hey all, I’m relatively new to Linux generally and SL in particular. I’m running SL7,

Re: [SCIENTIFIC-LINUX-USERS] SL5 initrd.img

Thanks for the pointer. I've started down that path after writing the email. It seems buildinstall calls mk-images, etc, etc. Looks like I just need to get the kernel-lt rpms in place and possibly modify mk-images to look for it. It's been a while since I've had to dig into this sort of

SL5 initrd.img

Is there a resource/information/script on generating the initrd.img used in the SL5 installation media? I'm trying to inject kernel-lt from ELrepo in place of the usual one. Replacing vmlinuz is easy, but I'm not sure where to start getting the initrd updated with the appropriate kernel

Re: Licensing and EULA

Hi Yilmaz, Thanks for the inquiry. Questions like these should be directed to Fermilab's Office of Partnerships and Technology Transfer. The email address is o...@fnal.gov. On 04/18/2017 05:58 AM, Cankaya, Yilmaz wrote: Dear All, We are as Airbus DS CyberSecurity running projects with

Re: Scientific Linux 6.9 now Released for i386/x86_64

On Mon, 17 Apr 2017, Pat Riehecky wrote: Scientific Linux 6.9 i386/x86_64 Apr 17, 2017 SL 6x users: Please run yum clean expire-cache That did not work for me, but yum clean metadata did. Sorry, I have lost the original error message, but it was to the effect that the