Bug 101704 - kernel panic with shared memory graphic cards
Summary: kernel panic with shared memory graphic cards
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: John Dennis
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-05 20:27 UTC by Florian Brand
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-05 23:21:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages (117.47 KB, text/plain)
2003-08-05 20:37 UTC, Florian Brand 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Florian Brand 2003-08-05 20:27:59 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030709

Description of problem:
On a Dell Latitude 640 w/ Radeon 7500 (512M RAM) the kernel (boot and i686)
panics while accessing high memory. 
During Install, the Kernel Panic happens immediatly after "running /sbin/loader".

After install, irreproducible errors happen after boot with similar messages.

Current workaround is to use a mem=480M paramenter at install and boot.


Version-Release number of selected component (if applicable):
kernel-2.4.21-1.1931.2.349.2.2.ent

How reproducible:
Always

Steps to Reproduce:
1. Boot Linux
2. wait for panic :)

    

Actual Results:  "invalid kernel-mode pagefault 0! "

Expected Results:  no kernel panic?

Additional info:
Comment 1 Florian Brand 2003-08-05 20:37:31 UTC 
Created attachment 93415 [details]
/var/log/messages

today's /var/log/messages
notice the problem doesn't occur when the system is started with mem=480M
Comment 2 Florian Brand 2003-08-05 20:42:55 UTC 
just forgot: I did check for fauly memory with memtest86. No problems found.
Comment 3 Arjan van de Ven 2003-08-05 20:45:35 UTC 
we've had a problem with this for a long time
somehow it doesn't happen with the installed kernel usually, is that the case
for you ?
Comment 4 Matt Wilson 2003-09-10 23:10:03 UTC 
Florian, does this still happen?
Comment 5 Ernie Petrides 2004-04-08 22:21:26 UTC 
Hello, Florian.  Is there still a problem with a more recent
RHEL 3 kernel (such as U1 -- 2.4.21-9.EL)?  Thanks.  -ernie
Comment 7 Ernie Petrides 2005-10-05 23:21:13 UTC 
Closing due to lack of response.
Comment 8 Florian Brand 2005-10-06 07:22:13 UTC 
(In reply to comment #7)
> Closing due to lack of response.

Sorry. Somehow I didn't recieve the comments prior to the 'bug closed' message.
The problem disappeared w/ more recent kernels.

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