From owner-freebsd-mobile Sat Aug 10 13:28:37 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 543EE37B400 for ; Sat, 10 Aug 2002 13:28:34 -0700 (PDT) Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB94C43E65 for ; Sat, 10 Aug 2002 13:28:33 -0700 (PDT) (envelope-from metrol@metrol.net) Received: (qmail 18130 invoked from network); 10 Aug 2002 20:28:32 -0000 Received: from unknown (HELO metlap.priv.metrol.net) ([66.92.40.27]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Aug 2002 20:28:32 -0000 Content-Type: text/plain; charset="iso-8859-1" From: "Michael W. Collette" To: Andy Sparrow Subject: Re: Thinkpad T23 Coming Out of Sleep Date: Sat, 10 Aug 2002 13:28:29 -0700 User-Agent: KMail/1.4.2 Cc: plasma , FreeBSD Mailing Lists References: <20020810163207.6D3A5FE@CRWdog.demon.co.uk> In-Reply-To: <20020810163207.6D3A5FE@CRWdog.demon.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200208101328.29082.metrol@metrol.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Saturday 10 August 2002 09:32 am, Andy Sparrow wrote: > > I was thinking that this might be mouse related. It seemed to happen > > when I was wiggling the mouse as the system was coming back to life. It > > was just too intermittent to be sure that it was related. > > Hmmm... > > > On the other, this has > > a tendency to corrupt files so I don't want to see it happen a lot. > > You're using softupdates? Or not? Oh yeah. Never leave home without it! :) > I've found that this seems to make the filesystems much more resilient - > leastways, operator intervention is only extremely rarely required here > after a crash, and I've certainly not noticed any corrupt files (of > course, if they were open/being written/being edited, it's hard to say > how anything could help you much there....) Again, it's real tough to say. It doesn't happen often enough to relate the crashes to other glitches. They only "seem" to coincide. For instance, I use KNotes quite a bit for keeping odds and ends in. Following one of these sleep induced crashes a couple of the notes got glitched pretty bad. Was it a problem with KNotes? A file that was open that didn't recover? There's just not enough data to know if there is a relationship or not. There have been other little things like this over time, but even these are rare. The vast majority of the time fsck runs on the reboot and everything comes back perfectly. When you consider I only crash from sleep mode 5-10% of the time, and of those maybe 5-10% exhibit any post reboot problems it is about impossible to know if the two are related. It may be that I'm incorrectly associating a big event happening (system crash) to a smaller unrelated (note corruption) event. I just don't know. Later on, -- "Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read." - Groucho Marx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message