On Wed, Jul 14, 2010 at 15:57:32 +0200, Vincent Danjean wrote:

> reopen 545125
> found 545125 2.6.32-17
> thanks
> 
>   Hi,
> 
>   Even if the problem occurs less often, I still experiment it sometimes
> with 2.6.32-17.
>   The last time (yesterday), just after a resume, any new processus
> segfault within the ld.so code... So I rebooted.
>   And today, I discovered, just before submitting a new bug, that the
> fact that bash core dump each time I hit [tab] or [backspace] was due
> to a disk corruption of bash binary (ie pb fixed by reinstalling my current
> version of bash). I will now start a global fsck to check if other
> on-disk structures have been corrupted or not.
>   So, this bug is not fully fixed.
> 
New patch in mainline:

commit cd9f040df6ce46573760a507cb88192d05d27d86
Author: Linus Torvalds <torva...@linux-foundation.org>
Date:   Sun Jul 18 09:44:37 2010 -0700

    drm/i915: add 'reclaimable' to i915 self-reclaimable page allocations
    
    The hibernate issues that got fixed in commit 985b823b9192 ("drm/i915:
    fix hibernation since i915 self-reclaim fixes") turn out to have been
    incomplete.  Vefa Bicakci tested lots of hibernate cycles, and without
    the __GFP_RECLAIMABLE flag the system eventually fails to resume.
    
    With the flag added, Vefa can apparently hibernate forever (or until he
    gets bored running his automated scripts, whichever comes first).
    
    The reclaimable flag was there originally, and was one of the flags that
    were dropped (unintentionally) by commit 4bdadb978569 ("drm/i915:
    Selectively enable self-reclaim") that introduced all these problems,
    but I didn't want to just blindly add back all the flags in commit
    985b823b9192, and it looked like __GFP_RECLAIM wasn't necessary.  It
    clearly was.
    
    I still suspect that there is some subtle reason we're missing that
    causes the problems, but __GFP_RECLAIMABLE is certainly not wrong to use
    in this context, and is what the code historically used.  And we have no
    idea what the causes the corruption without it.
    
    Reported-and-tested-by: M. Vefa Bicakci <bic...@superonline.com>
    Cc: Dave Airlie <airl...@gmail.com>
    Cc: Chris Wilson <ch...@chris-wilson.co.uk>
    Cc: KOSAKI Motohiro <kosaki.motoh...@jp.fujitsu.com>
    Cc: Hugh Dickins <hugh.dick...@tiscali.co.uk>
    Cc: sta...@kernel.org
    Signed-off-by: Linus Torvalds <torva...@linux-foundation.org>

Maybe this time it'll be fixed for good...

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature

Reply via email to