From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage
Date: Mon, 28 Feb 2005 21:22:26 +0100 [thread overview]
Message-ID: <20050228202226.GA16284@isilmar.linta.de> (raw)
In-Reply-To: <200502281948.j1SJmKdV006528@turing-police.cc.vt.edu>
On Mon, Feb 28, 2005 at 02:48:20PM -0500, Valdis.Kletnieks@vt.edu wrote:
> Symptoms: Running '/etc/init.d/pcmcia start' bombs - cardmgr goes into
> a loop spewing repeated 'Common memory region at 0x0: Generic or SRAM'
> messages. In the dmesg, we find:
>
> [4294764.989000] <6>cs: IO port probe 0xc00-0xcff: clean.
> [4294859.195000] cs: IO port probe 0xc00-0xcff: clean.
> [4294859.195000] cs: IO port probe 0xc00-0xcff: clean.
> [4294859.199000] cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x370-0x37f
> [4294859.202000] cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x370-0x37f
> [4294859.205000] cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x370-0x37f
> [4294859.207000] cs: IO port probe 0xa00-0xaff: clean.
> [4294859.208000] cs: IO port probe 0xa00-0xaff: clean.
> [4294859.209000] cs: IO port probe 0xa00-0xaff: clean.
> [4294859.369000] cs: unable to map card memory!
> [4294859.369000] cs: unable to map card memory!
>
> Now the odd part:
>
> 2.6.11-rc4 works, doesn't show the last 2 'unable to map' messages.
> 2.6.11-rc4 + linus.patch from -rc4-mm1 works as well - so it's a -mm patch doing it.
>
> A full -rc4-mm1 fails, *as does* a -rc4-mm1 with all the following patches -R'ed:
>
> broken-out/fix-u32-vs-pm_message_t-confusion-in-pcmcia.patch
> broken-out/pcmcia-add-pcmcia-devices-autonomously.patch
> broken-out/pcmcia-bridge-resource-management-fix.patch
> broken-out/pcmcia-determine-some-useful-information-about-devices.patch
> broken-out/pcmcia-mark-resource-setup-as-done.patch
> broken-out/pcmcia-pcmcia_device_add.patch
> broken-out/pcmcia-pcmcia_device_probe.patch
> broken-out/pcmcia-pcmcia_device_remove.patch
> broken-out/pcmcia-pd6729-convert-to-pci_register_driver.patch
> broken-out/pcmcia-per-device-sysfs-output.patch
> broken-out/pcmcia-rsrc_nonstatic-sysfs-input.patch
> broken-out/pcmcia-rsrc_nonstatic-sysfs-output.patch
> broken-out/pcmcia-update-vrc4171_card.patch
> broken-out/pcmcia-use-bus_rescan_devices.patch
> broken-out/pcmcia-yenta_socket-ti4150-support.patch
>
> So the breakage is in *some other* -rc4-mm1 patch. Any hints to speed up
> the binary search?
Most likely it's
pcmcia-bridge-resource-management-fix.patch
Dominik
next prev parent reply other threads:[~2005-02-28 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 19:48 Valdis.Kletnieks
2005-02-28 20:22 ` Dominik Brodowski [this message]
2005-02-28 20:46 ` Valdis.Kletnieks
2005-03-01 8:56 ` Valdis.Kletnieks
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=20050228202226.GA16284@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®