Bug 440113 - Kernel general protection fault with 2.6.24.3-50.fc8
Summary: Kernel general protection fault with 2.6.24.3-50.fc8
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-01 19:03 UTC by Andre Costa
Modified: 2008-04-01 19:31 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-01 19:31:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages and /var/log/Xorg.0.log (16.90 KB, application/zip)
2008-04-01 19:03 UTC, Andre Costa
no flags Details

Description Andre Costa 2008-04-01 19:03:42 UTC
Description of problem:
After resuming from suspend all terminals showed a message like:
"kernel: general protection fault: 0000 [1] SMP"
After a couple of minutes, system locked.


Version-Release number of selected component (if applicable):
2.6.24.3-50.fc8


How reproducible:
this is the first time, I'm not sure this is related to suspend-resume.


Steps to Reproduce:
1.resume from user-triggered suspend
2.
3.
  
Actual results:
Error message on all terminals: "kernel: general protection fault: 0000 [1]
SMP", system lock after a couple of minutes


Expected results:
System doesn't lock up =)

Additional info:
These are the applications that were running, IIRC: thunderbird, firefox,
rhythmbox (stopped), pidgin, Eclipse (IDE) with Sun JDK 1.6.0_05. System is an
Intel Core 2 Duo, 2G RAM, GeForce 8600GT with NVidia binary driver (latest
version 169.12)
/var/log/messages and /var/log/Xorg.0.log follow as attachment.
/var/log/messages has some comments on it.

Comment 1 Andre Costa 2008-04-01 19:03:42 UTC
Created attachment 299945 [details]
/var/log/messages and /var/log/Xorg.0.log

Comment 2 Dave Jones 2008-04-01 19:31:20 UTC
we can't debug problems that have the nvidia binary module loaded.



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