From owner-freebsd-x11@freebsd.org Fri Jan 13 04:42:42 2017 Return-Path: Delivered-To: freebsd-x11@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 69451CAD52A for ; Fri, 13 Jan 2017 04:42:42 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41F0F1F75 for ; Fri, 13 Jan 2017 04:42:42 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484282556810489.67111449008314; Thu, 12 Jan 2017 20:42:36 -0800 (PST) Date: Thu, 12 Jan 2017 20:42:36 -0800 From: Matthew Macy To: "Anindya Mukherjee" Cc: "freebsd-x11@freebsd.org" Message-ID: <1599622717e.b20ae7df163785.3066731730254505348@nextbsd.org> In-Reply-To: References: , <15994d9f54d.10dcb859e146706.6480944492081388621@nextbsd.org> , <15996070960.c3ab3668162091.4357860180622603422@nextbsd.org> Subject: RE: Crash with radeonkms MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 04:42:42 -0000 OK. That's odd. I'll look in to it and get back to you. Does the same thing not happen when you load amdgpu or i915? -M ---- On Thu, 12 Jan 2017 20:33:12 -0800 Anindya Mukherjee wrote ---- > Interesting... I did build a new kernel from the drm-next branch: > > uname -a > FreeBSD triskelion 12.0-CURRENT FreeBSD 12.0-CURRENT #0 7ec6ee8bca5(drm-next): Tue Jan 10 22:06:43 PST 2017 root@triskelion:/usr/obj/usr/home/anindya/graphics/freebsd-base-graphics/sys/GENERIC amd64 > > anindya@triskelion:~/graphics/freebsd-base-graphics [20:30:22]% git branch > * drm-next > drm-next-4.7 > > My /boot/kernel/kernel file is also new and different from the installed version. There were no errors during the build. I wonder if I made a mistake somewhere. > > Anindya > ________________________________________ > From: Matthew Macy [mmacy@nextbsd.org] > Sent: January 12, 2017 8:12 PM > To: Anindya Mukherjee > Cc: freebsd-x11@freebsd.org > Subject: RE: Crash with radeonkms > > I'm guessing you're trying to run it on a kernel that isn't drm-next. > -M > > > ---- On Thu, 12 Jan 2017 20:08:38 -0800 Anindya Mukherjee wrote ---- > > Thanks for the tip! I loaded linuxkpi, drm first, and then tried to load radeonkms with the following results: > > > > [drm] Initialized > > link_elf_obj: symbol acpi_get_table undefined > > linker_load_file: Unsupported file type > > > > I see a protoype for this function (and others) in sys/compat/linuxkpi/common/include/acpi/acpifx.h:494. Perhaps all of them are missing? Can we add a linker script or something similar? > > > > Anindya > > > > ________________________________________ > > From: Matthew Macy [mmacy@nextbsd.org] > > Sent: January 12, 2017 2:43 PM > > To: Anindya Mukherjee > > Cc: freebsd-x11@freebsd.org > > Subject: RE: Crash with radeonkms > > > > ---- On Thu, 12 Jan 2017 09:52:21 -0800 Anindya Mukherjee wrote ---- > > > There seems to be an error while trying to load the "radeonkms" module (#15). It then tries to unload it, and crashes. > > > > Correct. It's almost certainly missing symbols. To find out what they are without crashing your system, load linuxkpi, then load drm, and *then* load radeon. Note that if your hardware is SI or newer it's supported by amdgpu. > > > > -M > > > > > _______________________________________________ > > > freebsd-x11@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > > > > > > > > > > >