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 88868] PowerPC e5500, kernel crash, GT520, GT610
Date: Sun, 01 Feb 2015 22:34:02 +0000	[thread overview]
Message-ID: <bug-88868-8800-aftyd1kzhA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88868-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #16 from Dmitriy <oboturoff-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Created attachment 113026
  --> https://bugs.freedesktop.org/attachment.cgi?id=113026&action=edit
incorrect image

Dear Ben and Ilia. Thank you for your answers.

There is no BIOS on our device. We have u-boot instead of it. But that patch
from Ben is necessary even in kernel of the version 3.18.5.

The result of the monitor connection is in attach picture. The image is
incorrect. I tested both video cards GT520 and GT610, the result is the same.

There are some errors in the initialisation log.
nouveau E[   PFIFO][0000:01:00.0] PBDMA0: (unknown bits 0x00004000)
nouveau E[   PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data
0x00000000
.......
nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
nouveau 0000:01:00.0: registered panic notifier

Could the wrong work of video card  be the reason of these errors?  Or what
else is to be tested to find out the cause of wrong function.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2015-02-01 22:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:06 [Bug 88868] New: PowerPC e5500, kernel crash, GT520, GT610 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-88868-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-01-29 15:12   ` [Bug 88868] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 16:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 19:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 22:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30  1:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30  1:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30  9:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30  9:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30  9:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 10:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 22:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-02-01 22:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 10:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 10:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 12:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-03 16:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-03 23:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04  9:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 16:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:55   ` 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-88868-8800-aftyd1kzhA@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.