Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261163AbVE1QRY (ORCPT ); Sat, 28 May 2005 12:17:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261161AbVE1QRX (ORCPT ); Sat, 28 May 2005 12:17:23 -0400 Received: from clock-tower.bc.nu ([81.2.110.250]:57793 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S261160AbVE1QRM (ORCPT ); Sat, 28 May 2005 12:17:12 -0400 Subject: Re: How to find if BIOS has already enabled the device From: Alan Cox To: Parag Warudkar Cc: John Livingston , Aleksey Gorelov , Linux Kernel Mailing List In-Reply-To: <200505281018.18092.kernel-stuff@comcast.net> References: <0EF82802ABAA22479BC1CE8E2F60E8C31B5206@scl-exch2k3.phoenix.com> <200505280957.46853.kernel-stuff@comcast.net> <1117289090.2390.14.camel@localhost.localdomain> <200505281018.18092.kernel-stuff@comcast.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1117296905.2356.23.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Sat, 28 May 2005 17:15:07 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 571 Lines: 13 On Sad, 2005-05-28 at 15:18, Parag Warudkar wrote: > dmesg is perfectly normal, not even timestamp differences before and after > call to pci_enable_device - since the machine is completely hung for that > period - not even the clock is ticking? A spurious jammed IRQ is one candidate - but you haven't provided dmesg data - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/