Date: Thu, 29 Mar 2001 19:19:20 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: "Georg-W. Koltermann" <gwk@sgi.com> Cc: current@FreeBSD.ORG Subject: Re: lockup after resume Message-ID: <Pine.BSF.4.21.0103291912280.32700-100000@besplex.bde.org> In-Reply-To: <20010328212426.A32322@hunter.munich.sgi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Mar 2001, Georg-W. Koltermann wrote: > I am experiencing a strange lockup with -current as of about a week > ago: It will suspend and resume, but after the resume the console is > dead and the system hangs after a short while. > > When I type on the console after a resume, nothing is shown, neither > echo nor command output. If I break into DDB, the output suddenly > appears, just above the DDB prompt. I can continue to UNIX, type > another command, again nothing visible. Breaking into DDB again shows > what I typed, and the output. After a few round-trips of this sort > the system locks up solidly. > > If I'm in X (XFree86-4.0.2) after the resume, the system will respond > for a few seconds and then lock up. > > All this happens with the GENERIC kernel as well as my cardbus kernel. > > Should I assume the console needs resetting after the resume? How > could I try a reset? I can't find anything obvious in vidcontrol(1) > or kbdcontrol(1). Assume that the i8254 needs reinitializing. The console driver just uses timeouts for screen updates. Timeouts depend on the i8254 generating interrupts. When you break into ddb, the screen gets updated directly. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0103291912280.32700-100000>