From owner-freebsd-current@FreeBSD.ORG Wed Feb 18 19:36:20 2015 Return-Path: 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 96058997; Wed, 18 Feb 2015 19:36:20 +0000 (UTC) Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 582A8C32; Wed, 18 Feb 2015 19:36:20 +0000 (UTC) Received: by mail-ig0-f171.google.com with SMTP id h15so39066670igd.4; Wed, 18 Feb 2015 11:36:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8UkURyHk79qTPiVTWvwfi50qPeLYy2UJF/cMZk7zZvQ=; b=UK0IQcG6O0iGx3FNRq933Ak+KILHrLaZniR7wrFXM4YdRnXzoPOrKnFoUz2knoVXF/ 4fsRjhCORX/r8FypUJVnoobTiWbMDjmniSRgbVW1fng0hpTZ6zGjCWsaQKebEApjSIVk qqQWt1l6cE8XFboqKKoraphxG1oCBiLSE+X8ylng0KIxJMJFmZKkeg/tRG5PVvDoO+ds b3jWpXZHIgFbVYTfFND0kmrxj4DGVdwOIwQGMEwXf8/xR15OoBuI7QqzhkUYlNGELbMV XhbSCA1e30wYJAhr91Q0skyIVUzlglUdAWHtCHCJFFggWW4z3ZFJh1zcn53pC8V+MnDi vGUA== X-Received: by 10.50.122.68 with SMTP id lq4mr5022986igb.10.1424288179607; Wed, 18 Feb 2015 11:36:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Wed, 18 Feb 2015 11:35:56 -0800 (PST) In-Reply-To: References: <54E3D2A0.2090903@FreeBSD.org> From: Miguel Clara Date: Wed, 18 Feb 2015 19:35:56 +0000 Message-ID: Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 To: "Lundberg, Johannes" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-x11@freebsd.org" , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 19:36:20 -0000 On Wed, Feb 18, 2015 at 12:09 AM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Hi > > Good job! Will do some testing! As for the i915 driver, what versions ar= e > supported? Up until and including HD4000 Gen7 Ivy bridge? > > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. > > On Wed, Feb 18, 2015 at 8:45 AM, Jean-S=C3=A9bastien P=C3=A9dron < > dumbbell@freebsd.org > > wrote: > > > Hi! > > > > An update to the DRM subsystem, not including the drivers, is ready for > > wider testing! > > > > The patch against HEAD is here: > > https://people.freebsd.org/~dumbbell/graphics/drm-update-38.f.patch > > > > I'm interested in success/failure reports for amd64, powerpc and > > powerpc64 users, for i915 and Radeon GPUs. I already know there is a > > build issue on i386, please wait for the next patch if you are in this > > case. > > > > The changes brought by this patch are explained in a blog post: > > http://blogs.freebsdish.org/graphics/2015/02/18/testing-the-drm-update/ > > > > This is working well for some Radeon users for more than a year. > > However, it only started to work with i915 a month ago, when the i915 > > refresh was committed. > > > > Try your day-to-day applications, try suspend/resume, try all output > > connectors, try OpenGL stuff, try backlight controls, everything :) > Testing suspend/resume by closing/opening the LID works for me but I did get this: lock order reversal: 1st 0xfffffe0000e1c728 ath0 (ath0) @ /usr/src/sys/dev/ath/if_ath.c:6654 2nd 0xfffffe0000fc1838 ath0_node_lock (ath0_node_lock) @ /usr/src/sys/net80211/ieee80211_node.c:1824 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0115c71790 witness_checkorder() at witness_checkorder+0xe45/frame 0xfffffe0115c71820 __mtx_lock_flags() at __mtx_lock_flags+0xa8/frame 0xfffffe0115c71870 ieee80211_node_delucastkey() at ieee80211_node_delucastkey+0x52/frame 0xfffffe0115c718c0 node_free() at node_free+0x25/frame 0xfffffe0115c718e0 ieee80211_tx_complete() at ieee80211_tx_complete+0x2c/frame 0xfffffe0115c71900 ath_tx_draintxq() at ath_tx_draintxq+0x22/frame 0xfffffe0115c71930 ath_edma_tx_drain() at ath_edma_tx_drain+0x10d/frame 0xfffffe0115c71970 ath_stop_locked() at ath_stop_locked+0x148/frame 0xfffffe0115c719a0 ath_ioctl() at ath_ioctl+0x223/frame 0xfffffe0115c719e0 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xfffffe0115c71a4= 0 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xfffffe0115c71a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0115c71ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0115c71ab0 --- trap 0, rip =3D 0, rsp =3D 0xfffffe0115c71b70, rbp =3D 0 --- So something fails in the ath side, which I'm guesssing I should report to the wireless list? As for backlight I still have no control of that, unless I use intel_backlight or the patch proposed a while back which adds "hw.dri.0.i915_backlight" The latptop I just tested is an Acer S3-391 Ivy Bridge and I only have the single card (I have another with dual graphics that I'll test later) the hardware keys for backlight control in this one are "Fn-Left/Right Arrow". > > > > Thank you! > > > > -- > > Jean-S=C3=A9bastien P=C3=A9dron > > > > > > --