linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Courbot <acourbot@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>,
	<dri-devel@lists.freedesktop.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Nouveau crashes in 4.6-rc on arm64
Date: Fri, 8 Apr 2016 13:47:49 +0900	[thread overview]
Message-ID: <570737F5.30105@nvidia.com> (raw)
In-Reply-To: <57064992.1060509@arm.com>

Hi Robin,

On 04/07/2016 08:50 PM, Robin Murphy wrote:
> Hello,
>
> With 4.6-rc2 (and -rc1) I'm seeing Nouveau blowing up at boot, from the
> look of it by dereferencing some offset from NULL inside
> nouveau_fbcon_imageblit(). My setup is an old XFX 7600GT card plugged
> into an ARM Juno r1 board, which works fine with 4.5 and earlier.
>
> Attached are a couple of logs from booting arm64 defconfig plus DRM and
> Nouveau enabled - the second also has framebuffer console rotation
> turned on, which interestingly seems to move the point of failure, and
> the display does eventually come up to show the tail end of the panic in
> that case.
>
> I might be able to find time for a full bisection next week if isn't
> something sufficiently obvious to anyone who knows this driver.

Looking at the log it is not clear to me what could be causing this. I 
can boot 4.6-rc2 with a GM206 card without any issue. A bisect would 
indeed be useful here.

Thanks,
Alex.

  reply	other threads:[~2016-04-08  4:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 11:50 Nouveau crashes in 4.6-rc on arm64 Robin Murphy
2016-04-08  4:47 ` Alexandre Courbot [this message]
2016-04-08  6:27   ` Ilia Mirkin
2016-04-08 18:46   ` Robin Murphy
2016-04-11  7:22     ` Alexandre Courbot
2016-04-11  7:55       ` Alexandre Courbot
2016-04-20  4:35       ` Alexandre Courbot
2016-04-20 10:44         ` Robin Murphy
2016-04-20 10:51           ` Robin Murphy

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=570737F5.30105@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).