From: Alberto Gonzalez <alberto6674@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
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: Mon, 20 Jul 2009 21:06:51 +0000 [thread overview]
Message-ID: <200907202306.52305.info@gnebu.es> (raw)
In-Reply-To: <20090720111010.28bf7b76@jbarnes-g45>
On Monday 20 July 2009 20:10:10 Jesse Barnes wrote:
> Alberto Gonzalez <alberto6674@gmail.com> wrote:
> > I now tried a vanilla 2.6.30.1 kernel with a custom config (so I
> > don't have to wait 45 minutes for it to compile) and I still see the
> > problem. This is what I get in dmesg:
> >
> > [ 83.506496] ------------[ cut here ]------------
> > [ 83.506500] WARNING: at drivers/gpu/drm/drm_sysfs.c:452
> > drm_sysfs_hotplug_event+0x2b/0x63()
> > [ 83.506502] Hardware name: Studio 540
> > [ 83.506503] hotplug uevent
> > [ 83.506504] Modules linked in:
> > [ 83.506506] Pid: 7, comm: events/0 Tainted: G W 2.6.30.1 #1
> > [ 83.506507] Call Trace:
> > [ 83.506511] [<c1025df9>] warn_slowpath_common+0x65/0x7c
> > [ 83.506514] [<c11e9f9e>] ? drm_sysfs_hotplug_event+0x2b/0x63
> > [ 83.506517] [<c1025e44>] warn_slowpath_fmt+0x24/0x27
> > [ 83.506520] [<c11e9f9e>] drm_sysfs_hotplug_event+0x2b/0x63
> > [ 83.506523] [<c11f33de>] i915_hotplug_work_func+0xe/0x10
> > [ 83.506525] [<c1032f28>] worker_thread+0x131/0x1ab
> > [ 83.506528] [<c11f33d0>] ? i915_hotplug_work_func+0x0/0x10
> > [ 83.506531] [<c1035f61>] ? autoremove_wake_function+0x0/0x2f
> > [ 83.506534] [<c1032df7>] ? worker_thread+0x0/0x1ab
> > [ 83.506536] [<c1035c84>] kthread+0x46/0x6a
> > [ 83.506538] [<c1035c3e>] ? kthread+0x0/0x6a
> > [ 83.506541] [<c10033cf>] kernel_thread_helper+0x7/0x10
> > [ 83.506542] ---[ end trace 08f91010f92f7c3c ]---
>
> Sorry I missed this update; what about the register dump part of the
> patch? Presumably you get a ton of these in your log, but with some
> IIR register info beforehand?
The problem is that when this happens I get these messages at a very high
rate, so they flood my dmesg in a few seconds. Is there a way I could access
that register dump that should precede them?
Thanks,
Alberto.
next prev parent reply other threads:[~2009-07-20 21:06 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 [this message]
[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
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=200907202306.52305.info@gnebu.es \
--to=alberto6674@gmail.com \
--cc=airlied@linux.ie \
--cc=jbarnes@virtuousgeek.org \
--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).