Thank you. For what it’s 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 @
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.
In addition I did a little further testing to narrow down the issue.
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
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.
> On Nov 21, 2015, at 5:53 AM, Jean-Sébastien Pédron
> <jean-sebastien.ped...@dumbbell.fr> wrote:
> On 13/11/2015 18:15, Joe Maloney wrote:
>> Sometime after changes in FreeBSD 10-STABLE, 10.2 onwards, and
>> 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’t really see what happened. I’m curious
>> if there is anything else I can do besides enabling dumpdev or
>> kldload -v i915kms > output.txt that doesn’t give me any detail.
>> Nothing shows up in /var/crash or whatever the directory was.
> You could try to set debug.debugger_on_panic=0 in /etc/sysctl.conf. It
> often helps to at least get core dumps when the crash happens in a video
> Jean-Sébastien Pédron
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"