Re: Kernel OOPS when reloading i915 after resume from suspend

[Pavel Machek]

Hi!

> still experimenting with the resume from suspend on the Fujitsu
> S6010. I can, however, still create a kernel oops. The kernel source
> comes from alm_fixes5, kernel 3.15.0-rc7+. For that, do the
> following:
> 
> 1) Shut down X,
> 2) Unbind the consoles:
> 
> echo 0 > /sys/class/vtconsole/vtcon1/bind
> echo 0 > /sys/class/vtconsole/vtcon0/bind
> 
> 3) Remove the i915
> 
> rmmod i915
> 
> 4) Suspend the system
> 
> pm-suspend

Does it also break with plain echo mem > /sys/power/state?

Does it break when you don't suspend at all?

> 5) Resume the system by pressing on the power-button.
> 6) Reload the i915 module with
> 
> modprobe i915.
> 
> Result is a kernel-Oops:

Sounds like problem in suspend/resume framework, actually :-(.

									Pavel

> 
> Jun 29 19:34:00 tyleet kernel: [  321.283072] [drm] Memory usable by
> graphics device = 128M
> Jun 29 19:34:00 tyleet kernel: [  321.286770] [drm] Supports vblank
> timestamp caching Rev 2 (21.10.2013).
> Jun 29 19:34:00 tyleet kernel: [  321.286782] [drm] Driver supports
> precise vblank timestamp query.
> Jun 29 19:34:00 tyleet kernel: [  321.286959] [drm] applying pipe a
> force quirk
> Jun 29 19:34:00 tyleet kernel: [  321.286965] [drm] applying pipe b
> force quirk
> Jun 29 19:34:00 tyleet kernel: [  321.307436] *pde = 00000000
> Jun 29 19:34:00 tyleet kernel: [  321.307568] Oops: 0000 [#1]
> Jun 29 19:34:00 tyleet kernel: [  321.307751] Modules linked in:
> i915(+) michael_mic arc4 ecb lib80211_crypt_tkip lib80211_crypt_ccmp
> binfmt_misc fuse netconsole loop firewire_sbp2 hid_generic usbhid
> hid snd_intel8x0 sg snd_ac97_codec ac97_bus snd_pcm sr_mod snd_seq

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/