From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:33886 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758184Ab2EUUVY (ORCPT ); Mon, 21 May 2012 16:21:24 -0400 Message-ID: <4FBAA3A5.4070200@ladisch.de> Date: Mon, 21 May 2012 22:20:53 +0200 From: Clemens Ladisch MIME-Version: 1.0 To: Rob Allen CC: Yinghai Lu , Stefan Richter , Ram Pai , linux1394-devel@lists.sourceforge.net, linux-pci@vger.kernel.org Subject: Re: [Bug 43244] New: firewire_ohci prevents boot References: <20120513221357.7574ae79@stein> <4FB0A6F6.9050504@ladisch.de> <4FB3B159.2090401@ladisch.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-pci-owner@vger.kernel.org List-ID: Rob Allen wrote: > I've built the kernel and I can replicate the failure. > > However, I'm having trouble getting the log output. As soon as I see > the "firewire_ohci: Failed to set Link Power Status" message, the > machine locks up. After cycling the power, that log output isn't > anywhere in /var/log anywhere (even if I booted with 'rw'). Blacklist the firewire-ohci module (man modprobe.d), then you should be able to get the log output until before the driver loads. To see the remaining messages on the screen, load it with "modprobe firewire-ohci" after raising the console log level with "dmesg -n 8". Regards, Clemens