[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#703640: marked as done (src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework)

Your message dated Fri, 26 Apr 2013 12:43:37 +0100
with message-id <1366976617.5955.2.camel@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#703640: src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework
has caused the Debian Bug report #703640,
regarding src:linux: [3.8 -> 3.8.1 regression]: Resume from suspend stuck with framebuffer locking rework
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
703640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703640
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 3.8.3-1~experimental.1
Severity: important
Tags: upstream

Hi,

As mentioned in the subject, the following commit prevents me to resume from
suspend in kernel ≥ 3.8.1: 

commit cace7c323ddde7358ab2f2390ece964c55f30330
Author: Alan Cox <alan@linux.intel.com>
Date:   Fri Jan 25 10:28:15 2013 +1000

    fb: rework locking to fix lock ordering on takeover
        
    commit 50e244cc793d511b86adea24972f3a7264cae114 upstream.
                
    Adjust the console layer to allow a take over call where the caller
    already holds the locks.  Make the fb layer lock in order.
                            
    This is partly a band aid, the fb layer is terminally confused about the
    locking rules it uses for its notifiers it seems.
                                        
    [akpm@linux-foundation.org: remove stray non-ascii char, tidy comment]
    [akpm@linux-foundation.org: export do_take_over_console()]
    [airlied: cleanup another non-ascii char]
    Signed-off-by: Alan Cox <alan@linux.intel.com>
    Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Jiri Kosina <jkosina@suse.cz>
    Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
    Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

I didn't try to boot with this commit reverted, and looking at its size,
I fear there will be some conflict to solve before attempting to do so.

I guess it could be interesting to try 3.9-rc. to see how it
behaves (I didn't see what have been merged in this area in the last
merge window). I might try to connect through ssh to see if I get a
trace.

Cheers,
Vincent


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Fri, 2013-04-26 at 11:51 +0200, Vincent Blut wrote:
> #forgot to tag this bug, sorry!
> fixed 703640 3.8.5-1~experimental.1
> thanks

So it can be closed...

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                                    A fail-safe circuit will destroy others.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: