Date: Thu, 3 May 2018 12:55:58 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: hpet vs suspend to ram Message-ID: <20180503095558.GJ6887@kib.kiev.ua> In-Reply-To: <8d3f5a6f-f2be-f2e1-18d5-f774f4909694@icyb.net.ua> References: <8d3f5a6f-f2be-f2e1-18d5-f774f4909694@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 03, 2018 at 11:40:24AM +0300, Andriy Gapon wrote: > > Just want to share a strange problem that I see on one system. > > If I use HPET as an eventtimer, then after a seemingly successful resume > the system starts to act weird. It becomes unresponsive for periods of > time, then it gets more normal, then it's sluggish, then unresponsive > again. After some time struggling the system finally locks up entirely. > > I see this problem both with FreeBSD and Linux (tested with Ubuntu 16 > and 17). > > If I use any other timer hardware, then everything is okay. > Also, if I switch to HPET after a resume, then it's okay too. > I tried uncommenting the code in acpi_hpet.c that disables the HPET > before suspend, but it didn't change anything. > > I suspect that the problem is with SMM code, but don't know how to check > it or whether it would make any difference. > I also tried disabling various devices (e.g. USB) through BIOS config, but that > also didn't help. Did you tried to clear comparators, besides disabling the HPET ? > > The system uses Asus M4A89GTD PRO motherboard. > > -- > Andriy Gapon > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180503095558.GJ6887>