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 13257] New: using nouveau on NV17 kills the KDE VNC server
Date: Thu, 15 Nov 2007 08:24:45 -0800 (PST)	[thread overview]
Message-ID: <bug-13257-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: using nouveau on NV17 kills the KDE VNC server
           Product: xorg
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: debian-E6TheL+NHo3k1uMJSBkQmQ@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


using nouveau on NV17 kills the KDE VNC server

I connect to a distant desktop using VNC. The environment is KDE and I use its
VNC server, krfb.

The adapter is as following:

  01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go]
(rev a3)

Using nv, I used to connect and disconnect several times a day.

Using nouveau, I can only connect once. The second time, vncviewer fails.

First time
----------

VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Thu Nov 15 17:23:59 2007
 CConn:       connected to host localhost port 5599

Thu Nov 15 17:24:01 2007
 CConnection: Server supports RFB protocol version 3.3
 CConnection: Using RFB protocol version 3.3
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 6 (8bpp) rgb222
 CConn:       Using ZRLE encoding


Second time
-----------

VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Thu Nov 15 17:25:12 2007
 CConn:       connected to host localhost port 5599
 main:        End of stream


I only close the vncviewer window between the tries.

I tried "-log *:stdout:100" to get maximum information but nothing more is
printed.

Nothing is printed in syslog nor Xorg.0.log at the moment I try.

Last ouput of syslog is:

Nov 15 17:03:49 ourson kernel: [54925.848000] [drm] nouveau_fifo_free: freeing
fifo 1
Nov 15 17:03:51 ourson kernel: [54926.684000] [drm:nouveau_fifo_free] *ERROR*
Failed to idle channel 1 before destroy.Prepare for strangeness..
Nov 15 17:03:51 ourson kernel: [54926.684000] [drm] cleanning a channel with
graph in current context
Nov 15 17:03:51 ourson kernel: [54926.684000] [drm] nouveau_fifo_free: freeing
fifo 0
Nov 15 17:03:51 ourson kernel: [54927.524000] [drm:nouveau_fifo_free] *ERROR*
Failed to idle channel 0 before destroy.Prepare for strangeness..
Nov 15 17:05:09 ourson NetworkManager: <info>  Updating allowed wireless
network lists.
Nov 15 17:05:10 ourson NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error
received: org.freedesktop.NetworkManagerInfo.NoNetworks -
org.freedesktop.NetworkManagerInfo.NoNetworks.
Nov 15 17:17:02 ourson /USR/SBIN/CRON[14947]: (root) CMD (   cd / && run-parts
--report /etc/cron.hourly)
Nov 15 17:22:10 ourson kernel: [56028.228000] agpgart: Found an AGP 2.0
compliant device at 0000:00:00.0.
Nov 15 17:22:10 ourson kernel: [56028.228000] agpgart: Putting AGP V2 device at
0000:00:00.0 into 4x mode
Nov 15 17:22:10 ourson kernel: [56028.228000] agpgart: Putting AGP V2 device at
0000:01:00.0 into 4x mode
Nov 15 17:22:10 ourson kernel: [56028.308000] [drm] Allocating FIFO number 0
Nov 15 17:22:10 ourson kernel: [56028.308000] [drm] nouveau_fifo_alloc:
initialised FIFO 0
Nov 15 17:22:10 ourson kernel: [56028.308000] [drm] Allocating FIFO number 1
Nov 15 17:22:10 ourson kernel: [56028.308000] [drm] nouveau_fifo_alloc:
initialised FIFO 1
Nov 15 17:22:34 ourson NetworkManager: <info>  Updating allowed wireless
network lists.
Nov 15 17:22:34 ourson NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error
received: org.freedesktop.NetworkManagerInfo.NoNetworks -
org.freedesktop.NetworkManagerInfo.NoNetworks.

I have a nice .xsession-errors that I'll attach afterwards.


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

             reply	other threads:[~2007-11-15 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 16:24 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-13257-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-11-15 16:26   ` [Bug 13257] using nouveau on NV17 kills the KDE VNC server bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-01 19:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-01 21:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-25  2:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-08 13:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-27  3:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-27  9:01   ` 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-13257-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.