Date: Mon, 11 Feb 2019 09:56:31 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Niclas Zeising <zeising+freebsd@daemonic.se> Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org, freebsd-x11@freebsd.org Subject: Re: drm2 removed? Message-ID: <20190211175631.GA42723@troutmask.apl.washington.edu> In-Reply-To: <1a9ec129-84e8-0fd3-3768-9e40590347ff@daemonic.se> References: <20190211161205.GB41262@troutmask.apl.washington.edu> <20190211162020.GA41438@troutmask.apl.washington.edu> <e65fc614-3723-bcce-ef34-c1e24b09e4b5@daemonic.se> <20190211173653.GA42437@troutmask.apl.washington.edu> <1a9ec129-84e8-0fd3-3768-9e40590347ff@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote: > On 2/11/19 6:36 PM, Steve Kargl wrote: > > > > The patch allows the port to be built. > > > > kldloading the i915kms module causes a 'black screen > > of death' > > > > I'll note that there seems to be a race condition in > > booting a kernel (with or without the drm2 stuff). > > During boot the kernel hangs (see below) : > > > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > FreeBSD/SMP: 1 package(s) x 2 core(s) > > Firmware Warning (ACPI): Incorrect checksum in table [TCPA] - 0x80, should be 0x24 (20190108/tbprint-337) > > ioapic0: Changing APIC ID to 2 > > ioapic0 <Version 2.0> irqs 0-23 on motherboard > > Launching APs: 1 > > > > *** kernel hangs here sometimes *** > > > > Timecounter "TSC" frequency 1995048460 Hz quality 1000 > > random: entropy device external interface > > kbd1 at kbdmux0 > > I assume you load the kernel module either manually with kldload or > using kld_list in rc.conf, not by loading it from the loader? After a succesful boot. I login as root and manually kldload the i915kms module. > So there is two bugs? One bug is that the kernel hangs while booting, > and the other is that you get a black screen when loading the drm module > after the kernel is mostly done booting? Yes, two bugs. kernel sometimes hangs after lauching the cpus but before random device is ready. Loading the new drm2 module cause a black screen of death. Don't know if it helps. Extracted info from /var/log/messages login[987]: ROOT LOGIN (root) ON ttyv0 (manually kldload i915kms.ko module) kernel: info: [drm] Initialized drm 1.1.0 20060810 kernel: drmn0: <Intel i965GM> on vgapci0 kernel: intel_iicbb0 on drmn0 kernel: iicbus0: <Philips I2C bus> on iicbb0 addr 0x30 kernel: iic0: <I2C generic I/O> on iicbus0 kernel: iicbus1: <Philips I2C bus> on intel_gmbus0 kernel: iic1: <I2C generic I/O> on iicbus1 kernel: intel_iicbb1 on drmn0 kernel: iicbus2: <Philips I2C bus> on iicbb1 addr 0x30 kernel: iic2: <I2C generic I/O> on iicbus2 kernel: iicbus3: <Philips I2C bus> on intel_gmbus1 kernel: iic3: <I2C generic I/O> on iicbus3 kernel: intel_iicbb2 on drmn0 kernel: iicbus4: <Philips I2C bus> on iicbb2 addr 0x30 kernel: iic4: <I2C generic I/O> on iicbus4 kernel: iicbus5: <Philips I2C bus> on intel_gmbus2 kernel: iic5: <I2C generic I/O> on iicbus5 kernel: intel_iicbb3 on drmn0 kernel: iicbus6: <Philips I2C bus> on iicbb3 addr 0x30 kernel: iic6: <I2C generic I/O> on iicbus6 kernel: iicbus7: <Philips I2C bus> on intel_gmbus3 kernel: iic7: <I2C generic I/O> on iicbus7 kernel: intel_iicbb4 on drmn0 kernel: iicbus8: <Philips I2C bus> on iicbb4 addr 0x30 kernel: iic8: <I2C generic I/O> on iicbus8 kernel: iicbus9: <Philips I2C bus> on intel_gmbus4 kernel: iic9: <I2C generic I/O> on iicbus9 kernel: intel_iicbb5 on drmn0 kernel: iicbus10: <Philips I2C bus> on iicbb5 addr 0x30 kernel: iic10: <I2C generic I/O> on iicbus10 kernel: iicbus11: <Philips I2C bus> on intel_gmbus5 kernel: iic11: <I2C generic I/O> on iicbus11 kernel: vgapci0: attempting to allocate 1 MSI vectors (1 supported) kernel: msi: routing MSI IRQ 34 to local APIC 1 vector 55 kernel: vgapci0: using IRQ 34 for MSI kernel: info: [drm] MSI enabled 1 message(s) kernel: info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). kernel: info: [drm] Driver supports precise vblank timestamp query. kernel: composite sync not supported kernel: intel_sdvo_ddc_proxy397632 on drmn0 kernel: intel_sdvo_ddc_proxy397632: detached kernel: intel_sdvo_ddc_proxy397664 on drmn0 kernel: intel_sdvo_ddc_proxy397664: detached kernel: drmn0: taking over the fictitious range 0xe0000000-0xf0000000 kernel: info: [drm] initialized overlay support kernel: info: [drm] Connector LVDS-1: get mode from tunables: kernel: info: [drm] - kern.vt.fb.modes.LVDS-1 kernel: info: [drm] - kern.vt.fb.default_mode kernel: info: [drm] Connector VGA-1: get mode from tunables: kernel: info: [drm] - kern.vt.fb.modes.VGA-1 kernel: info: [drm] - kern.vt.fb.default_mode kernel: info: [drm] Connector SVIDEO-1: get mode from tunables: kernel: info: [drm] - kern.vt.fb.modes.SVIDEO-1 kernel: info: [drm] - kern.vt.fb.default_mode kernel: composite sync not supported kernel: fbd0 on drmn0 kernel: VT: Replacing driver "vga" with new "fb". -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190211175631.GA42723>