On Fri, May 10, 2019 at 03:30:41PM +0100, Oriol Demaria wrote:
> Actually both things fix the issue. Seems to be better just changing the
> timecounter, rather than running on just one core. I noticed by the way that
> when I run sysupgrade, or upgrade as before the SP kernel is the one
> installed. And I have to change manually and reboot. Also I noticed that
> when I run dmesg both kernels output data. Can't recall if this was the
> usual behavior.
> 
> So, are there any advise against running with acpihpet0 timecounter instead
> of tsc? I'm attaching my dmesg.

On AMD hardware, it's best to use acpihpet0 as your timecounter.

+--+
Carlos

> 
> timecounters:
> 
> sysctl kern.timecounter
> kern.timecounter.tick=1
> kern.timecounter.timestepwarnings=0
> kern.timecounter.hardware=acpihpet0
> kern.timecounter.choice=i8254(0) tsc(2000) acpihpet0(1000) acpitimer0(1000)
> dummy(-1000000)
> 
> Regards,
> 
> ---
> Oriol Demaria
> 2FFED630C16E4FF8
> 
> On 10/05/2019 01:15, Jonathan Gray wrote:
> > On Thu, May 09, 2019 at 04:17:40PM +0100, Oriol Demaria wrote:
> > > I have this laptop and I'm having issues with this laptop. Wireless
> > > has to
> > > be replaced and basically have to wait till the graphics card is
> > > properly
> > > supported, right now is running X with the UEFI framebuffer. So this
> > > issues
> > > are expected.
> > > 
> > > But I'm having a very annoying bug on X. The mouse stops working,
> > > specially
> > > Firefox seems to be a problem, but other apps too (perhaps I notice
> > > more
> > > here as others I mainly use the keyboard). When I run xprop to try
> > > to figure
> > > out something I get the error "Can't grab the mouse" and won't run.
> > > Seems
> > > that some event holds the mouse, and prevents you from "clicking".
> > > 
> > > Changed the touchpad to synaptics to see if it makes difference,
> > > seems to
> > > improve a bit, but still the problem comes back. The other mouse
> > > devices are
> > > using ws driver. Has someone got a workaround for this? Similar
> > > experience?
> > 
> > Try a non-mp kernel or sysctl kern.timecounter.hardware=acpihpet0

Reply via email to