[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100329091241.GA3237@oracle.com>
Date: Mon, 29 Mar 2010 12:12:41 +0300
From: Ozgur Yuksel <ozgur.yuksel@...cle.com>
To: Dominik Brodowski <linux@...inikbrodowski.net>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Andrew Morton <akpm@...ux-foundation.org>,
Yinghai Lu <yinghai@...nel.org>,
Dmitry Torokhov <dtor@...l.ru>,
bugzilla-daemon@...zilla.kernel.org,
bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 15621] New: BUG: unable to handle kernel
paging request - comm: pccardd
Thu, Mar 25, 2010 at 06:01:38PM +0100 was the time for Dominik Brodowski to speak thus:
>
> On Thu, Mar 25, 2010 at 10:51:39AM -0600, Bjorn Helgaas wrote:
> > > It looks like the iomem_resource tree got wrecked. Has anyone been
> > > changing anything in there lately?
> >
> > My pci=use_crs patches change the contents of the iomem_resource tree,
> > and it's possible they broke some assumptions PCMCIA was making, so
> > you might see if "pci=nocrs" makes any difference. If it does, please
> > attach an acpidump and the entire dmesg logs with and without that option.
>
> ... and /proc/iomem as well as /proc/ioports , please.
Using pci=nocrs workarounds the problem. For data collection, since the boot
does not complete without the w/a - only dmesg is available.
With pci=nocrs, accessing /proc/iomem gets killed by kernel for some reason.
/proc/iomem /proc/ioports and acpidump are provided for 2.6.31-20-generic-pae
kernel for convenience / comparison.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists