<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Nov 11, 2008 at 2:09 PM, arne anka <span dir="ltr"><<a href="mailto:openmoko@ginguppin.de">openmoko@ginguppin.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> does no one else experience problems with suspend after turning off GSM<br>
> modem?<br>
<br>
</div>could you please prefix the subject with distribution used? thanks.<br>
i am not able to infer, what exactly you're doing:<br>
- disabling gsm via call to sysfs<br>
- calling apm -s manually<br>
?<br>
<br>
or<br>
- disabling gsm via call to sysfs<br>
- pressing pwr/hitting a button/ whatever your distribution offers to<br>
suspend<br>
?</blockquote><div><br>yes calling apm -s gives device or resource busy and pressing pwr button turns the screen off but not suspending, but u have ssh still active and everything still on, only screen off, so both ways disabling gsm via call to sysfs is disabling us from suspend <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
what i could think of is, that (either as script executed by apm or as<br>
part of your distribution's way to suspend) there are requests made to the<br>
gsm, to prepare suspend:<br>
- minimize rescanning<br>
- go to sleep state<br>
since gsm is powered of. these request do a) not return or b) not<br>
successfully<br>
case<br>
a) a timeout is probably to big -- decreasing might lead to b)<br>
b) the returncode != success in turn results in an uncatched exception<br>
that prevents any further process of suspend<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div><br>yes that's what i believe but problem is i don't know how the distribution goes to do the suspend exactly, any references to how suspend is being called in om2008.9 ? <br>
<br>does the same occur in debian arne?<br></div></div><br></div>