From owner-freebsd-questions@FreeBSD.ORG Sat May 20 02:06:59 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F2216A422 for ; Sat, 20 May 2006 02:06:59 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.19.101.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD4C143D45 for ; Sat, 20 May 2006 02:06:58 +0000 (GMT) (envelope-from hugo@barafranca.com) Received: from localhost (localhost [127.0.0.1]) by mail.barafranca.com (Postfix) with ESMTP id 97D6DC3904; Sat, 20 May 2006 02:16:26 +0000 (UTC) Received: from mail.barafranca.com ([67.19.101.164]) by localhost (mail.barafranca.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00978-08; Sat, 20 May 2006 02:16:24 +0000 (UTC) Received: from [192.168.0.1] (unknown [81.84.174.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTP id 93936C389B; Sat, 20 May 2006 02:16:18 +0000 (UTC) Message-ID: <446E79C3.6010105@barafranca.com> Date: Sat, 20 May 2006 03:06:59 +0100 From: Hugo Silva User-Agent: Thunderbird 1.5.0.2 (X11/20060516) MIME-Version: 1.0 To: jekillen , freebsd-questions@freebsd.org References: <446DF9AE.8030002@barafranca.com> <6e214f4181bcbf37aa8c06cf9094c601@prodigy.net> In-Reply-To: <6e214f4181bcbf37aa8c06cf9094c601@prodigy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at barafranca.com Cc: Subject: Re: A really really weird problem with FreeBSD 6.. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 02:06:59 -0000 jekillen wrote: > > On May 19, 2006, at 10:00 AM, Hugo Silva wrote: > >> Hi list, >> >> I've been using FreeBSD on the desktop for several years now without >> any major problems. However, as of lately, I've been running into a >> very annoying problem. I'll try to explain: >> >> I play some OpenGL games on FreeBSD and have always played them >> without trouble. However, now I can't play my game of election >> (Wolfenstein: Enemy Territory) for more than 20 or 30 minutes. The >> same thing is happening over and over (and this is the weird part): >> >> The game will stop responding to most keys, and the ones that do >> respond, output rubbish characters. The mouse dies. I can >> CTRL-ALT-F1, login, and kill the game - the keyboard works on the >> console! >> >> Then I get back to KDE (CTRL-ALT-F2). The keyboard is useless at this >> point, as typing something will result in something else. The mouse >> moves, but I can't maximise windows (seems to ignore double click) >> and stuff. CTRL-ALT-BACKSPACE and logging in again solves the problem. >> >> Now, the only thing that I've changed in the last month was a new >> piece of hardware - a Logitech G5 mouse (connected via USB). After >> giving it some thought, this problem started a few days after I >> purchased the mouse. I can't see how this could be related to what is >> happening with me, but it's the only thing I remind changing. >> >> I was running 6.0-RELEASE-p5, and have upgraded to 6.1-RELEASE and >> xorg-6.9.0, kde-3.5.1, in the hopes that it would probably fix this. >> Unfortunately, the situation remains. >> >> Has anyone experienced a similar problem at all ? I didn't even try >> google as I have no idea of what I'm after.. > > Sounds like some kind of buffer overrun problem, some memory > allocation problem in the driver(?) > JK I thought about something like this too, but what I can't explain is why it only started happening when I got the new mouse (and most likely after the "usb0: host controller process error" error, altough I can't say for sure - and if this was the cause, howcome it persists across reboots? I never got the error anymore (ok.. maybe 1 time).). There isn't a special driver for this mouse, and the previous one was also detected as ums0 (a Logitech MX 700). I am 100% sure that I didn't touch any configuration at all, anywhere, when this started to happen. Thoughts, ideas, maybe someone who's been through the same, altough I find it highly unlikely ? >> >> >> >> Some random info: >> nvidia0: port 0xe800-0xe87f mem >> 0xcf000000-0xcfffffff,0xd0000000-0xdfffffff,0xce000000-0xceffffff irq >> 16 at device 0.0 on pci4 >> >> ums0: Logitech USB Gaming Mouse, rev 2.00/46.00, addr 2, iclass 3/1 >> uhid0: Logitech USB Gaming Mouse, rev 2.00/46.00, addr 2, iclass 3/1 >> >> --> I cannot remember exactly if this problem only occured after this: >> usb0: host controller process error >> (happened a few weeks ago for the first time) >> ^^ My mouse died during a gaming session, and after some >> investigation, I found that error message. Restarting the computer >> was the only way I found to get USB support functional again. I'm not >> sure, but it could have started happening ONLY after I experienced >> this error for the first time. >> >> >> >> >> That's all, I guess. Let me know if you have some clues.. >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >