![]() | ||||||||||
Messages in this thread |
On Sunday 05 February 2006 03:02, Ed Sweetman wrote: [snip] > In any case it's been generally accepted that pm timer is suggested to > get around these errors, but i've been unable to use mine, there is no > config option in menuconfig/gconfig etc and my .config seems to show > that it's compiled in. Boot args like timer=pmtmr and just pmtmr and > having nothing have resulted in the same dmesg output , with no mention > of using the pm-timer. I know I used it in 2.6.14.3 and never had any > sync issues, my setup and config hasn't changed since then except for > the use of libata for pata. So how can i determine what's going on > here? Default or not, i'd like to get the pmtmr in use if it's what > works. On x86 (NOT x86-64), clock=pmtmr does what you want. -- Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2006-02-05 05:10 [from the cache] ©2003-2008 | ||||||||||