linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Armando Di Cianno <fafhrd@gentoo.org>
To: linuxppc-dev@ozlabs.org
Subject: Re: Test patch for sleep on Aluminium PowerBooks
Date: Mon, 08 Nov 2004 22:11:31 -0500	[thread overview]
Message-ID: <fc01eab7ddb069d0da7030a94b467f8f@nephilim.localdomain> (raw)
In-Reply-To: <1098870636.6159.13.camel@gaston>


[-- Attachment #1.1: Type: text/plain, Size: 1475 bytes --]

On 2004-10-27 05:50:36 -0400 Benjamin Herrenschmidt 
<benh@kernel.crashing.org> wrote:
> This is an experimental patch against 2.6.9. It concerns the ATI based
> Aluminium PowerBook. The nVidia based ones aren't concerned at all, 
> and
> the iBook G4 will have to wait a bit more for me to get the video 
> wakeup
> code right.

Hello all; a little late in responding to this, but I wanted to ask 
some questions concerning possible issues I've been having.  I'm 
running on an AluBook 1.5Ghz, Linux kernel 2.6.9.  I suppose this is 
mainly addressed to Ben H.

Does this patch do, or should have to do, anything special to 
"normalize" the mounted filesystems before sleep?  When I patched the 
kernel first, I was running XFS, and of course that is notorious for 
file corruptions with power abnormalities on a system.  I started to 
get really odd file corruptions, where 'ls file' would should the 
file, but 'ls -l file' would not.

I switched to ReiserFS (v3) now, and have seen symptoms like this 
problem caused appear once more (but not to the extent that XFS showed 
[where I thought my system was disintegrating before my eyes]).

Is there something that was overlooked in the patch, or something that 
I'm overlooking that needs to be done?

If filesystems do not need to be "normalized" at sleep, what 
filesystems are known to work?  (Hesistant about ext3, as it's quite 
slow, imho, but I'll go that route if needed, I suppose).

Thanks!

__Armando Di Cianno

[-- Attachment #1.2: RFC3156.txt --]
[-- Type: text/plain, Size: 65 bytes --]

RFC3156 defines security multipart formats for MIME with OpenPGP.

[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

  parent reply	other threads:[~2004-11-09  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  9:50 Test patch for sleep on Aluminium PowerBooks Benjamin Herrenschmidt
2004-10-27 17:50 ` David Woodhouse
2004-11-09  3:11 ` Armando Di Cianno [this message]
2004-11-22 22:20   ` Benjamin Herrenschmidt
2004-11-22 22:26     ` Colin Leroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fc01eab7ddb069d0da7030a94b467f8f@nephilim.localdomain \
    --to=fafhrd@gentoo.org \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).