Date: Mon, 05 Mar 2007 09:52:04 +0100 From: Stefan Ehmann <shoesoft@gmx.net> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-acpi@FreeBSD.org Subject: Re: notebook freezes Message-ID: <1173084724.1850.3.camel@localhost> In-Reply-To: <20070305142926.O2780@besplex.bde.org> References: <200703011612.07110.shoesoft@gmx.net> <20070305004000.B17935@delplex.bde.org> <45EB28A1.5010803@root.org> <200703042242.58748.shoesoft@gmx.net> <20070305142926.O2780@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2007-03-05 at 15:21 +1100, Bruce Evans wrote:
> On Sun, 4 Mar 2007, Stefan Ehmann wrote:
> > Oops, seems I somehow screwed up Bruce's patch on first try (pmtimer was
> > already in my config). Probably the aftermath of the lunar eclipse :)
> >
> > On my second try, timer_restore really gets called and it also fixes my
> > problem.
>
> Could you add some RTC accesses to determine exactly what state is
> inconsistent? Something like the following:
>
> cur_rtc_reg = inb(IO_RTC); /* Sloppy locking. */
> printf("cur_rtc_reg = %02x, rtc_reg = %02x\n", cur_rtc_reg, rtc_reg);
> rtc_reg = -1;
> cur_rtc_statusa = rtcin(RTC_STATUSA);
> printf(...);
> cur_rtc_statusb = rtcin(RTC_STATUSB);
> printf(...);
>
Putting this on top of rtc_resume, I get this on resume (all values are
hexadecimal):
cur_rtc_reg = ff, rtc_reg = 0c
cur_rtc_statusa = 29
cur_rtc_statusb = 42
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1173084724.1850.3.camel>