microSDHC card behaving unusual**

15
Apr 2011

Happen to partition the mmc into 5 partitions 3p +2extended but later on with some tweaking in the fstab wasn't able to mount the swap partition, not only that the fdisk /dev/mmcblk0 was not showing any partition with p switch (the mmc was detected properly by the kernel used dmesg|grep mmc and also the /dev was populated by created partitions ) . so commented the mmcblk partition in fstab and restarted the device which enabled to see the partition in fdisk - no idea why it behaved that way. So again formatted mmc card into 4 primary partition. lets see what happens now.

[u-19-04-2011] With the 4 pri partition stuffs are up and running without any glitches. The dmesg o/p for mmc

neo:~# dmesg |grep mmc
[21474538.845000] mmc0: new high speed SDHC card at address d736
[21474539.030000] mmcblk0: mmc0:d736 SU04G 3.69 GiB
[21474539.035000]  mmcblk0: p1 p2 p3 p4
[21474539.790000] mmc1: queuing CIS tuple 0x01 length 3
[21474539.815000] mmc1: queuing CIS tuple 0x1a length 5
[21474539.840000] mmc1: queuing CIS tuple 0x1b length 8
[21474539.860000] mmc1: queuing CIS tuple 0x80 length 1
[21474539.865000] mmc1: queuing CIS tuple 0x81 length 1
[21474539.870000] mmc1: queuing CIS tuple 0x82 length 1
[21474539.875000] mmc1: new SDIO card at address 0001
[21474571.255000] Adding 500024k swap on /dev/mmcblk0p4.  Priority:-1 extents:1 across:500024k SS
[ 6231.230000] mmc1: card 0001 removed
[ 6231.525000] mmc1: queuing CIS tuple 0x01 length 3
[ 6231.540000] mmc1: queuing CIS tuple 0x1a length 5
[ 6231.545000] mmc1: queuing CIS tuple 0x1b length 8
[ 6231.550000] mmc1: queuing CIS tuple 0x80 length 1
[ 6231.550000] mmc1: queuing CIS tuple 0x81 length 1
[ 6231.550000] mmc1: queuing CIS tuple 0x82 length 1
[ 6231.550000] mmc1: new SDIO card at address 0001
[ 6231.550000] mmc mmc1:0001: parent mmc1 should not be sleeping
[ 6308.480000] mmc1: card 0001 removed
[ 6308.775000] mmc1: queuing CIS tuple 0x01 length 3
[ 6308.790000] mmc1: queuing CIS tuple 0x1a length 5
[ 6308.795000] mmc1: queuing CIS tuple 0x1b length 8
[ 6308.800000] mmc1: queuing CIS tuple 0x80 length 1
[ 6308.800000] mmc1: queuing CIS tuple 0x81 length 1
[ 6308.800000] mmc1: queuing CIS tuple 0x82 length 1
[ 6308.800000] mmc1: new SDIO card at address 0001
[ 6308.800000] mmc mmc1:0001: parent mmc1 should not be sleeping
neo:~#

[u-01-06-2011] - The unusual behaviour has surfaced again. This time when I tried to use apt in the target(gta02) the device stops responding and the swap partition does not mount after hard boot

neo:~# dmesg |grep mmc
[21474538.810000] mmc0: new high speed SDHC card at address d736
[21474539.050000] mmcblk0: mmc0:d736 SU04G 3.69 GiB
[21474539.055000]  mmcblk0: p1 p2 p3 p4
[21474539.795000] mmc1: queuing CIS tuple 0x01 length 3
[21474539.820000] mmc1: queuing CIS tuple 0x1a length 5
[21474539.845000] mmc1: queuing CIS tuple 0x1b length 8
[21474539.860000] mmc1: queuing CIS tuple 0x80 length 1
[21474539.870000] mmc1: queuing CIS tuple 0x81 length 1
[21474539.880000] mmc1: queuing CIS tuple 0x82 length 1
[21474539.885000] mmc1: new SDIO card at address 0001
[21474571.720000] Adding 500024k swap on /dev/mmcblk0p4.  Priority:-1 extents:1 across:500024k SS
neo:~#

the kernel is detecting the partition but qtmoko is not mounting the partition

neo:~# fdisk -l

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
4 heads, 16 sectors/track, 121008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x6d6c6e00

Disk /dev/mmcblk0 doesn't contain a valid partition table

neo:~# mount
rootfs on / type auto (rw,noatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /var/cache/apt type tmpfs (rw,noatime)
neo:~#

Command (m for help): p

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
4 heads, 16 sectors/track, 121008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x3b9023bf

        Device Boot      Start         End      Blocks   Id  System

Command (m for help):  

yep the first resolution held its ground i,e after commenting the mmc partition in fstab the cmd fdisk -l displayed the partition

neo:~# fdisk -l

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
4 heads, 16 sectors/track, 121008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x7928fdff

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1       15626      500024    6  FAT16
/dev/mmcblk0p2           15627       46877     1000032   83  Linux
/dev/mmcblk0p3           46878       78128     1000032   83  Linux
/dev/mmcblk0p4           78129       93754      500032   82  Linux swap / Solaris

even
Command (m for help): p

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
4 heads, 16 sectors/track, 121008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0x7928fdff

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1       15626      500024    6  FAT16
/dev/mmcblk0p2           15627       46877     1000032   83  Linux
/dev/mmcblk0p3           46878       78128     1000032   83  Linux
/dev/mmcblk0p4           78129       93754      500032   82  Linux swap / Solaris

Command (m for help):
worked but wait can't access the partition so had to repartition in may be because of running apt/nerongps. Happen to make use of mmcblk0p1 for nerongps yesterday that might be the cause.[/u-01-06-2011]

Some what related stuff:-

http://gnumen.org/blog/foss/31/03/2011/gps-tracing-using-gta02-u-blox-atr0635-module