yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] morfic:
I will have to check if I can better analyze the gpu scaling.

Until then I'd ignore the files.

If it was staying up, you'd get pretty bad drain.

I see 266 MHz, not 620, so something is going on, but as sysfs can show anything, I'd judge by usage results right now.
[Nexus 10 Original Android Development] szale9001:
Fair enough. Just as an FYI too, the time_in_state file also reflects the increased 620 usage. Not that this is surprising. On an unrelated note, I hate that each Nexus 10 manages to be so different and unique. It makes for annoyingly complicated problem diagnosis lol.
[Nexus 10 Original Android Development] brees75:
Default stock is around 1000 points less, and 4.2.2 Trinity with 620 MHz GPU was about 8100 so I would say 4.3 holds a lot of promise!

With the TX10b kernel I only have DVFS disabled and I haven't had any issues with it staying at 620 under load. Battery life is excellent too so it must be doing what it's supposed to.
[Nexus 10 Original Android Development] CazeW:
There's no denying that this kernel is blazingly fast but for the first time my tablet also got almost too hot to touch near the front camera. Granted the tablet was charging and I was playing Middle Manager of Justice (which seems to be badly optimized at least as far as GPU usage goes) but it did scare me a little.

As what comes to the scaling, when checking from terminal emulator the clock seemed to jump between 533 and 620 but dvfs always reported that it was off. When exactly should it report that it's on?
[Nexus 10 Original Android Development] stonebear:
Try setting the cpu to 1.2 Ghz, you should find games perform just as well with less heat.
[Nexus 10 Original Android Development] cien12:
With TX10 and TX10b I will get a reboot while Antutu Benchmark at the end of OpenGL2.0 Test. First the screen freezes and 3-4 seconds later it reboots. But if i dont consider the reboot at Benchmark, TX10 seems to run pretty good.

If i limit CPU to 1200MHz, Antutu runs through.
[Nexus 10 Original Android Development] CazeW:
I actually had it set to 1.0 Ghz but it still got that hot.
[Nexus 10 Original Android Development] :
In 1 out of 3 runs I have the exact same freeze and hard reset after(!) finishing the Opengl2.0 test on stock (stock kernel) and flaming monkey (flaming monkey kernel). So I don't think it's trinity_ten, but due to the heat it's triggered more often.

[MENTION=1122306]morfic[/MENTION]: I've tested tx10 (without b) for 24h now. In my usecase (little gaming, little more working via ssh on server [betterterminal pro], lot of surfing the web, mostly watching tv and recordings from my vdr) I got a real smooth expirience, superior to stock kernel. I got 8:20 h screen on (so I'm f#+ä#+** sure, gpu isn't idleing at 620 MHz... ;). Besides antutu tx10 is rock solid on my device. I've run the kernel with no configuration changes.

Perhaps you could make the temprature, when throttleing kicks in configurable? And I would really appreciate if you could include CONFIG_SCSI_MULTI_LUN=y. I used to compile kernels myself, so it doesn't really matter, but for the test-kernels without commits in your git, I need this to use my multicard reader.

Thanx for your work and for discovering the 450Mhz limit in stock!

EDIT: logcat from antutu reset from yestetday attached. Seems to be something in the mmu in mali driver.

EDIT2: I don't belive in benchmarks, so I don't realize till now. But after some testing I found with tx6 antutu works to the end. scaling to 1700, no changes to gpu settings after booting the kernel. So my device either dislikes the uv (though I had never a prob on 4.2.2 with -50mv all over the boatd with different kernels) or it dislokes the new temperature tresholds.
[Nexus 10 Original Android Development] morfic:
Thanks, I'll keep throttling stock and see about making it configurable.

Hysteresis might be to blame for the reboots as throttling threshold is reached later, hysteresis could let it rise to the trip temperature.

We'll test that.

If the reboots remain I'll change the uv.
[Nexus 10 Original Android Development] brees75:
Please don't mess with the UV, this issue has absolutely nothing to do with the Trinity kernel. It is reproducible regardless of 4.3 ROM or kernel. I get the same results on stock kernel, hell it is reproducible on the flaming monkey kernel as well. I have been able to complete the antutu bench as well, but it was because of a rom version. I have had it work on a version of flaming monkey ROM and cm 10.2, but it hasn't worked since and I can't remember which versions they were. Lol. I can say that both times it worked I was on different Trinity versions. Personally I think it's something antutu needs to fix. It doesn't appear to be a driver issue.
[Nexus 10 Original Android Development] stonebear:
We likes the UV. :)
[Nexus 10 Original Android Development] morfic:
TX11 pushed to www.derkernel.com, relaxed the elevation of the threshold.

