Just so you all know (the list included) how I have fixed my silo
overflow problem which occurred while running xmame (and after I quit
until I restarted the X server)
I have found the problem doesn't occur if I remove the following lines
from the shell script I use to start xmame:
Just so you all know (the list included) how I have fixed my silo
overflow problem which occurred while running xmame (and after I quit
until I restarted the X server)
I have found the problem doesn't occur if I remove the following lines
from the shell script I use to start xmame:
I mailed a simple way to reproduce the serious brokeness of the
serial port driver on my system and no one responds.
What does this mean ?
Does core know that sio is seriously broken and doesn't want to
admit it ? [dont take that comment too seriously please].
What am I supposed to think ?
I mailed a simple way to reproduce the serious brokeness of the
serial port driver on my system and no one responds.
What does this mean ?
It means that nobody is probably willing to go bring up a MAME
environment just to test this. You need to isolate it to a more
minimal test case if you
Bruce said, in his own quite way, that somebody had broken fast
interrupts as part of newbus, and that is the end of that story.
Poul-Henning
In message 9.926181...@zippy.cdrom.com, Jordan K. Hubbard writes:
I mailed a simple way to reproduce the serious brokeness of the
serial port
On Sat, 8 May 1999, Jordan K. Hubbard wrote:
I mailed a simple way to reproduce the serious brokeness of the
serial port driver on my system and no one responds.
What does this mean ?
It means that nobody is probably willing to go bring up a MAME
environment just to test this. You
MAME is a great piece of software, and in and of itself entirely legal; what
problem do you have with it?
I'm not talking about MAME, go read the message again.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
As far as I can tell, this is unrelated to newbus as the same actions
would trigger this problem before and after newbus.
I have been seeing this problem for many months (maybe years - but I've
only recently identified a set of actions to reproduce it every time).
The wierd thing is that I can
*** STOP PRESS *** I have just confirmed that restarting the X server
is enough to fix the problem. So my apologies to Bruce, -CURRENT
and the whole FreeBSD community in general for blaming sio.
For the benefit of David Dawes, I'll quickly restate the problem:
Running xmame (from the
On Sun, May 09, 1999 at 12:39:56PM +0930, Matthew Thyer wrote:
*** STOP PRESS *** I have just confirmed that restarting the X server
is enough to fix the problem. So my apologies to Bruce, -CURRENT
and the whole FreeBSD community in general for blaming sio.
For the benefit of David
10 matches
Mail list logo
