On Monday 17 November 2003 10:45, Patrick Mochel wrote:> > Currently, patrick's code isn't working for me anymore either. I think> > it's because I haven't figured out how I had ACPI set up last time> > (performance covernor, probably. If I tell it to use the userspace> > governor, there's still nothing in /sys/devices/system/cpu/cpu0, the> > directory is empty. Maybe the documentation isn't up to date anymore, I> > don't know...) When I tried to suspend with it, it sort of worked but> > the writing to disk phase (which never caused a problem before) had a> > visible pause between each sector written, and writing out the 3000> > sectors took over 5 minutes, and the end result wasn't something it could> > resume from anyway. Sigh...>> Are you using preempt? There was a similar problem reported a while back> that was solved by disabling it. Though it's not a true fix, it should at> least get you going again.

That might explain some stuff. I'm now getting messages from my orinoco card during the writing phase about negotiating to talk with the access point, which is interfering with the writing of the dots. That didn't happen before.

Might it also be possible to just invent a new spinlock, grab it at the start of suspend, and release it at the end of resume? (It's not like suspend really needs to be preempted. I vaguely remember a "disable_preempt" call, but haven't a clue what it or its semantics might actually be.)

I have an appointment in half an hour but I'll give it a shot this evening.