yashsingh1/xdaforums huggingface dataset:
[Motorola Milestone Android Development] Benny1988:
No, the fix doesn't work well for me. Now it was the fourth reboot in the last 3 hours without do anything on the phone.

But I can't attach the apanic-files, 'cause the files aren't there. Last two files are from 08/08/11. Any way to post a log for you?

I'm using FroyoMod 2.9.2 and the last fix I used before 2.51 was 2.41 (out of your last CM7-build).

Best regards and nice work you do,

Benny.

EDIT:

Now - 37 minutes after this post - I see the Bootscreen the fifth time. It sucks. :x
[Motorola Milestone Android Development] moe6:
2.41 went great for me no issues, just switched 2.51. Will report if I have a freeze.
[Motorola Milestone Android Development] vadonka:
froyomod will reboot sometime without the dsi modul, try it with cm6 or cm7. with cm7 no problem at all. i have the latest cm7 based gb rom and my phone running for a weak now without poroblem, no slow down, no any problem.
[Motorola Milestone Android Development] Benny1988:
Curious,... I replace the 2.51 fix with the 2.50 fix and now I don't have a reboot since 5 hours. So, I think it's the fix 'cause 2.50 works well like 2.41 and also 2.40.

2.51 ~> Lots of reboots.

2.50 ~> No reboot or freeze.

2.41 & 2.40 ~> No reboot or freeze.

2.30 ~> No reboot, but sometimes a short freeze.

Regards, Benny.
[Motorola Milestone Android Development] papadawgg:
since i was using the v2.41 i had no problems anymore and with 2.51 my phone feels even faster than before. im using tfm 2.7
[Motorola Milestone Android Development] enrsil1983:
I'm using v2.41 in CM7 since the release of official RC13 and I didn't experience a single reboot or slowdown, and battery usage is OK.
[Motorola Milestone Android Development] pcphobic:
This goes to show that not all Milestone are built the same.

Some DSI versions work great with some of u and some version do not.
[Motorola Milestone Android Development] wisefreakz:
@PEOPLE: Instead of just complain that the Fix sucks... why not do as asked by Kadalban and post your logs??

It's the only way he can see whats going on and try - FOR FREE - to really address the problem that Motorola coundn't.

Peace!
[Motorola Milestone Android Development] Benny1988:
When you read my post you see I asked for a way to sent him the logs he need, 'cause there aren't any new dontpanic-files. :x

Regards, Benny.
[Motorola Milestone Android Development] HinotoriBR:
In theory, if you don't have DSI errors, this fix should not change anything at all, as it will not get called. The size of the module is so small that I guess that it wouldn't really matter overall as far as free memory or memory usage is concerned.
[Motorola Milestone Android Development] luukmulder:
no more reboots

Since I've been using 2.51 I have not had any reboots. I can see in the log that occasionally an error has occured, but these are nicely recovered.

Great work, Kabaldan :)
[Motorola Milestone Android Development] MorfeuZ:
Just stopping by to let you guys know that I'm on 2.41 for several days now and haven't noticed anymore issues.

GREAT WORK Kabaldan. Thank you so much.

I will try 2.51 soon.
[Motorola Milestone Android Development] legalghost:
Brilliant

v2.5.1 working flawlessly in Froyomod, CM6 and CM7..

Great work nadlabak!
[Motorola Milestone Android Development] zrima167:
Reboot with RC14, after deleting widgets from my main screen:

http://pastebin.com/uWnqMehw
[Motorola Milestone Android Development] papadawgg:
now im using the fix v2.52 from your github and now my phone even became snappier, again. using cm7 rc13. what did you changed in this version?

download: http://www.multiupload.com/MPOW96Z6T4

edit: had a reboot a few hours ago, so i will stick with 2.51. apanic_console is attached.
[Motorola Milestone Android Development] cronot:
I may be wrong, nadlabak may be able to confirm it, but from that log output, it doesn't look like that kernel panic is DSI related, at least not directly. It looks like something else.
[Motorola Milestone Android Development] kabaldan:
Right, the KP in the log posted by zrima167 is not related to DSS/DSI subsystem.

As I've experienced about 20s freeze when running DSI-fix v2.51 in the end after several days of flawless use, I've made new DSI-fix v2.52.

In 2.52, dsi hw reset is always forced when framedone timeout appears (previously it was sw reset + communication test, and hw reset afterwards only when the test failed).

As I'm experiencing the common OMAP SD card issue pointed out by HinotoriBR here: http://xdaforums.com/showpost.php?p=17033833&postcount=5563

