On Tue, 2006-08-01 at 19:10 +0200, Andi Kleen wrote: > > I had some faith in this patch , but this just enable boot parameter > > notsc (which I already use). And "just" disable tsc don't solve all > the > > problems. > > What problems do you have? > Hi Andi , if I boot without notsc , I have many lost timer tickets. if I boot with notsc , I have,at begging, a few lost timer ticket, and after some stress usb modem I got uhci_hcd 0000:00:10.1: host controller process error, something bad happened! uhci_hcd 0000:00:10.1: host controller halted, very bad! uhci_hcd 0000:00:10.1: HC died; cleaning up usb 3-2: USB disconnect, address 2 Thanks for your reply -- Sérgio M. B.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Follow-Ups:
- References:
- [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- From: "Andi Kleen" <[email protected]>
- Re: [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- From: Sergio Monteiro Basto <[email protected]>
- Re: [discuss] Re: [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- From: Andi Kleen <[email protected]>
- [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- Prev by Date: Re: [PATCH 7 of 13] Make __FIXADDR_TOP variable to allow it to make space for a hypervisor
- Next by Date: Re: tickle NMI watchdog on serial output.
- Previous by thread: Re: [discuss] Re: [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- Next by thread: Re: [discuss] Re: [PATCH for 2.6.18] [2/8] x86_64: On Intel systems when CPU has C3 don't use TSC
- Index(es):
 |