From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank van Maarseveen Subject: 2.6.39.3 radeon crash when firmware loading fails Date: Tue, 19 Jul 2011 14:41:07 +0200 Message-ID: <20110719124107.GA20793@janus> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from janus.localdomain (frankvm.xs4all.nl [83.163.148.79]) by gabe.freedesktop.org (Postfix) with ESMTP id 6C4409E980 for ; Tue, 19 Jul 2011 05:47:56 -0700 (PDT) Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org When booting 2.6.39.3 with radeon and KMS enabled the boot messages stop at some point (clocksource switching to TSC or something) and about 60 seconds later the screen turns into a noise pattern with some irregularities on top (i.e. crash). This happens when the radeon driver is built-in. This can be triggered too when it is a module by "insmod radeon.ko" when there is no provision to automatically load firmware (e.g via /sbin/hotplug). The insmod hangs for `cat /sys/class/firmware/timeout` seconds (default 60) and after that it crashes with identical symptoms. When /sbin/hotplug is present for loading firmware (radeon/RV620_pfp.bin, radeon/RV620_me.bin, radeon/R600_rlc.bin in this case) then all goes well. Because of this it is not possible to use a built-in radeon driver with KMS enabled. lspci -vv: 01:00.0 VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD 3450] (prog-if 00 [VGA controller]) Subsystem: Dell Device 0342 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: radeon -- Frank