atomic changes break drm-next-kmod?
John Baldwin
jhb at FreeBSD.org
Tue Jul 3 22:56:28 UTC 2018
On 7/3/18 3:34 PM, Pete Wright wrote:
>
>
> On 07/03/2018 15:29, John Baldwin wrote:
>> That seems like kgdb is looking at the wrong CPU. Can you use
>> 'info threads' and look for threads not stopped in 'sched_switch'
>> and get their backtraces? You could also just do 'thread apply
>> all bt' and put that file at a URL if that is easiest.
>>
>
>
> sure thing John - here's a gist of "thread apply all bt"
>
> https://gist.github.com/gem-pete/d8d7ab220dc8781f0827f965f09d43ed
That doesn't look right at all. Are you sure the kernel matches the
vmcore? Also, which kgdb version are you using?
--
John Baldwin
More information about the freebsd-current
mailing list