I am running fdisk on an SD card that has 4 partitions

Partition 1 is fat32
Partition 3 is ext2
Partition 4 is jfs

(I don't know what file system resides on partition 2)

I get the following when I do an fdisk

Disk /dev/sdb: 8010 MB, 8010072064 bytes
247 heads, 62 sectors/track, 1021 cylinders, total 15644672 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 256 8447 4096 c W95 FAT32 (LBA)
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 4, 13) logical=(0, 4, 9)
Partition 1 has different physical/logical endings:
phys=(17, 2, 30) logical=(0, 136, 16)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 8448 14591 3072 da Non-FS data
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(2, 12, 17) logical=(0, 136, 17)
Partition 2 has different physical/logical endings:
phys=(3, 49, 22) logical=(0, 235, 22)
Partition 2 does not end on cylinder boundary.
/dev/sdb3 16640 19711 1536 da Non-FS data
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(16, 12, 25) logical=(1, 21, 25)
Partition 3 has different physical/logical endings:
phys=(19, 13, 58) logical=(1, 70, 58)
Partition 3 does not end on cylinder boundary.

Is there something wrong with the partition table ? could this cause problems on the long run ?

Yes. The partition table does looks messed up. You might run into problems later when the disk fills up. I've seen many SD cards (especially Sandisk ones) that seem to ship with this funky partition scheme. It seems to work ok in camera's and such, but if you intend to run linux you will have problems.

I suggest backing up all the data & starting over. Recreating all the partition with fdisk or gparted.