Bug 164976
Summary: | system locks up | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Charles C. Van Tilburg <ctilburg> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | pfrields, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-09-30 15:28:59 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Charles C. Van Tilburg
2005-08-03 09:10:22 UTC
Created attachment 117389 [details]
scimark2 compiled with gcc 2.95.3 -O2
Things to try.. can you try booting with exec-shield=0 and also try vdso=0 also try echo 0 > /proc/sys/kernel/randomize_va_space trying the easiest first, the randomize_va_space definately helped, but did not solve the problem; it survived three runs with X running and locked up on the fourth. This is better than locking up on the first run. rebooting with only the exec-shield=0 and vdso=0, running at console made things worse; immediate lock up. This is down from surviving three or four. I'm about to try a combination of all three under X... all three under X result in it surviving the first run, but locking up on the second (when I started an sh loop). This is an improvement over the original situation, but not much, and certainly not as good as just doing the randomize_va_space. if it means anything, SELinux is (and has been) disabled. what graphics driver are you using ? I thought I had eliminated the whole graphics system for consideration by running at the console, right after boot, which doesn't even have the nvidia kernel module loaded. However, I guess I have not tried running at the console, with only the randomize_va_space set to 0. I'll try it. The fact that having X running exacerbates a possible kernel problem is not completely unbelievable. To finally answer the question, the graphics drivers are Nvidia's latest; 7667. Fresh boot, no nvidia kernel module loaded, console, the only fix applied is the randomize_va_space set to 0. Runs three times, locks up on the fourth. Which is probably exactly what happened at console mode before, without any fix applied (I wasn't counting as precisely then, as now). However, setting randomize_va_space to 0 sure did help while X was running... Also... to be clear, my system does *NOT* boot to an xdm or such login screen... it comes up to console only (run level 3). I have to type startx to get X going after login. FYI. Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. Survived five runs... |