Date: Sat, 28 Nov 2015 16:50:41 -0600 From: Joe Maloney <jmaloney@pcbsd.org> To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= <jean-sebastien.pedron@dumbbell.fr> Cc: freebsd-current@freebsd.org Subject: Re: EFI and i915kms questions Message-ID: <5BC149BC-8BA6-4089-A9E6-763E2494A30A@pcbsd.org> In-Reply-To: <56505B3F.2070403@dumbbell.fr> References: <54B18FFE-063F-4F62-9343-28FDE68EE358@pcbsd.org> <56505B3F.2070403@dumbbell.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 = <jean-sebastien.pedron@dumbbell.fr> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5BC149BC-8BA6-4089-A9E6-763E2494A30A>