Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756476AbYCVW3y (ORCPT ); Sat, 22 Mar 2008 18:29:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753282AbYCVW3p (ORCPT ); Sat, 22 Mar 2008 18:29:45 -0400 Received: from einhorn.in-berlin.de ([192.109.42.8]:56436 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753098AbYCVW3o (ORCPT ); Sat, 22 Mar 2008 18:29:44 -0400 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <47E587E8.4050103@s5r6.in-berlin.de> Date: Sat, 22 Mar 2008 23:27:52 +0100 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080219 SeaMonkey/1.1.8 MIME-Version: 1.0 To: "H. Peter Anvin" CC: Linus Torvalds , Ingo Molnar , Thomas Gleixner , Ivan Kokshaysky , Thomas Meyer , "Rafael J. Wysocki" , LKML , Adrian Bunk , Andrew Morton , Natalie Protasevich , bugme-daemon@bugzilla.kernel.org Subject: Re: ohci1394 problem (MMIO broken) (was 2.6.25-rc6-git6: Reported regressions from 2.6.24) [Bug 10080] References: <200803220259.48534.rjw@sisk.pl> <47E5350D.101@s5r6.in-berlin.de> <47E540E7.7030108@m3y3r.de> <47E54FA6.3060809@s5r6.in-berlin.de> <47E557D5.9020604@s5r6.in-berlin.de> <47E5815B.4080002@kernel.org> In-Reply-To: <47E5815B.4080002@kernel.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1815 Lines: 42 H. Peter Anvin wrote at http://bugzilla.kernel.org/show_bug.cgi?id=10080#c9 : > I'm confused about this. I looked at the original threads, and what really > stands out to me is that the original reporter had two drivers loaded for the > same hardware (firewire-ohci and ohci1394.) *In the best case* there is a > fundamental race condition there, meaning unpredictable behaviour would be the > norm. Hmm, right -- I didn't see this until now. Today's dmesg: http://bugzilla.kernel.org/attachment.cgi?id=15397&action=view [ 1.236587] firewire_ohci: Failed to remap registers [ 243.640549] ohci1394: fw-host0: Get PHY Reg timeout (etc.) However, the two drivers for the same device don't seem to be the problem. Looks like firewire-ohci was attempted to be bound to the controller much earlier than ohci1394. The error message means that firewire-ohci's pci_request_region() succeeded but pci_iomap() failed, hence the pci_driver.probe failed, hence firewire-ohci wasn't bound to the device, hence subsequent loading of ohci1394 (manually, I presume) was a valid action. IOW firewire-ohci was indeed already loaded, but not bound to the device because of the .probe failure; and ohci1394 was loaded much later. Same thing in the report in February: http://lkml.org/lkml/2008/2/23/244 [ 1.326958] firewire_ohci: Failed to remap registers [ 856.943807] ohci1394: fw-host0: Get PHY Reg timeout (here: ohci1394 manually loaded by insmod) (Let's see if bugme-daemon captures this...) -- Stefan Richter -=====-==--- --== =-==- http://arcgraph.de/sr/ -- 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/