Bug 563188 - WARNING: at lib/kref.c:43 kref_get+0x23/0x2d() / Oops: 0002 [#1] SMP
Summary: WARNING: at lib/kref.c:43 kref_get+0x23/0x2d() / Oops: 0002 [#1] SMP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-09 13:54 UTC by Giacomo Montagner
Modified: 2010-12-03 23:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:04:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Full kernel trace of WARNING and subsequent Ooops (6.77 KB, text/plain)
2010-02-09 13:54 UTC, Giacomo Montagner
no flags Details
Log from /var/log/messages containing the kernel Ooops messages (838.33 KB, application/octet-stream)
2010-03-01 21:02 UTC, Jaroslaw Mroczek
no flags Details

Description Giacomo Montagner 2010-02-09 13:54:25 UTC
Created attachment 389751 [details]
Full kernel trace of WARNING and subsequent Ooops

Description of problem:
I keep seeing this message: 

WARNING: at lib/kref.c:43 kref_get+0x23/0x2d() (Not tainted)
(I'll attach the full trace for better readability)

in /var/log/messages. When it happens X freezes and I must reset the machine. It ususally happens when browsing flash-intensive internet sites, but not only in those cases. 

I suspected mesa-dri-drivers-experimental.x86_64 being responsible for it, but it keeps happening after I uninstalled the package. The problem never happens when using the machine remotely through ssh, but always when a user is logged-in and using the machine in a graphical session. 


Version-Release number of selected component (if applicable):
kernel 2.6.31.12-174.2.3.fc12.x86_64


How reproducible:
Always


Steps to Reproduce:
1. start machine in runlevel 5 (default)
2. login using graphical login manager
3. start working
  
Actual results:
After some time (even a short time in some cases: 1 to 3 minutes after login) the X session freezes. After resetting the machine (sometimens Alt+SysRq+s-u-b works to reset the machine, sometimes no) the WARNING is found in /var/log/messages. 

Expected results:
no freeze, no WARNING, no Ooops... 

Additional info:
# lspci | grep VGA
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 Graphics

CPU: AMD Phenom(tm) II X4 955 Processor

Comment 1 Jaroslaw Mroczek 2010-03-01 21:02:08 UTC
Created attachment 397178 [details]
Log from /var/log/messages containing the kernel Ooops messages

Comment 2 Jaroslaw Mroczek 2010-03-01 21:04:10 UTC
I observe similar issue on my machine (AMD Phenom II X4 945/4GB RAM). It also looks that other people experience this problem http://forums.fedoraforum.org/showthread.php?p=1335695. I have attached my log from /var/log/messages.

Comment 3 michiel 2010-03-01 21:48:55 UTC
Similar on AMD Athlon X4 630 / HD3200. Now running kernel 2.6.32.8-58.fc12.x86_64 from testing for a few days without oops. Just 1 crash in X11, no oops.

Comment 4 Jaroslaw Mroczek 2010-03-05 22:10:15 UTC
I have installed the debug version of this kernel (2.6.31.12-174.2.22.fc12.x86_64.debug) and it seems that this problem does not appear on that build. I haven't seen the sympthoms for the last 4 days.

Comment 5 Adeel 2010-03-30 16:07:20 UTC
This issue is related with a WARN_ON(condition) function. If you comment out this warning function in kernel code, you'll be having no more problem.

Comment 6 Bug Zapper 2010-11-03 22:36:29 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-12-03 23:04:25 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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