I get errors in dmesg at any speed over 200mhz, it didn't work. 200mhz is still much faster than the stock 122.88mhz.
The new module is not working on V9.
Was set to 160mhz, set to max axi clock speed (200mhz)
We leak at least 32bits of kernel memory to user land in tc dump, because we dont init all fields (capab ?) of the dumped structure. Use C99 initializers so that holes and non explicit fields are zeroed. Signed-off-by: Eric Dumazet <firstname.lastname@example.org> Signed-off-by: David S. Miller <email@example.com> Conflicts: net/sched/act_nat.c Signed-off-by: nobodyAtall <firstname.lastname@example.org>
High temperature related shutdowns are happening much later in 2.6.35. The battery status returned is still good so assume that temperature is bad if battery status is good but temperature is over 68 degrees.
The battery temperature sensor reports invalid readings for some time after resume. As these are much too high typically, sometimes an Android overheating shutdown is triggered. The previous workaround of ignoring N readings that seemed too high is incomplete as it would still trigger very rarely. Ignore temperature readings for 90 seconds after resume instead. This also helps keeping noise out of stats created by battery apps.