Added CONFIG_SCSI_MULTI_LUN=y.

Since it's on the site, source on git matches, since i commited after i test ran the kernel you'll still see a -dirty kernel.

Let me know if there is anything else in the config you might need, changing the configuration is the easiest thing to do, so i don't mind unless it has broad negative side effects or it's incomplete in source and won't build. (Rare but can happen)
[Nexus 10 Original Android Development] :
I like the uv, too. As I stated I've never had a problem with -50mv on different 4.2.2 kernels. I just observed that tx6 is running antutu fine - tx10 and tx10b let antutu crash. Everything else was speculative - and I belive morfic knows that. And: even stock kernel and flamingmonkey kernel sometimes crash antutu...

Of course you are right, antutu has to work on their app - but on the other hand a userspace app shouldn't be able to crash a kernel. And as you wrote: there were antutu resistent versions of trinity, so why not help morfic to get this back?

---------- Post added at 03:07 PM ---------- Previous post was at 03:02 PM ----------

Thank you very much - you are so much faster than samsung and google - I told them both in january about the missing multi lun support (which samsung included in their stock kernels for many devices) and it's still missing. And thank you for updating your git - there's so much to learn...

I will test your kernel later this evening.
[Nexus 10 Original Android Development] 8enigma4:
Tx11 rebooting on antutu(graphical test with green swordman), but fast as hell

KT manta can hendle 720 MHz on my device
[Nexus 10 Original Android Development] hanspampel:
Yepp its rebooting all the time in AnTuTu. But after some trys it runs through. But its not really faster as TX10 or TX3. Maybe 50 points to TX10. Got 7654 points in 3D Mark. Mean with TX10 was 7600 and TX3 7500.
[Nexus 10 Original Android Development] brees75:
Trinity is NOT the problem. It happens with any kernel including stock. It is the benchmark that is the problem.
[Nexus 10 Original Android Development] sam45:
I'm using tx11 and changing the max Cpu frequency doesn't stick. It was also like that on previous versions. Using trickster mod and flaming monkey rom.

Everything else works great, thank you!
[Nexus 10 Original Android Development] :
I've never said trinity is the problem. I've said that antutu has homework to do. But I strongly belive, if an missbehaving app is crashing one kernel more often then an other kerne, the latter is more stable. No app - no matter how bad it is implementet - should be able to crash a kernel. Tx6 is more stable then tx1[01] and stock.

---------- Post added at 05:30 PM ---------- Previous post was at 05:19 PM ----------

Tx11 is not only crashing with antutu but also with nfs most wanted - don't know about tx10, because I haven't played nfs on tx10. It's running fine on tx6. I can say that only for my device. The lastlogs I captured are always the same, it's crashing in mali_kbase_mmu.c.

Iwould like to try step by step which commit introduces this. Can you tell me wich commit is tx11? Is it 7d6757d?

Edit: more likely be7f093
[Nexus 10 Original Android Development] brees75:
The app is crashing not the kernel. I haven't had issues with anything but that benchmark on all the 4.3 Trinity versions including NFSMW. 4.3 is new so it's not a big deal or a surprise that apps are having issues.
[Nexus 10 Original Android Development] morfic:
http://goo.gl/K0quC6 TX12d-4.3-2000-ANY.zip

Well this is NOT a "eh, i just flash this and see what happens" kernel.

This kernel adds 1800, 1900 and 2000MHz.

1800 and 1900 complete a quadrant for me, 2000MHz does not, for me.

It has the -50mV suspended for testing.

This kernel is only for those interested in helping me map out the voltages.

I'd need feedback on each frequency to figure out how stable the extra steps for the ~45 people in here who download the test kernels are.

