From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM lockups since 2.6.25
Date: Thu, 17 Apr 2008 02:14:25 +0200 [thread overview]
Message-ID: <200804170214.26368.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0804162243550.25729@artax.karlin.mff.cuni.cz>
On Wednesday, 16 of April 2008, Mikulas Patocka wrote:
> > So it didn't help, I just got this (2.6.25-rc8):
> >
> > (I have turned lockdep on few days ago, and it seems to try to release a
> > lock that's not held ... and then reacquire that lock again and deadlock)
>
> BTW. the first one message happened immediatelly after APM resume, the
> second message 2 minutes later.
>
> APMD didn't set time after resume, it's completely locked up.
Well, unfortunately, APM uses the generic code for suspending and resuming
devices, but it doesn't use the freezing of tasks, so it's not very reliable in
its present form.
Thanks,
Rafael
next prev parent reply other threads:[~2008-04-17 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 15:15 APM lockups since 2.6.25 Mikulas Patocka
2008-03-20 10:31 ` Rafael J. Wysocki
2008-03-21 0:00 ` Mikulas Patocka
2008-03-21 0:27 ` Rafael J. Wysocki
2008-03-21 20:01 ` APM crashes when IO is going on Mikulas Patocka
2008-03-21 21:15 ` Rafael J. Wysocki
2008-03-21 21:17 ` Mikulas Patocka
2008-03-21 21:45 ` Rafael J. Wysocki
2008-03-21 22:49 ` Mikulas Patocka
2008-03-21 22:51 ` Rafael J. Wysocki
2008-03-22 0:29 ` Mikulas Patocka
2008-03-25 8:49 ` Pavel Machek
2008-03-25 8:46 ` Pavel Machek
2008-04-16 20:42 ` APM lockups since 2.6.25 Mikulas Patocka
2008-04-16 20:45 ` Mikulas Patocka
2008-04-17 0:14 ` Rafael J. Wysocki [this message]
2008-04-22 13:00 ` 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=200804170214.26368.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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