Comment 17 for bug 574137

Just to clear the air a bit.... and make sure that I am not misleading anyone with false impressions.... (often the case)...

I took my Toshiba nb305 and wiped the Ubuntu partition and reinstalled lucid 10.04 from a USB key as previously. I tried the sound by turning on the system sound (Ubuntu), opening a terminal window and holding down the back arrow at the CLI prompt. The sound is fine.

Now I
1) sudo gedit /etc/default/grub
2) Change: GRUB_CMDLINE_LINUX_DEFAULT="splash nohz=off highres=off"
3) save and sudo update-grub

I have to do this to get the machine to boot quickly and to suspend/re-awaken when I close/open the lid. I cannot change the SATA BIOS parameter to compatibility from AHCI as I am dual booting with Windows 7 and using compatibility instead of AHCI craps up my Windows partition.

But here is the catch 22. After putting nohz=off and highres=off on the GRUB command line, the sound no longer works!!!! It appears to have had nothing to do with Twinkle installation (see messages above). If I remove the highres=off from the command line, the sound becomes normal.... but then I can't recover from suspend.

So.... What do the nohz=off and highres=off parameters do? Is highres=off turning off high resolution timers? Why does the sound get restored to normal when I shut off pulseaudio? Can I compile pulseaudio in a way such that it is not susceptible to these high resolution timer issues?