Bug 1071798

Summary: INFO: possible irq lock inversion dependency detected
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-04 07:46:36 UTC Type: Bug
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 Flags
dmesg output none

Description Peter H. Jones 2014-03-03 07:50:01 UTC
Created attachment 869825 [details]
dmesg output

Description of problem:
Trace booting Fedora-Live-Jam-KDE-x86_64-rawhide-20140302.iso.

Version-Release number of selected component (if applicable):
kernel-3.14.0-0.rc4.git3.1.fc21.x86_64

How reproducible:
Sometimes. Got it selecting basic graphics mode 3.

Steps to Reproduce:
1. Boot, select Troubleshooting, edit Basic Graphics boot to remove rhgb and quiet, and adding 3.

Actual results:
Kernel trace in dmesg output. It's a bit too long to copy here.

Expected results:
No trace

Comment 1 Josh Boyer 2014-03-03 17:26:28 UTC
Stanislaw, is this similar to the issue you just fixed for EHCI?

As an aside, I have no idea why this Fedora spin passes threadirqs.  The bugs that are popping up are interesting I guess, but they aren't going to hit the majority of Fedora users at the moment.

Comment 2 Stanislaw Gruszka 2014-03-04 07:46:36 UTC
Yes. The lockdep warning is different than in bug 1056170, but the patch from that bug, should fix problem here too.

That fix was not applied in the rawhide, but it is committed in today's git as a1227f3c1030e96ebc51d677d2f636268845c5fb, hence I'm closing this bug.

Peter, if issue will happen again on updated kernel please reopen it.