Bug 15307 - irq11: nobody cared, during yenta registration
irq11: nobody cared, during yenta registration
Status: CLOSED INSUFFICIENT_DATA
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64
All Linux
: P1 normal
Assigned To: platform_x86_64@kernel-bugs.osdl.org
:
Depends on:
Blocks: 13615
  Show dependency treegraph
 
Reported: 2010-02-14 23:14 UTC by Rafael J. Wysocki
Modified: 2012-03-13 23:00 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.33-rc8
Tree: Mainline
Regression: Yes


Attachments

Description Rafael J. Wysocki 2010-02-14 23:14:40 UTC
Subject    : 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration
Submitter  : Meelis Roos <mroos@ut.ee>
Date       : 2010-02-14 15:32
Message-ID : alpine.SOC.1.00.1002141720120.679@math.ut.ee
References : http://marc.info/?l=linux-kernel&m=126616327302771&w=4

This entry is being used for tracking a regression from 2.6.32.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Rafael J. Wysocki 2010-02-15 19:48:39 UTC
On Monday 15 February 2010, Meelis Roos wrote:
> > > Just tried 2.6.33-rcx8 on my laptop (Thinkpad X20 in a dock) that was 
> > > last running 2.6.33-rc5 without problems. Gor irq11: nobody carec like 
> > > below. Seems to be repeatabale. lspci also below.
> > 
> > I have created the Bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=15307
> > for your report.
> > 
> > Peter, Ingo, did we do anything to the interrupt handling between .33-rc5 and .33-rc8?
> 
> I just retested it and the problem appears even in -rc5 (missed it 
> before). Come to think of it, I only tested -rc5 out of dock before.
> 
> With dock, the problem is there in 2.6.33-rc4-00399-g24bc734.
> 
> Without dock, even -rc8 is OK, so it only happens docked.
Comment 2 Rafael J. Wysocki 2010-02-15 22:14:04 UTC
On Monday 15 February 2010, Meelis Roos wrote:
> > > > I have created the Bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=15307
> > > > for your report.
> > > > 
> > > > Peter, Ingo, did we do anything to the interrupt handling between .33-rc5 and .33-rc8?
> > > 
> > > I just retested it and the problem appears even in -rc5 (missed it 
> > > before). Come to think of it, I only tested -rc5 out of dock before.
> > > 
> > > With dock, the problem is there in 2.6.33-rc4-00399-g24bc734.
> > > 
> > > Without dock, even -rc8 is OK, so it only happens docked.
> > > 
> > > Will try to bisect but this takes time because I'm rarely near that 
> > > computer.
> 
> It's even worse - or my memory is, actually.
> 
> With dock, both 2.6.32 and 2.6.31 exhibit the problem, so it's not a 
> recent regression - but the bugzilla entry still holds.
> 
> In fact, googling tells that I reported the issue back in 2006 together 
> with a USB problem that I thought was related, and that has been fixed 
> meanwhile:
> 
> http://lkml.indiana.edu/hypermail/linux/kernel/0607.2/1331.html
> 
> Strange that I haven't noticed it meanwhile.
Comment 3 Rafael J. Wysocki 2010-02-15 22:15:23 UTC
Not a recent regression, moving to another list.
Comment 4 Dominik Brodowski 2010-03-06 14:23:41 UTC
What happens if you use the module parameter "isa_probe=0" for the module yenta_socket?
Comment 5 Florian Mickler 2012-03-13 23:00:35 UTC
Timeout... please post a note, if the discussed issue is still a problem.

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