similar to: [PATCH] drm/nouveau/fb: fix suspend/resume fbcon

On 03/10/13 15:41, Christoph Rudorff wrote: > On resume of a hibernated notebook, I get garbled virtual consoles. > > fb_set_suspend(*dev, state == 0 means dev is running ...) > > This patch fixes that issue for me: > Ouch, nice catch Christoph :) Seems like the following commit flipped the logic unintentionally, thus causing the issue. Stange enough I have no problems with

Current code disables fbcon acceleration before fbcon is suspended, leading to corrupted console after resume from s2disk. In a similar fashion we must make sure that fbcon acceleration is enabled before we revive the console. With this patch s2disk works correctly on my MacBookPro6,2 with GT216 [GeForce GT 330M] hibernate: kernel: nouveau [ DRM] suspending fbcon... kernel: nouveau [

On Tue, Nov 19, 2013 at 05:59:13PM +0100, Christoph Rudorff wrote: > Current code disables fbcon acceleration before fbcon is suspended, > leading to corrupted console after resume from s2disk. In a similar > fashion we must make sure that fbcon acceleration is enabled before we > revive the console. > > With this patch s2disk works correctly on my MacBookPro6,2 with GT216 >

Am Donnerstag, den 03.10.2013, 23:50 +0100 schrieb Emil Velikov: > I'm not entirely sure this is correct. One needs to save and disable > accleration before suspending the fb. Please try the following > > - if (state == 0) > + if (state == 1) > nouveau_fbcon_save_disable_accel(dev); > fb_set_suspend(drm->fbcon->helper.fbdev, state); > - if (state == 1) > +

Hi, With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits I get following errors in kernel log (repeating much more often). (once there was a corrupted fbcon with matrix-like strings of unrecognizable glyph-strings hanging down from screen top border) These errors do stop once I switch to Xorg. [ 13.825627] nouveau E[ PFB][0000:02:00.0] trapped write at 0x0000408280 on

Hi Ilia, On Thu, 5 Dec 2013 10:55:06 -0500 Ilia Mirkin wrote: > On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont wrote: > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits > > I get following errors in kernel log (repeating much more often). > > (once there was a corrupted fbcon with matrix-like strings of > > unrecognizable glyph-strings hanging

On Wed, Dec 11, 2013 at 6:43 AM, Bruno Pr?mont <bonbons at linux-vserver.org> wrote: > Hi Ilia, > >> On Thu, 5 Dec 2013 10:55:06 -0500 Ilia Mirkin wrote: >> > On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont wrote: >> > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits >> > > I get following errors in kernel log (repeating

On 17.11.2013 00:22, Emil Velikov wrote: > On 04/10/13 01:54, Christoph Rudorff wrote: >> Am Donnerstag, den 03.10.2013, 23:50 +0100 schrieb Emil Velikov: >>> I'm not entirely sure this is correct. One needs to save and disable >>> accleration before suspending the fb. Please try the following >>> >>> - if (state == 0) >>> + if (state == 1)

On Wed, Jan 1, 2014 at 3:29 PM, Michele Baldessari <michele at acksyn.org> wrote: > On Wed, Dec 11, 2013 at 07:21:05AM -0500, Ilia Mirkin wrote: >> >> On Thu, 5 Dec 2013 10:55:06 -0500 Ilia Mirkin wrote: >> >> > On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont wrote: >> >> > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound

On 19.11.2013 19:48, Greg KH wrote: > On Tue, Nov 19, 2013 at 05:59:13PM +0100, Christoph Rudorff wrote: >> Current code disables fbcon acceleration before fbcon is suspended, >> leading to corrupted console after resume from s2disk. In a similar >> fashion we must make sure that fbcon acceleration is enabled before we >> revive the console. >> >> With this

On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont <bonbons at linux-vserver.org> wrote: > Hi, > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits > I get following errors in kernel log (repeating much more often). > (once there was a corrupted fbcon with matrix-like strings of > unrecognizable glyph-strings hanging down from screen top border) > >

On Wed, Dec 11, 2013 at 07:21:05AM -0500, Ilia Mirkin wrote: > >> On Thu, 5 Dec 2013 10:55:06 -0500 Ilia Mirkin wrote: > >> > On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont wrote: > >> > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits > >> > > I get following errors in kernel log (repeating much more often). > >>

Hi Ilia, > On Thu, 5 Dec 2013 10:55:06 -0500 Ilia Mirkin wrote: > > On Thu, Dec 5, 2013 at 10:17 AM, Bruno Pr?mont wrote: > > > With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits > > > I get following errors in kernel log (repeating much more often). > > > (once there was a corrupted fbcon with matrix-like strings of > > >

https://bugs.freedesktop.org/show_bug.cgi?id=57350 --- Comment #27 from Ankur <ankur at lipidity.com> --- Bug is still present with linux-3.8.4, xf86-video-nouveau-1.0.7 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

There's a short window between module load and fbcon initalization when it's possible for vgacon to write to VGA RAM. Nouveau uses this memory for different purposes, so if we are unlucky, it causes mysterious memory corruptions. For me, booting with nv_printk debug levels set to 5 was enough to trigger it. It manifested as long stream of: "trapped write at ... on channel 0x0001fea0

----- Mail original ----- > De: "Ilia Mirkin" <imirkin at alum.mit.edu> > ?: "pierre morrow" <pierre.morrow at free.fr> > Cc: nouveau at lists.freedesktop.org > Envoy?: Vendredi 31 Janvier 2014 21:16:40 > Objet: Re: [Nouveau] Help needed for bug 58556 > Unfortunately this is a *massive* bug... and confused by the "other" > very

On Wed, Jul 13, 2016 at 11:54:49AM +0200, Daniel Vetter wrote: > On Tue, Jul 12, 2016 at 06:49:34PM +0200, Peter Wu wrote: > > The FBIOPUT_CON2FBMAP ioctl takes a console_lock(). When this is called > > while nouveau was runtime suspended, a deadlock would occur due to > > nouveau_fbcon_set_suspend also trying to obtain console_lock(). > > > > Fix this by delaying

The vblank on nvc0 was not working correctly and would freeze X, I managed to track it down and fix it with some help from m.b.lankhorst, see https://bugs.freedesktop.org/show_bug.cgi?id=56692 for details. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20121106/27ceb48e/attachment.html> --------------

Hello List, I am trying to solve bug 58556 [1], but I will need some help as I don't understand all that is going on. The system is composed of an NV96 (9600 GT) and an NVAC (9400 M) card; acceleration is disabled, otherwise the system hangs at boot after initialising the NV96 card. The problem consist of a complete garbage screen in console mode, and a one-third gabage screen in GUI.

On 04/10/13 01:54, Christoph Rudorff wrote: > Am Donnerstag, den 03.10.2013, 23:50 +0100 schrieb Emil Velikov: >> I'm not entirely sure this is correct. One needs to save and disable >> accleration before suspending the fb. Please try the following >> >> - if (state == 0) >> + if (state == 1) >> nouveau_fbcon_save_disable_accel(dev); >>