From: Pavel Machek <pavel@ucw.cz>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.18-rc1 broke resume from APM suspend on Latitude CPi
Date: Sat, 8 Jul 2006 15:51:57 +0200 [thread overview]
Message-ID: <20060708135156.GA2912@elf.ucw.cz> (raw)
In-Reply-To: <200607081338.k68Dcvux007655@harpo.it.uu.se>
On Sat 2006-07-08 15:38:57, Mikael Pettersson wrote:
> On Fri, 7 Jul 2006 21:47:37 +0000, Pavel Machek wrote:
> >> Kernel 2.6.18-rc1 broke resume from APM suspend (to RAM)
> >> on my old Dell Latitude CPi laptop. At resume the disk
> >> spins up and the screen gets lit, but there is no response
> >> to the keyboard, not even sysrq. All other system activity
> >> also appears to be halted.
> >>
> >> I did the obvious test of reverting apm.c to the 2.6.17
> >> version and fixing up the fallout from the TIF_POLLING_NRFLAG
> >> changes, but it made no difference. So the problem must be
> >> somewhere else.
> >
> >driver model changes?
> >
> >Can you retry with minimum drivers loaded, init=/bin/bash?
>
> Did that, no change.
Too bad... Quite a lot of driver model changes were merged in -rc1...
Can you remove device_*() calls from apm.c and see what happens?
(First do it on 2.6.17 to confirm apm still works without driver
model...)
Pavel--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-07-08 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 13:38 [BUG] 2.6.18-rc1 broke resume from APM suspend on Latitude CPi Mikael Pettersson
2006-07-08 13:51 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 19:01 Mikael Pettersson
2006-07-07 21:47 ` 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=20060708135156.GA2912@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.