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 60007] New: BUG: nouveau crashes in various ways in 32-bits Fedora 18
Date: Tue, 29 Jan 2013 09:47:19 +0000	[thread overview]
Message-ID: <bug-60007-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 60007
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: BUG: nouveau crashes in various ways in 32-bits Fedora
                    18
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: cpanceac-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 73815
  --> https://bugs.freedesktop.org/attachment.cgi?id=73815&action=edit
messages

During normal usage, xorg crashes in various ways. In dmesg and Xorg.0.log i
didn't find anything. In /var/log/messages, i did found various messages from
nouveau. I'll attach the file. This happens often: xorg restarts, or just
temprarily loses the "display" function, or artefacts are shown whenever i lock
gnome. 

Roy Spliet says that nv_wo32() has a problem, on 32-bit version.

From #nouveau: 

<RSpliet> nouveau_gpuobj_create:134 says nv_wo32(gpuobj, i, 0x00000000);
<RSpliet> the second parameter is supposed to be 64-bit, but i is 32-bits

Hopefully this will be fixed soon. Most of my family computers have NVIDIA
video cards and all that were migrated to Fedora 18 have these kinds of
problems :)

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

[-- Attachment #1.2: Type: text/html, Size: 2960 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-01-29  9:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  9:47 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-60007-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-01-29  9:53   ` [Bug 60007] BUG: nouveau crashes in various ways in 32-bits Fedora 18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-29 10:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-29 10:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-29 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-30  9:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-30 15:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 20:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  6:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03  7:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 20:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 20:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 21:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-05 21:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 16:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 11:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 17:46   ` 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-60007-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.