[HTC Rezound] cgearhar:
CyanogenMod 10.1 Predictable Reboot while Wifi Tethered

<First Post><Tried to find the right place><Watched the video><noob>

Last night I used the HTCDev HBoot Unlock technique to Unlock my Hboot 2.28 on my HTC Rezound. S-ON.

It now reflects "TAMPERED, UNLOCKED" - no problems to speak of with the process.

I installed TWRP 2.6 recovery, did a factory reset and multiple wipes across the partitions shown as available on TWRP.

I installed the Unofficial CyanogenMod 10.1 here: vp-zp com snuzzo roms flyhalf205 cm10 I used the 0819-NIGHTLY.

I've since loaded the device up with my usual apps and and decided to try the WIFI AP/WIFI Tether option.

I had only 1 random reboot prior to attempting the WIFI AP.

On the surface WIFI AP appears to work - devices can connect with WPA2 PSK, obtain IP, routing works, etc.

If I try speedtest on tethered device, however, the phone almost immediately reboots to the white HTC screen (and has gotten stuck in a loop several times requiring a battery pull).

I'd like to help diagnose what's happening, but I'm afraid I need some assistance for the best way to start.

What's the best way to start diag? Gather kernel logs? Gather wpa_supplicant logs? Look @ HBoot versions? Look @ Radio Firmware versions? Go S-OFF?

Here's a quick post from /dev/log/kernel_log -- note, I'm not OC'd (1512Mhz)

08-20 01:09:15 <4>[ 2.592498] ------------[ cut here ]------------

08-20 01:09:15 <4>[ 2.592681] WARNING: at arch/arm/mach-msm/clock-local.c:376 __branch_clk_disable_reg+0xd4/0xec()

08-20 01:09:15 <4>[ 2.592742] sdc3_p_clk status stuck at 'on'

08-20 01:09:15 <4>[ 2.592926] Modules linked in:

08-20 01:09:15 <4>[ 2.593170] [<c00532d4>] (unwind_backtrace+0x0/0xf0) from [<c00da384>] (warn_slowpath_common+0x4c/0x64)

08-20 01:09:15 <4>[ 2.593353] [<c00da384>] (warn_slowpath_common+0x4c/0x64) from [<c00da41c>] (warn_slowpath_fmt+0x2c/0x3c)

08-20 01:09:15 <4>[ 2.593505] [<c00da41c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c00986f4>] (__branch_clk_disable_reg+0xd4/0xec)

08-20 01:09:15 <4>[ 2.593658] [<c00986f4>] (__branch_clk_disable_reg+0xd4/0xec) from [<c009876c>] (branch_clk_disable+0x28/0x44)

08-20 01:09:15 <4>[ 2.593750] [<c009876c>] (branch_clk_disable+0x28/0x44) from [<c005a8c0>] (clk_disable+0x6c/0xf4)

08-20 01:09:15 <4>[ 2.593933] [<c005a8c0>] (clk_disable+0x6c/0xf4) from [<c0373950>] (msmsdcc_switch_clock+0x390/0x3e4)

08-20 01:09:15 <4>[ 2.594085] [<c0373950>] (msmsdcc_switch_clock+0x390/0x3e4) from [<c0373ac4>] (msmsdcc_runtime_suspend+0x98/0xf4)

08-20 01:09:15 <4>[ 2.594268] [<c0373ac4>] (msmsdcc_runtime_suspend+0x98/0xf4) from [<c02a041c>] (pm_generic_runtime_suspend+0x2c/0x38)

08-20 01:09:15 <4>[ 2.594421] [<c02a041c>] (pm_generic_runtime_suspend+0x2c/0x38) from [<c02a287c>] (rpm_callback+0x44/0x5c)

08-20 01:09:15 <4>[ 2.594604] [<c02a287c>] (rpm_callback+0x44/0x5c) from [<c02a2d38>] (rpm_suspend+0x270/0x458)

08-20 01:09:15 <4>[ 2.594757] [<c02a2d38>] (rpm_suspend+0x270/0x458) from [<c02a3c70>] (pm_runtime_work+0x7c/0x98)

08-20 01:09:15 <4>[ 2.594848] [<c02a3c70>] (pm_runtime_work+0x7c/0x98) from [<c00ed1b4>] (process_one_work+0x248/0x3a4)

08-20 01:09:15 <4>[ 2.595031] [<c00ed1b4>] (process_one_work+0x248/0x3a4) from [<c00ed6ec>] (worker_thread+0x224/0x3e0)

08-20 01:09:15 <4>[ 2.595184] [<c00ed6ec>] (worker_thread+0x224/0x3e0) from [<c00f3050>] (kthread+0x80/0x88)

08-20 01:09:15 <4>[ 2.595336] [<c00f3050>] (kthread+0x80/0x88) from [<c004e69c>] (kernel_thread_exit+0x0/0x8)

08-20 01:09:15 <4>[ 2.595428] ---[ end trace 65f8ea860415c054 ]---

<Update>

I found another forum post with similar issue and I raised my min clock speed from 192Mhz to 384Mhz and re-ran the test and it did NOT reboot. Will continue testing and update if I get another reboot. 2 days solid @ the new min clock speed, no more reboots, battery remains dreadfully bad, but no worse.

VIGOR PVT SHIP S-ON RL

HBOOT-2.28

RADIO-2.23.10.0123r/2.23.10.0124r

OpenDSP-v14.6.0.7708.00.0507

eMMC-boot

Sep 20, 2012