I've added omap hsmmc set_data_timeout kernel function replacement to DSI-fix v2.6.

Therefore DSI-fix becomes DSI/MMC-fix now.

v2.6 can be downloaded here: http://www.multiupload.com/DZGUJFVCPJ
[Motorola Milestone Android Development] papadawgg:
just had a reboot with the dsifix 2.6 using cm7 rc13.
[Motorola Milestone Android Development] kabaldan:
papadawgg:

"PC is at cgroup_pidlist_open+0xcc/0x3c0"

Definitely not related to DSS/DSI nor MMC kernel drivers.

Possibly caused by overclock settings? Too low vsel? Cpu overheated?

Hard to say. But I've never experienced KP at this spot.
[Motorola Milestone Android Development] papadawgg:
ok, thanks. im gonna increase my vsels and see what will happen.
[Motorola Milestone Android Development] HinotoriBR:
Nadlabak/Kabaldan,

MMC work-around work great. Now my class 10 SD Card is working flawlessly and no error messages in dmesg.

On the other hand, it seems that it affects the write performace of the card over USB, at least in the USB interface, where I got a write speed of 3,79MB/s for a file of 1.4GB while usually I would get at least 6-8MB/s...

Now, read speeds seem unchanged over USB, around 16-17MB/s...

Read and Write speeds using SD Tools also got great results, around 9.4MB/s Writing and over 18MB/s reading.

Thanks for the great fix!
[Motorola Milestone Android Development] HinotoriBR:
Btw, would it be possible to use this fix in AOR?
[Motorola Milestone Android Development] vadonka:
1. put the dsifix.ko to the c:\dsifix folder

2. in a cmd shell

adb push c:\dsifix\dsifix.ko /sdcard
adb remount
adb shell

3. then in the adb shell

rmmod dsifix
rm /system/lib/modules/dsifix.ko
cp /sdcard/dsifix.ko /system/lib/modules
chmod 0644 /system/lib/modules/dsifix.ko
insmod /system/lib/modules/dsifix.ko
exit

no need to boot to OR or reboot, you can do while the phone running.
[Motorola Milestone Android Development] HinotoriBR:
I believe you did not undestand my question...

As far as I know, OR and its variants use a different kernel, and those need modules compiled for that specific kernel...

Altough I have the fix running in my phone and did it without using AOR or any OR, still, the fix is not applied in my OR (in my case, AOR), so, if I try to make a nandroid backup, an update, or anything else, SDCARD errors will occur (i.e.: I'm not able to restore a nandroid backup of SDDATA due to that).

So, I'm asking if this dsifix.ko can be used in OR (I believe we can't), if not, if there are plans of having it available. :-)
[Motorola Milestone Android Development] vadonka:
try to buy a bear for kabaldan and ask him to compile the modul to the OR kernel :)
[Motorola Milestone Android Development] kabaldan:
I've added mmcfix.ko (compiled for recovery 2.6.29 kernel) to my OpenRecovery update package:

http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OR1.46_extfs_mmcfix_update.zip

The only files that changed and are related to mmc fix are:

OpenRecovery/lib/modules/2.6.29/mmcfix.ko

OpenRecovery/bin/switch.sh
[Motorola Milestone Android Development] HinotoriBR:
Hmm... I don't think my girl will like if I send a teddy bear to anyone that is not herself... :D But I've donated a couple of beers to nadlabak, not only due to the recent MMC fix but for all his great help. :D
[Motorola Milestone Android Development] vadonka:
sorry, my bad :) i had a typo :D teddy bear :D

kabaldan already do this job without the teddy bear :D
[Motorola Milestone Android Development] HinotoriBR:
HAve been testing mmc fix since day one, it is working flawlessly, my class 10 sdcard is now working like a charm, no more corrupted files and no more updates or installation failures and no more force closes on known-good applications

Also, tested quite a bit the Open Recovery mmc fix and it is working flawlessly as well.

As far as DSI fix is concerned, my phone is not prone to DSI reboots, perhaps sometimes it freezes for a while (DSI fix installed or not), but in these days with this latest fix I did not observe any freezing, so, so far so good.

