2.6.11-rc4-mm1 - pcmcia weirdness/breakage

2.6.11-rc4-mm1 - pcmcia weirdness/breakage

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

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?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage

[Dominik Brodowski]

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

Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

On Mon, 28 Feb 2005 21:22:26 +0100, Dominik Brodowski said:
> On Mon, Feb 28, 2005 at 02:48:20PM -0500, Valdis.Kletnieks@vt.edu wrote:

> > A full -rc4-mm1 fails, *as does* a -rc4-mm1 with all the following patches -R'ed:
...
> > broken-out/pcmcia-bridge-resource-management-fix.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

I'd believe you, except that patch has already been -R'ed and I'm still seeing
the problem.  That's why I'm mystified - I backed out all the obvious culprits
already, and the problem's still there...

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.11-rc4-mm1 - pcmcia weirdness/breakage

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]

On Mon, 28 Feb 2005 14:48:20 EST, Valdis.Kletnieks@vt.edu said:

> 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:

> [4294859.369000] cs: unable to map card memory!
> [4294859.369000] cs: unable to map card memory!

I backed the bk-pci.patch out, and it started working again, so the problem is
somewhere in there (progress - we've got it down to one 5,500 patch ;).
Perhaps related, the following compile warnings also went away:

   CC [M]  drivers/ieee1394/ohci1394.o
drivers/ieee1394/ohci1394.c: In function `ohci_initialize':
drivers/ieee1394/ohci1394.c:589: warning: long unsigned int format, different type arg (arg 7)
drivers/ieee1394/ohci1394.c:589: warning: long unsigned int format, different type arg (arg 8)
drivers/ieee1394/ohci1394.c: In function `ohci1394_pci_probe':
drivers/ieee1394/ohci1394.c:3266: warning: long unsigned int format, different type arg (arg 4)

   CC      drivers/pci/rom.o
drivers/pci/rom.c: In function `pci_map_rom':
drivers/pci/rom.c:74: warning: cast to pointer from integer of different size
drivers/pci/rom.c: In function `pci_map_rom_copy':
drivers/pci/rom.c:160: warning: cast to pointer from integer of different size
drivers/pci/rom.c:164: warning: cast to pointer from integer of different size
drivers/pci/rom.c: In function `pci_cleanup_rom':
drivers/pci/rom.c:217: warning: cast to pointer from integer of different size

   CC [M]  drivers/pcmcia/rsrc_nonstatic.o
drivers/pcmcia/rsrc_nonstatic.c: In function `nonstatic_find_io_region':
drivers/pcmcia/rsrc_nonstatic.c:629: warning: passing arg 7 of `pci_bus_alloc_resource' from incompatible pointer type
drivers/pcmcia/rsrc_nonstatic.c:633: warning: passing arg 7 of `allocate_resource' from incompatible pointer type
drivers/pcmcia/rsrc_nonstatic.c: In function `nonstatic_find_mem_region':
drivers/pcmcia/rsrc_nonstatic.c:672: warning: passing arg 7 of `pci_bus_alloc_resource' from incompatible pointer type
drivers/pcmcia/rsrc_nonstatic.c:676: warning: passing arg 7 of `allocate_resource' from incompatible pointer type

I'm suspicious of the warnings for rsrc_nonstatic.o, because we end up in that
exact piece of code just before failing with the 'unable to map card memory'
message. Maybe that arg 7 is causing us to pass a stack that doesn't quite
match what's expected, and thus the bug?



[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]