Mailing List Archive: Linux: Kernel

resume problem with i915/drm

Index | Next | Previous | View Threaded

Charles at Schwieters

Aug 5, 2008, 7:25 PM

Post #1 of 5 (85 views)
Permalink

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

Attachments:

lsmod.works (3.71 KB)

lsmod.fails (3.78 KB)

config-2.6.26.1 (62.8 KB)

rjw at sisk

Aug 7, 2008, 1:08 PM

Post #2 of 5 (66 views)
Permalink

Re: resume problem with i915/drm [In reply to]

On Wednesday, 6 of August 2008, Charles[at]schwieters.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.

Can you retest with 2.6.27-rc2, please?

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

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

jbarnes at virtuousgeek

Aug 7, 2008, 2:27 PM

Post #3 of 5 (66 views)
Permalink

Re: resume problem with i915/drm [In reply to]

On Tuesday, August 5, 2008 7:25 pm Charles[at]schwieters.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[at]vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

rjw at sisk

Aug 7, 2008, 2:39 PM

Post #4 of 5 (66 views)
Permalink

Re: resume problem with i915/drm [In reply to]

On Thursday, 7 of August 2008, Jesse Barnes wrote:
> On Tuesday, August 5, 2008 7:25 pm Charles[at]schwieters.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...

I think it may be related to this report:

http://marc.info/?l=linux-kernel&m=121789312607006&w=4

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

Charles at schwieters

Aug 7, 2008, 5:42 PM

Post #5 of 5 (71 views)
Permalink

Re: resume problem with i915/drm [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Folks--

I'm a moron. It turns out that CONFIG_ACPI_VIDEO had come unset when
CONFIG_VIDEO_OUTPUT_CONTROL came into existence (sometime after 2.6.17)
- - through my use of make oldconfig. Resume works fine with 2.6.26.1 if I
re-enable these. The i915/drm module unload warning message does seem to
be real, but perhaps unrelated to resume.

thanks for your earnest responses--

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

iD8DBQFIm5ZdPK2zrJwS/lYRAnOFAJ9ygKd3rBTqWZy3+aMSw9p+hYX2iQCdEe3t
Qhwle4QF+Torx/aA/ZNgJqI=
=64VA
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo[at]vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com