Re: Xorg error 'alphasort'
On 31/05/2017 18:21, Masachika ISHIZUKA wrote: Hi. I was using 12-current r318249 and did 'pkg upgrade', and could not start xorg with alphasort error. After updating r319315, xorg works again. Right I had more or less the same with r319216. And I was going to reinstall from a snapshot, but now I'll try and move forward. --WjW ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ino64, java and intellij products problem
01.06.2017 00:29, Konstantin Belousov пишет: > On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: >> Hi All, >> >> Seems that after ino64 transition some java programs stopped >> to fully function. I.e. java/intellij (IntellJ IDEA and Co) >> starts but does not show any files. >> >> I'm not sure if it's a java or IntelliJ problem. Any help to >> diagnose the culprit is welcome. > > Is it after full rebuild of all ports for post-ino64, or with all ports > built on pre-ino64 ? (Mixes are not supported and not supposed to work). Hm. I've rebuild all required ports: --- % pkg info -d intellij-2017.1.3 intellij-2017.1.3: python27-2.7.13_3 openjdk8-8.131.11 intellij-pty4j-0.5_1 intellij-fsnotifier-20160221_2 --- But sure not *all* ports. > Check java programs for JNI calls which return struct stat or struct > dirent to java code, and java code which knows the layout. It is, e.g., > the problem with Firefox and its javascript, but there the recompilation > seems to work. OK, thanks. I'll wait for FreeBSD cluster[*] to build post-ino64 packages, reinstall all of them and see what's next. [*] Seems to occur RSN. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Firefox (and other Mozilla products) after ino64
On Wed, 31 May 2017 23:27:16 +0200 Dimitry Andric wrote: [snip] > This also applies to other Mozilla products, such as Thunderbird, > SeaMonkey, and so on. These should all be rebuilt from scratch under > ino64. > FYI Seamonkey still works after updating kernel and world to ino64. -- Gary Jennejohn ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
nvidia drivers mutex lock
I'm running nvidia-drivers 375.66 with a GTX 1070 on FreeBSD-Current This problem just started happening recently but, every so often my laptop screen will just blank out and then I have to power cycle to get the machine up and running again. It seems to be a problem with nvidia drivers acquiring duplicate lock. Any info on this? Jun 2 02:29:41 blubee kernel: acquiring duplicate lock of same type: "os.lock_mtx" Jun 2 02:29:41 blubee kernel: 1st os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: 2nd os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: stack backtrace: Jun 2 02:29:41 blubee kernel: #0 0x80ab7770 at witness_debugger+0x70 Jun 2 02:29:41 blubee kernel: #1 0x80ab7663 at witness_checkorder+0xe23 Jun 2 02:29:41 blubee kernel: #2 0x80a35b93 at __mtx_lock_flags+0x93 Jun 2 02:29:41 blubee kernel: #3 0x82f4397b at os_acquire_spinlock+0x1b Jun 2 02:29:41 blubee kernel: #4 0x82c48b15 at _nv012002rm+0x185 Jun 2 02:29:41 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170303/nsarguments-205) Jun 2 02:29:42 blubee kernel: nvidia-modeset: Allocated GPU:0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI::01:00.0 Best, Owen ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: nvidia drivers mutex lock
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, every so often my laptop screen will just blank out and then I have to power cycle to get the machine up and running again. It seems to be a problem with nvidia drivers acquiring duplicate lock. Any info on this? Jun 2 02:29:41 blubee kernel: acquiring duplicate lock of same type: "os.lock_mtx" Jun 2 02:29:41 blubee kernel: 1st os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: 2nd os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: stack backtrace: Jun 2 02:29:41 blubee kernel: #0 0x80ab7770 at witness_debugger+0x70 Jun 2 02:29:41 blubee kernel: #1 0x80ab7663 at witness_checkorder+0xe23 Jun 2 02:29:41 blubee kernel: #2 0x80a35b93 at __mtx_lock_flags+0x93 Jun 2 02:29:41 blubee kernel: #3 0x82f4397b at os_acquire_spinlock+0x1b Jun 2 02:29:41 blubee kernel: #4 0x82c48b15 at _nv012002rm+0x185 Jun 2 02:29:41 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170303/nsarguments-205) Jun 2 02:29:42 blubee kernel: nvidia-modeset: Allocated GPU:0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI::01:00.0 Best, Owen ___ freebsd-po...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ... then Xorg will run happily twelve hours or so. 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. So no help, just a 'me too'. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: firefox/ rust failed to install on FreeBSD 12-CURRENT
On 28.05.2017 19:21, blubee blubeeme wrote:
> ===> Building for rust-1.17.0
> ...
> extracting
> rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd/lib/GNUSparseFile.0/librustc_llvm-74a1be1110b5d4d0.so
> gmake[7]: Leaving directory '/usr/ports/lang/rust/work/rustc-1.17.0-src'
> *** Error code 1
Hi!
This failure is caused by Python 2's tarfile module not supporting
sparse files in archives. Python 3 supports them but the configure
script insists on using Python 2.
Before a proper fix is committed, you can change the following line in
lang/rust/Makefile:
https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L159
to say (this is a single line):
gtar -c -C ${WRKSRC} -f -
rust-std-1.16.0-${RUST_ARCH_${ARCH}}-unknown-freebsd | gzip >
${WRKSRC}/rustc.tbz
Then, change the following line:
https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L34
to say:
BUILD_DEPENDS= cmake:devel/cmake \
gtar:archivers/gtar
This will use GNU tar instead of BSD tar to recreate the bootstrap and
GNU tar doesn't seem to produce sparse file entries in the archive.
--
Jean-Sébastien Pédron
signature.asc
Description: OpenPGP digital signature
