>-----Original Message-----It depends on whether we are HPET is being force detected based on the chipset or whether it was exported by the BIOS in ACPI table. If it was force enabled and above patch is having any effect, then you should see a message like In any case, off late there seems to be quite a few breakages that are related to HPET/timer interrupts. One of them was on a system which has HPET being exported by BIOS http://bugzilla.kernel.org/show_bug.cgi?id=10409 And the other one where we are force enabling based on chipset http://bugzilla.kernel.org/show_bug.cgi?id=10561 And then we have hangs once in a while reports by you, Roman and Mark here http://bugzilla.kernel.org/show_bug.cgi?id=10377 http://bugzilla.kernel.org/show_bug.cgi?id=10117 Thanks, Venki --
| David Miller | [GIT]: Networking |
| Linus Torvalds | Linux 2.6.26-rc4 |
| Fred . | Please add ZFS support (from GPL sources) |
| Greg KH | Linux 2.6.25.10 |
git: | |
| Alexander Gladysh | [Q] Encrypted GIT? |
| Kevin Leung | Edit log message after commit |
| Pietro Mascagni | GIT vs Other: Need argument |
| Michael Hendricks | removing content from git history |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Edwin Eyan Moragas | poll(2) vs kqueue(2) performance |
| Didier Wiroth | win32-codecs, avi and amd64 question |
| Daniel Ouellet | identifying sparse files and get ride of them trick available? |
| Daniel Brewer | Re: fsync performance hit on 1.6.1 |
| Hubert Feyrer | Compressed vnd handling tested successfully |
| Elad Efrat | Integrating securelevel and kauth(9) |
| YAMAMOTO Takashi | yamt-km branch |
