Could it also mean that there is something wrong with the gs package? On 10/13/06, Feizhou <feizhou@xxxxxxxxxxxx> wrote:
Devraj Mukherjee wrote: > Hi Everyone, > > I found these in my log files. I am running the latest version of gs, > as distributed by CentOS > > Oct 11 18:03:27 charlie kernel: gs[9960]: segfault at 0000000000000000 > rip 0000003f0cd2063e rsp 0000007fbfffe090 error 6 > Oct 12 14:40:58 charlie sshd(pam_unix)[12919]: session opened for user > root by root(uid=0) > Oct 13 15:16:11 charlie kernel: gs[16302]: segfault at > 0000000000000000 rip 0000003f0cd2063e rsp 0000007fbfffe090 error 6 > Oct 13 18:10:58 charlie sshd(pam_unix)[17189]: session opened for user > root by root(uid=0) Any recent changes? segfaults are usually due to bad RAM but it could be something else. Try shutting down, cleaning the memory slots and reseating the RAM. > > Kernel details > > Linux charlie.networketernity.com 2.6.9-42.0.2.plus.c4smp #1 SMP Sat > Aug 26 12:53:43 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux > > Please let me know if I should be panicing about this. > gs = ghostscript. Do you do any printing with non-postscript capable printers or any translation of postscript to other formats? _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
-- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles) _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
