Hello, I have seen recently that libdrm has has been revised for an obscur minor/major checking. So I have updated libdrm and I have rebuilt the intel driver hoping this woult be linked with my issue.
Unfortunately…. Same result = kernel panic I can confirm that my system is intializing drm on drm0 minor (not major) Regards David Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 De : Microsoft Roaming<mailto:[email protected]> Envoyé le :jeudi 9 mars 2017 20:54 À : [email protected]<mailto:[email protected]> Objet :RE: FreeBSD Port: xf86-video-intel-2.99.917.20170228 Hello, CrashReport = FreeBSD 11 amd64 USB portable drive Panic line suggests that system tries to create a device dri/card0 already existing on my system with mode 666 owned by root/video. DRI device is already present in my system due to vt console in graphic mode and some stuffs that seem to initialize libdrm at startup even with no « x » session open. Moreover, preloading i915kms.ko was also a workaround to block an attempt to load mistakenly the i915ko when invoking « « x ». Xorg.0.log = FreeBSD 11 i386 USB portable drive On i386 in seems that intel driver get corrupted. The first time I launch « « x » it goes to kernel panic with immediate restart in the same way described ebove for amd64, but after when I try again xorg hangs complaining of a bad intel driver file format (see the log). If I rebuild the driver, so it goas again to Kernel panic, and just after to a freeze of Xorg launching process… this is the reason why I think that Intel driver file get corrupted on i386, but not on amd64 where the symptoms are always the same. It is as if the system tried to load KMS module that is already loaded in my case or tried to initialize drm that is already set up. In the two case, Rolling back to previous revison port version solves the issue. Regards, David Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 De : Martin MATO<mailto:[email protected]> Envoyé le :mercredi 8 mars 2017 09:00 À : Microsoft Roaming<mailto:[email protected]> Objet :Re: FreeBSD Port: xf86-video-intel-2.99.917.20170228 Greetings So the problem is more complicated than a simple Xorg crash, and/or a broken port. Please, post on the lists the result of the procedure here https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html they surely help you there. regards Martin Le 07/03/2017 à 19:26, Microsoft Roaming a écrit : > > Hello, > > > > There is no error in Xorg log because it generates immedately a kernel > panic before xorg can start > > > > I have tried again on another computer an HP EL800O… same problems > (but with the same FreeBSD as I am testing with a FreeBSD intalled on > a USB drive) > > > > HP EL8000 : Chipset Intel Q45 > > > > HP Elite 2530P : QS45 Express > > > > I have also tried to rebuild all libraries : libdrm, dri libGL libEGL > > > > Maybe an issue related to some old chipsets > > > > Regards > > > > David > > > > > > Provenance : Courrier <https://go.microsoft.com/fwlink/?LinkId=550986> > pour Windows 10 > > > > *De : *Martin MATO <mailto:[email protected]> > *Envoyé le :*mardi 7 mars 2017 01:14 > *À : *Microsoft Roaming <mailto:[email protected]> > *Objet :*re: FreeBSD Port: xf86-video-intel-2.99.917.20170228 > > > > Greetings > > Just updated the port on my latitude D830 > > no crashes , no problems. running compiz-manager flawlessly also. > > > > what is the errors shown in Xorg.0.log or the console output? > > > > > > > > > Message du 06/03/17 21:10 > > De : "Microsoft Roaming" <[email protected]> > > A : "[email protected]" <[email protected]> > > Copie à : "[email protected]" <[email protected]> > > Objet : FreeBSD Port: xf86-video-intel-2.99.917.20170228 > > > > Hello, > > > > Please U R G E N T L Y mark this port as broken or roll back to the > revision r433863 > > > > Invoking ‘X’ now causes crashes. Even when I force deactivation of > any acceleration in the xorg.conf, it crashes. The sole solution is to > use the sfcb or vesa driver, it crashes also with driver modesetting > > > > So I suspect it could be an issue related to KMS > > > > I rolled back to r433863 and it works back > > > > NOTE : tested on an old HP laptop 2530p > > > > Best Regards, > > > > David > > > > > > > > Provenance : > Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 > > > > _______________________________________________ > > [email protected] mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "[email protected]" > > > > >
CrashReport
Description: CrashReport
Xorg.0.log
Description: Xorg.0.log
_______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
