Compiling custom kernels for P1.1 (with fiasco-gen) - Page 18 - maemo.org

nightfire | # 171 | 2010-04-07, 20:34 | Report

Excuse the threadspamming..

I just noticed some stack dumps in my ring buffer:

Code:

[91202.267547] WARNING: at /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()
...

Seems to be happening fairly frequently. Otherwise system normal and stable, though. Anyone else seeing this?

Last edited by nightfire; 2010-04-07 at 20:39.

titan | # 172 | 2010-04-07, 21:12 | Report

Originally Posted by nightfire View Post

Code:

[91202.267547] WARNING: at /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()

didn't see it on my device yet. which max. frequency did you set?
it seems that the frequency is not a multiple of a certain factor.

nightfire | # 173 | 2010-04-07, 21:22 | Report

I allowed up to 1ghz; I'll see if I can figure out what's causing it.

On another note... I've done something incredibly dumb. I created an infinite loop in a script under /etc/event.d.... with predictable results.

I'm trying to build a kernel with init=/bin/sh right now.

Edit: nevermind.. whew. The kernel I flashed didn't enable console (missing something in the config), but for some inexplicable reason, booted all the way into X. Won't do that again.

Edit 2: It appears the kernel message is a warning generated by this code block:

Code:

                freqsel = _omap3_dpll_compute_freqsel(clk, dd->last_rounded_n);
                if (!freqsel)
                        WARN_ON(1);

Later in the file it refers to memory timing in a comment:

Code:

 * CORE DPLL (DPLL3) rate programming functions
 *
 * These call into SRAM code to do the actual CM writes, since the SDRAM
 * is clocked from DPLL3.

I wonder if they're related. I'm getting this at 950mhz now.

Last edited by nightfire; 2010-04-07 at 22:09.

The Following User Says Thank You to nightfire For This Useful Post:
egoshin

Fox5 | # 174 | 2010-04-08, 02:47 | Report

For those who have a debian image installed:
There's a stress testing application in the repos called stress. You can run it from within lxde using a terminal.

Not sure what it outputs upon failure, I haven't attempted to overclock my n900 yet. Still, it might be useful for stress testing all these overclocks.

titan | # 175 | 2010-04-08, 12:01 | Report

qwerty12 seems to have found a workaround for the problem that a phone call would reset
the max. freq to 600Mhz
http://talk.maemo.org/showpost.php?p...postcount=1722

The Following User Says Thank You to titan For This Useful Post:
iKneaDough

titan | # 176 | 2010-04-08, 17:29 | Report

Originally Posted by titan View Post

this probably the dsme daemon setting it to the values in /etc/pmconfig.
so the only way to fix it permanently is to change the file.

this is my workaround (will probably be included in the next version of the kernel)
http://talk.maemo.org/showpost.php?p...postcount=1765

The Following User Says Thank You to titan For This Useful Post:
iKneaDough

craftyguy | # 177 | 2010-04-09, 02:07 | Report

Titan:
Have you given any thought of working in the undervolting capabilities mentioned in the (massive) OC thread?

The Following User Says Thank You to craftyguy For This Useful Post:
iKneaDough

smoku | # 178 | 2010-04-09, 05:26 | Report

Originally Posted by titan View Post

INSTALLATION:
0. make the extras-testing catalogue is enabled
1. install the package "kernel-flasher-maemo" from App manager (section System) or using apt-get
2. reboot and enjoy.

Why don't you add "XB-Maemo-Flags: reboot" line to debian/control file, to do step 2 automatically after installation?

mdengler | # 179 | 2010-04-09, 07:14 | Report

Originally Posted by smoku View Post

Why don't you add "XB-Maemo-Flags: reboot" line to debian/control file, to do step 2 automatically after installation?

Please don't do this unless the reboot is optional and is not forced upon the user.

It's not at all the thing to do after installing a kernel.

smoku | # 180 | 2010-04-09, 07:50 | Report

Originally Posted by mdengler View Post

Please don't do this unless the reboot is optional and is not forced upon the user.

It's not optional. The just installed new kernel is not active until you reboot.