Bug 235203 - Xorg crashes on startup since updating 2019-01-24
Summary: Xorg crashes on startup since updating 2019-01-24
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-x11 mailing list
URL:
Keywords: i915
Depends on:
Blocks:
 
Reported: 2019-01-25 20:19 UTC by Jason W. Bacon
Modified: 2019-02-19 00:01 UTC (History)
0 users

See Also:


Attachments
Xorg log (15.53 KB, text/plain)
2019-01-25 20:19 UTC, Jason W. Bacon
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason W. Bacon freebsd_committer 2019-01-25 20:19:47 UTC
Created attachment 201399 [details]
Xorg log

Running on a Lenovo X201 with Intel video.

vgapci0@pci0:0:2:0:     class=0x030000 card=0x215a17aa chip=0x00468086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Core Processor Integrated Graphics Controller'
    class      = display
    subclass   = VGA

FreeBSD mako.acadix.biz 11.2-RELEASE-p8 FreeBSD 11.2-RELEASE-p8 #0: Tue Jan  8 21:35:12 UTC 2019     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

rc.conf:

kld_list="i915kms"

Xorg has always worked fine and no configuration changes were made, but after running pkg upgrade yesterday, Xorg crashes on startup.  Xorg log attached.

I tried switching to graphics/drm-kmod and /boot/modules/i915kms.ko, but this causes a panic instead.

Worked around it for now by installing the xf86-video-intel package.
Comment 1 Jason W. Bacon freebsd_committer 2019-01-27 14:12:46 UTC
Same issue on a ThinkCenter M92p, also using modesetting driver from base.  In this case, switching to drm-kmod resolved the issue.

pciconf -lv:

vgapci0@pci0:0:2:0:     class=0x030000 card=0x308617aa chip=0x01528086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller'
    class      = display
    subclass   = VGA

Xorg.0.log:

[    59.092] (--) PCI:*(0:0:2:0) 8086:0152:17aa:3086 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/65536

1. pkg install drm-kmod

2. In rc.conf, change kld_list="i915kms" to kld_list="/boot/modules/i915kms.ko"

I would consider this a more or less permanent fix, pending the future organization of DRM modules.

It would still be good to know why the new xorg is apparently incompatible with the base i915 module, since the newer module causes a panic on my X201 and running the obsolete xf86-video-intel driver is probably not sustainable.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2019-02-07 11:12:01 UTC
Override bogus default assignment.
Comment 3 Jan Beich freebsd_committer 2019-02-07 11:47:36 UTC
Likely a duplicate of bug 235487. Thank you for documenting workarounds.
Comment 4 Jan Beich freebsd_committer 2019-02-19 00:01:51 UTC
(In reply to Jason W. Bacon from comment #0)
> I tried switching to graphics/drm-kmod and /boot/modules/i915kms.ko,
> but this causes a panic instead.

Can you report the panic to https://github.com/FreeBSDDesktop/kms-drm/issues/ ? Also try newer FreeBSD version (or just kernel) which supports newer drm-*-kmod.

Probably all hardware supported by drm2 (i915kms, radeonkms) from base or drm-legacy-kmod is supposed to work with drm-kmod. Obviously, there're bugs because the focus is on recent hardware, usually *not* supported by drm2.

(In reply to Jason W. Bacon from comment #1)
> Same issue on a ThinkCenter M92p, also using modesetting driver from
> base.  In this case, switching to drm-kmod resolved the issue.

SandyBridge is known to work on drm-kmod, so IvyBridge also working isn't surprising. Did you test on the same FreeBSD version? I'm curious if drm-fbsd11.2-kmod is less stable on old hardware.