From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alberto Gonzalez <alberto6674@gmail.com>
Cc: Michal Soltys <soltys@ziu.info>, Dave Airlie <airlied@linux.ie>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Kernel 2.6.30 and udevd problem
Date: Wed, 22 Jul 2009 19:44:36 +0000 [thread overview]
Message-ID: <20090722124436.0daa2079@jbarnes-g45> (raw)
In-Reply-To: <200907222043.57244.info@gnebu.es>
On Wed, 22 Jul 2009 20:43:56 +0200
Alberto Gonzalez <alberto6674@gmail.com> wrote:
> On Wednesday 22 July 2009 19:12:51 Jesse Barnes wrote:
> > Ah I must have been looking at the wrong register. This one makes
> > it look like one of your HDMI hotplug bits is getting stuck (HDMIC
> > in particular). This might not even be wired up on your platform...
>
> Yes, I don't use HDMI, my screen is attached via VGA
> >
> > This test hack should prevent us from responding to those
> > interrupts...
>
> I've been hitting it hard for over an hour with all the usual tricks
> to trigger it (and a few reboots) and I've been unable to reproduce
> the problem with this patch. Before I could trigger it reliably in a
> few minutes, so I'm pretty sure this patch fixes it. If something new
> comes up, I'll let you know anyway.
Hm, so this type of interrupt problem is *supposed* to be handled by
setting of the PEG_BAND_GAP_DATA reg (low bits set to 0xd). Do you
have that in your tree? Does git master have this problem?
Maybe we need to add a patch to 2.6.30.x to set PEG_BAND_GAP_DATA as a
workaround (git master already has code to do this properly for HDMI
and DP outputs afaict).
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-07-22 19:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 6:21 Kernel 2.6.30 and udevd problem Alberto Gonzalez
2009-06-28 10:37 ` Kay Sievers
2009-06-28 12:37 ` Alberto Gonzalez
2009-06-28 12:49 ` Kay Sievers
2009-06-28 14:22 ` Alberto Gonzalez
2009-06-28 14:28 ` Kay Sievers
2009-06-30 3:40 ` Alberto Gonzalez
2009-06-30 3:46 ` Dave Airlie
2009-06-30 16:08 ` Jesse Barnes
2009-07-01 7:09 ` Alberto Gonzalez
2009-07-01 17:22 ` Jesse Barnes
2009-07-02 6:18 ` Alberto Gonzalez
2009-07-02 16:35 ` Jesse Barnes
2009-07-02 19:37 ` Alberto Gonzalez
2009-07-02 22:00 ` Michal Soltys
2009-07-04 22:10 ` Alberto Gonzalez
2009-07-20 18:10 ` Jesse Barnes
2009-07-20 21:06 ` Alberto Gonzalez
[not found] ` <200907210048.37432.info@gnebu.es>
[not found] ` <200907221525.29507.info@gnebu.es>
2009-07-22 16:08 ` Jesse Barnes
[not found] ` <200907221851.20916.info@gnebu.es>
2009-07-22 17:12 ` Jesse Barnes
2009-07-22 18:43 ` Alberto Gonzalez
2009-07-22 19:17 ` Jesse Barnes
2009-07-22 19:44 ` Jesse Barnes [this message]
2009-07-22 20:00 ` Alberto Gonzalez
2009-07-23 0:06 ` Alberto Gonzalez
2009-08-06 13:53 ` Alberto Gonzalez
2009-08-06 21:30 ` Jesse Barnes
2009-08-06 22:17 ` Alberto Gonzalez
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=20090722124436.0daa2079@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=alberto6674@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soltys@ziu.info \
/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;
as well as URLs for NNTP newsgroup(s).