Skip site navigation (1)Skip section navigation (2)
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 patch manually and give you the resultsMy chip is Intel Corei7 4th gen (Haswell)
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: https://github.com/dervishe-/ 

     Le Samedi 21 février 2015 4h33, J.R. Oldroyd <fbsd@opal.com> a écrit :
   

 On Fri, 20 Feb 2015 15:49:44 +0100 Anders Bolt-Evensen <andersbo87@icloud.com> wrote:
>> 
> I saw that you had updated your patchfile to drm-update-38.h.patch, and 
> ...
> applied the patch, it seemed to be more successful, but on 22 occations 
> the patch still fails (the following list contains all the fails; the 
> entire output can be seen here: 
> 
> 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.rej
> 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.rej
> 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 
> 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.rej
> 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.rej
> 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.  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 = 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 0xfffffe00b2966680
Feb 20 21:58:22 xx kernel: kassert_panic() at kassert_panic+0x132/frame 0xfffffe00b29666f0
Feb 20 21:58:22 xx kernel: __mtx_lock_flags() at __mtx_lock_flags+0x14a/frame 0xfffffe00b2966740
Feb 20 21:58:22 xx kernel: drm_vblank_post_modeset() at drm_vblank_post_modeset+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+0x14/frame 0xfffffe00b29667e0
Feb 20 21:58:22 xx kernel: drm_crtc_helper_set_mode() at drm_crtc_helper_set_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+0xf0/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 0xfffffe00b2966bf0
Feb 20 21:58:22 xx kernel: fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00b2966bf0
Feb 20 21:58:22 xx kernel: --- trap 0, rip = 0, rsp = 0xfffffe00b2966cb0, rbp = 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.

    -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-x11@FreeBSD.ORG  Mon Feb 23 09:22:21 2015
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 42190A2A
 for <freebsd-x11@FreeBSD.org>; Mon, 23 Feb 2015 09:22:21 +0000 (UTC)
Received: from st11p00mm-asmtp002.mac.com (st11p00mm-asmtp002.mac.com
 [17.172.81.1])
 (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1515275A
 for <freebsd-x11@FreeBSD.org>; Mon, 23 Feb 2015 09:22:20 +0000 (UTC)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; charset=utf-8; format=flowed
Received: from pc162-217.hiof.no (pc162-217.hiof.no [158.39.162.217])
 by st11p00mm-asmtp002.mac.com
 (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014))
 with ESMTPSA id <0NK700I5GWP0WN20@st11p00mm-asmtp002.mac.com> for
 freebsd-x11@FreeBSD.org; Mon, 23 Feb 2015 09:22:14 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure
 engine=2.50.10432:5.13.68,1.0.33,0.0.0000
 definitions 15-02-23_01:2015-02-20,2015-02-22,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policyÞfault score=0 spamscore=0
 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0
 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502230089
Message-id: <54EAF144.4000706@icloud.com>
Date: Mon, 23 Feb 2015 10:22:12 +0100
From: Anders Bolt-Evensen <andersbo87@icloud.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0)
 Gecko/20100101 Thunderbird/31.0
To: freebsd-x11@FreeBSD.org
Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8
References: <54E3D2A0.2090903@FreeBSD.org> <54E74988.1050301@icloud.com>
 <54E9A706.4080602@FreeBSD.org>
In-reply-to: <54E9A706.4080602@FreeBSD.org>
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>;
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 09:22:21 -0000


Oops, forgot to send the reply to the thread, so I'm sending it again:

On 22/02/15 10:53, Jean-Sébastien Pédron wrote:
> On 20.02.2015 15:49, Anders Bolt-Evensen wrote:
>> To avoid unnecessary conflicts, I decided to remove local sources and
>> redownload the newest sources from FreeBSD's svn repository. When I then
>> applied the patch, it seemed to be more successful, but on 22 occations
>> the patch still fails (...)
> Hi!
>
> Hmm, I guess it is because of all the non-expanded $FreeBSD$ in my
> patch... Can you try with "svn patch"?
>
> If it doesn't work either, I recommend you check out the Git branch:
> git clone -b kms-drm-update-38 https://github.com/dumbbell/freebsd.git
>
> For the next tests, you will only have to update that checkout.
>
> If it is too much to download, I prepared an archive with all files in
> sys/dev/drm2 and the relevant Makefiles in sys/modules:
> https://people.freebsd.org/~dumbbell/graphics/drm-update-38.h.tar.gz
>

Doing the "svn patch patchfile" worked just fine.
Thanks for the tip.
I'll test it on both a CMS/BIOS based hard drive and a UEFI based hard
drive (though I don't expect Radeon KMS to work on the EFI partitioned
hard drive, since it hasn't worked in the past, but I'll give it a try).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1227462529.6746581.1424602457182.JavaMail.yahoo>