Re: nvidia drivers mutex lock

2017-06-06 Thread blubee blubeeme 
This is getting out of hand. I can't even keep x going for ten minutes
sometimes.
I've tested all the suggestions in this thread and they just don't work.

I have put out a print of sysctl hw. here : https://paste2.org/

With this CPU: hw.model: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
The bios on this laptop I can either set graphics to discrete or mshybrid.

I've tried in the past to disable discrete and run mshybrid but that always
comes up with 0 screens found. Even just doing Xorg -configure.

Anyone have some tips on disabling nvidia drivers, running this cpu with
igpu for a while?

Best,
Owen

On Sun, Jun 4, 2017, 18:11 blubee blubeeme  wrote:

> Thanks a lot! I'll give it a shot in a bit.
>
> Best,
> Owen
>
> On Sun, Jun 4, 2017, 16:59 Tomoaki AOKI  wrote:
>
>> Yes. FreeBSD patches in x11/nvidia-drivers/files are applied as usual.
>>
>> But beware! Sometimes upstream changes make any of FreeBSD patches not
>> applicable (incorporating any of these, incompatible modifies, ...).
>>
>> For 381.22, current patchset applies and builds fine for me.
>>
>>
>> On Sun, 04 Jun 2017 08:04:50 +
>> blubee blubeeme  wrote:
>>
>> > I'm running with svn and I build by make.
>> > If in use these steps, the BSD related patches will be applied, etc?
>> >
>> > Best,
>> > Owen
>> >
>> > On Sun, Jun 4, 2017, 15:53 Tomoaki AOKI 
>> wrote:
>> >
>> > > Hi.
>> > >
>> > > Not in ports tree, but easily overridden by adding
>> > >
>> > >   DISTVERSION=381.22 -DNO_CHECKSUM
>> > >
>> > > on make command line. Makefile of x11/nvidia-driver has a mechanism
>> > > to do so for someone requires newer version (newer GPU support, etc.).
>> > >
>> > > If you're using portupgrade,
>> > >
>> > >   portupgrade -m 'DISTVERSION=381.22 -DNO_CHECKSUM' -f
>> x11/nvidia-driver
>> > >
>> > > would do the same.
>> > >
>> > > If you installed it via pkg, there's no way to try. :-(
>> > > (As it's pre-built.)
>> > >
>> > >
>> > > On Sun, 04 Jun 2017 07:04:01 +
>> > > blubee blubeeme  wrote:
>> > >
>> > > > Hi @tomoaki
>> > > > Is that version of nvidia drivers currently in the ports tree? I
>> just
>> > > > checked but it seems not to be.
>> > > >
>> > > > @jeffrey
>> > > > I just generated a new xorg based on the force composition setting.
>> I
>> > > > merged it with my previous xorg I'll reboot, see if it gives better
>> > > > performance.
>> > > >
>> > > > It seems like my system is locking up more frequently now. Sometimes
>> > > right
>> > > > after a reboot the system, the screen locks and it's reboot and
>> pray.
>> > > >
>> > > > Best,
>> > > > Owen
>> > > >
>> > > > On Sat, Jun 3, 2017, 21:59 Jeffrey Bouquet <
>> jeffreybouq...@yahoo.com>
>> > > wrote:
>> > > >
>> > > > > SOME LINES BOTTOM POSTED, SEE...
>> > > > > 
>> > > > > On Fri, 6/2/17, Tomoaki AOKI  wrote:
>> > > > >
>> > > > >  Subject: Re: nvidia drivers mutex lock
>> > > > >  To: freebsd-current@freebsd.org
>> > > > >  Cc: "Jeffrey Bouquet" , "blubee
>> blubeeme" <
>> > > > > gurenc...@gmail.com>
>> > > > >  Date: Friday, June 2, 2017, 11:25 PM
>> > > > >
>> > > > >  Hi.
>> > > > >  Version
>> > > > >  381.22 (5 days newer than 375.66) of the driver states...
>> > > > >  [1]
>> > > > >
>> > > > >   Fixed hangs and
>> > > > >  crashes that could occur when an OpenGL context is
>> > > > >   created while the system is out of available
>> > > > >  memory.
>> > > > >
>> > > > >  Can this be related
>> > > > >  with your hang?
>> > > > >
>> > > > >  IMHO,
>> > > > >  possibly allocating new resource (using os.lock_mtx
>> > > > >  guard)
>> > > > >  without checking the lock first while
>> > > > >  previous request is waiting for
>> > > > >  another can
>> > > > >  cause the duplicated lock situation. And high memory
>> > > > >  pressure would easily cause the situation.
>> > > > >
>> > > > >   [1] http://www.nvidia.com/Download/driverResults.aspx/
>> 118527/en-us
>> > > > >
>> > > > >  Hope it helps.
>> > > > >
>> > > > >
>> > > > >  On Thu, 1 Jun
>> > > > >  2017 22:35:46 + (UTC)
>> > > > >  Jeffrey Bouquet
>> > > > >  
>> > > > >  wrote:
>> > > > >
>> > > > >  > I see the same
>> > > > >  message, upon load, ...
>> > > > >  >
>> > > > >  
>> > > > >  > On Thu, 6/1/17, blubee blubeeme 
>> > > > >  wrote:
>> > > > >  >
>> > > > >  >  Subject:
>> > > > >  nvidia drivers mutex lock
>> > > > >  >  To: freebsd-po...@freebsd.org,
>> > > > >  freebsd-current@freebsd.org
>> > > > >  >  Date: Thursday, June 1, 2017, 11:35
>> > > > >  AM
>> > > > >  >
>> > > > >  >  I'm
>> > > > >  running nvidia-drivers 375.66 with a GTX
>> > > > >  >  1070 on FreeBSD-Current
>> > > > >  >
>> > > > >  >  This problem
>> > > > >  just started happening
>> > > > >  >  recently but,
>> > > > >

Re: mount_smbfs gives error when stored crypted pw is used

2017-06-06 Thread Matthias Apitz 
El día martes, junio 06, 2017 a las 12:00:34p. m. +0200, Matthias Apitz 
escribió:

> 
> Hello,
> 
> At work I have to run FreeBSD (12-CURRENT, amd64) in vbox on Win7 host
> and used successful mount_smbfs to mount the hosts disk to FreeBSD. This
> worked fine until the last password change of the domain pw we have todo
> every 12 weeks or so.
> 
> Now the new crypted and stored pw from /etc/nsmb.conf is not accepted
> anymore. In detail, when I do:
> 
> ...

I looked into the sources in src/contrib/smbfs/lib/smb to understand how
the hashed pw is translated to clear text and wrote a small test pgm
which uses the same function of the /usr/lib/libsmb.so


$ cc -o smbpw smbpw.c -l smb

I now crypt a dummy pw with the following chars '1234567890-1-1234567':

$ smbutil crypt 1234567890-1-1234567
$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312

the resulting hash gives retranslated by smb_simpledecrypt():

$ ./smbpw 
smb_simpledecrypt(): hash: [$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312] gives 
clear [1234567890-1-12345]

i.e. the last two chars are missing.

$ cat smbpw.c

#include 

int
smb_simpledecrypt(char *dst, const char *src);

int main()
{

char *hash = "$$12a1a06767a6a5e4ebaa0b09b9af5e3eddfcd1312";
char clear[256];

clear[0] = '\0';

smb_simpledecrypt(clear, hash);

printf("smb_simpledecrypt(): hash: [%s] gives clear [%s]\n", hash, clear);

}

This seems to be an issue in the libsmb...

matthias



-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature

Re: freebsd-current Digest, Vol 711, Issue 2

2017-06-06 Thread Brandon Kastning 
FreeBSD 12-Current Community and Developers,

Regarding Issue #8; I too am having issues. I removed Firefox because it was 
randomly closing. And upon reinstall, I was receiving the python rust build 
error.

What is the proper syntax for a build with the "--format=ustar" ?

I apologize if I am participating incorrectly. As I am new to the community and 
unix.

Best Regards,

Brandon Kastning
AKA. StreetDancer (IRC & Forums)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

 Original Message 
Subject: freebsd-current Digest, Vol 711, Issue 2
Local Time: June 6, 2017 5:00 AM
UTC Time: June 6, 2017 12:00 PM
From: freebsd-current-requ...@freebsd.org
To: freebsd-current@freebsd.org

Send freebsd-current mailing list submissions to
freebsd-current@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freebsd.org/mailman/listinfo/freebsd-current
or, via email, send a message with subject or body 'help' to
freebsd-current-requ...@freebsd.org

You can reach the person managing the list at
freebsd-current-ow...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-current digest..."

Today's Topics:

1. Re: old syslog (jail) and new kernel = 100% CPU (Bryan Drewery)
2. Re: old syslog (jail) and new kernel = 100% CPU
(Ngie Cooper (yaneurabeya))
3. Re: Time to increase MAXPHYS? (Kenneth D. Merry)
4. Boot CURRENT without efi (Andy Neustadter)
5. Re: Boot CURRENT without efi (Allan Jude)
6. Re: Time to increase MAXPHYS? (Edward Tomasz Napiera?a)
7. Re: Boot CURRENT without efi (Toomas Soome)
8. Re: firefox/ rust failed to install on FreeBSD 12-CURRENT
(Jean-S?bastien P?dron)

--

Message: 1
Date: Mon, 5 Jun 2017 08:20:47 -0700
From: Bryan Drewery 
To: Alexander Leidinger 
Cc: curr...@freebsd.org
Subject: Re: old syslog (jail) and new kernel = 100% CPU
Message-ID: 
Content-Type: text/plain; charset="utf-8"

On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
>
> Quoting Bryan Drewery  (from Sun, 4 Jun 2017 14:38:07
> -0700):
>
>> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
>>> Hi,
>>>
>>> new kernel (surely r318877 and later) and old syslog in a jail = NOK.
>>>
>>
>> What branch and revision is the syslogd? From my understanding the bug
>> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
>> not released. If it was MFC'd we need to fix it before the 11.1 release.
>
> This was a syslogd from head for sure.
>
> So the issue was that for an intermediate period of time a bug was in
> syslogd in head which was causing this, and if I would have upgraded a
> system were the jail would have been head from before the or after the
> bug, then I wouldn't have noticed it?
>

Yes, that's my understanding. So it's ultimately a non-issue for
releases since it is just a temporary issue on head.

--
Regards,
Bryan Drewery

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: 


--

Message: 2
Date: Mon, 5 Jun 2017 08:53:50 -0700
From: "Ngie Cooper (yaneurabeya)" 
To: Bryan Drewery 
Cc: Alexander Leidinger , curr...@freebsd.org
Subject: Re: old syslog (jail) and new kernel = 100% CPU
Message-ID: <55114361-9212-49ae-a3ff-7691cadb2...@gmail.com>
Content-Type: text/plain; charset="utf-8"

> On Jun 5, 2017, at 08:20, Bryan Drewery  wrote:
>
> On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
>>
>> Quoting Bryan Drewery  (from Sun, 4 Jun 2017 14:38:07
>> -0700):
>>
>>> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
 Hi,

 new kernel (surely r318877 and later) and old syslog in a jail = NOK.

>>>
>>> What branch and revision is the syslogd? From my understanding the bug
>>> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
>>> not released. If it was MFC'd we need to fix it before the 11.1 release.
>>
>> This was a syslogd from head for sure.
>>
>> So the issue was that for an intermediate period of time a bug was in
>> syslogd in head which was causing this, and if I would have upgraded a
>> system were the jail would have been head from before the or after the
>> bug, then I wouldn't have noticed it?
>>
>
> Yes, that's my understanding. So it's ultimately a non-issue for
> releases since it is just a temporary issue on head.

Yes. syslogd was refactored on ^/head. Some of the refactoring caused the issue 
Alexander brought up. The changes were never backported though, so the concern 
you had in the previous message isn?t

Re: freebsd-current Digest, Vol 711, Issue 2

2017-06-06 Thread blubee blubeeme 
I was able to sort this out by installing rust from pkg. The pkg and ports
version was the same when I did it a lil while ago.

Try that, then running the Firefox build again.

Best,
Owen

On Tue, Jun 6, 2017, 20:18 Brandon Kastning 
wrote:

> FreeBSD 12-Current Community and Developers,
>
> Regarding Issue #8; I too am having issues. I removed Firefox because it
> was randomly closing. And upon reinstall, I was receiving the python rust
> build error.
>
> What is the proper syntax for a build with the "--format=ustar" ?
>
> I apologize if I am participating incorrectly. As I am new to the
> community and unix.
>
> Best Regards,
>
> Brandon Kastning
> AKA. StreetDancer (IRC & Forums)
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
>  Original Message 
> Subject: freebsd-current Digest, Vol 711, Issue 2
> Local Time: June 6, 2017 5:00 AM
> UTC Time: June 6, 2017 12:00 PM
> From: freebsd-current-requ...@freebsd.org
> To: freebsd-current@freebsd.org
>
> Send freebsd-current mailing list submissions to
> freebsd-current@freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> or, via email, send a message with subject or body 'help' to
> freebsd-current-requ...@freebsd.org
>
> You can reach the person managing the list at
> freebsd-current-ow...@freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-current digest..."
>
> Today's Topics:
>
> 1. Re: old syslog (jail) and new kernel = 100% CPU (Bryan Drewery)
> 2. Re: old syslog (jail) and new kernel = 100% CPU
> (Ngie Cooper (yaneurabeya))
> 3. Re: Time to increase MAXPHYS? (Kenneth D. Merry)
> 4. Boot CURRENT without efi (Andy Neustadter)
> 5. Re: Boot CURRENT without efi (Allan Jude)
> 6. Re: Time to increase MAXPHYS? (Edward Tomasz Napiera?a)
> 7. Re: Boot CURRENT without efi (Toomas Soome)
> 8. Re: firefox/ rust failed to install on FreeBSD 12-CURRENT
> (Jean-S?bastien P?dron)
>
> --
>
> Message: 1
> Date: Mon, 5 Jun 2017 08:20:47 -0700
> From: Bryan Drewery 
> To: Alexander Leidinger 
> Cc: curr...@freebsd.org
> Subject: Re: old syslog (jail) and new kernel = 100% CPU
> Message-ID: 
> Content-Type: text/plain; charset="utf-8"
>
> On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
> >
> > Quoting Bryan Drewery  (from Sun, 4 Jun 2017 14:38:07
> > -0700):
> >
> >> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
> >>> Hi,
> >>>
> >>> new kernel (surely r318877 and later) and old syslog in a jail = NOK.
> >>>
> >>
> >> What branch and revision is the syslogd? From my understanding the bug
> >> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
> >> not released. If it was MFC'd we need to fix it before the 11.1 release.
> >
> > This was a syslogd from head for sure.
> >
> > So the issue was that for an intermediate period of time a bug was in
> > syslogd in head which was causing this, and if I would have upgraded a
> > system were the jail would have been head from before the or after the
> > bug, then I wouldn't have noticed it?
> >
>
> Yes, that's my understanding. So it's ultimately a non-issue for
> releases since it is just a temporary issue on head.
>
> --
> Regards,
> Bryan Drewery
>
> -- next part --
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: OpenPGP digital signature
> URL: <
> http://lists.freebsd.org/pipermail/freebsd-current/attachments/20170605/6435eaef/attachment-0001.sig
> >
>
> --
>
> Message: 2
> Date: Mon, 5 Jun 2017 08:53:50 -0700
> From: "Ngie Cooper (yaneurabeya)" 
> To: Bryan Drewery 
> Cc: Alexander Leidinger , curr...@freebsd.org
> Subject: Re: old syslog (jail) and new kernel = 100% CPU
> Message-ID: <55114361-9212-49ae-a3ff-7691cadb2...@gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> > On Jun 5, 2017, at 08:20, Bryan Drewery  wrote:
> >
> > On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
> >>
> >> Quoting Bryan Drewery  (from Sun, 4 Jun 2017 14:38:07
> >> -0700):
> >>
> >>> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
>  Hi,
> 
>  new kernel (surely r318877 and later) and old syslog in a jail = NOK.
> 
> >>>
> >>> What branch and revision is the syslogd? From my understanding the bug
> >>> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
> >>> not released. If it was MFC'd we need to fix it before the 11.1
> release.
> >>
> >> This was a syslogd from head for sure.
> >>
> >> So the issue was that for an intermediate period of time a bug was in
>