Date: Fri, 06 Jan 2006 02:31:46 +0900 From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org> To: Dejan Lesjak <dejan.lesjak@ijs.si> Cc: freebsd-x11@freebsd.org Subject: Re: problem with starting xorg after upgrade Message-ID: <86mziad1j1.fsf@ra333.heimat.gr.jp> In-Reply-To: <200601051701.43891.dejan.lesjak@ijs.si> (Dejan Lesjak's message of "Thu, 5 Jan 2006 17:01:43 %2B0100") References: <20060104152624.GB15636@uws1.starlofashions.com> <20060105004418.GA34297@mail.scottro.net> <8664oyeq00.fsf@ra333.heimat.gr.jp> <200601051701.43891.dejan.lesjak@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> In <200601051701.43891.dejan.lesjak@ijs.si> >>>>> Dejan Lesjak <dejan.lesjak@ijs.si> wrote: > > Is it ok to send PR that "X kills my system, I cannot get any more > > information"? > Well... Without more information it will probably just stay there > and you would get a periodic "Is this still a problem with recent > release of X.Org/FreeBSD". Of cource, I know it. So, I cannot send PR. > Are there any messages about the problem in /var/log/messages? Did > you try to break to debugger at the time system froze? Unfortunately, I cannot do any operation when system froze. CTRL-ALT-ESC has no effect, and sending break signal from serial console ditto. When system froze, the keyboard connected to the pc98 is useless, in other word, offline. No LEDs turn on or off when pressing CAPS or KANA. So, CTRL-ALT-ESC is meaningless. And, on serial console which is cu on the next FreeBSD/i386 5.4-STABLE, pressing "~#" gets no response. In addition, there are no messages about the problem in /var/log/messages. What I can know is "system freezes". This is very difficult to solve or report. But I have the luck that X still works fine if I run it ONCE. OK, I'll try to press CTRL-ALT-ESC just before the system freezes next time. If possible. > > Oh, I recognized only one thing. /tmp/.X11-unix and /tmp/.XIM-unix > > are created just before system hangup, but /var/log/Xorg.0.log is > > not updated. > The directories should be there even since system startup. Is > your /etc/rc.d/cleartmp up to date? That is probably unrelated though. Because I removed them before system freeze. I agree that is unrelated to the problem. -- NAKAJI Hiroyuki
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86mziad1j1.fsf>