From owner-freebsd-current@FreeBSD.ORG Sat Jan 25 17:56:26 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DEAD7D24 for ; Sat, 25 Jan 2014 17:56:25 +0000 (UTC) Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 68CDC14A9 for ; Sat, 25 Jan 2014 17:56:25 +0000 (UTC) Received: by mail-bk0-f51.google.com with SMTP id w10so1936678bkz.24 for ; Sat, 25 Jan 2014 09:56:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version:content-type:subject :from:date:to:message-id; bh=ju45PvSvMTRHKJr2A+2FOArfPBBL6Id6exgNdVA1vWM=; b=qSjiak9cKNt46K4K/DwS0y9XFjGHTjRwGXcTxQNo+BNA6RngnLfQXpmI92gZxlX+8j dnFYUu545z7nHArmBVO+QDcX92LsgWAkl560XIeVQw9G9vMctxmbCVWMlT8J+RS0bg0u OjWuhQiBNHu4g/XSTJgon5TnFScUQH4HzTrz3fMgq6Husr62e/34kJgGIhMaa+u/daFO vtceOsZ98y4QkGmKrNS0ZXeFy5uvvD4hi5FNCsjjyYABy+FL7xNGNZ0HLMtk9w0tnzlx rMco/mYpThKgRl6vcVoad3297zH6pJQtkY3q5NghVWtRJtofWxoLSi5jYBDCk05K5abr vang== X-Received: by 10.204.171.204 with SMTP id i12mr37648bkz.126.1390672583817; Sat, 25 Jan 2014 09:56:23 -0800 (PST) Received: from ?IPV6:2001:470:7b2f:0:d02b:d335:23e4:fe54? ([2001:470:7b2f:0:d02b:d335:23e4:fe54]) by mx.google.com with ESMTPSA id o11sm6993370bkg.13.2014.01.25.09.56.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 09:56:23 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: <1367fd4d-9128-4df0-a250-fb3c1f67f0c5@email.android.com> References: <1367fd4d-9128-4df0-a250-fb3c1f67f0c5@email.android.com> MIME-Version: 1.0 Subject: Re: Newcons radeonkms - Failed to load firmware "radeonkmsfw_TURKS_PFP" From: "Mike C." Date: Sat, 25 Jan 2014 17:56:19 +0000 To: "freebsd-current@freebsd.org" Message-ID: <83d3287c-e2d1-4512-92a8-4bed5be1455b@email.android.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Sat, 25 Jan 2014 17:56:26 -0000 the line: error: [drm:pid0evergreen_startup] *ERROR* radeon: MC ucode required for NI+ is maybe more relevant? the other error seems to be related with GPU acceleration, but this one seems to be causing me init failure? Or not... Thanks "Mike C." wrote: > >Please see the attached jpeg for the full error. > >After rebuilding the kernel with newcons support (which is working) >I've placed radeonkms_load="YES" in boot loader and rebooted and get >this screen. > >what am I doing wrong? > >thanks >-- >Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-current@FreeBSD.ORG Sat Jan 25 18:58:40 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE741688 for ; Sat, 25 Jan 2014 18:58:40 +0000 (UTC) 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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 72CA21957 for ; Sat, 25 Jan 2014 18:58:40 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id s0PIwdUp068155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 25 Jan 2014 10:58:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id s0PIwdsw068154 for freebsd-current@freebsd.org; Sat, 25 Jan 2014 10:58:39 -0800 (PST) (envelope-from sgk) Date: Sat, 25 Jan 2014 10:58:39 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: Re: Instant panic CAM or USB subsystem Message-ID: <20140125185839.GA68145@troutmask.apl.washington.edu> References: <20140125172106.GA67590@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140125172106.GA67590@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.22 (2013-10-16) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Sat, 25 Jan 2014 18:58:40 -0000 On Sat, Jan 25, 2014 at 09:21:06AM -0800, Steve Kargl wrote: > If I plug my Samsung Intensity II cellphone into a usb port, > I get an instant panic. This is 100% reproducible. I have > the core and kernel for further debugging. Dmesg.boot follows > my sig. Panic occurs with a kernel compiled with either clang or gcc. -- steve