From owner-freebsd-current@FreeBSD.ORG Wed Apr 3 17:50:49 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 77CC12C4 for ; Wed, 3 Apr 2013 17:50:49 +0000 (UTC) (envelope-from daemon@dx.burplex.com) Received: from dx.burplex.com (dx.burplex.com [50.197.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 6759E2B1 for ; Wed, 3 Apr 2013 17:50:49 +0000 (UTC) Received: by dx.burplex.com (Postfix, from userid 1) id 7303C36F4856; Wed, 3 Apr 2013 10:50:43 -0700 (PDT) To: Subject: Re: RE: rebooting nvidia + keyboard issues From: Waitman Gobble X-UUID-HOR: 5c2f9e47-9c43-11e2-a35d-902b34a86bc3 Message-Id: <20130403175043.7303C36F4856@dx.burplex.com> Date: Wed, 3 Apr 2013 10:50:43 -0700 (PDT) Cc: Thomas Sparrevohn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 17:50:49 -0000 On Wed, 3 Apr 2013 10:35:47 +0100, "Thomas Sparrevohn" wrote: > >I have had the same problem - it seems like a "sysctl" call provokes a >overrun in a strlen call. It is not reproducible with a GENERIC kernel with >debugging in my case. However a simple workaround is to compile >nvidia-driver with gcc. > >-----Original Message----- >From: owner-freebsd-current@freebsd.org >[mailto:owner-freebsd-current@freebsd.org] On Behalf Of Waitman Gobble >Sent: 31 March 2013 08:25 >To: current@freebsd.org >Subject: rebooting nvidia + keyboard issues > >Hi, > >After updating my machine tonight with >> uname -a >FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248937: Sat Mar >30 21:53:14 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA >amd64 > >I noticed the machine rebooting randomly every 20 seconds to 5 minutes. >Disabling the nvidia driver seems to fix the problem, and I was able to >update after applying ports/177459 patch. The updated nvidia driver seems to >have solved the rebooting issue. (it could (also?) be related to linux.ko?) >If people are using the nvidia driver and are experiencing a constant reboot >issue, it might be good to pop in that patch ASAP. > >The problem I am noticing now is keyboard related. Booting to single user >mode, I cannot type anything at the login prompt with an attached USB >keyboard. However in single user mode a PS2 keyboard will allow me to login. >I would not say it's not working.. the keyboard functions fine until hitting >the login prompt. There are no errors and everything appears to be working >fine, however I cannot login. Numlock key lights on and off when pressed. > >Also, if I boot into multi user mode, I cannot type anything at the login >prompt when a PS2 keyboard is attached. But the USB keyboard will work in >mutli user mode. > >Thank you, > >-- >Waitman Gobble >San Jose California USA > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Thank you for the information, I'll give it a try and see what happens. I noticed two other ports that don't even seem to build with clang, but generally everything else seems to be working. I noticed a previous message from a day or two ago regarding gcc and nvidia, but I lost the message. I'm in the middle of moving my mail system to a 'more' horizontally based system, so it's kind of like building a boat around you while floating down a river. Anyhow, I read an article this morning about AMD opening up drivers, that sounds cool, going to check it out. -- Waitman Gobble San Jose California USA +1.5108307875