public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Rajesh Shah <rajesh.shah@intel.com>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-mm1
Date: Thu, 23 Jun 2005 13:32:39 -0700	[thread overview]
Message-ID: <20050623133238.A24026@unix-os.sc.intel.com> (raw)
In-Reply-To: <42BAFADF.2030804@ens-lyon.org>; from Brice.Goglin@ens-lyon.org on Thu, Jun 23, 2005 at 08:09:35PM +0200

On Thu, Jun 23, 2005 at 08:09:35PM +0200, Brice Goglin wrote:
> dmesg and dsdt are attached.
> 
The host bridge resources being reported were fine. I think this
failure is a yenta bug exposed by the combination of the host
bridge resource collection patch and the patch to improve the
handling for transparent bridges. I think the yenta code thinks
there's a resource conflict for the ranges being decoded by the
cardbus bridge when in fact there isn't any conflict in this case.
It then claims and reprograms the cardbus bridge to IO resources
that are already programmed into another device (winmodem in this
case), causing problems.

Does the following patch to 2.6.12-mm1 fix the problem?
------------------------------

Index: linux-2.6.12-mm1/drivers/pcmcia/yenta_socket.c
===================================================================
--- linux-2.6.12-mm1.orig/drivers/pcmcia/yenta_socket.c
+++ linux-2.6.12-mm1/drivers/pcmcia/yenta_socket.c
@@ -562,9 +562,6 @@ static int yenta_try_allocate_res(struct
 	bus = socket->dev->subordinate;
 	res = socket->dev->resource + PCI_BRIDGE_RESOURCES + nr;
 	res->name = bus->name;
-	res->flags = type;
-	res->start = 0;
-	res->end = run;
 	root = pci_find_parent_resource(socket->dev, res);
 
 	if (!root)

  reply	other threads:[~2005-06-23 20:38 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20  6:30 2.6.12-mm1 Andrew Morton
2005-06-20  6:57 ` 2.6.12-mm1 Benjamin Herrenschmidt
2005-06-20  8:54   ` 2.6.12-mm1 Ethan Benson
2005-06-20  7:46 ` 2.6.12-mm1 Brice Goglin
2005-06-20  8:14   ` 2.6.12-mm1 Dominik Brodowski
2005-06-20  8:49     ` 2.6.12-mm1 Brice Goglin
     [not found]       ` <20050620085449.GA32330@isilmar.linta.de>
2005-06-20 13:11         ` 2.6.12-mm1 Brice Goglin
2005-06-22 23:34           ` 2.6.12-mm1 Rajesh Shah
2005-06-23  6:25             ` 2.6.12-mm1 Brice Goglin
2005-06-23 17:05               ` 2.6.12-mm1 Rajesh Shah
2005-06-23 18:09                 ` 2.6.12-mm1 Brice Goglin
2005-06-23 20:32                   ` Rajesh Shah [this message]
2005-06-23 21:07                     ` 2.6.12-mm1 Brice Goglin
2005-06-23 21:33                       ` 2.6.12-mm1 Brice Goglin
2005-06-20  7:59 ` 2.6.12-mm1 Brice Goglin
2005-06-21 12:40   ` 2.6.12-mm1 Brice Goglin
2005-06-21 16:27     ` 2.6.12-mm1 Takashi Iwai
2005-06-21 16:32       ` 2.6.12-mm1 Takashi Iwai
2005-06-21 17:02       ` 2.6.12-mm1 Brice Goglin
2005-06-21 17:16         ` 2.6.12-mm1 Takashi Iwai
2005-06-21 19:39           ` 2.6.12-mm1 Brice Goglin
2005-06-22 10:10             ` 2.6.12-mm1 Takashi Iwai
2005-06-20  9:48 ` [patch] 2.6.12-mm1: saa7134-core.c compile error Adrian Bunk
2005-06-20 22:19   ` Michael Krufky
2005-06-20 11:36 ` [PATCH] bttv fix [was: 2.6.12-mm1] J.A. Magallon
2005-06-20 11:38 ` 2.6.12-mm1 J.A. Magallon
2005-06-20 16:36   ` 2.6.12-mm1 Jeff Garzik
2005-06-20 22:35     ` 2.6.12-mm1 J.A. Magallon
2005-06-20 12:32 ` [PATCH] Fix Reiser4 Dependencies Andrew James Wade
2005-06-20 18:26   ` Hans Reiser
2005-06-20 20:44     ` Andrew James Wade
2005-06-21 11:27       ` Edward Shishkin
2005-06-21 18:47         ` Hans Reiser
2005-06-21 19:26           ` Andrew James Wade
2005-06-22  8:56             ` Edward Shishkin
2005-06-22  8:39           ` Edward Shishkin
2005-06-20 13:14 ` 2.6.12-mm1 Andy Whitcroft
2005-06-21 22:55   ` 2.6.12-mm1 Greg KH
2005-06-22  9:23     ` 2.6.12-mm1 Andy Whitcroft
2005-06-22 10:04       ` 2.6.12-mm1 Ivan Kokshaysky
2005-06-20 13:21 ` 2.6.12-mm1: Kernel BUG at "fs/open.c":935 Rafael J. Wysocki
2005-06-20 13:54   ` Dipankar Sarma
2005-06-20 14:05     ` Rafael J. Wysocki
2005-06-20 17:38 ` 2.6.12-mm1: drivers/misc/ibmasm/ compile error Adrian Bunk
2005-06-20 20:24   ` Andrew Morton
2005-06-20 18:29 ` 2.6.12-mm1 Jean Delvare
2005-06-20 20:41   ` 2.6.12-mm1 Andrew Morton
2005-06-20 21:11     ` 2.6.12-mm1 Jean Delvare
2005-06-20 21:23       ` 2.6.12-mm1 Andrew Morton
2005-06-20 21:42         ` 2.6.12-mm1 Jean Delvare
2005-06-20 21:53           ` 2.6.12-mm1 Andrew Morton
2005-06-21 20:06           ` 2.6.12-mm1 Mauro Carvalho Chehab
2005-06-21 21:25             ` 2.6.12-mm1 Jean Delvare
2005-06-20 18:39 ` gregkh-usb-usb-isp116x-hcd-add.patch (was 2.6.12-mm1) Alexey Dobriyan
2005-06-20 22:15 ` 2.6.12-mm1 J.A. Magallon
2005-06-20 22:34   ` iptables bug (was: Re: 2.6.12-mm1) Andrew Morton
2005-06-20 23:39     ` iptables bug Patrick McHardy
2005-06-21 19:21       ` Stephen Jones
2005-06-22  1:52         ` Patrick McHardy
2005-06-21 22:09 ` [PATCH] more signed char cleanups in scripts J.A. Magallon
2005-06-21 22:18   ` Andrew Morton
2005-06-21 22:59     ` J.A. Magallon
2005-06-22 11:46       ` Paulo Marques
2005-06-22  0:05     ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050623133238.A24026@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox