From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <petkovbb@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alex Deucher <alexdeucher@gmail.com>,
Jerome Glisse <glisse@freedesktop.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: Linux 2.6.33-rc5
Date: Sun, 24 Jan 2010 10:30:22 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001241018500.3574@localhost.localdomain> (raw)
In-Reply-To: <20100124111946.GA4170@liondog.tnic>
On Sun, 24 Jan 2010, Borislav Petkov wrote:
>
> 1. After suspend, the right monitor shows very funny colors, as if it is
> on crack, in contrast to the left one which looks fine:
>
> http://userweb.kernel.org/~bp/right_monitor.jpg
> http://userweb.kernel.org/~bp/left_monitor.jpg
Ok, at a guess, it looks like something isn't restoring the palette
registers for the second output. You didn't say what GPU you have, but
judging by your CC list, it's a radeon. You might want to let the Radeon
KMS people know exactly what your setup is etc.
> 2. During suspend I get this juicy lockdep warning:
I'm pretty sure that this is not actually a new problem, it's a new
warning for an old problem, see commit 846f99749 ("sysfs: Add lockdep
annotations for the sysfs active reference"). So I'm not considering it a
regression, even though I do agree that the messages look scary and very
annoying.
I'm not at all convinced that we are going to be able to fix the problems
that this made visible in time for 2.6.33. The sysfs-related lock chains
easily get rather involved, although it is always possible that this
particular one might be easily fixable (ie if radeon is able to call the
final kref_put outside any locks - or whatever it is that ends up
generating a dependency from struct_mutex for the sysfs active ref).
Or maybe I'm misreading the lockdep chain. Eric Biederman added to cc.
Linus
next prev parent reply other threads:[~2010-01-24 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 23:44 Linux 2.6.33-rc5 Linus Torvalds
2010-01-24 11:19 ` Borislav Petkov
2010-01-24 18:30 ` Linus Torvalds [this message]
2010-01-24 19:08 ` Borislav Petkov
2010-01-25 3:46 ` Alex Deucher
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.LFD.2.00.1001241018500.3574@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=alexdeucher@gmail.com \
--cc=ebiederm@xmission.com \
--cc=glisse@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.com \
/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