Interesting. Let's see if I have this straight? The current kernels are using dynamic ticks. nohz=off turns off dynamic ticks so we get regular ticks as in the old OSs and the scheduler will regularly get asked to check to see what jobs should be run and prevent one process from hogging the CPUs. I guess highres=off must just reduce the rate that the scheduler is poked to check for jobs waiting. I am not sure how this fits with nohpet which also will cure the boot problem but not the resume from hibernate hang. I guess nohpet means no high precision event timer so maybe this supports your ideas of this being a timer problem. Indeed, I see another mention of this (see message 5 on http://www.linuxquestions.org/questions/fedora-installation-39/fc-10-my- installation-hangs-after-the-first-white-progress-bar-696298/) on a completely different machine where the user says that tapping the left SHIFT key will help bypass the problems with the interrupt bug.... and that adding nohpet to the kernel line will help cure his problem.
I am not sure why changing the BIOS disk parameter from ahci to compatibility cures the problem as well (although this screws up access to your windows partition if you still have it). What we do know is that we don't want to use nohz=off highres=off as it makes the machine run hot, screws up pulse audio and reduces the time the machine will run on the battery. I continue to use bootchart as it still seems to boot faster than tapping the left SHIFT key. But both will work. We really need to get a developer that understands all of this interested in this problem. -- Disk driver problems on Toshiba NB305Netbook https://bugs.launchpad.net/bugs/601986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
