linux-kernel - 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-next>] [day] [month] [year] [list]

Message-Id: <E1KQYiX-0002Nl-Ud@oaf.wireless>
Date:	Tue, 05 Aug 2008 22:25:37 -0400
From:	Charles@...wieters.org
To:	linux-kernel@...r.kernel.org
cc:	charles@...wieters.org
Subject: resume problem with i915/drm

-----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

Aug  5 21:39:47 oaf kernel: WARNING: at fs/proc/generic.c:799 remove_proc_entry+0xf9/0x115()
Aug  5 21:39:47 oaf kernel: Modules linked in: drm(-) binfmt_misc rfcomm l2cap bluetooth lp nfsd exportfs nfs lockd nfs_acl sunrpc deflate zlib_deflate zlib_inflate ctr twofish twofish_common camellia serpent blowfish des_generic cbc aes_i586 aes_generic xcbc sha256_generic sha1_generic md5 crypto_null af_key fuse dm_crypt crypto_blkcipher dm_snapshot dm_mirror dm_log dm_mod eeprom i2c_core snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi pcmcia crc32 snd_seq_midi_event snd_seq snd_timer snd_seq_device ipw2200 snd ieee80211 ieee80211_crypt soundcore 8250_pnp firmware_class yenta_socket rsrc_nonstatic 8250_pci snd_page_alloc pcspkr parport_pc psmouse 8250 pcmcia_core parport e100 serial_core cdrom iTCO_wdt fan bay dock ehci_hcd toshiba_acpi backlight thermal battery ac uhci_hcd processor button usbcore intel_agp agpgart unix [last unloaded: i915]
Aug  5 21:39:47 oaf kernel: Pid: 3890, comm: modprobe Not tainted 2.6.26.1 #9
Aug  5 21:39:47 oaf kernel:  [<c0114778>] warn_on_slowpath+0x40/0x79
Aug  5 21:39:47 oaf kernel:  [<c0110b90>] check_preempt_wakeup+0x8f/0xc3
Aug  5 21:39:47 oaf kernel:  [<c01220d5>] autoremove_wake_function+0xd/0x2d
Aug  5 21:39:47 oaf kernel:  [<c010ff37>] __wake_up_common+0x2d/0x52
Aug  5 21:39:47 oaf kernel:  [<c010ff6b>] __wake_up+0xf/0x15
Aug  5 21:39:47 oaf kernel:  [<c0114cee>] wake_up_klogd+0x2b/0x2d
Aug  5 21:39:47 oaf kernel:  [<c0144237>] vma_merge+0x1a3/0x23a
Aug  5 21:39:47 oaf kernel:  [<c0179649>] remove_proc_entry+0xf9/0x115
Aug  5 21:39:47 oaf kernel:  [<c014260c>] free_pgtables+0x67/0x7b
Aug  5 21:39:47 oaf kernel:  [<dff46f7b>] drm_core_exit+0xc/0x2a [drm]
Aug  5 21:39:47 oaf kernel:  [<c012df88>] sys_delete_module+0x193/0x1eb
Aug  5 21:39:47 oaf kernel:  [<c014345b>] remove_vma+0x43/0x48
Aug  5 21:39:47 oaf kernel:  [<c0144046>] do_munmap+0x1ba/0x1d4
Aug  5 21:39:47 oaf kernel:  [<c0102a55>] sysenter_past_esp+0x6a/0x91
Aug  5 21:39:47 oaf kernel:  =======================
Aug  5 21:39:47 oaf kernel: ---[ end trace dd188b4354a41352 ]---

For 2.6.26.1, if I don't start X, I have the following list of modules

View attachment "lsmod.works" of type "text/plain" (3794 bytes)

and suspend-to-ram resumes successfully.
If I load the i915 module I have this list of modules

View attachment "lsmod.fails" of type "text/plain" (3869 bytes)

and the suspend part seems to work, but I get a blank screen upon
resume, and no virtual terminals are responsive.

The processor is a pentium M and Xorg reports 
  (--) Chipset 852GM/855GM found

and the kernel configuration for the 2.6.26.1 setup is

View attachment "config-2.6.26.1" of type "text/plain" (64291 bytes)


any ideas--
Charles
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFImQugPK2zrJwS/lYRAilVAJ9zV7t9/GvWNa6wkZr1pLANG+iXdwCeJmFx
7Gz8yna1xrUlGJEK3yZa3N0=
=J3Oh
-----END PGP SIGNATURE-----