From: Ozgur Yuksel <ozgur.yuksel@oracle.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yinghai Lu <yinghai@kernel.org>, Dmitry Torokhov <dtor@mail.ru>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 15621] New: BUG: unable to handle kernel paging request - comm: pccardd
Date: Mon, 29 Mar 2010 12:12:41 +0300 [thread overview]
Message-ID: <20100329091241.GA3237@oracle.com> (raw)
In-Reply-To: <20100325170138.GA5424@comet.dominikbrodowski.net>
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.
next prev parent reply other threads:[~2010-03-29 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15621-10286@https.bugzilla.kernel.org/>
2010-03-24 11:12 ` Andrew Morton
2010-03-25 16:51 ` Bjorn Helgaas
2010-03-25 17:01 ` Dominik Brodowski
2010-03-29 9:12 ` Ozgur Yuksel [this message]
2010-03-30 23:10 ` Bjorn Helgaas
2010-04-01 9:18 ` Ozgur Yuksel
2010-04-01 17:34 ` Bjorn Helgaas
2010-04-02 16:59 ` Ozgur Yuksel
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=20100329091241.GA3237@oracle.com \
--to=ozgur.yuksel@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dtor@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=yinghai@kernel.org \
/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
Powered by JetHome