Running out of ideas here. It just opens the ashmem device and makes two ioctl calls - one to set a label and the other allocate the size. If either fail, you get the error. Device permissions could be an issue or there isn't enough memory to successfully allocate. Since it worked before, I would guess device permissions. The init.rc script does remount / as read only. I would test /dev/ out by getting into the console and seeing if I can read, write, create a device - preferably as a non-root user - since dalik will most likely be running as a non-prived user. ...Kd > -----Original Message----- > From: twebb [mailto:taliaferro62@xxxxxxxxx] > Sent: Thursday, October 09, 2008 5:00 PM > To: Deacon, Keith > Cc: Adrian Hunter; linux-omap@xxxxxxxxxxxxxxx Mailing List; > anilvpr@xxxxxxxxx; Mat Johnson > Subject: Re: android on omap > > > Ashmem is the Android shared memory subsystem. You can find it in the > kernel under mm/ashmem.c. There is a config option to turn it on and off. > The error indicates that it's having trouble with the driver - although > it's not specific as to exactly what. Make sure it's enabled, the device > is present (/dev/ashmem), etc.. > > > > ...Kd > > > > I have ashmem properly configured and it works when the FS is mounted > via NFS. However as pointed out previously that seemed to be causing > other issues so I moved the FS into JFFS2. That too had it's issues > (where mmap was failing under certain conditions) that Adrian and Anil > pointed out were due to JFFS2. So I moved it to YAFFS2. Now I'm > seeing this "ashmem" issue. Up to this point, ashmem has worked fine > so I don't believe it's really the culprit. I feel like it has to do > with permissions or the filesystem. One difference is that the > emulator uses three different yaffs2 partitions (userdata, system, and > cache) while I currently have all of these on a single partition. > > Any other ideas as to what might cause the ... > > E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack > > message? > > Thanks, > twebb -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
