Panic on boot with r353298 (last known working r35295)
Gary Jennejohn
gljennjohn at gmail.com
Tue Oct 8 10:15:09 UTC 2019
On Tue, 8 Oct 2019 09:23:30 +0000
M&S - Krasznai Andr__s <Krasznai.Andras at mands.hu> wrote:
> Hi
>
> r353298 running on lenovo T510. Panics after starting X session, the panic is
>
> panic: vm_fault, fault on nofault entry, addr: 0xfffffe00821a000
>
> It is preceded by several error messages referring to
>
> drm_modeset_is_locked failed at /usr/local/sys/modules/drm-current-kmod/drivers/gpu/drm_atomic_helper.c:577. then line 622 and then line 821 of the same
> drm_atomic_helper.c module.
>
>
> best regards
>
> Andras Krasznai
>
> -----Eredeti __zenet-----
> Felad__: owner-freebsd-current at freebsd.org [mailto:owner-freebsd-current at freebsd.org] Meghatalmaz__ Evilham
> K__ldve: 2019. okt__ber 8. 11:00
> C__mzett: FreeBSD Current
> T__rgy: Panic on boot with r353298 (last known working r35295)
>
> Hey, just a heads up that on a Lenovo A485 (AMD Ryzen processor),
> r353298 panics somewhat late in the boot process. r352925 is my
> last known working build.
> I am building GENERIC-NODEBUG.
>
> Sadly my pulse is shaky and I can't properly read the picture I
> took, it appears to say:
>
> Fatal trap 32: page fault while in kernel mode
> *something, something*
> fault mode = supervisor read data, page not present
>
> Will try to get more details and a proper dump when I have some
> time off (hopefully later today), just thought I'd warn before.
>
Works for me with a first-generation Ryzen 5 (but in a tower, not
a laptop) and I use a graphics card from Nvidia.
X11 also starts without errors, but I use nvidia-driver and not
drm-current-kmod.
Maybe recompiling drm-current-kmod would help.
--
Gary Jennejohn
More information about the freebsd-current
mailing list