No - BUS is arrived:) It seems PMEM now is required in kernel. On 21 ноя, 01:54, Porting beginner <porting.begin...@gmail.com> wrote: > On Fri, Nov 20, 2009 at 2:47 PM, Alexey Roslyakov < > > > > alexey.roslya...@gmail.com> wrote: > > solution is simple: just remove lock&&unlock of mutex. > > it is locked before (in the same thread), so deadlock occurs. > > > And probably next problem appears:( > > > I/gralloc ( 710): refresh rate = 53.04 Hz > > I/gralloc ( 710): fb_device_open res: 0 > > E/gralloc ( 710): couldn't open pmem (Unknown error: -2) > > E/gralloc ( 710): gralloc failed err=No such file or directory > > E/FramebufferNativeWindow( 710): fb buffer 0 allocation failed w=800, > > h=480, err=No such file or directory > > E/gralloc ( 710): couldn't open pmem (Unknown error: -2) > > E/gralloc ( 710): gralloc failed err=No such file or directory > > E/FramebufferNativeWindow( 710): fb buffer 1 allocation failed w=800, > > h=480, err=No such file or directory > > E/FramebufferNativeWindow( 710): xDpi -2097152000 > > E/FramebufferNativeWindow( 710): yDpi -2097152000 > > D/libEGL ( 710): egl.cfg not found, using default config > > D/libEGL ( 710): loaded /system/lib/egl/libGLES_android.so > > I/SurfaceFlinger( 710): EGL informations: > > I/SurfaceFlinger( 710): # of configs : 8 > > I/SurfaceFlinger( 710): vendor : Android > > I/SurfaceFlinger( 710): version : 1.4 Android META-EGL > > I/SurfaceFlinger( 710): extensions: EGL_KHR_image EGL_KHR_image_base > > EGL_KHR_image_pixmap EGL_ANDROID_image_native_buffer > > EGL_ANDROID_swap_rectangle EGL_ANDROID_get_render_buffer > > I/SurfaceFlinger( 710): Client API: OpenGL ES > > I/SurfaceFlinger( 710): EGLSurface: 5-6-5-0, config=0x1000000 > > I/SurfaceFlinger( 710): flags : 001c0000 > > W/SurfaceFlinger( 710): ro.sf.lcd_density not defined, using 160 dpi > > by default. > > I/DEBUG ( 695): *** *** *** *** *** *** *** *** *** *** *** *** *** > > *** *** *** > > I/DEBUG ( 695): Build fingerprint: 'newsycat/mini2440/ > > mini2440/:AOSP/MASTER/eng.e-yes.20091117.221242:eng/test-keys' > > I/DEBUG ( 695): pid: 710, tid: 717 >>> system_server <<< > > I/DEBUG ( 695): signal 7 (SIGBUS), fault addr 00000000 > > I/DEBUG ( 695): r0 00000000 r1 426e4ee1 r2 0013ff20 r3 0013ebb8 > > I/DEBUG ( 695): r4 0013ec68 r5 accac0e8 r6 0013ec68 r7 0029b780 > > I/DEBUG ( 695): r8 00000320 r9 0013eda0 10 00000000 fp ac70bbdc > > I/DEBUG ( 695): ip ac440358 sp 44f82cb8 lr afe0ff58 pc > > acc9f568 cpsr 20000010 > > I/DEBUG ( 695): #00 pc 0001f568 /system/lib/egl/ > > libGLES_android.so > > I/DEBUG ( 695): #01 pc 0001fdb8 /system/lib/egl/ > > libGLES_android.so > > I/DEBUG ( 695): #02 pc 00006d8c /system/lib/libEGL.so > > I/DEBUG ( 695): #03 pc 00015f38 /system/lib/ > > libsurfaceflinger.so > > I/DEBUG ( 695): #04 pc 00016330 /system/lib/ > > libsurfaceflinger.so > > I/DEBUG ( 695): #05 pc 0002741c /system/lib/ > > libsurfaceflinger.so > > I/DEBUG ( 695): #06 pc 000299f4 /system/lib/libutils.so > > I/DEBUG ( 695): #07 pc 0002994c /system/lib/libutils.so > > I/DEBUG ( 695): #08 pc 00010ce8 /system/lib/libc.so > > I/DEBUG ( 695): #09 pc 0001071c /system/lib/libc.so > > I/DEBUG ( 695): > > I/DEBUG ( 695): code around pc: > > I/DEBUG ( 695): acc9f558 e5943038 e593103c e3510000 0a000002 > > I/DEBUG ( 695): acc9f568 e5910000 e350000c 0a00003c e3a06000 > > I/DEBUG ( 695): acc9f578 e58d6000 e5932020 e594c040 e58d2004 > > I/DEBUG ( 695): > > I/DEBUG ( 695): code around lr: > > I/DEBUG ( 695): afe0ff48 e5964000 e2144903 1a00000a ebfffbf8 > > I/DEBUG ( 695): afe0ff58 e3500001 0a000005 e5864000 e1a00006 > > I/DEBUG ( 695): afe0ff68 e3a01001 ebfffc1e e1a00004 e8bd81f0 > > I/DEBUG ( 695): > > I/DEBUG ( 695): stack: > > I/DEBUG ( 695): 44f82c78 0013ff20 [heap] > > I/DEBUG ( 695): 44f82c7c afe10040 /system/lib/libc.so > > I/DEBUG ( 695): 44f82c80 00000000 > > I/DEBUG ( 695): 44f82c84 afe0ff58 /system/lib/libc.so > > I/DEBUG ( 695): 44f82c88 0013fea0 [heap] > > I/DEBUG ( 695): 44f82c8c 0013ff20 [heap] > > I/DEBUG ( 695): 44f82c90 0013ebb8 [heap] > > I/DEBUG ( 695): 44f82c94 0029b780 [heap] > > I/DEBUG ( 695): 44f82c98 00000320 > > I/DEBUG ( 695): 44f82c9c ac420a84 /system/lib/libui.so > > I/DEBUG ( 695): 44f82ca0 00000000 > > I/DEBUG ( 695): 44f82ca4 0013ec68 [heap] > > I/DEBUG ( 695): 44f82ca8 accac0e8 /system/lib/egl/ > > libGLES_android.so > > I/DEBUG ( 695): 44f82cac 0013ec68 [heap] > > I/DEBUG ( 695): 44f82cb0 e3a07077 > > I/DEBUG ( 695): 44f82cb4 ef900077 > > I/DEBUG ( 695): #00 44f82cb8 000001e0 > > I/DEBUG ( 695): 44f82cbc 0000125c > > I/DEBUG ( 695): 44f82cc0 000001e0 > > I/DEBUG ( 695): 44f82cc4 0013ec68 [heap] > > I/DEBUG ( 695): 44f82cc8 000001e0 > > I/DEBUG ( 695): 44f82ccc 0013ec68 [heap] > > I/DEBUG ( 695): 44f82cd0 0013ec68 [heap] > > I/DEBUG ( 695): 44f82cd4 0029b780 [heap] > > I/DEBUG ( 695): 44f82cd8 00000320 > > I/DEBUG ( 695): 44f82cdc acc9fdbc /system/lib/egl/ > > libGLES_android.so > > I/DEBUG ( 695): #01 44f82ce0 000001e0 > > I/DEBUG ( 695): 44f82ce4 ac70baa0 /system/lib/libEGL.so > > I/DEBUG ( 695): 44f82ce8 00000000 > > I/DEBUG ( 695): 44f82cec ac70baa0 /system/lib/libEGL.so > > I/DEBUG ( 695): 44f82cf0 0013eda0 [heap] > > I/DEBUG ( 695): 44f82cf4 0013ece8 [heap] > > I/DEBUG ( 695): 44f82cf8 0013ece8 [heap] > > I/DEBUG ( 695): 44f82cfc 0013ece8 [heap] > > I/DEBUG ( 695): 44f82d00 0013ece8 [heap] > > I/DEBUG ( 695): 44f82d04 ac706d90 /system/lib/libEGL.so > > > hmmm, got home screen at least with this solution ? > > On 20 ноя, 18:00, AchimNohl <achim.n...@coware.com> wrote: > > > Hi all, > > > > I have see the same symptom while brining up 2.0 on an ARM926EJS based > > > (virtual) platform. 1.5 was working fine and my kernel remained > > > unchanged. In my analysis tools, I see that in my case the boot gets > > > stuck in a pthread_mutex_lock. After that the CPU is just idle. The > > > lock is called from hardware/libhardware/modules/gralloc.cpp in > > > init_pmem_area. I do not know if the problem is the same as yours but > > > I will update you once I found out more. > > > > Regards, > > > Achim > > > > On Nov 20, 4:52 am, Porting beginner <porting.begin...@gmail.com> > > > wrote: > > > > > On Thu, Nov 19, 2009 at 7:10 PM, Alexey Roslyakov < > > > > > alexey.roslya...@gmail.com> wrote: > > > > > Can you share your diff and/or logcat output? > > > > > I/SurfaceFlinger( 784): SurfaceFlinger is starting > > > > I/SurfaceFlinger( 784): SurfaceFlinger's main thread ready to run. > > > > Initializing graphics H/W... > > > > E/FramebufferNativeWindow( 784): +++++++++++ CALLING framebuffer_open > > > > ++++++ > > > > W/gralloc ( 784): ----------- here in framebuffer, doing ioctl for > > page > > > > flippping ------ > > > > W/gralloc ( 784): ----------- here in framebuffer, doing ioctl for > > page > > > > flippping ------- > > > > W/gralloc ( 784): ----------- here in framebuffer, doing ioctl for > > page > > > > flippping -------- > > > > I/gralloc ( 784): ++++++++++++using (fd=23) > > > > I/gralloc ( 784): id = LCDfb > > > > I/gralloc ( 784): xres = 240 px > > > > I/gralloc ( 784): yres = 320 px > > > > I/gralloc ( 784): xres_virtual = 240 px > > > > I/gralloc ( 784): yres_virtual = 640 px > > > > I/gralloc ( 784): bpp = 16 > > > > I/gralloc ( 784): r = 11:5 > > > > I/gralloc ( 784): g = 5:6 > > > > I/gralloc ( 784): b = 0:5 > > > > I/gralloc ( 784): width = 240 mm (25.400000 dpi) > > > > I/gralloc ( 784): height = 320 mm (25.400000 dpi) > > > > I/gralloc ( 784): refresh rate = 60.00 Hz > > > > E/FramebufferNativeWindow( 784): +++++++++++ CALLING gralloc_open > > ++++++ > > > > E/FramebufferNativeWindow( 784): +++++++++++ INITIALIZE THE BUFFER > > FIFO > > > > +++++ > > > > E/FramebufferNativeWindow( 784): +++++++++++ AFTER GRDEV->ALLOC O > > +++++ > > > > E/FramebufferNativeWindow( 784): xDpi -2097152000 > > > > E/FramebufferNativeWindow( 784): yDpi -2097152000 > > > > > On Nov 20, 12:22 am, Michael Trimarchi <trimar...@gandalf.sssup.it> > > > > > > wrote: > > > > > > Hi, > > > > > > > Alexey Roslyakov wrote: > > > > > > > I added LOGI just before return from fb_device_open. > > > > > > > > I/gralloc ( 713): fb_device_open res: 0 > > > > > > > > fb device initialized successfully. Problem is not here. > > > > > > > But where? > > > > > > > maybe we have the same architecture. I'm compiling eclair for > > openmoko > > > > > but > > > > > > the issue that I have is a crash in opencore. I'm trying to find > > the > > > > > > related problem, > > > > > > can you share with us your configuration for compile on the armv4t > > > > > > architecture? > > > > > > > Michael > > > > > > -- > > > > > unsubscribe: > > > > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > <android-porting%2bunsubscr...@googlegroups.com> > > > > > website:http://groups.google.com/group/android-porting > > > > > -- > > > > Thanks > > > > Rizavan- Hide quoted text - > > > > > - Show quoted text - > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting > > -- > Thanks > Rizavan
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting