Date: Sun, 22 Feb 2015 10:54:17 +0000 (UTC) From: dervishe <dervishe@yahoo.fr> To: "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org> Cc: "freebsd-x11@FreeBSD.org" <freebsd-x11@FreeBSD.org> Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 Message-ID: <1227462529.6746581.1424602457182.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <20150220221246.661f2d01@shibato> References: <20150220221246.661f2d01@shibato>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your work :)I apply the h version of the patch on r279140 and it= failed on some hunk (Same result as J.R Oldroyd)I will try to apply the pa= tch manually and give you the resultsMy chip is Intel Corei7 4th gen (Haswe= ll) K G+ : https://plus.google.com/u/0/+AlexandreKeledjian/posts Twitter: @dervyshe Blog: https://blogs.fsfe.org/dervishe/ Public key: https://keybase.io/dervishe/key.asc GitHub:=C2=A0https://github= .com/dervishe-/=20 Le Samedi 21 f=C3=A9vrier 2015 4h33, J.R. Oldroyd <fbsd@opal.com> a = =C3=A9crit : =20 On Fri, 20 Feb 2015 15:49:44 +0100 Anders Bolt-Evensen <andersbo87@icloud.= com> wrote: >>=20 > I saw that you had updated your patchfile to drm-update-38.h.patch, and= =20 > ... > applied the patch, it seemed to be more successful, but on 22 occations= =20 > the patch still fails (the following list contains all the fails; the=20 > entire output can be seen here:=20 >=20 > Hunk #2 failed at 29. > 1 out of 3 hunks failed--saving rejects to sys/dev/drm2/drm_agpsupport.c.= rej > Hunk #2 failed at 31. > 1 out of 4 hunks failed--saving rejects to sys/dev/drm2/drm_auth.c.rej > Hunk #2 failed at 31. > 1 out of 26 hunks failed--saving rejects to sys/dev/drm2/drm_bufs.c.rej > Hunk #2 failed at 31. > 1 out of 17 hunks failed--saving rejects to sys/dev/drm2/drm_context.c.re= j > Hunk #1 failed at 21. > 1 out of 39 hunks failed--saving rejects to sys/dev/drm2/drm_crtc.h.rej > Hunk #2 failed at 31. > 1 out of 5 hunks failed--saving rejects to sys/dev/drm2/drm_dma.c.rej > Hunk #1 failed at 0. > 1 out of 1 hunks failed--saving rejects to sys/dev/drm2/drm_drawable.c.re= j > Hunk #2 failed at 44. > 1 out of 8 hunks failed--saving rejects to sys/dev/drm2/drm_drv.c.rej > Hunk #1 failed at 19. > 1 out of 5 hunks failed--saving rejects to sys/dev/drm2/drm_edid.h.rej > Hunk #1 failed at 21. > 1 out of 17 hunks failed--saving rejects to=20 > sys/dev/drm2/drm_edid_modes.h.rej > Hunk #1 failed at 26. > 1 out of 7 hunks failed--saving rejects to sys/dev/drm2/drm_fb_helper.h.r= ej > Hunk #2 failed at 32. > 1 out of 9 hunks failed--saving rejects to sys/dev/drm2/drm_fops.c.rej > Hunk #1 failed at 19. > 1 out of 3 hunks failed--saving rejects to sys/dev/drm2/drm_fourcc.h.rej > Hunk #1 failed at 0. > 1 out of 1 hunks failed--saving rejects to sys/dev/drm2/drm_internal.h.re= j > Hunk #2 failed at 31. > 1 out of 4 hunks failed--saving rejects to sys/dev/drm2/drm_ioctl.c.rej > Hunk #2 failed at 27. > 1 out of 50 hunks failed--saving rejects to sys/dev/drm2/drm_irq.c.rej > Hunk #2 failed at 31. > 1 out of 3 hunks failed--saving rejects to sys/dev/drm2/drm_lock.c.rej > Hunk #2 failed at 31. > 1 out of 2 hunks failed--saving rejects to sys/dev/drm2/drm_memory.c.rej > Hunk #1 failed at 25. > 1 out of 10 hunks failed--saving rejects to sys/dev/drm2/drm_mm.h.rej > Hunk #1 failed at 22. > 1 out of 11 hunks failed--saving rejects to sys/dev/drm2/drm_mode.h.rej > Hunk #1 failed at 0. > 1 out of 1 hunks failed--saving rejects to sys/dev/drm2/drm_sman.c.rej > Hunk #1 failed at 0. > 1 out of 1 hunks failed--saving rejects to sys/dev/drm2/drm_sman.h.rej > _______________________________________________ Same errors here.=C2=A0 Applying patch to r279092 from svn master. Did you diff against the github source and is there perhaps some divergence between that and the svn master? I worked through the rejects and applied them manually. But, booting does not go well: Feb 20 21:58:22 xx kernel: panic: mtx_lock() of destroyed mutex @ /usr/src/= sys/modules/drm2/drm2/../../../dev/drm2/drm_irq.c:1036 Feb 20 21:58:22 xx kernel: cpuid =3D 0 Feb 20 21:58:22 xx kernel: KDB: stack backtrace: Feb 20 21:58:22 xx kernel: db_trace_self_wrapper() at db_trace_self_wrapper= +0x2b/frame 0xfffffe00b2966600 Feb 20 21:58:22 xx kernel: vpanic() at vpanic+0x189/frame 0xfffffe00b296668= 0 Feb 20 21:58:22 xx kernel: kassert_panic() at kassert_panic+0x132/frame 0xf= ffffe00b29666f0 Feb 20 21:58:22 xx kernel: __mtx_lock_flags() at __mtx_lock_flags+0x14a/fra= me 0xfffffe00b2966740 Feb 20 21:58:22 xx kernel: drm_vblank_post_modeset() at drm_vblank_post_mod= eset+0x3f/frame 0xfffffe00b2966770 Feb 20 21:58:22 xx kernel: atombios_crtc_dpms() at atombios_crtc_dpms+0x208= /frame 0xfffffe00b29667b0 Feb 20 21:58:22 xx kernel: atombios_crtc_commit() at atombios_crtc_commit+0= x14/frame 0xfffffe00b29667e0 Feb 20 21:58:22 xx kernel: drm_crtc_helper_set_mode() at drm_crtc_helper_se= t_mode+0x480/frame 0xfffffe00b2966a30 Feb 20 21:58:22 xx kernel: drm_crtc_helper_set_config() at drm_crtc_helper_= set_config+0x9c1/frame 0xfffffe00b2966b00 Feb 20 21:58:22 xx kernel: vt_restore_fbdev_mode() at vt_restore_fbdev_mode= +0x4e/frame 0xfffffe00b2966b20 Feb 20 21:58:22 xx kernel: taskqueue_run_locked() at taskqueue_run_locked+0= xf0/frame 0xfffffe00b2966b80 Feb 20 21:58:22 xx kernel: taskqueue_thread_loop() at taskqueue_thread_loop= +0x9b/frame 0xfffffe00b2966bb0 Feb 20 21:58:22 xx kernel: fork_exit() at fork_exit+0x84/frame 0xfffffe00b2= 966bf0 Feb 20 21:58:22 xx kernel: fork_trampoline() at fork_trampoline+0xe/frame 0= xfffffe00b2966bf0 Feb 20 21:58:22 xx kernel: --- trap 0, rip =3D 0, rsp =3D 0xfffffe00b2966cb= 0, rbp =3D 0 --- Feb 20 21:58:22 xx kernel: Uptime: 37s Feb 20 21:58:22 xx kernel: Dumping 236 out of 2915 MB:..7%..14%..21%..34%..= 41%..55%..61%..75%..82%..95% Feb 20 21:58:22 xx kernel: Dump complete Feb 20 21:58:22 xx kernel: Automatic reboot in 15 seconds - press a key on = the console to abort Feb 20 21:58:22 xx kernel: Rebooting... I can also see earlier that the cp still did not init... same old CAFEDEAD in r100_cp_init. Chip is ATI Radeon RS690 X1270 IGP. =C2=A0=C2=A0=C2=A0 -jr _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Feb 22 12:13:17 2015 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F19F8BA for <freebsd-current@freebsd.org>; Sun, 22 Feb 2015 12:13:17 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 4CEDC929 for <freebsd-current@freebsd.org>; Sun, 22 Feb 2015 12:13:17 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id D3667A8A for <freebsd-current@freebsd.org>; Sun, 22 Feb 2015 12:13:16 +0000 (UTC) Date: Sun, 22 Feb 2015 12:13:16 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-current@freebsd.org Message-ID: <1600200767.31.1424607196115.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1948528528.30.1424599553523.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1948528528.30.1424599553523.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to stable : FreeBSD_HEAD-tests2 #744 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_HEAD-tests2 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 22 Feb 2015 12:13:17 -0000 See <https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/744/>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1227462529.6746581.1424602457182.JavaMail.yahoo>