Date: Wed, 3 Apr 2013 11:07:55 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Waitman Gobble <uzimac@da3m0n8t3r.com> Cc: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com>, current@freebsd.org Subject: Re: RE: rebooting nvidia + keyboard issues Message-ID: <CAJ-VmonhGrEo8qcyht_aaoKBuyUu72CmrE7e6Lj42PiT0EUMqQ@mail.gmail.com> In-Reply-To: <20130403175043.7303C36F4856@dx.burplex.com> References: <20130403175043.7303C36F4856@dx.burplex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, can you guys please ensure a PR is filed with all the information you've just included? the clang team would likely love to have this much information in a bug rep= ort. Thanks! adrian On 3 April 2013 10:50, Waitman Gobble <uzimac@da3m0n8t3r.com> wrote: > On Wed, 3 Apr 2013 10:35:47 +0100, "Thomas Sparrevohn" <Thomas.Sparrevohn= @btinternet.com> 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 wi= th >>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 reb= oot >>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 log= in. >>I would not say it's not working.. the keyboard functions fine until hitt= ing >>the login prompt. There are no errors and everything appears to be workin= g >>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 gene= rally everything else seems to be working. > > I noticed a previous message from a day or two ago regarding gcc and nvid= ia, 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 aro= und 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 > > > _______________________________________________ > 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= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonhGrEo8qcyht_aaoKBuyUu72CmrE7e6Lj42PiT0EUMqQ>