Steven P. Ulrick wrote, at 05/06/2008 03:13 PM +9:00:
On Mon, 05 May 2008 19:06:02 -0400
Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:
Steven P. Ulrick writes:
Installing: kernel
######################### [1/3] nash received SIGSEGV! Backtrace
(11): /sbin/nash[0x805314a]
[0x110440]
/lib/libglib-2.0.so.0[0x314ce13]
/usr/lib/libbdevid.so.6.0.19(bdevid_module_unload_all+0x31)[0x8c3e37]
/usr/lib/libbdevid.so.6.0.19(bdevid_destroy+0x2d)[0x8c357c]
/usr/lib/libnash.so.6.0.19[0x967174]
/usr/lib/libnash.so.6.0.19(nash_vitals_destroy_probes+0x3f)[0x9677ec]
/usr/lib/libnash.so.6.0.19(_nashFreeContext+0x1c)[0x957fc6]
/sbin/nash[0x80536e4]
/lib/libc.so.6(__libc_start_main+0xe0)[0xafe390]
/sbin/nash[0x804ae61]
/sbin/nash[0x804ae61]
error: %post(kernel-2.6.24.5-85.fc8.i686) scriptlet failed,
signal 2
Run memtest86, and check for bad RAM.
Hello Sam
I ran memtest86 for about 45 minutes and there were no errors. I'll
try running it again this evening for a much longer period of time.
If memtest comes up clean, you probably have some core system
libraries corrupted in some way. Try running rpm -V glibc
glibc-common nash
Hello Sam,
I re-ran Memtest86 for 3 hours and 26 minutes and it reported no
errors. So I ran "rpm -V glibc glibc-common nash" and the results were
as follows:
[root@afolkey2 ~]# rpm -V glibc glibc-common nash
[root@afolkey2 ~]#
Please see
https://bugzilla.redhat.com/show_bug.cgi?id=443332
and check if your problem is reproducible. If so, please file a bug
against nash.
Regards,
Mamoru
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
