[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)




Requoted




Figaro wrote:
This is due to the clocksource set up. (Bug#412194: linux-image-2.6.18-3-k7: total system freeze after max. 10 minutes uptime).
Add boot option: clocksource=tsc


See below for GRUB /boot/grub/menu.lst

--------------snip------------------------------------------------ from 022507
Hello all,
I've done as Alexander has suggested:
added a boot option in /boot/grub/menu.lst
----snip---->
title        Debian GNU/Linux, kernel 2.6.18-4-k7
root        (hd0,0)
kernel /vmlinuz-2.6.18-4-k7 root=/dev/sda2 ro clocksource=tsc initrd /initrd.img-2.6.18-4-k7
savedefault
rebooted and:
># echo "tsc" > /sys/devices/system/clocksource/clocksource0/current_clocksource <
># cat  /sys/devices/system/clocksource/clocksource0/* <
jiffies tsc pit
tsc
We are up and running now (45min.). Alex. has been up for some hours (9+) using this method. So maybe others can use this and help us understand later the "why" of it.
Anyway, fingers crossed let us see........
matthew

Alexander Schories wrote:
Hello Steve,
Hello Steve,


uptime with "nosmp" so far: 57 min. Everything runs fine and smoothly. Of course overall system load is about 5 percent (average) to 20 percent (peak) higher than usual - man, i do love and miss smp.. :D

Just kidding, i can easily live happily either with "nosmp" or particularly with 2.6.17 for now. Maybe other affected users might agree to lower the initial severity to "important"?


But guess who appears on stage now again (dmesg log):

#Time: pit clocksource has been installed.
#...
#Real Time Clock Driver v1.12ac
#Generic RTC Driver v1.07

RTC is back for good!

This makes me so curios about the mysticals of linux time again:

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=734efb467b31e56c2f9430590a9aa867ecf3eea1

After reading, re-reading and hopefully understanding i will try to find a solution, why 2.6.18-k7 decides to use "Programmable Interval Timer" of 1981(!) instead of our even younger and trusted friend "rtc" or even the fancy "acpi_pm" ..

Once i find helpful information or even a solution, i will post it here.


Thank you very much again!


Alexander Schories
Tuebingen, Germany


Sure, it could be, but I don't know anything about the architecture of the
kernel's clocksource stuff.

Good luck,
--Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/



--To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org







Reply to: