From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Pavel Machek" <pavel@ucw.cz>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Anvin" <hpa@zytor.com>,
"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: x86 git tree broken (bisected)
Date: Fri, 11 Apr 2008 13:26:06 -0700 [thread overview]
Message-ID: <86802c440804111326t4c3ff4b6od33a128560b58aec@mail.gmail.com> (raw)
In-Reply-To: <200804112126.29455.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On Fri, Apr 11, 2008 at 12:26 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Friday, 11 of April 2008, Rafael J. Wysocki wrote:
> > On Thursday, 10 of April 2008, Ingo Molnar wrote:
> > >
> > > * Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > > > > > First, the X server doesn't want to start (it says it couldn't
> > > > > > > mmap the framebuffer).
> > > > > >
> > > > > > could you send your .config?
> > > > >
> > > > > Attached.
> > > >
> > > > could you disable this option:
> > > >
> > > > CONFIG_NONPROMISC_DEVMEM=y
> > > >
> > > > does it help with the X problem?
> >
> > That didn't help.
> >
> > > btw., Xorg works fine here on a comparable AMD system - but i use a
> > > rather new distro (Fedora 8) which has Xorg 7.2.
> >
> > My system is an OpenSUSE 10.3 and it has Xorg 7.2 as well.
> >
> > I think the problem is somehow related to the Radeon.
>
> The bisection turned up commit ea1441bdf53692c3dc1fd2658addcf1205629661
> "x86: use bus conf in NB conf fun1 to get bus range on, on 64-bit" as the one
> causing problems.
>
> Unfortunately, I can't revert cleanly it, because there are two more commits
> depending on it in a highly nontrivial fashion, so I have reverted all three
> commits
>
> a365998cd2cecfb827469dbd57c29602c106cb83
> 44f7f90fbe7a3a99aab082f765346514b7b5c705
> ea1441bdf53692c3dc1fd2658addcf1205629661
>
> and X starts again. Also, suspend to RAM works from under X.
please keep the three patches and applied the two attached debug patches.
i wonder if there is some io allocation overlapping with your system.
YH
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: debug_extra_pci_bus_res.patch --]
[-- Type: text/x-patch; name=debug_extra_pci_bus_res.patch, Size: 1299 bytes --]
Index: linux-2.6/drivers/pci/setup-bus.c
===================================================================
--- linux-2.6.orig/drivers/pci/setup-bus.c
+++ linux-2.6/drivers/pci/setup-bus.c
@@ -536,6 +536,36 @@ void __ref pci_bus_assign_resources(stru
}
EXPORT_SYMBOL(pci_bus_assign_resources);
+static void pci_bus_dump_res(struct pci_bus *bus)
+{
+ int i;
+
+ for (i = 0; i < PCI_BUS_NUM_RESOURCES; i++) {
+ struct resource *res = bus->resource[i];
+ if (!res)
+ continue;
+
+ printk(KERN_INFO "bus: %02x index %x %s: [%llx, %llx]\n", bus->number, i, (res->flags & IORESOURCE_IO)? "io port":"mmio", res->start, res->end);
+ }
+}
+
+static void pci_bus_dump_resources(struct pci_bus *bus)
+{
+ struct pci_bus *b;
+ struct pci_dev *dev;
+
+
+ pci_bus_dump_res(bus);
+
+ list_for_each_entry(dev, &bus->devices, bus_list) {
+ b = dev->subordinate;
+ if (!b)
+ continue;
+
+ pci_bus_dump_resources(b);
+ }
+}
+
void __init
pci_assign_unassigned_resources(void)
{
@@ -551,4 +581,9 @@ pci_assign_unassigned_resources(void)
pci_bus_assign_resources(bus);
pci_enable_bridges(bus);
}
+
+ /* dump the resource on buses */
+ list_for_each_entry(bus, &pci_root_buses, node) {
+ pci_bus_dump_resources(bus);
+ }
}
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: debug_extra_pci_res_range.patch --]
[-- Type: text/x-patch; name=debug_extra_pci_res_range.patch, Size: 1787 bytes --]
Index: linux-2.6/drivers/pci/probe.c
===================================================================
--- linux-2.6.orig/drivers/pci/probe.c
+++ linux-2.6/drivers/pci/probe.c
@@ -246,6 +246,7 @@ static void pci_read_bases(struct pci_de
}
res->start = l64 & PCI_BASE_ADDRESS_MEM_MASK;
res->end = res->start + sz64;
+ printk(KERN_INFO "PCI: %s reg %x 64bit mmio: [%llx, %llx]\n", pci_name(dev), reg, res->start, res->end);
#else
if (sz64 > 0x100000000ULL) {
printk(KERN_ERR "PCI: Unable to handle 64-bit "
@@ -261,6 +262,8 @@ static void pci_read_bases(struct pci_de
res->end = sz;
}
#endif
+ } else {
+ printk(KERN_INFO "PCI: %s reg %x %s: [%llx, %llx]\n", pci_name(dev), reg, (res->flags & IORESOURCE_IO)? "io port":"32bit mmio", res->start, res->end);
}
}
if (rom) {
@@ -327,6 +330,7 @@ void __devinit pci_read_bridge_bases(str
res->start = base;
if (!res->end)
res->end = limit + 0xfff;
+ printk(KERN_INFO "PCI: bridge %s io port: [%llx, %llx]\n", pci_name(dev), res->start, res->end);
}
res = child->resource[1];
@@ -338,6 +342,7 @@ void __devinit pci_read_bridge_bases(str
res->flags = (mem_base_lo & PCI_MEMORY_RANGE_TYPE_MASK) | IORESOURCE_MEM;
res->start = base;
res->end = limit + 0xfffff;
+ printk(KERN_INFO "PCI: bridge %s 32bit mmio: [%llx, %llx]\n", pci_name(dev), res->start, res->end);
}
res = child->resource[2];
@@ -372,6 +377,7 @@ void __devinit pci_read_bridge_bases(str
res->flags = (mem_base_lo & PCI_MEMORY_RANGE_TYPE_MASK) | IORESOURCE_MEM | IORESOURCE_PREFETCH;
res->start = base;
res->end = limit + 0xfffff;
+ printk(KERN_INFO "PCI: bridge %s %sbit mmio pref: [%llx, %llx]\n", pci_name(dev), (res->flags & PCI_PREF_RANGE_TYPE_64)?"64":"32",res->start, res->end);
}
}
next prev parent reply other threads:[~2008-04-11 20:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 19:59 x86 git tree broken Rafael J. Wysocki
2008-04-10 20:13 ` Ingo Molnar
2008-04-10 20:25 ` Rafael J. Wysocki
2008-04-10 20:29 ` Ingo Molnar
2008-04-10 20:38 ` Ingo Molnar
2008-04-10 22:28 ` Rafael J. Wysocki
2008-04-11 19:26 ` x86 git tree broken (bisected) Rafael J. Wysocki
2008-04-11 20:23 ` Rafael J. Wysocki
2008-04-11 20:29 ` Rafael J. Wysocki
2008-04-11 20:26 ` Yinghai Lu [this message]
2008-04-11 20:51 ` Rafael J. Wysocki
2008-04-11 21:11 ` Yinghai Lu
2008-04-11 21:21 ` Rafael J. Wysocki
2008-04-11 21:31 ` Yinghai Lu
2008-04-13 8:24 ` Yinghai Lu
2008-04-13 8:41 ` Yinghai Lu
2008-04-13 16:14 ` Rafael J. Wysocki
2008-04-14 9:02 ` Ingo Molnar
2008-04-13 16:12 ` Rafael J. Wysocki
2008-04-13 18:07 ` Yinghai Lu
2008-04-13 18:47 ` Rafael J. Wysocki
2008-04-13 18:53 ` Yinghai Lu
2008-04-13 18:54 ` Yinghai Lu
2008-04-13 22:00 ` Yinghai Lu
2008-04-13 22:10 ` Rafael J. Wysocki
2008-04-13 22:32 ` Yinghai Lu
2008-04-13 23:41 ` Rafael J. Wysocki
2008-04-13 23:45 ` H. Peter Anvin
2008-04-14 0:09 ` Rafael J. Wysocki
2008-04-14 0:12 ` H. Peter Anvin
2008-04-14 0:19 ` Rafael J. Wysocki
2008-04-14 1:42 ` Yinghai Lu
2008-04-14 9:16 ` Ingo Molnar
2008-04-14 18:08 ` Yinghai Lu
2008-04-14 20:21 ` Rafael J. Wysocki
2008-04-14 21:06 ` Yinghai Lu
2008-04-14 21:09 ` Rafael J. Wysocki
2008-04-14 21:36 ` Yinghai Lu
2008-04-13 7:51 ` Ingo Molnar
2008-04-13 7:59 ` Yinghai Lu
2008-04-13 7:58 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Ingo Molnar
2008-04-13 8:18 ` Yinghai Lu
2008-04-13 9:19 ` Ingo Molnar
2008-04-13 9:39 ` [rfc] hw resource debugging checks Andi Kleen
2008-04-13 17:53 ` Arjan van de Ven
2008-04-13 18:19 ` Yinghai Lu
2008-04-13 18:29 ` Andi Kleen
2008-04-13 19:29 ` Yinghai Lu
2008-04-14 3:52 ` Arjan van de Ven
2008-04-14 5:01 ` Yinghai Lu
2008-04-14 14:12 ` Arjan van de Ven
2008-04-14 18:11 ` Yinghai Lu
2008-04-13 15:48 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Arjan van de Ven
2008-04-10 20:51 ` x86 git tree broken Ingo Molnar
2008-04-10 22:27 ` Rafael J. Wysocki
2008-04-11 6:43 ` Ingo Molnar
[not found] <fa.2mJjVaMdmV5IWp3mQiYHE1u4pHU@ifi.uio.no>
[not found] ` <fa.SO/I64FxJXD1oLBH54BTs4pc56c@ifi.uio.no>
[not found] ` <fa.fJC0A/aGr6H8XE94NUuvl1ixoc0@ifi.uio.no>
[not found] ` <fa.qs5oa+YMIJd6h2hpuGCULc8ODY4@ifi.uio.no>
2008-04-16 4:27 ` x86 git tree broken (bisected) Robert Hancock
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=86802c440804111326t4c3ff4b6od33a128560b58aec@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®