All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 69349] New: Random image corruptions (in Debian Wheezy with Linux 3.2)
Date: Sat, 14 Sep 2013 08:25:11 +0000	[thread overview]
Message-ID: <bug-69349-8800@http.bugs.freedesktop.org/> (raw)


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

https://bugs.freedesktop.org/show_bug.cgi?id=69349

          Priority: medium
            Bug ID: 69349
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: Random image corruptions (in Debian Wheezy with Linux
                    3.2)
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: paulepanter-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

Created attachment 85813
  --> https://bugs.freedesktop.org/attachment.cgi?id=85813&action=edit
Screenshot taken with `import` after opening a new tab in Iceweasel 17.0.8

Using Debian Wheezy with

    linux-image-3.2.0-4-686-pae 3.2.46-1+deb7u1
    xserver-xorg-video-nouveau 1:1.0.1-5
    libglu1-mesa:i386 8.0.5-4+deb7u2
    libdrm2                                2.4.40-1~deb7u2
    libudev0                               175-7.2
    xserver-xorg-core [xorg-video-abi-12]  2:1.12.4-6

sometimes there is an image corruption where some areas are garbled with other
colors. See the attached screenshot taken with `import` from the ImageMagick
suite. (What is that type of corruption called?)

The obfuscation was done with the following command.

    $ convert 20130909-Debian_Wheezy-nouveau-corruption.png -draw "rectangle
231,165 1703,953" 20130909-Debian_Wheezy-nouveau-corruption--obfuscated.png

This issue happened five times and I do not know how to force it. Three of
these five times it happened after resuming from suspend to RAM. Additionally
after these corruption start, the system is going to freeze after some time.
There are no error messages in `/var/log/syslog`, `/var/log/messages`,
`/var/log/Xorg.0.log` and `~/.xsession-errors`.

Please tell me, what else you need for debugging.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3563 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-09-14  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14  8:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-69349-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-14 15:47   ` [Bug 69349] Random image corruptions (in Debian Wheezy with Linux 3.2) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-14 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-16 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-17  2:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01  0:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-02  7:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-02  7:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-04  6:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-23  6:57   ` [Bug 69349] Random image corruptions bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  4:54   ` [Bug 69349] [NV98] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-69349-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.