Date: Tue, 1 May 2001 14:28:01 -0400 (EDT) From: User Ipt Ian Patrick Thomas <ipthomas_77@yahoo.com> To: bartequi@neomedia.it (Salvo Bartolotta) Cc: freebsd-questions@freebsd.org Subject: Re: sio overflows Message-ID: <200105011828.OAA01714@scarlet.my.domain> In-Reply-To: <988662237.3aedc9dd92730@webmail.neomedia.it> from Salvo Bartolotta at "Apr 30, 2001 10:23:57 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Operating System: FreeBSD X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I don't have a work around but I get sio overflows after coming back from a suspend using apm -Z and zzz. I'm running 3.2 RELEASE right now with no X of any kind installed as of yet. I too have a Matrox G400 32MB and mine is an AGP(not sure if that is relevant). The problem with this card seems to have deeper roots than XFree because it works on Linux(although I have not used apm at all on Linux). Maybe a bug report needs to be sent or someone can point me in the right direction on where the problem may lie. I only have Java programming experience but am not afraid to learn C or assembly if that is what it takes. Ian As told by, Salvo Bartolotta [Charset ISO-8859-1 unsupported, filtering to ASCII...] > [ redirected to -questions, the issue being far more general ] > > > There is a known problem with serial > > I/O and version 4 of XFree86 -- though this problem doesn't seem to > > exist with the XFree86 version (3.3.6) that is included by default in > > FreeBSD. If you are using XFree86-4 and aren't willing to go back to > > version 3.3.6, there may be a workaround for the serial I/O problem; > > go to http://www.FreeBSD.org/cgi/query-pr.cgi and look up PR #26261 > > for more details. > > > > I have also been experiencing the problem since I switched to XFree86-4 -- > several days ago. This is a 4.3-RELEASE machine. > > Relevant hardware: sio type16550A; Matrox G400 32MB 300MHz; > Relevant software: XFree86-4.0.3_3 (DRI enabled); KDE2 (built on 16 Apr 2001); > How to repeat: while wget'ing files, launch KDE2 and Konqueror; next, drag its window > to and fro; finally, switch to the console. A number of "silo overflow" messages will have > been displayed. > > The workaround you mention in PR 26261 doesn't function for me. I specified both > options -- just to be more conservative -- but the problem is still there. As the > following couple of logs show, the two options ARE understood; nevertheless, I can > still see "silo overflow" messages, as before (ie under the same or similar conditions), > with no significant change in their "rate" (if I may say so). > > > With options (ie features disabled): > > 221 10:15pm /var/log >====> grep -i -A 12 "Acceleration architecture" XFree86.1.log > (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) > Screen to screen bit blits > 8x8 mono pattern filled rectangles > 8x8 mono pattern filled trapezoids > Screen to Screen color expansion > Solid Lines > Dashed Lines > Scanline Image Writes > Offscreen Pixmaps > Driver provided FillMono8x8PatternRects replacement > Setting up tile and stipple cache: > 20 128x128 slots > 4 256x256 slots > > > > Without options (ie features enabled): > > 222 10:16pm /var/log >====> grep -i -A 15 "Acceleration architecture" XFree86.2.log > (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) > Screen to screen bit blits > Solid filled rectangles > Solid filled trapezoids > 8x8 mono pattern filled rectangles > 8x8 mono pattern filled trapezoids > Indirect CPU to Screen color expansion > Screen to Screen color expansion > Solid Lines > Dashed Lines > Scanline Image Writes > Offscreen Pixmaps > Driver provided FillMono8x8PatternRects replacement > Setting up tile and stipple cache: > 20 128x128 slots > 4 256x256 slots > > > The problem appears to be X-related; in particular, it seems to be dependent on > hardware acceleration, but the relation is not quite obvious (to me). > > Q0) Should I bloat^H^H^H^Hinclude the above information in PR 26261? :-) > Q1) Has anyone with the same hardware found a workaround? > > TIA, > Salvo > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -- Have blue screens given you the blues, go to www.freebsd.org for the cure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105011828.OAA01714>