lkml.org 
[lkml]   [2006]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectDisplay corruption with radeonfb after resuming from suspend-to-ram
    From
    Hi,
    I have a hard-to-reproduce problem with radeonfb and suspend-to-ram:

    I'm using radeonfb with fbcon in a pure console environment for most
    os the time (with mplayer on X11 being the rare exception) and I
    sometimes encounter display corruption after resuming from suspend to
    RAM. My notebook is a ThinkPad X31 with this Radeon model:

    0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
    Subsystem: IBM: Unknown device 052f
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
    Latency: 66 (2000ns min), Cache Line Size: 0x08 (32 bytes)
    Interrupt: pin A routed to IRQ 11
    Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
    Region 1: I/O ports at 3000 [size=256]
    Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
    Expansion ROM at c0120000 [disabled] [size=128K]
    Capabilities: <available only to root>

    Resuming from suspend-to-ram works flawless in roughly 98% of all cases, but
    sometimes the display gets corrupted; some bits are set in the display in a
    weird way and the display starts to shift with every line break. An example:

    $ foo
    $ foo
    $ foo

    (The display wraps around on the after side for each line)

    When running reset(1) the display returns to a state where the whole screen is shifted
    to the left by two chars.

    The last time the problem occured I started X11 to check, whether it is affected as well
    and everything seemed alright expect a blocky area following the mouse cursor, but after
    roughly 30 seconds the system locked up hard.

    I cannot really reproduce it reliably, but if someone tells me which data I would
    need to collect (a register dump or something similar?) I can send it the next time
    the problem occurs.

    This problem is not specific to the 2.6.15 kernel, it occured with several previous
    kernels as well.

    Cheers,
    Moritz
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-01-28 16:55    [W:3.889 / U:1.572 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site