From: Meelis Roos <mroos@linux.ee>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.33-rc8 regression: irq11: nobody cared, during yenta registration
Date: Mon, 15 Feb 2010 23:19:05 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1002152315580.12096@math.ut.ee> (raw)
In-Reply-To: <201002152048.59832.rjw@sisk.pl>
> > > 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@linux.ee)
next prev parent reply other threads:[~2010-02-15 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 15:32 Meelis Roos
2010-02-14 23:18 ` Rafael J. Wysocki
2010-02-15 6:03 ` Meelis Roos
2010-02-15 19:48 ` Rafael J. Wysocki
2010-02-15 21:19 ` Meelis Roos [this message]
2010-02-15 22:15 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.SOC.1.00.1002152315580.12096@math.ut.ee \
--to=mroos@linux.ee \
--cc=hpa@zytor.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®