Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage
From: Dominik Brodowski (linux_at_dominikbrodowski.net)
Date: 02/28/05
- Previous message: Pavel Machek: "Fix few remaining u32 vs. pm_message_t issues"
- In reply to: Valdis.Kletnieks_at_vt.edu: "2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Next in thread: Valdis.Kletnieks_at_vt.edu: "Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Reply: Valdis.Kletnieks_at_vt.edu: "Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 28 Feb 2005 21:22:26 +0100 To: Valdis.Kletnieks@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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Pavel Machek: "Fix few remaining u32 vs. pm_message_t issues"
- In reply to: Valdis.Kletnieks_at_vt.edu: "2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Next in thread: Valdis.Kletnieks_at_vt.edu: "Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Reply: Valdis.Kletnieks_at_vt.edu: "Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
