NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/58053: Issues on -current with nouveau graphics



The following reply was made to PR kern/58053; it has been noted by GNATS.

From: Paul Goyette <paul%whooppee.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/58053: Issues on -current with nouveau graphics
Date: Sat, 18 May 2024 10:41:49 -0700 (PDT)

 > The most common problem results in the following console message:
 >
 > 	nouveau0: autoconfiguration error: error: DRM: core
 > 	notifier timeout
 >
 > This occurs frequently whenever I switch back and forth from a
 > console session to an X session using ctrl-alt-f<n>.  Often there
 > is a delay before which  keystrokes are not recognized for a few
 > seconds.  Most of the time the system recovers, but not always.
 >
 > In the X session, cursor movement can be "jerky".  The cursor
 > will follow mouse movement for a bit, and then stop/pause before
 > continuing.  The stop/pause usually occurs when the cursor is
 > ready to enter a region which needs to change the curson icon
 > (Ie, entering a button needsd cursor to become hand/finger).  As
 > above, the stall only lasts a couple of seconds, after which (in
 > most cases) normal cursor tracking resumes.
 
 This seems to happen _every_ time I switch between Ctrl-Alt-F1 and
 Ctrl-Alt-F5.
 
 The jerky/stalling cursor movement occurs only in certain apps.
 It is consistent when running either gnucash or libreoffice (both
 from pkgsrc).  Interestingly, firefox seems to be unaffected.
 The cursor stalling also generates the timeout messages, although
 occassionally a different message is generated:
 
  	[ 318189.124414] nouveau0: autoconfiguration error: error:
  	DRM: base-0: timeout
 
  	[ 31564.485889] kqueue_register: cmTC_e3127[8440]: event
  	type 6 not supported for file type -1/? (error 22)
 
 > 	nouveau0: autoconfiguration error: error: fifo: fault
 > 	00 [READ] at 00000000000be000 engine 04 [BAR1] client
 > 	07 [HUB/HOST_CPU] reason 02 [PTE] on channel -1
 > 	[007fce7000 unknown]
 >
 > (The specific values printed vary.)
 >
 > The final issue occurs when xdm is exiting, either during system
 > shutdown or whwen I terminate an X session.  The following message
 > gets logged, for channel values of 4 down to 1:
 >
 > 	nouveau0: autoconfiguration error: error: user: failed
 > 	to idle channel <n> [user]
 >
 > There is a roughly 11-second timeout associated with these errors,
 > but the system does recover; the timeout process takes 2+ minutes.
 
 The actual timeout  is usually closer to 15 seconds, and most of the
 channels fail more than once.  (Usually channel 4 fails twice, while
 channel 2 can fail five or moore times.)
 
 
 These errors make using the workstation cumbersome/awkward at best.
 
 
 +---------------------+--------------------------+----------------------+
 | Paul Goyette (.sig) | PGP Key fingerprint:     | E-mail addresses:    |
 | (Retired)           | 1B11 1849 721C 56C8 F63A | paul%whooppee.com@localhost    |
 | Software Developer  | 6E2E 05FD 15CE 9F2D 5102 | pgoyette%netbsd.org@localhost  |
 | & Network Engineer  |                          | pgoyette99%gmail.com@localhost |
 +---------------------+--------------------------+----------------------+
 


Home | Main Index | Thread Index | Old Index