Project

General

Profile

Samsung S3 GT-I9300 Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4656 (app_process)Binder driver could not be opened. Terminating.

Added by Le Citron over 9 years ago

Hi
All was working well but this morning i switched on:pressing on any app became unresponsive,the widgets refuse to open and change to darker colour,
the phone crash's and reboots,it seems to freeze and just got worse,multiple crash's and reboots.*I'm attaching the system Log from CatLog..* But mostly it show's

11-23 07:34:55.395 F/ProcessState(4656): Binder driver could not be opened. Terminating.
11-23 07:34:55.395 F/libc (4656): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4656 (app_process)
11-23 07:34:55.400 I/ActivityManager(2258): Start proc com.andrew.apollo for broadcast com.andrew.apollo/.appwidgets.AppWidgetLarge: pid=4715 uid=10000 gids={50000, 1015, 3003, 1028}
11-23 07:34:55.420 E/ProcessState(4715): Using /dev/binder failed: unable to mmap transaction memory.
11-23 07:34:55.420 F/ProcessState(4715): Binder driver could not be opened. Terminating.
11-23 07:34:55.420 F/libc (4715): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4715 (zygote)
11-23 07:34:55.440 D/dalvikvm(4679): Trying to load lib libjavacore.so 0x0
11-23 07:34:55.445 D/su (4725): su invoked.
11-23 07:34:55.450 E/ProcessState(4646): Using /dev/binder failed: unable to mmap transaction memory.
11-23 07:34:55.450 F/ProcessState(4646): Binder driver could not be opened. Terminating.
11-23 07:34:55.450 F/libc (4646): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4646 (app_process)
11-23 07:34:55.455 D/dalvikvm(4679): Added shared lib libjavacore.so 0x0
11-23 07:34:55.455 D/su (4738): db allowed
11-23 07:34:55.460 D/dalvikvm(4679): Trying to load lib libnativehelper.so 0x0
11-23 07:34:55.460 D/dalvikvm(4679): Added shared lib libnativehelper.so 0x0
11-23 07:34:55.460 I/BootReceiver(2258): Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
11-23 07:34:55.465 D/su (4741): 10061 dev.ukanth.ufirewall executing 0 /system/bin/sh using binary /system/bin/sh : sh
11-23 07:34:55.490 I/AFWall (4698): logservice shell started
11-23 07:34:55.515 W/Settings(2453): Setting auto_time_zone has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
11-23 07:34:55.520 D/AlarmManagerService(2258): Kernel timezone updated to -60 minutes west of GMT
11-23 07:34:55.520 W/Settings(2453): Setting auto_time has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
11-23 07:34:55.525 D/SystemClock(2453): Setting time of day to sec=1416724496
11-23 07:34:56.070 I/DEBUG (1891): * *
11-23 07:34:56.070 I/DEBUG (1891): Build fingerprint: 'samsung/m0xx/m0:4.1.1/JRO03C/I9300XXDLIB:user/release-keys'
11-23 07:34:56.070 I/DEBUG (1891): Revision: '12'
11-23 07:34:56.070 I/DEBUG (1891): pid: 4575, tid: 4575, name: app_process >>> app_process <<<
11-23 07:34:56.070 I/DEBUG (1891): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
11-23 07:34:56.120 I/DEBUG (1891): r0 00000027 r1 deadbaad r2 00000000 r3 00000000
11-23 07:34:56.120 I/DEBUG (1891): r4 00000000 r5 beae015c r6 401da058 r7 401da064

1-23 07:34:56.160 I/DEBUG (1891): memory map around fault addr deadbaad:
11-23 07:34:56.160 I/DEBUG (1891): beac0000-beae1000 [stack]
11-23 07:34:56.160 I/DEBUG (1891): (no map for address)
11-23 07:34:56.160 I/DEBUG (1891): ffff0000-ffff1000 [vectors]
11-23 07:34:56.225 E/ProcessState(4671): Using /dev/binder failed: unable to mmap transaction memory.
11-23 07:34:56.225 F/ProcessState(4671): Binder driver could not be opened. Terminating.
11-23 07:34:56.225 F/libc (4671): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4671 (app_process)
11-23 07:34:56.235 I/BootReceiver(2258): Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)>

What's Dropbox SYSTEM TOMBSTONE?Copying data!.../BootReceiver..?
the only thing i did recently was to update OrWall and did not fiddle around with it.
Be gratefull for any insights(i'm thinking of doing a re-installation from Zip seing i have no knowledge on debugging)
Regards

2014-11-23-07-41-02.txt (853 KB) 2014-11-23-07-41-02.txt 2014-11-23-41-02.txt-Catlog-Citron-Replicant

Replies (2)

RE: Samsung S3 GT-I9300 Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4656 (app_process)Binder driver could not be opened. Terminating. - Added by Paul Kocialkowski over 9 years ago

The problem seems to be:

11-23 07:34:55.420 E/ProcessState(4715): Using /dev/binder failed: unable to mmap transaction memory.
11-23 07:34:55.420 F/ProcessState(4715): Binder driver could not be opened.  Terminating.

So probably something to do with the binder kernel driver. Maybe attaching dmesg would help. If it still doesn't work, you can always reinstall and wipe data to have a fresh installation.

RE: Samsung S3 GT-I9300 Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 4656 (app_process)Binder driver could not be opened. Terminating. - Added by Le Citron over 9 years ago

Thank you PaulK ;-)
for such a quick reply.

https://en.wikipedia.org/wiki/Dmesg
just looking in to that &
http://www.linfo.org/dmesg.html

*Just tried but the phone is really unresponsive,i can't even open the file manager..the
terminal is unresponsive too..

Will reinstall and wipe data to have a fresh installation.

    (1-2/2)