From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alberto Gonzalez <alberto6674@gmail.com>
Cc: Alberto Gonzalez <alberto6674@gmail.com>,
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 16:08:34 +0000 [thread overview]
Message-ID: <20090722090834.6ab45aae@jbarnes-g45> (raw)
In-Reply-To: <200907221525.29507.info@gnebu.es>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Wed, 22 Jul 2009 15:25:29 +0200
Alberto Gonzalez <alberto6674@gmail.com> wrote:
> On Tuesday 21 July 2009 00:48:36 Alberto Gonzalez wrote:
> > If what you need is the exact lines just before the "storm" starts
> > let me know and I'll keep trying, but it's not easy because I'll
> > have to be very fast in detecting the problem has started and
> > logging the output of dmesg.
>
> Ok, I caught a complete log from boot to when the problem starts.
> There doesn't seem to be anything significantly different, but just
> in case.
Oh I guess this is without the debug patch I attached... this one
should be a bit less noisy but tell me which bit is stuck.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: i915-hotplug-error.patch --]
[-- Type: text/x-patch, Size: 596 bytes --]
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 228546f..6c31408 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -353,7 +353,7 @@ irqreturn_t i915_driver_irq_handler(DRM_IRQ_ARGS)
(iir & I915_DISPLAY_PORT_INTERRUPT)) {
u32 hotplug_status = I915_READ(PORT_HOTPLUG_STAT);
- DRM_DEBUG("hotplug event received, stat 0x%08x\n",
+ DRM_ERROR("hotplug event received, stat 0x%08x\n",
hotplug_status);
if (hotplug_status & dev_priv->hotplug_supported_mask)
schedule_work(&dev_priv->hotplug_work);
next prev parent reply other threads:[~2009-07-22 16:08 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 [this message]
[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
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=20090722090834.6ab45aae@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