mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
To: Patrick Mochel <mochel@osdl.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Power Management Update
Date: Tue, 9 Sep 2003 12:53:23 +0200	[thread overview]
Message-ID: <20030909105323.GA14859@lps.ens.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0309081244080.972-100000@localhost.localdomain>

On Mon, Sep 08, 2003 at 12:54:12PM -0700, Patrick Mochel wrote:
> > * swsusp doesn't like accelerated graphics. If the following modules are
> >   loaded:
> >     i830                   68120  20
> >     intel_agp              14744  1
> >     agpgart                25640  3 intel_agp
> >   resuming fails. (Different kind of failures, from spontaneous reboot to
> 
> This is not suprising, and likely something that many people will run 
> into. There is a lot of driver work that needs to be done, especially WRT 
> video devices, as many of them are not tied into the new driver model at 
> all. 

If you want more testers and interesting bug reports, that should be some
kinfd of priority, no ? Everybody is running with accelerated graphics
modules, nowadays.
> 
> For now, the best I can say is to manually unload those modules before 
> suspending and reloading them after resume. We'll work on getting the 
> drivers fixed up, but it will probably take a while. 
> 
> >   However, the mouse is not working anymore (mouse is usb, the only usb
> >   device connected) nor network on eth1 (I haven't tried eth0.)
> 
> For both the mouse and eth1, will they work if you unload the modules 
> first, and reload them after resuming? 

Ok, I tried this: after a normal boot, I went back to runlevel 3,
ifconfig'ed down eth1, unloaded modules i830, hid, ehci-hcd, uhcd-hcd
ne2K-pci and 8390 and echoed 4 to /proc/sleep/acpi. Note that intel_agp,
agpgart and usbcore were still there, those modules can't be removed once
loaded.

The system suspended and resumed correctly. 

I ifconfig'ed up eth1 (which loaded automagically the two modules), and
network was working. I loaded hid, ehci-hcd and uhcd-hcd, and mouse was
working. I telinit'ed 5, X started, went back to runlevel 3 to load i830
which I had forgotten, went back again to runlevel 5. X was working fine,
and video acceleration too. (I think I saw a little glitch on screen; a
little gray line, there, that diseapeared quickly.)

Then I tried to pinpoint more precisely what was wrong. Back to telinit
3. ifconfig down eth1, but keep the modules loaded. rmmod i830, hid, but
keep ehci-hcd and uhci-hcd. I expected that, at least, the computer would
suspend and resume, and I wanted to see if I could recover my mouse and
network interface. I got a black screen at suspend time, and had to
reboot with magic sysrq. I thought that the computer wouldn't suspend
twice in a row.

After a clean boot, I tried again my latest experiment: telinit 3, rmmod
i830, rmmod hid, ifconfig eth1 down, echo 4 > /proc/acpi/sleep.
As I said, the computer should be able to suspend/resume in that
configuration. This time, it failed at resuming. Beautifull kernel panic,
tried to kill init, etc.

It isn't logical. To sum up:

agpgart		i830		hid+uhci+ehci	eth1	  | suspend+resume
+intel_agp						  |
----------------------------------------------------------+--
unloaded	unloaded	loaded		loaded+up | works but
							  | mouse+eth1 fail

loaded		unloaded	unloaded	unloaded  | works and
							  | mouse+eth1 can be
							  | recovered

loaded		unloaded	partially	loaded	  | does not work.
				loaded		but down

What this probably means is that one of my succes was a piece of luck,
non reliably reproducible. Unfortunately, my wife came back from her
trip, and I now have much less time for testing...

If, anyway, I decide to try test5, what patches should be applied ?

Éric

  reply	other threads:[~2003-09-09 10:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030904224112.GA26556@lps.ens.fr>
     [not found] ` <Pine.LNX.4.33.0309041637440.940-100000@localhost.localdomain>
2003-09-07  9:54   ` Éric Brunet
2003-09-08 19:54     ` Patrick Mochel
2003-09-09 10:53       ` Éric Brunet [this message]
2003-09-09 15:54         ` Patrick Mochel
     [not found] <3F5F9509.8080708@btopenworld.com>
2003-09-10 22:51 ` Patrick Mochel
2003-09-10 19:53 Subodh Shrivastava
2003-09-10 21:09 ` Patrick Mochel
2003-09-10 20:44   ` Subodh Shrivastava
2003-09-11  0:12     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-09-10  0:38 Patrick Mochel
2003-09-10 13:04 ` Daniele Venzano
2003-09-10 18:10 ` Pavel Machek
2003-09-11  4:45 ` Michael Frank
2003-09-11  6:06 ` CaT
2003-09-01 10:57 Éric Brunet
2003-08-30 21:25 Patrick Mochel
2003-08-31 12:31 ` Felipe Alfaro Solana
2003-08-31 13:04   ` Mathieu LESNIAK
2003-09-02 18:13     ` Patrick Mochel
2003-09-02 23:50       ` Éric Brunet
2003-09-02 23:59         ` Patrick Mochel
2003-09-03  9:41       ` Mathieu LESNIAK
2003-09-03 22:41         ` Patrick Mochel
2003-09-04  9:34           ` Éric Brunet
2003-09-04 19:34             ` Patrick Mochel
     [not found]           ` <20031013194127.GA16791@lps.ens.fr>
2003-10-18  9:48             ` =?unknown-8bit?Q?=C9ric?= Brunet
2003-08-31 21:28 ` Pavel Machek
2003-08-31 22:15 ` Pavel Machek

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=20030909105323.GA14859@lps.ens.fr \
    --to=eric.brunet@lps.ens.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    /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®