dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Skeggs <skeggsb@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: Kernel panic on nouveau during boot on NVIDIA NV118 (GM108)
Date: Sat, 3 Jun 2017 14:13:36 +1000	[thread overview]
Message-ID: <e08d0a00-96ba-595e-da35-a597cf8af40c@gmail.com> (raw)
In-Reply-To: <CAD8Lp45dr7UXaY5rZzT7822ThoWXPywBhpvGOsxLpGVCuDS52Q@mail.gmail.com>

On 06/03/2017 12:24 AM, Daniel Drake wrote:
> On Fri, Jun 2, 2017 at 4:01 AM, Chris Chiu <chiu@endlessm.com> wrote:
>> We are working with new desktop that have the NVIDIA NV118
>> chipset.
>>
>> During boot, the display becomes unusable at the point where the
>> nouveau driver loads. We have reproduced on 4.8, 4.11 and linux
>> master (4.12-rc3).
Can you get a kernel log with "nouveau.debug=debug" set please?

Also worth trying with "nouveau.config=NvForcePost=1" to see if that 
works around the issue.

Ben.

> 
> To save digging into the attachment, here is the crash:
> 
> nouveau 0000:01:00.0: pci: failed to adjust cap speed
> nouveau 0000:01:00.0: pci: failed to adjust lnkctl speed
> nouveau 0000:01:00.0: fb: 0 MiB DDR3
> divide error: 0000 [#1] SMP
> Modules linked in: hid_generic usbmouse usbkbd usbhid i915 nouveau(+)
> mxm_wmi i2c_algo_bit drm_kms_helper sdhci_pci syscopyarea sysfillrect
> sysimgblt fb_sys_fops ttm sdhci drm ahci libahci wmi i2c_hid hid video
> CPU: 3 PID: 200 Comm: systemd-udevd Not tainted 4.11.0-2-generic
> #7+dev143.9f9ecd2beos3.2.2-Endless
> Hardware name: Acer Aspire Z20-730/IPMAL-BR3, BIOS D01 07/07/2016
> task: ffff8a3070288000 task.stack: ffffa3eb4103c000
> RIP: 0010:gf100_ltc_oneinit_tag_ram+0xba/0x100 [nouveau]
> RSP: 0018:ffffa3eb4103f6b8 EFLAGS: 00010206
> RAX: 00001000ffefdfff RBX: ffff8a306f915000 RCX: ffff8a3075570030
> RDX: 0000000000000000 RSI: dead000000000200 RDI: ffff8a307fd9b700
> RBP: ffffa3eb4103f6d0 R08: 000000000001e980 R09: ffff8a3077003900
> R10: ffffa3eb40cdbda0 R11: ffff8a307fd986a4 R12: 0000000000000000
> R13: 0000000100005fff R14: ffff8a306fa2e400 R15: ffff8a306f914e00
> FS:  00007f456d052900(0000) GS:ffff8a307fd80000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007fefceb1c020 CR3: 000000026fbc5000 CR4: 00000000003406e0
> Call Trace:
>   gm107_ltc_oneinit+0x7c/0x90 [nouveau]
>   nvkm_ltc_oneinit+0x13/0x20 [nouveau]
>   nvkm_subdev_init+0x50/0x210 [nouveau]
>   nvkm_device_init+0x151/0x270 [nouveau]
>   nvkm_udevice_init+0x48/0x60 [nouveau]
>   nvkm_object_init+0x40/0x190 [nouveau]
>   nvkm_ioctl_new+0x179/0x290 [nouveau]
>   ? nvkm_client_notify+0x30/0x30 [nouveau]
>   ? nvkm_udevice_rd08+0x30/0x30 [nouveau]
>   nvkm_ioctl+0x168/0x240 [nouveau]
>   ? nvif_client_init+0x42/0x110 [nouveau]
>   nvkm_client_ioctl+0x12/0x20 [nouveau]
>   nvif_object_ioctl+0x42/0x50 [nouveau]
>   nvif_object_init+0xc2/0x130 [nouveau]
>   nvif_device_init+0x12/0x30 [nouveau]
>   nouveau_cli_init+0x15e/0x1d0 [nouveau]
>   nouveau_drm_load+0x67/0x8b0 [nouveau]
>   ? sysfs_do_create_link_sd.isra.2+0x70/0xb0
>   drm_dev_register+0x148/0x1e0 [drm]
>   drm_get_pci_dev+0xa0/0x160 [drm]
>   nouveau_drm_probe+0x1d9/0x260 [nouveau]
> 
> Daniel
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-06-03  4:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 10:01 Kernel panic on nouveau during boot on NVIDIA NV118 (GM108) Chris Chiu
2017-06-02 14:24 ` Daniel Drake
2017-06-03  4:13   ` Ben Skeggs [this message]
     [not found] ` <CAB4CAwfQ21pAkSxhQoRbdzVXxb8XtyXR4a=R1XRTBVH-pkRVgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-07  7:56   ` Karol Herbst
2017-06-07 10:30     ` [Nouveau] " Chris Chiu

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=e08d0a00-96ba-595e-da35-a597cf8af40c@gmail.com \
    --to=skeggsb@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox