From owner-freebsd-current@freebsd.org Sat Nov 28 22:50:45 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7201A3B340 for ; Sat, 28 Nov 2015 22:50:45 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89A631EB6 for ; Sat, 28 Nov 2015 22:50:44 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1448751042-08ca042abc03a50002-XDYc8F Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id rqPqEJCaGQZlGBPg (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Nov 2015 14:50:43 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: EFI and i915kms questions From: Joe Maloney X-ASG-Orig-Subj: Re: EFI and i915kms questions In-Reply-To: <56505B3F.2070403@dumbbell.fr> Date: Sat, 28 Nov 2015 16:50:41 -0600 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5BC149BC-8BA6-4089-A9E6-763E2494A30A@pcbsd.org> References: <54B18FFE-063F-4F62-9343-28FDE68EE358@pcbsd.org> <56505B3F.2070403@dumbbell.fr> To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1448751043 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24804 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 28 Nov 2015 22:50:45 -0000 Thank you. For what it=E2=80=99s worth I was able to grab a dump after = setting that sysctl. It looks like this maybe the culprit? panic: _sx_xlock_hard: recursed on non-recursive sx gmbus @ = /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/intel_iic.c:362 Since it is to large for posting here. I will include a link to the = entire dump on pastebin if anyone is interesting in looking at it. http://pastebin.com/mzS5svy8 In addition I did a little further testing to narrow down the issue. 10.1-RELEASE WORKS 10.2-RELEASE WORKS I recall trying a 10.2-STABLE image that crashed as well. I can tell = you for sure that the following releases all the way back to August have = the issue for CURRENT. FreeBSD-11.0-CURRENT-amd64-20150804-r286285-memstick.img FreeBSD-11.0-CURRENT-amd64-20150917-r287930-memstick.img FreeBSD-11.0-CURRENT-amd64-20151001-r288459-memstick.img FreeBSD-11.0-CURRENT-amd64-20151119-r291085-memstick.img If there is an archive of older images for CURRENT I would be happy to = try those to help further narrow down where things broke. Joe Maloney > On Nov 21, 2015, at 5:53 AM, Jean-S=C3=A9bastien P=C3=A9dron = wrote: >=20 > On 13/11/2015 18:15, Joe Maloney wrote: >> Hello, >=20 > Hi! >=20 >> Sometime after changes in FreeBSD 10-STABLE, 10.2 onwards, and=20 >> recent 11 CURRENT the resolution no longer sets properly when using >> UEFI boot. It now boots with a 640x480 resolution, and kldload >> i915kms results in a black screen. I have not been able to grab a >> debug log, or crash dump even with all of the debugging features >> turned on. I cannot ssh into the laptop when this panic occurs, and >> the screen is black so I can=E2=80=99t really see what happened. = I=E2=80=99m curious >> if there is anything else I can do besides enabling dumpdev or >> kldload -v i915kms > output.txt that doesn=E2=80=99t give me any = detail. >> Nothing shows up in /var/crash or whatever the directory was. >=20 > You could try to set debug.debugger_on_panic=3D0 in /etc/sysctl.conf. = It > often helps to at least get core dumps when the crash happens in a = video > driver. >=20 > --=20 > Jean-S=C3=A9bastien P=C3=A9dron >=20