Messages in this thread | | | Date | Tue, 22 Apr 2008 15:00:14 +0200 | From | Pavel Machek <> | Subject | Re: APM lockups since 2.6.25 |
| |
On Thu 2008-04-17 02:14:25, Rafael J. Wysocki wrote: > 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.
In theory, BIOS is reponsible for saving/restoring device state in APM case... maybe we could just remove those calls?
If that works for mikulas, that already handles 50% of people using apm ;-).
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |