From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============0224436329139338420==" MIME-Version: 1.0 From: Gabriel Krisman Bertazi 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 Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> In-Reply-To: <20170104004504.GA721@yexl-desktop> List-Id: --===============0224436329139338420== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable kernel test robot 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 sec= onds, margin is 60 seconds). > [ 1.609913] [drm] radeon kernel modesetting enabled. > [ 1.610407] BUG: unable to handle kernel NULL pointer dereference at 0= 000002c > [ 1.610833] IP: [<8143c0ba>] drm_dev_register+0xe9/0x173 > [ 1.611131] *pdpt =3D 0000000000000000 *pde =3D 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 --===============0224436329139338420==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriel Krisman Bertazi Subject: Re: [lkp-developer] [drm] 75f6dfe3e6: BUG:unable_to_handle_kernel Date: Wed, 04 Jan 2017 01:41:39 -0200 Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> References: <20170104004504.GA721@yexl-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <20170104004504.GA721@yexl-desktop> (kernel test robot's message of "Wed, 4 Jan 2017 08:45:04 +0800") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: kernel test robot Cc: Daniel Vetter , intel-gfx@lists.freedesktop.org, lkp@01.org, LKML , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org a2VybmVsIHRlc3Qgcm9ib3QgPHhpYW9sb25nLnllQGludGVsLmNvbT4gd3JpdGVzOgoKPgo+IG9u IHRlc3QgbWFjaGluZTogcWVtdS1zeXN0ZW0teDg2XzY0IC1lbmFibGUta3ZtIC1tIDMyME0KPgo+ IGNhdXNlZCBiZWxvdyBjaGFuZ2VzOgo+Cgo+IFsgICAgMS42MDg5ODVdIG13YXZlOiBtd2F2ZWRk Ojptd2F2ZV9pbml0OiBFcnJvcjogRmFpbGVkIHRvIGluaXRpYWxpemUKPiBbICAgIDEuNjA5Mjk1 XSBIYW5nY2hlY2s6IHN0YXJ0aW5nIGhhbmdjaGVjayB0aW1lciAwLjkuMSAodGljayBpcyAxODAg c2Vjb25kcywgbWFyZ2luIGlzIDYwIHNlY29uZHMpLgo+IFsgICAgMS42MDk5MTNdIFtkcm1dIHJh ZGVvbiBrZXJuZWwgbW9kZXNldHRpbmcgZW5hYmxlZC4KPiBbICAgIDEuNjEwNDA3XSBCVUc6IHVu YWJsZSB0byBoYW5kbGUga2VybmVsIE5VTEwgcG9pbnRlciBkZXJlZmVyZW5jZSBhdCAwMDAwMDAy Ywo+IFsgICAgMS42MTA4MzNdIElQOiBbPDgxNDNjMGJhPl0gZHJtX2Rldl9yZWdpc3RlcisweGU5 LzB4MTczCj4gWyAgICAxLjYxMTEzMV0gKnBkcHQgPSAwMDAwMDAwMDAwMDAwMDAwICpwZGUgPSBm MDAwZmY1M2YwMDBmZjUzIAo+IFsgICAgMS42MTE0MjddCgpJIGJlbGlldmUgdGhpcyBpcyBhbHJl YWR5IGZpeGVkIGJ5IDYwOTg5MDljZjJkMCAoImRybTogQXZvaWQgTlVMTApkZXJlZmVyZW5jZSBv ZiBkcm1fZGV2aWNlLmRldiIpLiAgQnV0IHJpZ2h0IG5vdyB0aGUgdGlwIG9mIHRoZQpkcm0taW50 ZWwtbmlnaHRseSBhbHJlYWR5IGluY2x1ZGVzIHRoYXQgcGF0Y2gsIHNvIEknbSBub3Qgc3VyZSBp ZiB0aGUKdGVzdCBpbmNsdWRlZCBpdCwgSSB0aGluayBub3QuCgpJIGdhdmUgaXQgYSB0cnkgd2l0 aCB0aGUgam9iZmlsZSBqdXN0IHRvIGJlIHN1cmUgb24gdG9wIG9mCmRybS1taXNjLW5leHQsIGFu ZCBJIGNvdWxkbid0IHJlcHJvZHVjZSB0aGUgZXJyb3IgYW55bW9yZSBhZnRlciBhcHBseWluZwpD aHJpcycgcGF0Y2ggKGJ1dCBJIGNvdWxkIHJlcHJvZHVjZSB0aGUgT29wcyB3aGVuIHRyeWluZyBv bmx5IHdpdGggbXkKcGF0Y2gpLgoKQWxzbywgc29ycnkgZm9yIHRoZSBub2lzZSBhbmQgbGVzc29u IGxlYXJuZWQgYWJvdXQgdmlydHVhbCBkZXZpY2VzIDooCgotLSAKR2FicmllbCBLcmlzbWFuIEJl cnRhemkKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50 ZWwtZ2Z4IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBz Oi8vbGlzdHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vaW50ZWwtZ2Z4Cg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966142AbdADDmD (ORCPT ); Tue, 3 Jan 2017 22:42:03 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:55769 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935344AbdADDl6 (ORCPT ); Tue, 3 Jan 2017 22:41:58 -0500 From: Gabriel Krisman Bertazi To: kernel test robot Cc: Daniel Vetter , LKML , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, lkp@01.org Subject: Re: [lkp-developer] [drm] 75f6dfe3e6: BUG:unable_to_handle_kernel Organization: Collabora References: <20170104004504.GA721@yexl-desktop> Date: Wed, 04 Jan 2017 01:41:39 -0200 In-Reply-To: <20170104004504.GA721@yexl-desktop> (kernel test robot's message of "Wed, 4 Jan 2017 08:45:04 +0800") Message-ID: <87a8b7fq4s.fsf@dilma.collabora.co.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org kernel test robot 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