Date: Thu, 10 Feb 2005 18:34:18 -0500 From: Skip Ford <skip.ford@verizon.net> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: Jonathan Fosburgh <syjef@mdanderson.org> Subject: Re: Console freeze but still alive Message-ID: <20050210233418.GA683@lucy.pool-70-104-70-104.pskn.east.verizon.net> In-Reply-To: <200502102216.ab00205@salmon.maths.tcd.ie> References: <20050210210002.GA679@lucy.pool-70-104-70-104.pskn.east.verizon.net> <200502102216.ab00205@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Dowse wrote: > In message <20050210210002.GA679@lucy.pool-70-104-70-104.pskn.east.verizon.net> > , Skip Ford writes: >>Ian Dowse wrote: >>> FYI, I saw something similar once when I was testing my recent >>> callout changes, but I haven't seen it happen since. If the problem >>> did just appear around Sunday/Monday then I guess it could be >>> related... >> >>Yes, reverting your callout changes fixes the problem for me. >> >>In my case, with your changes the console worked fine unless I >>started X. When switching from or exiting X, the screen would >>stay blank. The shell still works at that point, I just couldn't >>see it. >> >>Changing video modes with vidcontrol didn't help. My startup >>scripts do change the video mode for all screens. I don't use >>moused at all FWIW. > > Thanks for the information. Could you try the following patch? It's > probably unlikely to help, but is the only potential issue I've > spotted so far. I think it worked but now I can't be sure. The screen behaves correctly when booting with your patch, but now it also seems to be working correctly without it. All of a sudden, I can't get any kernel to behave incorrectly, even though it did that consistenly over the last few days. -- Skip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050210233418.GA683>