From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Bunk Subject: Re: [Bugme-new] [Bug 8266] New: Exabyte 1x10 autoloader breaks on upgrade Date: Tue, 27 Mar 2007 00:49:01 +0200 Message-ID: <20070326224901.GK16477@stusta.de> References: <200703262150.l2QLopDA003694@fire-2.osdl.org> <20070326153346.7290081c.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="LwW0XdcUbUexiWVK" Return-path: Received: from emailhub.stusta.mhn.de ([141.84.69.5]:35389 "EHLO mailhub.stusta.mhn.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933762AbXCZWs6 (ORCPT ); Mon, 26 Mar 2007 18:48:58 -0400 Content-Disposition: inline In-Reply-To: <20070326153346.7290081c.akpm@linux-foundation.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Andrew Morton Cc: linux-scsi@vger.kernel.org, stable@kernel.org, "bugme-daemon@kernel-bugs.osdl.org" , freelsjd@ornl.gov, Jan Beulich , Alan Cox --LwW0XdcUbUexiWVK Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Mon, Mar 26, 2007 at 03:33:46PM -0700, Andrew Morton wrote: > On Mon, 26 Mar 2007 14:50:51 -0700 > bugme-daemon@bugzilla.kernel.org wrote: > > > http://bugzilla.kernel.org/show_bug.cgi?id=8266 > > > > Summary: Exabyte 1x10 autoloader breaks on upgrade > > Kernel Version: 2.6.20.4 > > Status: NEW > > Severity: high > > Owner: scsi_drivers-other@kernel-bugs.osdl.org > > Submitter: freelsjd@ornl.gov > > > > > > Most recent kernel where this bug did *NOT* occur: 2.6.20.3 > > Distribution: debian/stable/sarge > > Hardware Environment: amd64 > > Software Environment: amanda > > Problem Description: > > When upgrading from 2.6.20.3 to 2.6.20.4, the Exabyte 1x10 autoloader would be > > work anymore. I am using the aic79xx old driver because the aic79xx new driver > > had already broken (see my previous bugs 5268 and 7616) > > > > Steps to reproduce: > > upgrade from 2.6.20.3 to 2.6.20.4 > > We appear to have a regression in the stable kernel. > > Probably, that regression is in 2.6.21-rc5 as well. Please attach the dmesg's of both 2.6.20.3 and 2.6.20.4 in Bugzilla. Does reverting the attached patch fix it? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed --LwW0XdcUbUexiWVK Content-Type: text/x-diff; charset=utf-8 Content-Disposition: attachment; filename="adjust-legacy-ide-resource-setting.patch" >>From stable-bounces@linux.kernel.org Tue Mar 13 11:05:30 2007 From: Jan Beulich Date: Tue, 13 Mar 2007 14:04:11 -0400 Subject: adjust legacy IDE resource setting (v2) To: linux-stable Message-ID: <45F6E79B.1010208@redhat.com> From: Jan Beulich adjust legacy IDE resource setting (v2) The change to force legacy mode IDE channels' resources to fixed non-zero values confuses (at least some versions of) X, because the values reported by the kernel and those readable from PCI config space aren't consistent anymore. Therefore, this patch arranges for the respective BARs to also get updated if possible. Signed-off-by: Jan Beulich Acked-by: Alan Cox Signed-off-by: Andrew Morton Signed-off-by: Bartlomiej Zolnierkiewicz Cc: Chuck Ebbert Signed-off-by: Greg Kroah-Hartman --- drivers/pci/probe.c | 45 ++++++++++++++++++++++++++++++++------------- 1 file changed, 32 insertions(+), 13 deletions(-) --- a/drivers/pci/probe.c +++ b/drivers/pci/probe.c @@ -639,7 +639,34 @@ static void pci_read_irq(struct pci_dev dev->irq = irq; } -#define LEGACY_IO_RESOURCE (IORESOURCE_IO | IORESOURCE_PCI_FIXED) +static void change_legacy_io_resource(struct pci_dev * dev, unsigned index, + unsigned start, unsigned end) +{ + unsigned base = start & PCI_BASE_ADDRESS_IO_MASK; + unsigned len = (end | ~PCI_BASE_ADDRESS_IO_MASK) - base + 1; + + /* + * Some X versions get confused when the BARs reported through + * /sys or /proc differ from those seen in config space, thus + * try to update the config space values, too. + */ + if (!(pci_resource_flags(dev, index) & IORESOURCE_IO)) + printk(KERN_WARNING "%s: cannot adjust BAR%u (not I/O)\n", + pci_name(dev), index); + else if (pci_resource_len(dev, index) != len) + printk(KERN_WARNING "%s: cannot adjust BAR%u (size %04X)\n", + pci_name(dev), index, (unsigned)pci_resource_len(dev, index)); + else { + printk(KERN_INFO "%s: trying to change BAR%u from %04X to %04X\n", + pci_name(dev), index, + (unsigned)pci_resource_start(dev, index), base); + pci_write_config_dword(dev, PCI_BASE_ADDRESS_0 + index * 4, base); + } + pci_resource_start(dev, index) = start; + pci_resource_end(dev, index) = end; + pci_resource_flags(dev, index) = + IORESOURCE_IO | IORESOURCE_PCI_FIXED | PCI_BASE_ADDRESS_SPACE_IO; +} /** * pci_setup_device - fill in class and map information of a device @@ -692,20 +719,12 @@ static int pci_setup_device(struct pci_d u8 progif; pci_read_config_byte(dev, PCI_CLASS_PROG, &progif); if ((progif & 1) == 0) { - dev->resource[0].start = 0x1F0; - dev->resource[0].end = 0x1F7; - dev->resource[0].flags = LEGACY_IO_RESOURCE; - dev->resource[1].start = 0x3F6; - dev->resource[1].end = 0x3F6; - dev->resource[1].flags = LEGACY_IO_RESOURCE; + change_legacy_io_resource(dev, 0, 0x1F0, 0x1F7); + change_legacy_io_resource(dev, 1, 0x3F6, 0x3F6); } if ((progif & 4) == 0) { - dev->resource[2].start = 0x170; - dev->resource[2].end = 0x177; - dev->resource[2].flags = LEGACY_IO_RESOURCE; - dev->resource[3].start = 0x376; - dev->resource[3].end = 0x376; - dev->resource[3].flags = LEGACY_IO_RESOURCE; + change_legacy_io_resource(dev, 2, 0x170, 0x177); + change_legacy_io_resource(dev, 3, 0x376, 0x376); } } break; --LwW0XdcUbUexiWVK--