Re: lockup after resume
One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. Hmm, I might try that. BTW, last time I asked Warner about this his reply was (I paraphrase) it's not supposed to work, and if it ever worked for you it was out of sheer luck, which I find surprising. Me too, since it used to work on that same hardware. (A ThinkPad 600 was what I did the original suspend/resume work on during the FreeBSD 2.2 days.) Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
On Mon, Apr 09, 2001 at 11:10:54AM +0200, Dag-Erling Smorgrav wrote: Georg-W. Koltermann [EMAIL PROTECTED] writes: 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. I'm seeing this too on my laptop. Used to work fine, no longer does. I'll try the latest greatest and see if the problem goes away. DES Dag-Erling, I CVSuped twice since my initial report, and the problem is still there. On the other hand I have a report from David Wolfskill that suspend/resume works fine for him. a) Does suspend/resume now work for you? b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 with BIOS rev A12)? c) David, since it seems to work for you, what hardware/firmware do you have? One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
Date: Fri, 4 May 2001 14:39:12 +0200 From: Georg-W. Koltermann [EMAIL PROTECTED] I CVSuped twice since my initial report, and the problem is still there. On the other hand I have a report from David Wolfskill that suspend/resume works fine for him. Right. c) David, since it seems to work for you, what hardware/firmware do you have? It's similar to a Dell Inspiron 5000e (I suspect it's made by the same folks). http://www.catwhisker.org/~david/FreeBSD/laptop.html for more detail than folks are likely to want (though it does include a link to a floppy image that I used to update the BIOS; note that said BIOS claims to be for either my (type of) machine or a Dell Inspiron 5000e). One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. Curiouser and curiouser Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
Georg-W. Koltermann [EMAIL PROTECTED] writes: a) Does suspend/resume now work for you? No, but I haven't upgraded my kernel since right before Easter. b) What hardware/firmware do you have (mine is a DELL Inspiron 7500 with BIOS rev A12)? IBM ThinkPad 600E, don't remember the firmware revision but it's very recent. One surprising observation: If I disable APM in /boot/device.hints, my machine suspends and resumes JUST FINE. The BIOS alone seems to be able to suspend and awake the hardware behind FreeBSD's back. The system only hangs if FreeBSD is involved in the process. Hmm, I might try that. BTW, last time I asked Warner about this his reply was (I paraphrase) it's not supposed to work, and if it ever worked for you it was out of sheer luck, which I find surprising. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
On Thu, Mar 29, 2001 at 07:19:20PM +1000, Bruce Evans wrote: 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. I did some more debugging last night. I confirmed by a printf() that i8254_restore() actually *IS* being called during the resume. That routine is now in pmtimer.c, it used to be in apm.c in 4.2-R (and with 4.2 resume works fine on my laptop). I added an additional call to i8254_restore() to the end of apm_resume(), and I also called it directly from DDB--no effect. There must be some other problem, I guess. I figure there are a couple of laptop owners running current. Is suspend/resume working for all of you other guys, besides me and Dag-Erling? -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lockup after resume
"Georg-W. Koltermann" [EMAIL PROTECTED] writes: 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. I'm seeing this too on my laptop. Used to work fine, no longer does. I'll try the latest greatest and see if the problem goes away. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lockup after resume
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
