On Wednesday 25 July 2007 07:33, Eric Sesterhenn / Snakebyte wrote:Maybe yes, maybe no. Note that these are just noise -- new code being verbose when looking for an optional feature. The fact that hitting the power button a bunch of times to make the system move along suggests some sort of missing interrupt problem -- most likely the timer itself. [ 13.868574] Probing IDE interface ide0... [ 387.279576] Clocksource tsc unstable (delta = 370195339890 ns) 5-minutes -- a long probe:-) does CONFIG_NO_HZ=n make a difference? does CONFIG_HIGH_RES_TIMERS=n make a difference? does "irqpoll" make any difference? does "notsc" make any difference? does "idle=poll" make any difference? cheers, -Len -
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Joerg Roedel | [PATCH 03/34] AMD IOMMU: add defines and structures for ACPI scanning code |
| Eric W. Biederman | [PATCH] powerpc pseries eeh: Convert to kthread API |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
