看板 FB_hackers 關於我們 聯絡資訊
On Sat, 2014-06-07 at 19:04 +0300, Vladislav Prodan wrote: > > > --- Original message --- > From: "Dutch Ingraham" <stoa@gmx.us> > Date: 7 June 2014, 18:33:12 > > > > > > Thanks for the response. > > > > The output you requested: > > > > kern.eventtimer.choice: HPET1 (440) HPET2 (440) HPET3 (440) HPET4 (440) > > HPET5 (440) HPET6 (440) LAPIC (400) i8254 (100) RTC (0) > > > > kern.eventtimer.choice: HPET (did not specify 1, 2, etc.) > > > > I also changed the type of timer to LAPIC and rebooted; there was no > > appreciable change in the interrupt activity. > > After reboot what became timer? :) > > You can change the timer "on the fly", without rebooting the system. > > If LAPIC does not help, then try other timers. > > > -- > Vladislav V. Prodan > System & Network Administrator > support.od.ua > It's unclear to me why you are hung up on the idea of changing timers when the misbehaving interrupt is unshared and used only by a USB controller and there's no evidence of any kind that a timer is involved. -- Ian _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"