| 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
| ||
|
Date: Thu, 3 Jul 2014 12:38:46 +0200 From: Pavel Machek <pavel@....cz> To: Thomas Richter <thor@...h.tu-berlin.de> Cc: linux-kernel@...r.kernel.org, Ville Syrj?l? <ville.syrjala@...ux.intel.com>, Daniel Vetter <daniel@...ll.ch> Subject: Re: Kernel OOPS when reloading i915 after resume from suspend Hi! > >>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? > > No. If the modules stay resident, any user driven shutdown/resume > events by writing into /sys/power/state work just fine. > > >Does it break when you don't suspend at all? > > No. Unloading and reloading i915 under normal conditions also works fine. > > >>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 :-(. > > Good guess, but wrong. The BIOS leaves the 830GM in a state the i915 > does not seem to like. Ok, good, something for Intel people to solve, then... Pavel -- (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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists