All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 120591] BUG() in dmesg after loading nouveau module
Date: Sat, 18 Jun 2016 16:36:29 +0000	[thread overview]
Message-ID: <bug-120591-2300-2u24xJYrSd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-120591-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=120591

Ilia Mirkin <imirkin@alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imirkin@alum.mit.edu

--- Comment #2 from Ilia Mirkin <imirkin@alum.mit.edu> ---
Looks like

commit f045f459d925138fe7d6193a8c86406bda7e49da
Author: Ben Skeggs <bskeggs@redhat.com>
Date:   Thu Jun 2 12:23:31 2016 +1000

    drm/nouveau/fbcon: fix out-of-bounds memory accesses

does not properly deal with disabled fbdev emulation.

Can you add a

if (fbcon->helper.fbdev)

before that added line in nouveau_fbcon_init? I assume that will resolve your
issue.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-06-18 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 16:17 [Bug 120591] New: BUG() in dmesg after loading nouveau module bugzilla-daemon
2016-06-18 16:18 ` [Bug 120591] " bugzilla-daemon
2016-06-18 16:36 ` bugzilla-daemon [this message]
2016-06-19  9:00 ` bugzilla-daemon
2016-06-19  9:01 ` bugzilla-daemon
2016-06-19  9:01 ` bugzilla-daemon
2016-06-19 17:30 ` bugzilla-daemon
2016-06-20  0:27 ` bugzilla-daemon
2016-06-20 11:32 ` bugzilla-daemon
2016-06-24 22:30 ` bugzilla-daemon

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-120591-2300-2u24xJYrSd@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.