Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-03 Thread Pavel Machek
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 >

Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-03 Thread Thomas Richter
Am 02.07.2014 23:22, schrieb 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:

Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-03 Thread Thomas Richter
Am 02.07.2014 23:22, schrieb 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:

Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-03 Thread Pavel Machek
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

Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-02 Thread 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 >

Re: Kernel OOPS when reloading i915 after resume from suspend

2014-07-02 Thread 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

Kernel OOPS when reloading i915 after resume from suspend

2014-06-29 Thread Thomas Richter
Hi Ville, hi Daniel, 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 >

Kernel OOPS when reloading i915 after resume from suspend

2014-06-29 Thread Thomas Richter
Hi Ville, hi Daniel, 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