Bug 464773 - INFO: possible irq lock inversion dependency detected (2.6.27-0.372.rc8.fc10.ppc64)
Summary: INFO: possible irq lock inversion dependency detected (2.6.27-0.372.rc8.fc10....
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: ppc64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-30 13:04 UTC by Adam Tkac
Modified: 2013-04-30 23:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-18 16:02:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
dmesg output (101.14 KB, text/plain)
2008-09-30 13:04 UTC, Adam Tkac 		no flags Details
same problem with 2.6.27-0.352.rc7.git1.fc10.ppc64 (99.32 KB, text/plain)
2008-09-30 14:36 UTC, Adam Tkac 		no flags Details
View All

Description Adam Tkac 2008-09-30 13:04:17 UTC 
Created attachment 318069 [details]
dmesg output

Description of problem:
I have got info about possible irq lock inversion right after boot or during boot

Version-Release number of selected component (if applicable):
# uname -a
Linux ppc03.englab.brq.redhat.com 2.6.27-0.372.rc8.fc10.ppc64 #1 SMP Tue Sep 30 01:04:55 EDT 2008 ppc64 ppc64 ppc64 GNU/Linux

How reproducible:
quite often (once during boot, twice right after boot)

Steps to Reproduce:
1. download 2.6.27-0.372.rc8.fc10.ppc64 kernel from koji
2. boot it
3. wait for lockup
  
Actual results:
INFO: possible irq lock inversion dependency detected

Expected results:
no errors/warnings
Comment 1 Adam Tkac 2008-09-30 14:36:45 UTC 
Created attachment 318080 [details]
same problem with 2.6.27-0.352.rc7.git1.fc10.ppc64
Comment 2 Christopher D. Stover 2008-11-16 04:13:20 UTC 
Are you still having this issue with newer kernels Adam?
Comment 3 Adam Tkac 2008-11-18 16:02:45 UTC 
It seems problem no longer exists, closing
Note You need to log in before you can comment on or make changes to this bug.