Date: Sat, 3 Jun 2017 13:55:12 +0000 (UTC) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: <freebsd-current@freebsd.org>, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: Jeffrey Bouquet <jeffreybouquet@yahoo.com>, blubee blubeeme <gurenchan@gmail.com> Subject: Re: nvidia drivers mutex lock Message-ID: <1100140349.1166835.1496498112171@mail.yahoo.com> References: <1100140349.1166835.1496498112171.ref@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
SOME LINES BOTTOM POSTED, SEE... -------------------------------------------- On Fri, 6/2/17, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: Subject: Re: nvidia drivers mutex lock To: freebsd-current@freebsd.org Cc: "Jeffrey Bouquet" <jeffreybouquet@yahoo.com>, "blubee blubeeme" <guren= chan@gmail.com> Date: Friday, June 2, 2017, 11:25 PM =20 Hi. Version 381.22 (5 days newer than 375.66) of the driver states... [1] =20 Fixed hangs and crashes that could occur when an OpenGL context is created while the system is out of available memory. =20 Can this be related with your hang? =20 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. =20 [1] http://www.nvidia.com/Download/driverResults.aspx/118527/en-us =20 Hope it helps. =20 =20 On Thu, 1 Jun 2017 22:35:46 +0000 (UTC) Jeffrey Bouquet <jeffreybouquet@yahoo.com> wrote: =20 > I see the same message, upon load, ... > -------------------------------------------- > On Thu, 6/1/17, blubee blubeeme <gurenchan@gmail.com> wrote: >=20 >=C2=A0 Subject: nvidia drivers mutex lock >=C2=A0 To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org >=C2=A0 Date: Thursday, June 1, 2017, 11:35 AM >=C2=A0=20 >=C2=A0 I'm running nvidia-drivers 375.66 with a GTX >=C2=A0 1070 on FreeBSD-Current >=C2=A0=20 >=C2=A0 This problem just started happening >=C2=A0 recently but, every so often my laptop >=C2=A0 screen will just blank out and then I >=C2=A0 have to power cycle to get the >=C2=A0 machine up and running again. >=C2=A0=20 >=C2=A0 It seems to be a problem with nvidia >=C2=A0 drivers acquiring duplicate lock. Any >=C2=A0 info on this? >=C2=A0=20 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 acquiring duplicate lock of same type: >=C2=A0 "os.lock_mtx" >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: 1st >=C2=A0 os.lock_mtx @ nvidia_os.c:841 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: 2nd >=C2=A0 os.lock_mtx @ nvidia_os.c:841 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 stack backtrace: >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #0 >=C2=A0 0xffffffff80ab7770 at >=C2=A0 witness_debugger+0x70 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #1 >=C2=A0 0xffffffff80ab7663 at >=C2=A0 witness_checkorder+0xe23 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #2 >=C2=A0 0xffffffff80a35b93 at >=C2=A0 __mtx_lock_flags+0x93 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #3 >=C2=A0 0xffffffff82f4397b at >=C2=A0 os_acquire_spinlock+0x1b >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #4 >=C2=A0 0xffffffff82c48b15 at _nv012002rm+0x185 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: >=C2=A0 Argument #4 type mismatch - Found >=C2=A0 [Buffer], ACPI requires [Package] >=C2=A0 (20170303/nsarguments-205) >=C2=A0 Jun=E3=80=93 2 02:29:42 blubee kernel: >=C2=A0 nvidia-modeset: Allocated GPU:0 >=C2=A0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ >=C2=A0 PCI:0000:01:00.0 >=C2=A0 =20 >=C2=A0 Best, >=C2=A0 Owen >=C2=A0 _______________________________________________ >=C2=A0 freebsd-ports@freebsd.org >=C2=A0 mailing list >=C2=A0 https://lists.freebsd.org/mailman/listinfo/freebsd-ports >=C2=A0 To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >=C2=A0=20 >=20 >=20 > ... then Xorg will run happily twelve hours or so.=C2=A0 The lockups here happen usually > when too large or too many of number of tabs/ large web pages with complex CSS etc > are opened at a time.=C2=A0=20 >=C2=A0 =C2=A0 So no help, just a 'me too'.=C2=A0=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >=20 >=20 =20 =20 --=20 Tomoaki AOKI=C2=A0 =C2=A0 <junchoon@dec.sakura.ne.jp> =20 ........................ might be a workaround Xorg/nvidia ran all night with this: nvidia-settings >> X server display configuration >> Advanced >> Force = Full Composition Pipeline ... for the laptop freezing. Could not hurt to try. " merge with Xorg.con= f " from nvidia-settings... ...................... 18 hours uptime so far, even past the 3 am periodic scripts. Have not rebooted out of the Xorg though so ma= y require edit-out of xorg.conf if that is the case, in other words differing from real-time appl= y and xorg initially start applies. =20 ........ =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1100140349.1166835.1496498112171>