Skip site navigation (1)Skip section navigation (2)
Date:      12 Nov 1998 11:57:00 +0100
From:      Thomas Gellekum <tg@ihf.rwth-aachen.de>
To:        Mike Smith <mike@smith.net.au>
Cc:        Peter Johnson <pljohnsn@uiuc.edu>, current@FreeBSD.ORG, x@suse.de
Subject:   Re: XFree86 nonstandard server / ELF compat problem
Message-ID:  <87u305p4ar.fsf@tibatong.ihf.rwth-aachen.de>
In-Reply-To: Mike Smith's message of "Wed, 11 Nov 1998 22:48:41 -0800"
References:  <199811120648.WAA08374@dingo.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith <mike@smith.net.au> writes:

> The symptoms you're seeing are typically indicative of an interrupt 
> storm - the driver is enabling interrupts on the card but there is no 
> handler for them.
> 
> This is most likely a bug in the server.

[...]

> > Amazingly, the server actually starts up and seems to run ok (window
> > manager, xterm prompts start, etc), but I immediately am almost flooded by
> > kernel messages "calcru: negative time of -48128 usec for pid 342 (xterm)"
> > [with the time/pid/name changing].  Exiting the X server returns me to text
> > mode prompt, but I continue getting the calcru messages.  If I try to run
> > top or do anything other than just list files, it seems, I get a nasty
> > message "cputime limit exceeded".  End up not being able to shutdown
> > (because every process dies with a whole bunch of calcru messsages followed
> > immediately by a cputime message) and need to reset.
> > 
> > Ugh.. now I _need_ XF86 3.3.3 so I can compile the whole darn thing as ELF!!
> > 
> > (note: I'm using the SuSe ELSA GLORIA server for FreeBSD 2.1.5--tried to
> > use the Linux ELF binary, with no success)
> > 
> > I got the same messages right after upgrading to ELF, so I
> > recompiled/reinstalled the XFree86 port (compiling as ELF).. didn't fix it
> > *sigh*
> > 
> > Regards,
> > Peter Johnson
> > locke@mcs.net

[...]

Just a ``me too'', Cc'd to x@suse.de. I've gone back to
XFCom_3DLabs-4.1-FreeBSD and all is well again after a reboot. The
4.31 version does not behave on 2.2.7-stable either (same symptoms as
above) and should probably be removed from the ftp sites.

tg


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?87u305p4ar.fsf>