Why post a kernel that is not quadrant stable at 2000MHz for myself? I rather post a kernel that is rocky than one that uses needlessly high voltages. (And from past experience, i often couldn't run my fastest kernels that others ran without a single hiccup)

For this test i am using stock throttle thresholds for CPU and Memory.

Those with instabilities in antutu at 1700MHz could test this kernel at 1700MHz and let me know if the stock thresholds have an impact on the stability of antutu or not.

This kernel boots at 1700MHz max.

This kernel is only for hardcore users or those with a large supply of fresh underwear. ;P

http://goo.gl/zi0oVW TX12f which let me run quadrant at 2000MHz, increased voltage compensation by 25mV.

I'd still like to get feedback on 12d and 12f, just to get a feel for voltages for devices.
[Nexus 10 Original Android Development] morfic:
app crashes usually are a sign of miscomputations or failures brought on by instabilities due to various things, oc without enough extra voltage, too much UV, over optimizations.

Increased heat (increased noise) can bring on instabilities, so OC + heavy benchmarking can rock your boat, while normal use would let you sail on a calm sea.
[Nexus 10 Original Android Development] :
Look at my lastlog: the misbehaving app issues a kernel crash and a hard reset. And there is at least on kernel (tx6) that is not crashing. Please look at the provided logcat. Of course the app is crashing - no question, but then the kernel crashs hard.
[Nexus 10 Original Android Development] stonebear:
Lol, I count myself in!

So, what feedback specifically do you want?

We should do some benches and see if we get crashes?

Is it that 12d has no UV and 12f has +25mv Over-Volt?

edit

first test, Antutu at 1.7 caused a reboot. 12d kernel.
[Nexus 10 Original Android Development] szale9001:
Hmmm. So being the type of user that underclocks, I should probably pass on this one :silly:
[Nexus 10 Original Android Development] morfic:
0mV UV, and added 25mV to one comp value in f, along with editing a default max value still need time this weekend, to trace if that's indeed capping or not.

I took out the UV since that's faster than editing 36 voltage values for testing. Hmm..maybe it's only 33, still, for testing removing uv was quickest.

Later I can do this by index, again, to avoid editing the large table.
[Nexus 10 Original Android Development] stonebear:
I wonder if Brees has a point about Antutu needing updating?

What I mean is that some things may be crashing because they need updating rather than any kind of problem with the kernel?

So far- 12d

Antutu crashed at 1.7

Quadrant - stable at 2.0

GFX bench stable at 2.0

3dmark stable at 2.0

Epic Citadel crashed at 2.0 (not tried lower yet)
[Nexus 10 Original Android Development] dodo99x:
Tx11 @ 1700MHz' performance/sio

Antutu - reboots near the end of the OpenGL 2.0 test

---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------

Tx12f [MENTION=252019]2000[/MENTION]MHz, performance/sio
[Nexus 10 Original Android Development] sttovo:
12d is stable for me at 1900. I played a few graphically intensive games and they seemed to stutter more than 11 did. Games were RR3 and Infinite Flight. I put 11 back on and confirmed the stutter was gone. No crashes so far.

Ran one Basemark Taiji test on 12d and the score was slightly lower than 11. 27.3 to 27.6 fps respectively.
[Nexus 10 Original Android Development] :
Sure! He has a point here. And nfs needs an update too. The apps are crashing - no question about this.

But I don't talk about an app crash, force close or what ever happens to the apps - I try to address the hard reset of the tab, which is a completly diffrent thing then an app crash:

When I build a kernel from morfics git without the last commit (cflags and temp tresholds - 6a9868a) and reverting the fsync control commit (other matter - get a make rule error with it, I'm sure it makes no difference for the hard reset error) the resulting kernel prevents the hard reset of the device.

I don't want to insist on the term kernel crash. But fact is: there are kernels that allow antutu to run properly. Have not testet nfs yet.

[MENTION=1122306]morfic[/MENTION]: so it’s not uv, but either the last cflags or the temp tresholds. Tomorrow I will break the last commit in parts to see, what it is. from buttered aokp 4.2.2 I remember that some optimizations in gcc-4.8 are broken for -mcpu=cortex-a15.

Again thanks for your work, knowledge and research for better kernels.

In gmt+2 it's time to sleep; everybody have a nice testing time!
[Nexus 10 Original Android Development] morfic:
Sounds like I didn't add the fsync files then, I'll make sure they get added.

Sometimes -march= + -mtune= produces less hiccups, but unless there are hiccups I prefer -mcpu=

Coming to think of it, only change the -mfpu=neon back to -mfpu=neon-vfpv4 and let me know if that affects antutu, if you want to help track this down that is, strapped for time,I would appreciate it.

If that isn't it, relax the second mcpu after comma in arch/arm/Makefile
[Nexus 10 Original Android Development] newellj79:
Just flashed my first 4.3 ROM. I've been using your 4.2 kernels since I got this tablet. Is the 4.3 kernel undervolted like the 4.2 was? Also is there a GPU OC yet? Sorry if this was covered...
[Nexus 10 Original Android Development] morfic:
Yes, there is gpu oc, yes there is uv, however, there is no uv in the cpu oc builds while establishing stable voltages for 1800-2000 range.

I invite you to click a few pages back so you can see what's what :)

Everything is still in flux, getting started on 4.3 yet being further in some areas.
[Nexus 10 Original Android Development] :
Of course I help you. In the next step I'll add back the temp tresholds to be sure it's really cflags. Then tere are quite some combinations to test. It will take some time (there's live after xda and android... ;) ). I also want to test linari 13.07; perhaps there's some better behaving gcc regarding cortx-a15. I've not looked at the linaro development since may or so.

Which benchmark is good for testing io, threads, strings, memmove, memcopy and friends to check the impact of optimizations? I'm not sure how large - if any - the good of the cortex-a15 optimization is. Lately, when playing with cm's bionic i found that neon optimized mem-operations feel much smarter then cortex-a15 optimized ones. I know thats a completely other playground - but it's worth a thought (and a reallity-check).

Another thought (better call it wild guess): if performance&sio work for 12f and antutu, theres perhsps some side-effect in ondemand&deadline (and for that matter in interactive&cfq in stock). In 4.2 franco changed something in ondemand - worth a look... as I said: wild guessing...

OT: yestetday you gave me a broad smile: I was looking for boot.img in your zip for disassembling it to use same ramdisk... I LOVE the way you think. Just replacing the kernel and leave the roms ramdisk alone is great in my oppinion!
[Nexus 10 Original Android Development] morfic:
The coretx-a15 optimization was improved in gcc4.8, that's why i am using it. (after testing)

gcc4.7 google beat linaro in my book, but linaro gc4.8 beats google 4.7

now i am not saying linaro because "hey look, linaro", no, i am saying it because it happens to be the only gcc4.8 that's available, not because i prefer linaro (but have before it became the buzzword du jour) :)

There is no one benchmark that's best, i benchmark multiple things and look at impact on each.

Why do i use the old quadrant? It's quick and it's overly sensitive to changes, so i can use it like a microscope when looking for changes, and if the changes are in cpu, memory, io, 2D or 3D scores.

I know something made a positive impact when the helix goes from ~54fps to ~59fps. (but now at 59fps i can no longer see much unless it gets worse)

I tried the SGS4 dalvik that makes a huge impact on the N4, but on the N10 memory score drops by about 500 points (average of multiple runs)

2D and 3D of quadrant are now damn near maxed and not good for much, so to test GPU OC i use Taiji it is HEAVILY GPU bound, you can usually lower your max clock and still get same fps, that's how i noticed we aren't scaling past 450MHz since the 21fps were not what i remembered from 4.2, so i looked and yes it did get stuck on 450MHz, then once i got it to 533 i saw 24fps and 620 brought back 27fps, that recent change you reverted actually tickled out 28fps, which is why i kept it, it's rare for cflags to affect taiji (At least from what i remember seeing on the N10)

Antutu, 3dmark are nice benchmarks but take too long when i want to crank out a few builds in a row.

I rather add Windmill to the mix of quadrant and taiji as it is both cpu and gpu heavy.

If you want to see the impact of dalvik and bionic optimizations you will probably want to test cfbench, it is not only showing that nicely, it is also a nice stability test as it REALLY taxes your CPU and gets things nice and toasty.

-----

The anykernel script is from koush, i just like the idea as it improves rom compatibility and when i can avoid it, i will not create the boot.img, every once in a while i need to to have a module inside the ramdisk for example or just because anykernel fails on a device yet the boot.img runs perfectly fine.

Most Nexii you will find use anykernel scripts, franco tends to prefer boot.img which essentially makes any kernel flashed after franco a frankenkernel or is it a francostein? either way, it can lead to funny business.

------

About ondemand/deadline, if you can revert a commit that does not touch either and antutu completes i don't think we should add this to list of things to scrutinize right now.

------

Antutu runs through here on the last TX12 i'm on at 1700/1700 which was already an issue for you, no?
[Nexus 10 Original Android Development] morfic:
Also on a second thought, if i just expose samsung's magic number that held gpu at 450mhz (and is now 620), we can turn this easily into a max gpu clock sysfs file, oh yeah, that sounds good, we should do that.
[Nexus 10 Original Android Development] morfic:
http://goo.gl/OpDiRJ TX13

Now with an additional throttle point as it was obvious that it still hit the tripping temp of 110C while throttling at 1000MHz

It never hit the shutdown temp of 121C, but 119C i call damn close.

I never ran into hot temps in daily use of OCed devices but this now protects your device during benchmarks better than stock throttle, which is too slow, it will be more drastic during game play I'd wager, that's why we need a gpu max, to dial in the best combination of max gpu and max cpu for any given use case.

EDIT: That's still no solution, it can still raise up too high if the load persists, even if throttled to 400MHZ
[Nexus 10 Original Android Development] :
Disclaimer: I don't blame anything neither kernel nor app) for crashing. All my results are only valid for my device (devices differ as we al know). I love speed - but stability is just a little bit more important to me. Test base was current git - no TX12. I aleays tested with no changes to sysfs: ondemand/deadline; no limit fot cpu (1700 MHz)

First of all: on my last build yestetday (the one that was stable with antutu and nfs) I made a mistake in cut'n'paste commit hashes, so it was not ab06620 but be7f093; or in other words: WITHOUT UV.

Today I splitet the last git commit and only applied cflags: hard crash at the end of opengl2.

Next I changed the fpu optimazation back to plain neon: stable.

Then I put UV back: crash at the end of opengl2 - strange: very same errors in lastlog.

I reduced UV to -25mv: stable in the first run, crash at the end of opengl2.

So no UV and slightly modified cflags is stable for me. (For testing only one thing at a time I have temp tresholds on stock values, after seeing the throttle posting from morfic)

Conclusion: I'm confused. How can two completely different changes produce the very same (unwanted) outcome? But how ever: my device seems to be more sensitive to UV on 4.3 than on 4.2.2 - I know that the -50mv patch was working for me with trinity as well as with a modified aokp-kernel. Perhaps due to the changes in the mali driver... Question: is the -50mv patch only effecting cpu or the whole board (cpu, gpu and ram mainly)?

Hope this helps.

Edit: stable means three subsequent runs. Meanwhile I have put back the new treshold values, and have played two 40 minute sessions nfs (I'm no gamer type, but few kernel versions more, and I can mess with my kids). First session standard values: stuttering and slowmotion for 5 seconds every 15 seconds. Second session with cpu put to 1100 MHz: nearly no stuttering (honestly Ive seen none, but both of my sons said there was some...) and no slowmo anymore. Ok, now I'm a hardcore gamer - I need more $ - Ineed more cars - I've no time to test kernels anymore... ;)
[Nexus 10 Original Android Development] sttovo:
Thanks for all the work you do on this kernel morfic!

13 feels more like 12 to me, with 10 still being the best SOTP performance. 10/12/13 all score similar in fps tests, but when playing intensive games,10 is stutter free for me. 12/13 both stutter ever so slightly.

I also checked my kmsg for any temp warnings, but I didn't have any. Maybe I'm not pushing the N10 as hard as you guys. I'm sticking with default gov/sched to keep my test apples to apples.
[Nexus 10 Original Android Development] hospital349:
[MENTION=1122306]morfic[/MENTION]

Happy 10,000th THANK. :good: Big love, bro!!
[Nexus 10 Original Android Development] stonebear:
I was getting stutter in NFS MW with one of them, I can't remember which now -

but

I don't seem to have any with the latest.
[Nexus 10 Original Android Development] brees75:
Does 13 have undervolt back? I have no use for CPU overclock so I am just waiting for that to come back.
[Nexus 10 Original Android Development] morfic:
UV is not in that one, no.

It'll came back as an adjustable global UV.

Since I Don't believe inn that being ideal, I'll work on a real uv interface, the adjustable global uv just as interim solution to fixed (test) uv.

Why not just merge an existing interface? Because... :)

I just want to make one work "from scratch".

I'll probably take the weekend off, haven't felt right all week, all builds I did were pretty much just to keep my mind off whatever pains are bothering me this week.

Sorry for the Debby downer moment, just wouldn't feel right knocking out build after build and then go quiet without telling people wtf is going on.
[Nexus 10 Original Android Development] brees75:
Hope you feel better, sleep is the best thing for just about everything.
[Nexus 10 Original Android Development] stonebear:
I hope you feel better soon mate.
[Nexus 10 Original Android Development] :
Glad to hear of the configurable uv-interface, since my n10 seems to be very sensitive to voltage.

No downer at all. Take your time. Health is more important. Get well soon! Thank you for your explanations and your patience with me.
[Nexus 10 Original Android Development] morfic:
Thank me when it all exists. :)
[Nexus 10 Original Android Development] maxiclo:
That's the kernel.

Fastest of any other. Compared with Quadrant at least.

Just bought the Trinity Kernel Toolbox.

Thank you for supporting Nexus 10.