Date: Fri, 28 Apr 2017 21:34:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218944] i915kms panics the kernel Message-ID: <bug-218944-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218944 Bug ID: 218944 Summary: i915kms panics the kernel Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: domagoj.stolfa@gmail.com After approximately 20th of April, running 12.0-CURRENT on the following CP= Us has caused panics on kldloads: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 I am however, unable to provide a crash dump, as whenever the kernel does panic, I am unable to see the cause of it(due to the driver overtaking my screen), as well as getting I would assume ENXIO when trying to call doadum= p(). Furthermore, I've observed damage to the hardware(namely, the laptop screen= ) on a Lenovo G500 potentially caused by this panic. There has been a related post on the mailing lists as well: https://lists.freebsd.org/pipermail/freebsd-current/2017-April/065694.html. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218944-8>