From: Pavel Machek <pavel@ucw.cz>
To: Thomas Richter <thor@math.tu-berlin.de>
Cc: linux-kernel@vger.kernel.org,
Ville Syrj?l? <ville.syrjala@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: Kernel OOPS when reloading i915 after resume from suspend
Date: Thu, 3 Jul 2014 12:38:46 +0200 [thread overview]
Message-ID: <20140703103846.GA12400@amd.pavel.ucw.cz> (raw)
In-Reply-To: <53B4F3FB.6030108@math.tu-berlin.de>
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
prev parent reply other threads:[~2014-07-03 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 17:43 Thomas Richter
2014-07-02 21:22 ` Pavel Machek
[not found] ` <13976_1404336180_53B47834_13976_165_1_20140702212219.GA2842@xo-6d-61-c0.localdomain>
2014-07-03 6:11 ` Thomas Richter
2014-07-03 10:38 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140703103846.GA12400@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=daniel@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=thor@math.tu-berlin.de \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®