Bug 243015 - Folding@Home program seg faults
Summary: Folding@Home program seg faults
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-06 21:56 UTC by Darwin H. Webb
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-22 20:50:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Darwin H. Webb 2007-06-06 21:56:53 UTC
Description of problem:
Can not determine why Folding@Home program seg faults on these kernels
sig 11.
everything is the same from fc7 kernel 3194

Seperate user for fah
fah dir is on vg-lv of FC6 system and is monuted under the f7 fah mountpoint
i.g. mount /dev/mapper/vg21-lv06home /home/fahuser/fahmnt
at famnt cd down
cd fah

the execmem and execstk selinux booleans are on by default in f7 (shock)
in fc6 the are set and reminder setroubleshoot pops up if they are not.

With the newer f8 kernels no setroubleshoot alert, no audit messages
no messages
pam shows fahprogm abnorm abend seg 11

Version-Release number of selected component (if applicable):
f7 with a few updates (using f7 kernel 3194 or (f8 kernel )

How reproducible:

Steps to Reproduce:
1. Install f8 kernel and bootup start fah sig 11
Actual results:

Expected results:

Additional info:


Comment 1 Chuck Ebbert 2007-08-06 18:39:10 UTC
Signal 11 can be caused by bad memory, overheating CPU, inadequate power
supply and a long list of other reasons. Are you sure the hardware is 100%
OK? Do any other programs cause a problem? Has memtest86 been run on this

Comment 2 Darwin H. Webb 2007-08-22 20:34:34 UTC
This bug can be closed.
With the high summer temps and the Virtual-Box running several systems,
I was able to pin point the problem a cpu heat (mainly when the FAH is using the
FPU @ 100% for a few hours VS> the VB using normal CPU @ irregular intervals
avg. 84%.)

I also think the 23 kernel is way better than any since 18. :)



Note You need to log in before you can comment on or make changes to this bug.