Ver 2 of the patch [was: Re: i915 driver update testing]
kostikbel at gmail.com
Thu Oct 23 19:03:41 UTC 2014
On Wed, Oct 22, 2014 at 03:59:23PM -0400, Adam McDougall wrote:
> On 10/22/2014 08:26, Konstantin Belousov wrote:
> > On Wed, Oct 08, 2014 at 03:12:08PM -0400, Adam McDougall wrote:
> >> On 10/08/2014 13:05, Konstantin Belousov wrote:
> >>> There are more occurences of the bug I fixed once in patch version 2.
> >>> Also, since pmap changes were committed in modified form, please try
> >>> the updated patch at https://www.kib.kiev.ua/kib/drm/i915.3.patch .
> >> No apparent change:
> >> http://www.egr.msu.edu/~mcdouga9/i915-patch3-1.txt
> > cite> (kgdb) p *(struct drm_i915_private *)(dev_private)
> > cite> No symbol "dev_private" in current context.
> > This is p *(struct drm_i915_private *)(dev->dev_private)
> > I regenerated patch after recent merges and changes in KPI on HEAD.
> > https://www.kib.kiev.ua/kib/drm/i915.4.patch
> > Please apply it, I think the issue should be there still. Then apply
> > the following debugging patch, and set
> > kenv drm.debug=0x3
> > before loading i915kms.ko. I want to see the same debugging information,
> > and dmesg from the moment of loading the driver.
> > In fact, try
> > https://www.kib.kiev.ua/kib/drm/i915.5.patch
Due to my mistake during the patch generation, i915.5.patch is just
Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one
private report of the patch worked from person who got the same panic
More information about the freebsd-current