Date: Thu, 17 Mar 2016 18:23:18 +0100 From: Anders Bolt-Evensen <andersbo87@icloud.com> To: freebsd-x11@freebsd.org Subject: SV: i915 update to Linux 3.8 ready! Message-ID: <000801d18071$b45f9dc0$1d1ed940$@icloud.com> In-Reply-To: <56E333CD.2020404@dumbbell.fr> References: <56D9CE73.7040601@FreeBSD.org> <56DF3F20.8010208@FreeBSD.org> <CAMODbk=JihgYOQ_PHUmeDrOg4fQ8FmXY18T2ZHm-JJk70YEc4w@mail.gmail.com> <56E333CD.2020404@dumbbell.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Opprinnelig melding----- > Fra: owner-freebsd-x11@freebsd.org [mailto:owner-freebsd- > x11@freebsd.org] P=C3=A5 vegne av Jean-S=C3=A9bastien P=C3=A9dron > Sendt: fredag 11. mars 2016 22.08 > Til: freebsd-x11@freebsd.org > Emne: Re: i915 update to Linux 3.8 ready! >=20 > On 11/03/2016 21:23, Frederic Chardon wrote: > > Hi! >=20 > Hi! >=20 > > I now have a very reproducible panic in Xorg on my 965GM (Dell > > Latitude D630). No problem at the console with i915kms loaded. >=20 > How do you reproduce it? >=20 > > vm_fault: pager read error, pid 44151 (Xorg) Kernel page fault with > > the following non-sleepable locks held: > > exclusive rw vm object (vm object) r =3D 0 (0xfffff80205757528) = locked @ > > = /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_gem.c:16 > > 26 > > stack backtrace: > > #0 0xffffffff80405490 at witness_debugger+0x70 > > #1 0xffffffff80406777 at witness_warn+0x3d7 > > #2 0xffffffff805eb137 at trap_pfault+0x57 > > #3 0xffffffff805ea7c4 at trap+0x284 > > #4 0xffffffff805cc857 at calltrap+0x8 > > #5 0xffffffff805a1428 at vm_fault+0x78 > > #6 0xffffffff805eb1f5 at trap_pfault+0x115 > > #7 0xffffffff805ea882 at trap+0x342 > > #8 0xffffffff805cc857 at calltrap+0x8 >=20 > Could you please send the whole core.txt.$n? >=20 > -- > Jean-S=C3=A9bastien P=C3=A9dron I can now confirm I too have the same problem. A few days ago, I posted an answer where I said I wasn't sure I had the = same problem, but after compiling the GENERIC debug kernel (I used a = custom kernel up until yesterday), I can confirm that I too have the = same problem. I have attached the content of core.txt.0. I once again tried to attach = it here, but that message got rejected as it was almost 100 kb too big. Instead, core.txt.0is available here: = https://www.dropbox.com/s/kpe84o0j0bna22z/core.txt.0?dl=3D0 Anders
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000801d18071$b45f9dc0$1d1ed940$>