From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4c39f95205f7f5d1af72be754dbbe531@plan9.bell-labs.com> From: presotto@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] bitsy suspend/resume (was: ipaq dual pcmcia sleeve) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-jsajzwbolfucsllolwnvuqsgnv" Date: Tue, 22 Oct 2002 19:20:49 -0400 Topicbox-Message-UUID: 0a1b1dbc-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-jsajzwbolfucsllolwnvuqsgnv Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Perhaps we're not getting memory to refresh itself when we sleep and its contents is decaying? --upas-jsajzwbolfucsllolwnvuqsgnv Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Tue Oct 22 17:40:20 EDT 2002 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Tue Oct 22 17:40:19 EDT 2002 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id A393119AB7; Tue, 22 Oct 2002 17:40:10 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 4D24019AA0 for <9fans@cse.psu.edu>; Tue, 22 Oct 2002 17:39:47 -0400 (EDT) Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id XAA29045 for <9fans@cse.psu.edu>; Tue, 22 Oct 2002 23:38:28 +0200 (MET DST) Received: from zamenhof.cs.utwente.nl by zeus.cs.utwente.nl (8.10.2+Sun/csrelay-Sol1.4/RB) id g9MLcRQ05554; Tue, 22 Oct 2002 23:38:27 +0200 (MEST) Received: from localhost (belinfan@localhost) by zamenhof.cs.utwente.nl (8.11.6+Sun/8.10.2) with SMTP id g9MLcRe12274 for <9fans@cse.psu.edu>; Tue, 22 Oct 2002 23:38:27 +0200 (MEST) Message-Id: <200210222138.g9MLcRe12274@zamenhof.cs.utwente.nl> X-Authentication-Warning: zamenhof.cs.utwente.nl: belinfan@localhost didn't use HELO protocol To: 9fans@cse.psu.edu In-reply-to: Your message of "Tue, 22 Oct 2002 17:01:33 +0200." References: From: Axel Belinfante X-Organisation: University of Twente, Department of Computer Science, Formal Methods and Tools Group, PO Box 217, NL-7500 AE Enschede, The Netherlands X-Phone: +31 53 4893774 X-Telefax: +31 53 4893247 X-Face: 3YGZY^_!}k]>-k'9$LK?8GXbi?vs=2v*ut,/8z,z!(QNBk_>~:~"MJ_%i`sLLqGN,DGbkT@ N\jhX/jNLTz2hO_R"*RF(%bRvk+M,iU7SvVJtC*\B6Ud<7~`MGMp7rCI6LVp=%k=HE?-UCV?[p\$R? mI\n2/!#3/wZZsa[m7d;PKWiuH6'~ Subject: [9fans] bitsy suspend/resume (was: ipaq dual pcmcia sleeve) Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 22 Oct 2002 23:38:27 +0200 For your information: with my (admittedly hacked) kernel (based on the tar ball), (and minor hacking of the dual sleeve code) I get: without sleeve, light is slightly on before suspending; suspending only once rio has started (booting completed): suspend followed by resume within ca. 2 seconds: OK (and I see the debugging code on the serial line console) suspend followed by resume later than ca. 2 seconds: not OK display comes back (most of the times) but light is not switched back on and screen/buttons don't respond, and debugging output on console is garbled (if it appears at all) With the empty sleeve I get more or less the same effect (i.e. quick suspend/resume within the ca 2 (3?) seconds works) So, I have a short `window' in which I can resume; if I wait too long, I can see the screen, but that seems to be all. With the wavelan in the sleeve, suspend button seems to do almost nothing -- except that ping no longer works, even though the one led on the wavelan remains continously lit, and the other still occasionally blinks. However, cat/net/ipselftab returns nothing. Now running startip gives me: 'echo: write error: couldn't configure device'. Axel. > Ok. I'll build a fresh new kernel with the sources in the tar ball > and let you know of any problem. > In the mean time, you could try downloading the tar ball again, trying > it, and letting me know the behaviour of suspend/resume on your bitsy. --upas-jsajzwbolfucsllolwnvuqsgnv--