Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

[Meelis Roos]

> > 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.

Will try to bisect but this takes time because I'm rarely near that 
computer.

-- 
Meelis Roos (mroos-Y27EyoLml9s@public.gmane.org)

Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

[Rafael J. Wysocki]

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.
> 
> Will try to bisect but this takes time because I'm rarely near that 
> computer.

OK, thanks for the update.

Rafael

Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

[Meelis Roos]

> > > 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.

-- 
Meelis Roos (mroos-Y27EyoLml9s@public.gmane.org)

Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration

[Rafael J. Wysocki]

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.

OK, so let's tentatively regard this as a regression from 2.6.30, although I'm
not really sure that's a regression at all.

Rafael


> 
>