linux-kernel - Re: resume problem with i915/drm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200808071427.32457.jbarnes@virtuousgeek.org>
Date:	Thu, 7 Aug 2008 14:27:32 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Charles@...wieters.org, Matthew Garrett <mjg59@...f.ucam.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: resume problem with i915/drm

On Tuesday, August 5, 2008 7:25 pm Charles@...wieters.org wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hi--
>
>   I'm having a problem resuming (from RAM) if the i915 and drm modules
> are loaded (these are needed for running X on my machine). Vanilla
> kernel versions 2.6.25.x and 2.6.26.x. I get the same behavior with
> Debian linux-image-2.6.25-2-686 kernel. I can't believe I'm the first to
> encounter this.
>
> suspend-to-ram and resuming works fine with earlier kernels
> (e.g. 2.6.17), but I haven't tested exhaustively.
>
> Possibly related is a failure in modprobe -r i915 after it is
> loaded. The message printed is

[snip backtrace]

Well the backtrace makes it look like i915 didn't take care to remove some of 
its /proc files, which is weird.

Your "screen blank on resume" problem might be a duplicate of a bug that got 
reported awhile back (can't find it now, Matthew?).  If so, then you're not 
the first one to see it; unfortunately we don't have a fix yet...

Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/