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 15164] New: PTIMER broken in DRM (regression)
Date: Fri, 21 Mar 2008 15:16:18 -0700 (PDT)	[thread overview]
Message-ID: <bug-15164-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=15164

           Summary: PTIMER broken in DRM (regression)
           Product: xorg
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: pq-X3B1VOXEql0@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


The commit 1021799b6ca6b195ad2d5f002e45668f69c44651 in DRM,
http://gitweb.freedesktop.org/?p=mesa/drm.git;a=commit;h=1021799b6ca6b195ad2d5f002e45668f69c44651
"nouveau: do not set on-board timer's numerator/denominator to bad values"
breaks my nv20 (gf3) card.

When starting X, mode is set, I get a screen with colorful garbage on top,
black&white noise on the bottom, and black in the middle for couple of seconds
during which mouse cursor moves fine. Then I'm back in text console with a
kernel gone out to lunch.

There are two problems:
1. the mentioned commit apparently also breaks PTIMER, and
2. nouveau_fifo_free() uses PTIMER for a timeout, which will never happen,
hence the kernel becomes a zombie.

While the kernel is a zombie, I can SysRq tErminate, after which I can SysRq
show Program counter, which says it is in nouveau_fifo_free. All I can do is
SysRq reBoot.

Reverting the mentioned commit fixes the problem 1, and consequently the
problem 2. does not trigger.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-03-21 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 22:16 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-15164-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-25 18:40   ` [Bug 15164] PTIMER broken in DRM (regression) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 18: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-15164-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.