Code:
03-16 01:42:35.604 1485 1586 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-16 01:42:35.607 1485 1586 E mdm_panicd: connection broken - recreate socket
03-16 01:42:35.607 1485 1586 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-16 01:42:35.607 1485 1586 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-16 01:42:35.607 1485 1586 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, got 0
03-16 01:42:35.607 1485 1586 D mdm_panicd: Unsolicited thread finished
03-16 01:42:35.607 1485 1485 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-16 01:42:35.607 1485 1485 E mdm_panicd: Modem reset detected (BP_STATUS 0). Reboot system!
Code:
03-14 10:51:56.041 1545 1560 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-14 10:51:56.041 1545 1560 E mdm_panicd: connection broken - recreate socket
03-14 10:51:56.041 1545 1560 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-14 10:51:56.041 1545 1560 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-14 10:51:56.041 1545 1560 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, g
ot 0
03-14 10:51:56.041 1545 1560 D mdm_panicd: Unsolicited thread finished
03-14 10:51:56.047 1545 1545 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-14 10:51:56.047 1545 1545 E mdm_panicd: Modem power down detected (BP_RESOUT). Reboot system!
I figured out how to record the event, radio, and main system logs to the SD card while I'm out and about. I have recorded 5 reboots so far. They are all identicla. There is a problem with the radio which causes a kernel panic and therefore the reboot.
I first thought the rebooting was because I imported apps from my exchanged phone. But after several days of messing around with this stupid phone, I factory reset it and did NOTHING ELSE but turn on SD notification sounds (so I can hear it reboot). Lowe and behold the phone is still rebooting!
I am now
replacing my replacement Atrix, hopefully the next one will not have the rebooting problem. If it does, I will exchange again, and again, and again, until it works. I already have Motorola and AT&T notified about my problems but of course they dont seem to care.
Rebooting problems? Speak up. here is how to get at your logs:
usb debugging on. Have the motorola drivers installed. load adb shell.
..create files on your sd card:
adb shell
busybox mkdir /mnt/sdcard-ext/logs/
busybox touch /mnt/sdcard-ext/logs/log-radio
busybox touch /mnt/sdcard-ext/logs/log-system
busybox touch /mnt/sdcard-ext/logs/log-events
busybox touch /mnt/sdcard-ext/logs/log-main
..then cause logcat to log to these files:
adb shell busybox nohup logcat -b events -f /mnt/sdcard-ext/logs/log-events -n 60 -r 3600
(ctrl+c)
adb shell busybox nohup logcat -b system -f /mnt/sdcard-ext/logs/log-system -n 60 -r 3600
(ctrl+c)
adb shell busybox nohup logcat -b radio -f /mnt/sdcard-ext/logs/log-radio -n 60 -r 3600
(ctrl+c)
adb shell busybox nohup logcat -b main -f /mnt/sdcard-ext/logs/log-main -n 60 -r 3600
(ctrl+c)
Then you can disconnect your USB connection and use the phone. Logs are still going to your sdcard. When it reboots (YOU LIKELY WONT HAVE TO WAIT LONG), reconnect the phone with USB mass storage and copy the /logs/ folder to your PC. I bet you will find the same "RdsReadSvrMsg: READ HEADER FAIL 0" I am seeing.
I think the reboots happen more often when the cellular signal is spotty/weaker.. as they seem to happen when I go into the basement of my house
Very aggravating.
I was not yet able to capture that /data/panicreports/mdm_panicd.log file. I dont know if it is actually being created, upon reboot nothing is in that folder. I dont think it would be erased on reboot so I'm thinking its just not being created. I dont know how to redirect it elsewhere...
here are some other logs you can peak at (I did not find them to be as helpful as the above)
run:
adb shell dmesg > dmesg.txt
adb shell dumpstate > dumpstate.txt
adb shell dumpsys > dumpsys.txt
take a peak in those huge files for anything suspicious..