From owner-freebsd-current@freebsd.org Wed Feb 22 05:32:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8BE5CE9987; Wed, 22 Feb 2017 05:32:43 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C48CA873; Wed, 22 Feb 2017 05:32:43 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v1M5WgMc004254 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Feb 2017 21:32:42 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v1M5Wglt004253; Tue, 21 Feb 2017 21:32:42 -0800 (PST) (envelope-from sgk) Date: Tue, 21 Feb 2017 21:32:42 -0800 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Cc: kib@freebsd.org Subject: Re: drm2, i915kms cause instant lock-up Message-ID: <20170222053242.GA4204@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170220235224.GA91194@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170220235224.GA91194@troutmask.apl.washington.edu> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 05:32:43 -0000 Well, I found the guilty commit. r313934 breaks loading either i915kms.ko or drm2.ko on a Dell Latitude D530 laptop. details below. I'll also note that starting at r313902 or so, after loading i915kms.ko console output on vt is slooooooow. A simply 'time ls /usr/bin' reports 6.27 real, 4.00 user, and 1.08 sys, but the drawing on screen takes more than 30 seconds. One can painfully watch each line of output be rastered across the screen. Kib you can read the details below. If you need more info, ping me. I did notice that i686_mem.c used constants of the form 0xffffULL prior to the merge into x86_mem.c. You now use 0xfffUL. I have no idea whether this is related to cause. -- steve On Mon, Feb 20, 2017 at 03:52:24PM -0800, Steve Kargl wrote: > With a kernel and world from r313943 sources (circa > Feb 19, 2017), kldload of either drm2.ko or i915kms.ko > will lock up the system. There is no keyboard response, > screen output, or panic. Just a locked up system. > > A kernel from r313027 and its modules boots fine. > 'kldload drm2.ko' yields the following in /var/log/messages: > > agp0: on vgapci0 > agp0: aperture size is 256M, detected 7676k stolen memory > info: [drm] Initialized drm 1.1.0 20060810 > > 'kldload drm2.ko' yields the following in /var/log/messages: > drmn0: on vgapci0 > intel_iicbb0 on drmn0 > iicbus0: on iicbb0 addr 0xf2 > iic0: on iicbus0 > iicbus1: on intel_gmbus0 > iic1: on iicbus1 > intel_iicbb1 on drmn0 > iicbus2: on iicbb1 addr 0xf2 > iic2: on iicbus2 > iicbus3: on intel_gmbus1 > iic3: on iicbus3 > intel_iicbb2 on drmn0 > iicbus4: on iicbb2 addr 0xf2 > iic4: on iicbus4 > iicbus5: on intel_gmbus2 > iic5: on iicbus5 > intel_iicbb3 on drmn0 > iicbus6: on iicbb3 addr 0xf2 > iic6: on iicbus6 > iicbus7: on intel_gmbus3 > iic7: on iicbus7 > intel_iicbb4 on drmn0 > iicbus8: on iicbb4 addr 0xf2 > iic8: on iicbus8 > iicbus9: on intel_gmbus4 > iic9: on iicbus9 > intel_iicbb5 on drmn0 > iicbus10: on iicbb5 addr 0xf2 > iic10: on iicbus10 > iicbus11: on intel_gmbus5 > iic11: on iicbus11 > info: [drm] MSI enabled 1 message(s) > info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). > info: [drm] Driver supports precise vblank timestamp query. > composite sync not supported > intel_sdvo_ddc_proxy397632 on drmn0 > intel_sdvo_ddc_proxy397632: detached > intel_sdvo_ddc_proxy397664 on drmn0 > intel_sdvo_ddc_proxy397664: detached > drmn0: taking over the fictitious range 0xe0000000-0xf0000000 > info: [drm] initialized overlay support > info: [drm] Connector LVDS-1: get mode from tunables: > info: [drm] - kern.vt.fb.modes.LVDS-1 > info: [drm] - kern.vt.fb.default_mode > info: [drm] Connector VGA-1: get mode from tunables: > info: [drm] - kern.vt.fb.modes.VGA-1 > info: [drm] - kern.vt.fb.default_mode > info: [drm] Connector SVIDEO-1: get mode from tunables: > info: [drm] - kern.vt.fb.modes.SVIDEO-1 > info: [drm] - kern.vt.fb.default_mode > composite sync not supported > fbd0 on drmn0 > VT: Replacing driver "vga" with new "fb". > info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 > > A diff of dmesg.boot for the good kernel and bad kernel shows > > --- /root/dmesg.good 2017-02-20 13:30:06.707702000 -0800 > +++ /root/dmesg.bad 2017-02-20 13:42:10.271942000 -0800 > @@ -2,11 +2,11 @@ > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > -FreeBSD 12.0-CURRENT #3 r313027: Mon Feb 20 11:59:15 PST 2017 > +FreeBSD 12.0-CURRENT #1 r313943: Sun Feb 19 09:18:03 PST 2017 > root@laptop-kargl:/mnt/obj/mnt/src/sys/MOBILE i386 > FreeBSD clang version 3.9.1 (tags/RELEASE_391/final 289601) (based on LLVM 3.9.1) > VT(vga): text 80x25 > -CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.05-MHz 686-class CPU) > +CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.04-MHz 686-class CPU) > Origin="GenuineIntel" Id=0x6fd Family=0x6 Model=0xf Stepping=13 > Features=0xbfebfbff > Features2=0xe3bd > @@ -15,7 +15,7 @@ > VT-x: (disabled in BIOS) HLT,PAUSE > TSC: P-state invariant, performance statistics > real memory = 4294967296 (4096 MB) > -avail memory = 3663994880 (3494 MB) > +avail memory = 3665018880 (3495 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > @@ -24,7 +24,7 @@ > ioapic0 irqs 0-23 on motherboard > random: entropy device external interface > kbd1 at kbdmux0 > -module_register_init: MOD_LOAD (vesa, 0xc0bf7440, 0) error 19 > +module_register_init: MOD_LOAD (vesa, 0xc0ae6db0, 0) error 19 > nexus0 > vtvga0: on motherboard > acpi0: on motherboard > @@ -42,7 +42,7 @@ > attimer0: port 0x40-0x43,0x50-0x53 irq 2 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > -Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > +Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > pcib0: on acpi0 > pcib0: failed to parse resources: AE_AML_NO_RESOURCE_END_TAG > > The module_register_init difference seems suspicious. > > -- > Steve > 20161221 https://www.youtube.com/watch?v=IbCHE-hONow > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Steve 20161221 https://www.youtube.com/watch?v=IbCHE-hONow