All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: lkp@lists.01.org
Subject: Re: [lkp-developer] [drm] 75f6dfe3e6: BUG:unable_to_handle_kernel
Date: Wed, 04 Jan 2017 01:41:39 -0200	[thread overview]
Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <20170104004504.GA721@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

kernel test robot <xiaolong.ye@intel.com> writes:

>
> on test machine: qemu-system-x86_64 -enable-kvm -m 320M
>
> caused below changes:
>

> [    1.608985] mwave: mwavedd::mwave_init: Error: Failed to initialize
> [    1.609295] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds).
> [    1.609913] [drm] radeon kernel modesetting enabled.
> [    1.610407] BUG: unable to handle kernel NULL pointer dereference at 0000002c
> [    1.610833] IP: [<8143c0ba>] drm_dev_register+0xe9/0x173
> [    1.611131] *pdpt = 0000000000000000 *pde = f000ff53f000ff53 
> [    1.611427]

I believe this is already fixed by 6098909cf2d0 ("drm: Avoid NULL
dereference of drm_device.dev").  But right now the tip of the
drm-intel-nightly already includes that patch, so I'm not sure if the
test included it, I think not.

I gave it a try with the jobfile just to be sure on top of
drm-misc-next, and I couldn't reproduce the error anymore after applying
Chris' patch (but I could reproduce the Oops when trying only with my
patch).

Also, sorry for the noise and lesson learned about virtual devices :(

-- 
Gabriel Krisman Bertazi

WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, lkp@01.org,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [lkp-developer] [drm] 75f6dfe3e6: BUG:unable_to_handle_kernel
Date: Wed, 04 Jan 2017 01:41:39 -0200	[thread overview]
Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <20170104004504.GA721@yexl-desktop> (kernel test robot's message of "Wed, 4 Jan 2017 08:45:04 +0800")

kernel test robot <xiaolong.ye@intel.com> writes:

>
> on test machine: qemu-system-x86_64 -enable-kvm -m 320M
>
> caused below changes:
>

> [    1.608985] mwave: mwavedd::mwave_init: Error: Failed to initialize
> [    1.609295] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds).
> [    1.609913] [drm] radeon kernel modesetting enabled.
> [    1.610407] BUG: unable to handle kernel NULL pointer dereference at 0000002c
> [    1.610833] IP: [<8143c0ba>] drm_dev_register+0xe9/0x173
> [    1.611131] *pdpt = 0000000000000000 *pde = f000ff53f000ff53 
> [    1.611427]

I believe this is already fixed by 6098909cf2d0 ("drm: Avoid NULL
dereference of drm_device.dev").  But right now the tip of the
drm-intel-nightly already includes that patch, so I'm not sure if the
test included it, I think not.

I gave it a try with the jobfile just to be sure on top of
drm-misc-next, and I couldn't reproduce the error anymore after applying
Chris' patch (but I could reproduce the Oops when trying only with my
patch).

Also, sorry for the noise and lesson learned about virtual devices :(

-- 
Gabriel Krisman Bertazi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	lkp@01.org
Subject: Re: [lkp-developer] [drm]  75f6dfe3e6: BUG:unable_to_handle_kernel
Date: Wed, 04 Jan 2017 01:41:39 -0200	[thread overview]
Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <20170104004504.GA721@yexl-desktop> (kernel test robot's message of "Wed, 4 Jan 2017 08:45:04 +0800")

kernel test robot <xiaolong.ye@intel.com> writes:

>
> on test machine: qemu-system-x86_64 -enable-kvm -m 320M
>
> caused below changes:
>

> [    1.608985] mwave: mwavedd::mwave_init: Error: Failed to initialize
> [    1.609295] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds).
> [    1.609913] [drm] radeon kernel modesetting enabled.
> [    1.610407] BUG: unable to handle kernel NULL pointer dereference at 0000002c
> [    1.610833] IP: [<8143c0ba>] drm_dev_register+0xe9/0x173
> [    1.611131] *pdpt = 0000000000000000 *pde = f000ff53f000ff53 
> [    1.611427]

I believe this is already fixed by 6098909cf2d0 ("drm: Avoid NULL
dereference of drm_device.dev").  But right now the tip of the
drm-intel-nightly already includes that patch, so I'm not sure if the
test included it, I think not.

I gave it a try with the jobfile just to be sure on top of
drm-misc-next, and I couldn't reproduce the error anymore after applying
Chris' patch (but I could reproduce the Oops when trying only with my
patch).

Also, sorry for the noise and lesson learned about virtual devices :(

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2017-01-04  3:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  0:45 [lkp-developer] [drm] 75f6dfe3e6: BUG:unable_to_handle_kernel kernel test robot
2017-01-04  0:45 ` kernel test robot
2017-01-04  0:45 ` kernel test robot
2017-01-04  3:41 ` Gabriel Krisman Bertazi [this message]
2017-01-04  3:41   ` Gabriel Krisman Bertazi
2017-01-04  3:41   ` Gabriel Krisman Bertazi

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=87a8b7fq4s.fsf@dilma.collabora.co.uk \
    --to=krisman@collabora.co.uk \
    --cc=lkp@lists.01.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.