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 64488] New: 3.10.0-rc1: WARNING: at drivers/gpu/drm/drm_crtc.c:84 drm_fb_helper_restore_fbdev_mode+0x10/0x40()
Date: Sun, 12 May 2013 10:15:30 +0000	[thread overview]
Message-ID: <bug-64488-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 64488
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: 3.10.0-rc1: WARNING: at drivers/gpu/drm/drm_crtc.c:84
                    drm_fb_helper_restore_fbdev_mode+0x10/0x40()
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: ronald645-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86 (IA32)
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

Created attachment 79192
  --> https://bugs.freedesktop.org/attachment.cgi?id=79192&action=edit
Last DRM warning (typed over from a photo). Note the tainted flags(!)

Since a few cycles, it seems that nouveau is preventing the kernel from
correctly displaying OOPS, BUGS and Warnings etc etc.

This is because the DRM system seems to provide warnings each time the kernel
kills X and moves to console to display these messages.

Today, I enabled some debug options and captured the last WARNING by this
system. NOTE: The oops is typed over from a camera photo, so it might not be
entirely accurate.

This is an 32bit UP system with the notorious(?) Geforce FX5200 (NV34). I
attached the Warning as an attachment.

I modified rsyslog to log directly to disk, hoping to capture more information.
When that happens, I will post more.

I think this is also a regression, usually I got errors about page faults and
stuff.

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

[-- Attachment #1.2: Type: text/html, Size: 3236 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-05-12 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 10:15 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-64488-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-05-12 10:40   ` [Bug 64488] 3.10.0-rc1: WARNING: at drivers/gpu/drm/drm_crtc.c:84 drm_fb_helper_restore_fbdev_mode+0x10/0x40() bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-12 10:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-13  6:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-13 10:37   ` 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-64488-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.