Freez and a reboot

[TheBlaze]

Re: Freez and a reboot

I changed all "maverick"-s to "lucid"-s in sources.list. That enabled me to get the "linux-headers-2.6.32-25-generic" package. That in turn enabled me to do a "sudo apt-get install --reinstall nvidia-current".

So, now I'm writing this from Kubuntu with kernel 2.6.32-25. No freezing.

But if I boot the 2.6.35-22 kernel, I still get "kernel panic" - freeze.

To recap:
kernel 2.6.32-25 - no freeze
kernel 2.6.35-22 - freeze

[dibl]

Re: Freez and a reboot

Nice move -- very creative!

Although there's no specific indication of what is behind the 2.6.35 freeze/crash, the fact that it takes some time continues to suggest a thermal issue, to me. Different kernels do perform differently on any given hardware, and it's not unheard of that a certain kernel induces some kind of problem on hardware that works OK with a previous kernel.

You could eliminate the possibility by installing the lm-sensors package, then run

sudo sensors-detect

and let it update your /etc/modules file. After a reboot into the 2.6.35 kernel, run

acpi -t

and let's see what it says. And again after 5 minutes ....

Another experiment that comes to mind is to make a Live CD with the 10.10 daily build ISO, and boot that. With no special video driver, just play around using the browser and playing music or whatever you normally do. If it doesn't crash, we'll know that it is something about your installed system, versus the generic Live CD.

[TheBlaze]

Re: Freez and a reboot

@dibl:
My temps are around 40 °C idle (writing this post, updating to KDE 4.5.2,..), and around 55 °C under mprime (8 threads). This shouldn't be an issue. I can try it with 2.6.35 kernel, but I doubt it's going to be any different. Especially as it also freezes in console mode.

[dibl]

Re: Freez and a reboot

The other thing you could try, when booted into the "freezing/crashing" kernel, is to open a Konsole window, run

htop

and then park the window on your screen where you can watch it. Possibly some process/package is running amok, and you'll be able to see it suck the CPU and/or memory dry.