<3>[60925.993591] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[60925.993621] omapdss DSI error: ACK with ERROR (0x40):
<3>[60925.993652] omapdss DSI error: False Control Error
<3>[61590.045837] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[61590.045867] omapdss DSI error: ACK with ERROR (0x40):
<3>[61590.045898] omapdss DSI error: False Control Error
<3>[61928.112091] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[61928.112152] omapdss DSI error: ACK with ERROR (0x40):
<3>[61928.112182] omapdss DSI error: False Control Error
<3>[64292.652404] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[64292.652435] omapdss DSI error: ACK with ERROR (0x40):
<3>[64292.652435] omapdss DSI error: False Control Error
<3>[67020.171356] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[67020.171386] omapdss DSI error: ACK with ERROR (0x40):
<3>[67020.171386] omapdss DSI error: False Control Error
<3>[69435.720733] omapdss DSI error: rx fifo not empty when sending BTA, dumping
data:
<3>[69435.720764] omapdss DSI error: ACK with ERROR (0x40):
<3>[69435.720764] omapdss DSI error: False Control Error
[Motorola Milestone Android Development] dateno1:
kabaldan//can you compile dsi fix module for 29kernel?

it will prevent dsi error in recovery and CM7 for milestone on XT720 :D
[Motorola Milestone Android Development] dateno1:
mmcfix for recovery module not working on my phone :(

when i try insmod mmcfix.ko it print "Segmentation fault" and when i type lsmod it Loading forever (no logcat error)
[Motorola Milestone Android Development] vadonka:
mmcfix module compiled only for the OR kernel, for the main kernel just use the dsifix modul. this included the mmcfix too.
[Motorola Milestone Android Development] dateno1:
i try on recovery and shhijack recovery

but loading foever

when i try on normal boot it reboot my phone :(
[Motorola Milestone Android Development] vadonka:
are you have a milestone phone?

dsifix 2.61 out!

https://github.com/nadlabak/android...mmit/87baa0f91a6bae8cc27ddd93ad5c6d0f3aed78f7

DSI/MMC/NAND fix v2.61

- disable duplicated nand suspend/resume calls to get rid of the

'nand_resume called for a chip which is not in suspend_state' messages
[Motorola Milestone Android Development] kabaldan:
dateno1:

mmcfix.ko for Milestone 2.6.29 recovery kernel is compiled using hardcoded symbol addresses (as sysmsearch needs 2.6.32 kernel) and can be used only with that particular kernel.

If you upload kallsyms output of your xt720 kernel, I can build a version suitable for your kernel.

Do e.g. in terminal on your phone:

cat /proc/kallsyms > /sdcard/kallsyms.txt

Then upload kallsyms.txt e.g. to multiupload and post the link to it here.
[Motorola Milestone Android Development] dateno1:
thanks very much

http://www.megaupload.com/?d=1L828AJQ

you can download from here

it from XT720

39R=global kernel

50R=cm7 kernel

recovery=recovery
[Motorola Milestone Android Development] DannyDroid:
This may help in testing versions;

http://xdaforums.com/showthread.php?t=1228605

Easy install, remove and loading of .ko's.
[Motorola Milestone Android Development] Mioze7Ae:
Hi dateno1!

I ported symsearch.ko to 2.6.29 (source here: https://github.com/Mioze7Ae/android...mmit/5e3b8a1bfbac0adeefedce66865739ebb5e360d6)

Here are symsearch.ko and mmcfix.ko (source here: https://github.com/nadlabak/android...ingerbread/prebuilt/lib/modules/source/mmcfix) compiled using Milestone XT720 sources.

You have to load symsearch.ko first and then set /proc/symsearch/kallsyms_find_symbol to the right address (like we do for overclock.ko) before loading mmcfix.ko:

# Load the module
insmod symsearch.ko

# The module doesn't know the address of kallsyms_lookup_name yet
cat /proc/symsearch/kallsyms_lookup_name

# We can find it via /proc/kallsyms
grep '^........ T kallsyms_lookup_name$' /proc/kallsyms

# Feed it to the module
grep '^........ T kallsyms_lookup_name$' /proc/kallsyms \
> /proc/symsearch/kallsyms_lookup_name

# Now should match entry in /proc/kallsyms
cat /proc/symsearch/kallsyms_lookup_name

# Now mmcfix can be loaded
insmod mmcfix.ko
[Motorola Milestone Android Development] dateno1:
i test on my xt720 but it not work (same as milestone's :()

i think symsearch.ko work but mmcfix.ko not work
[Motorola Milestone Android Development] wisefreakz:
@Kadalban I have totally nood question:

Is there any chance the DSIFIX module be killed regarding the values applied by the minfree/adj/oom values?

Thanks!!
[Motorola Milestone Android Development] HinotoriBR:
No way, two tottally diffent worlds, minfreee/oom/etc are related to the dalvik (java virtual machine) world and modules are part of the kernel world. Once a module is loaded, it is loaded and no regular Android app/game/memory management can remove it.
[Motorola Milestone Android Development] wisefreakz:
Thanks for the clarification mate!!
[Motorola Milestone Android Development] DannyDroid:
2.61 fails to mount under MIUI. Not sure why =/ .

2.6 mounts fine.
[Motorola Milestone Android Development] diamond_lover:
There's a way to load this fix in ClockWorkMod Recovery? Because if I try make a backup my phone will stuck...
[Motorola Milestone Android Development] DannyDroid:
You have a Defy? This is for the Milestone.
[Motorola Milestone Android Development] diamond_lover:
symsearch.ko, smartass or mmcfix

I know, I have ported version for Defy, now it runs welll :D

My only issue is how can be loaded smartass.ko and mmcfix.ko, because both need symsearch.ko...
[Motorola Milestone Android Development] Skrilax_CZ:
Just load symsearch.ko prior loading them.
[Motorola Milestone Android Development] HGhertel1:
Hello, is this Fix for the DSI-Errors the Final Fix or will they be another one? Thanks
[Motorola Milestone Android Development] HinotoriBR:
Ghertel,

If you still have issues, you should post your logs as Nadlabak/Kabaldan requires, so he can investigate it and check if there is need for further improovments...;)
[Motorola Milestone Android Development] HGhertel1:
@hinotori: No, i don`t have any issue with the DSI-Errors, but i only want to know if there is any idea to fix some other issues or the work on this Fix is finished.

For example if i look into OSmonitor and there are some LOGs about this here:

I don´t know anything about this Error.
[Motorola Milestone Android Development] kabaldan:
Occasional device status conditions preventing suspend mode are normal.

Only if it would be constantly repeated, then it would pose a problem.

regarding "final": until I lose any interest in Milestone (not in sight so far), nothing is final :P
[Motorola Milestone Android Development] Benny1988:
And that (bold/blue) is the problem, I have. This message repeats everytime. In 5 minutes like 10 times, but not all the time. So I've a few hours without these messages and some hours with.

Sometimes I've a reboot ~> between 1-5 times a day, but not a hotboot - so only the OS restarts.

Regards, Benny.

(Sorry for bad english. :x)
[Motorola Milestone Android Development] HinotoriBR:
Are you using WiFi when this happens? I know that most of the times this message appears is due to some kernel module not supporting sleep or preventing sleep, and usually it is the WiFi module that does that, if I'm not mistaken the phone can't go to deep sleep if you are using WiFi... (just trying to figure out, it seems you have good knowledge and probably know that, just in case you don't know)
[Motorola Milestone Android Development] Benny1988:
Thanks, but I don't use Wifi and I don't use GPS, too. Wifi 1 time / month and GPS 1 time / week maximal. Unfortunately, that's not the problem. :(

Regards, Benny.
[Motorola Milestone Android Development] adamz667:
Hi!

I've got the same problems with dsi fix like user Benny. Phone is entering suspend and aborting suspend almost all the time when not used (wifi/gps/bt/mobile connection off, 2g, only GApps sync). I'm not using GPS, sometimes wifi/mobile connection but not often.

I'm using latest CM6 by milaq.

Log:

http://pastebin.com/hGXZSx4m
[Motorola Milestone Android Development] kabaldan:
What has happened / has been changed during the first two minutes after noon (phone screen mostly on at that time)?

Because since then, the phone suspends pretty well.
[Motorola Milestone Android Development] adamz667:
At 12:00 I had a phone call (outgoing), I was talking for 55 seconds. Probably nothing else or I can't remember.
[Motorola Milestone Android Development] wisefreakz:
Master... using the nightly version... phone had freezed... did not came back from the black screen so i ctrl alt del...lol

Here is the apanic file.... hope it helphttp://db.tt/L0WYSL3w
[Motorola Milestone Android Development] choonyoong:
Got a reboot and a freeze that doesn't recover (have to force reboot) with latest version CyanogenMod 7.1.0-11.09.30 (Android 2.3.7)

Attached apanic_console file.
[Motorola Milestone Android Development] Benny1988:
Had a reboot 10 minutes ago, too, but the dontpanic folder is empty? I've a few files in /data/logger/. The files have been created / modified at the same time like the reboot. Maybe they'll help?

Phone runs very well the last week with CM7.1.0_11.09.30, this reboot was the first. :(

Regards, Benny.
[Motorola Milestone Android Development] mrvek:
dsi-fix problems

Hy. I know this is rather old thread but unfortunately I have some issues with applying this fix.

The problem is that my screen freezes and when it happens it has some colored dots at the bottom of the screen. I belive that this is related to dsi error. There is some mention of dss/dsi errors in dmesg but I don't know how to interpret it.

I uploaded some images because I belive it'll explain a bit better if this is dsi error.

I hope you could help me to apply this fix. I've tried various versions and none works, the screen still freezes. What i've noticed is that the screen does not get theese errors/freezes until I switch off (lock) the screen. Basically, I reboot, use phone normally (half an hour without a problem) but then I lock the screen and after unlocking the error will apperar very soon.

Is there some dependancy between files? I've tried almost all versions of dsifix.ko from v. 2.4 to 2.61 and everything is the same. You've been mentioning symsearch. Is there a specific version I need?

I uploaded a few dmesg outputs, perhaps it will be usefull.

The other problem I have is Open Recovery update menu. I'm not sure if it is related to this MMC errors the fix is for but there are some errors when Open Recovery tries to read the update directory. The images should do a better job explaining the problem.

The ROM I'm using is milaq's CM 6.3.6. On 6.3.5 everything was the same.
[Motorola Milestone Android Development] HinotoriBR:
mvrek, if you are using Milaq's CM 6.3.5 or 6.3.6, it already contains the latest DSIFIX and everything it needs. I believe that you need to send the contents of dmesg when this issue happens, so kabaldan can try to figure out what is going on...
[Motorola Milestone Android Development] mrvek:
HinotoriBR, thank you for reply but the reason for trying out various versions of dsi fix is because it didn't work. I've been getting freezes constantly, so often that the phone wasn't usable.

The only solution that works is writing 1 in update_mode file. But that causes significant screen tearing and some slowdown. So I'm hoping that I could apply this fix.
[Motorola Milestone Android Development] HinotoriBR:
Like I said, this fix is already applied to Milaq's CM6 rom... So, if it doesn't work, even if you tried replacing the dsifix.ko file for older ones (did you remember to chmod the new dsifix.ko so it is executable, as files that you move from the SDCARD to the phone usually do not have execution permission, you need to chmod 644 dsifix.ko), all you can do is get dmesg output after the issue and hope that kabaldan figures it out. ;)
[Motorola Milestone Android Development] mrvek:
Hmm...

I'm not sure if the files i've tried are older (atleast not all of them). The original cm6 dsifix.ko has a file size of 9.50 kb (9728 bytes) and none of the files I've downloaded from this thread has this file size. The versions I've tried are all in range from 2.4 to 2.6.1. But I do not know if this file has some dependancy on something else, perhaps symsearch.ko (someone has been mentioning it in the context of dsifix).

Permissions have been set properly every time. Btw., octal permission 644 does not include execute permissions, it sets read and write for owner and read perms for group and others. .ko are kernel modules and are not executable in the sense of executable shell scripts. If you go to /etc/init.d and remove execute permissions from, say, 10overclock your system would boot with stock frequencies.

To return from offtopic... the only property I have not set in previous testings is the owner the file. But since you have reminded me of that I have just tested it and the result is the same. Screen freezes. And what I have noticed once again is that the screen does not freeze until I unlock the screen. Phone boots up, I enter sim pin, use phone normally without any problem but then I lock the screen (or it times out by it self, doesn't matter) and it froze in a second, I didn't even have time to launch an application. This pattern is consistent.

dmesg output is already atached to my first post, it has several dmesg files.
[Motorola Milestone Android Development] HinotoriBR:
I understand, symsearch.ko is basically what makes it possible to re-use modules without having to compile them specifically for each different kernel, it is part of CM 6.3 as well.... It allows to properly load the overclock and dsifix modules in the proper place, so those codes are executed when they should...

Just a silly question, have you tried a clean install of CM 7, latest version? You can just perform a full nandroid backup of your current phone rom/data, then try CM7 clean (wipe data and cache) and check if this behavior still occurs. I did not get any DSI error using CM 6.3, but, my phone is not the absolutely best to test this, as even before having any kind of DSI fix or workaround, my phone did not have those errors....
[Motorola Milestone Android Development] mrvek:
Have tried cm7, I think 7.1.1 was latest, but do not remember if it had these problems. Probably it did.

You said your phone didn't have these issues. I thout it was software (kernel) related. Or not?