Re: openjdk6 broken on current
On Wed, May 8, 2013 at 8:29 AM, Larry Rosenman l...@lerctr.org wrote: Can SOMEONE please look at this? I have a real need to get java back on my -CURRENT server soon. Roll back your -CURRENT and you will have your server running already. Thanks! On 2013-05-07 10:18, Alexander Yerenkow wrote: Can anyone look into latest changes in swapcontext? http://svnweb.freebsd.org/base/head/lib/libthr/thread/thr_sig.c?sortby=dateview=log [1] Seems some of it broke openjdk6 (more in java@ list archive). Thanks. 2013/5/7 Larry Rosenman l...@lerctr.org On 2013-05-07 02:10, Alexander Yerenkow wrote: Then seems that's it - swapcontext change probably culprit. I got rechecked generated classes at other pc - classes are fine, same command with classes from 10-current not segfaulting in a bit older 10-current. Thank you Larry for access, I'm done there :) Any idea(s) on how to fix it? 2013/5/7 Larry Rosenman l...@lerctr.org Alexander Yerenkow yeren...@gmail.com wrote: 2013/5/7 Larry Rosenman l...@lerctr.org I have 64G ram. and I have workdir saved. who wants an SSH account to look at and fix it? Okay, while we are here, here is backtrace from executing java while building port openjdk6: #0 0x000801e2da93 in JVM_handle_bsd_signal () from /usr/ports/java/openjdk6/work/build/bsd-amd64/lib/amd64/server/libjvm.so #1 0x000800a49116 in swapcontext () from /lib/libthr.so.3 #2 0x000800a48d39 in sigaction () from /lib/libthr.so.3 #3 0x71d3 in ?? () #4 0x000800a48c20 in sigaction () from /lib/libthr.so.3 #5 0x000801ba9540 in Deoptimization::unpack_frames () from /usr/ports/java/openjdk6/work/build/bsd-amd64/lib/amd64/server/libjvm.so #6 0x000803869f7e in ?? () #7 0x7fbfa080 in ?? () #8 0x00080383b828 in ?? () #9 0x00080685e6e0 in ?? () #10 0x00080684f000 in ?? () #11 0x7fbfa0d0 in ?? () #12 0x7fbfa148 in ?? () #13 0x00080308f000 in ?? () #14 0x000806bab450 in ?? () #15 0x000803869eb9 in ?? () #16 0x in ?? () Is there any known significant changes about libthr (or any other ) before r250047 ? There were some commits around swapcontext recently -- Sent from Kaiten Mail. Please excuse my brevity. -- Regards, Alexander Yerenkow -- Larry Rosenman http://www.lerctr.org/~ler [2] Phone: +1 214-642-9640 [3] (c) E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -- Regards, Alexander Yerenkow Links: -- [1] http://svnweb.freebsd.org/base/head/lib/libthr/thread/thr_sig.c?sortby=dateamp;view=log [2] http://www.lerctr.org/~ler [3] tel:%2B1%20214-642-9640 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Clang as default compiler November 4th
On Tue, Sep 11, 2012 at 7:21 AM, Konstantin Belousov kostik...@gmail.com wrote: snip Can you, please, read what I wrote ? Fixing _ports_ to compile with clang is plain wrong. Upstream developers use gcc almost always for development and testing. Establishing another constant cost on the porting work puts burden on the ports submitters, maintainers and even ports users. I do strongly oppose the attempt to drain the freebsd resources by forcing porters to port third-party code to other compiler. I agree with this pretty much. I haven't done fix any of port build with clang as I simply ignore clang (sorry). When user report to me and I tell them to stick with GCC as I don't support it. Cheers, Mezz -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng default schedule... registering a few reasons for rethinking the final implementation...
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote: On 08/23/2012 12:26, Jeffrey Bouquet wrote: I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 py27. cd /var/db/pkg ls -lac | grep py26 ls -lac | grep python as the more simple example. With due respect to its developers and the persons who agree that the package tools could be upgraded, the mandatory usage of a front-end database to a file directory one is here viewd as mutt-only-mbox, registry-and-bsod rather than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; ... I see concurrently too few tests on lower-end p2, p3 as to whether pkg can run with lesser memory machines (routers...) (pfsense) ... I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, pfsense..) due to less-reliability, more-possibility of bugs.. This is of some concern to me as well. A number of our utilities / scripts rely on checking /var/db/pkg as a means to test if a particular package is installed. This is often much faster than running the pkg_* commands, especially when we may be checking thousands of packages in a single run. It will be some work to adjust our utilities to using the various pkg commands now, but it can be done. What worries me is performance. If this is significantly slower, it may cause some issues on our end. Guys, please test it before you say anything. Otherwise it's going to be moved forward without you. -- Kris Moore PC-BSD Software iXsystems -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Is the :u behaves normal or not (a bug) in the make?
Hello all,
While I was working on add the :build/:run feature in the
bsd.gnome.mk. I got a bug where it will running some dependencies got
duplicate. Thanks to the make(1) that shows me the :u feature to get
rid of the duplicates. But it doesn't exactly help unless I use the :O
to get the words in order to make the :u works. I am not sure if it's
just limited on how it works (normal) or it's a bug. Here's an example
test:
-
USE_TEST= foo bar bar foobar foo
USE_TEST1= foo bar bar foobar foo
test:
@${ECHO_CMD} USE_TEST: ${USE_TEST:u}
@${ECHO_CMD} USE_TEST1: ${USE_TEST1:O:u}
-
Here's result:
-
# make test
USE_TEST: foo bar foobar foo
USE_TEST1: bar foo foobar
-
Thanks,
Mezz
--
mezz.free...@gmail.com - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is the :u behaves normal or not (a bug) in the make?
On Thu, Jul 26, 2012 at 3:11 PM, Jeremy Messenger
mezz.free...@gmail.com wrote:
Hello all,
While I was working on add the :build/:run feature in the
bsd.gnome.mk. I got a bug where it will running some dependencies got
duplicate. Thanks to the make(1) that shows me the :u feature to get
rid of the duplicates. But it doesn't exactly help unless I use the :O
to get the words in order to make the :u works. I am not sure if it's
just limited on how it works (normal) or it's a bug. Here's an example
test:
-
USE_TEST= foo bar bar foobar foo
USE_TEST1= foo bar bar foobar foo
test:
@${ECHO_CMD} USE_TEST: ${USE_TEST:u}
@${ECHO_CMD} USE_TEST1: ${USE_TEST1:O:u}
-
Here's result:
-
# make test
USE_TEST: foo bar foobar foo
USE_TEST1: bar foo foobar
-
BTW:
# uname -a
FreeBSD outlaws.localhost 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat Mar 31
12:43:40 CDT 2012
mezz@outlaws.localhost:/usr/obj/usr/src/sys/GENERIC amd64
Thanks,
Mezz
--
mezz.free...@gmail.com - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Is the :u behaves normal or not (a bug) in the make?
On Thu, Jul 26, 2012 at 5:10 PM, Olli Hauer oha...@freebsd.org wrote:
On 2012-07-26 22:11, Jeremy Messenger wrote:
Hello all,
While I was working on add the :build/:run feature in the
bsd.gnome.mk. I got a bug where it will running some dependencies got
duplicate. Thanks to the make(1) that shows me the :u feature to get
rid of the duplicates. But it doesn't exactly help unless I use the :O
to get the words in order to make the :u works. I am not sure if it's
just limited on how it works (normal) or it's a bug. Here's an example
test:
-
USE_TEST= foo bar bar foobar foo
USE_TEST1=foo bar bar foobar foo
test:
@${ECHO_CMD} USE_TEST: ${USE_TEST:u}
@${ECHO_CMD} USE_TEST1: ${USE_TEST1:O:u}
-
Here's result:
-
# make test
USE_TEST: foo bar foobar foo
USE_TEST1: bar foo foobar
-
It's normal, from man(1) make
u Remove adjacent duplicate words (like uniq(1)).
from man(1) uniq
Repeated lines in the input will not be detected if they are
not adjacent, so it may be necessary to sort the files first.
Damn it, I missed that line! :-P Thanks!
Cheers,
Mezz
--
Regards,
olli
--
mezz.free...@gmail.com - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP CFT] pkg 1.0rc1 and schedule
On Mon, Jul 16, 2012 at 2:24 AM, Matthew Seaman matt...@freebsd.org wrote: On 16/07/2012 05:22, Jeremy Messenger wrote: It's one of reason why I do not agree to remove the shared library version from the LIB_DEPENDS, so that way in future someone can add support in the package to check on shared library version then prevent package to install because it's not ABI compatible. Unless someone prefer to do it in the different way than putting shared library version in the LIB_DEPENDS is good to me either. Two points here: Firstly LIB_DEPENDS is all about *building* packages. In that case, the thing that matters is *API* compatibility, not ABI. Library APIs tend to be much more stable than ABIs, meaning you can compile your code against practically any version of a shared library. However, you won't be able to run your compiled program against a shared library with a different ABI. If the API does change incompatibly, then it is fine to use constraints on the ABI version in a port, but doing this as a matter of course is just being obstructive to people that may not want to upgrade dependency shlibs just yet. Secondly, the ABI version of shared libraries has no effect on the current dependency resolution mechanisms when installing packages (either pkgng or the old pkg_tools). At the moment, the only thing that is considered are package version numbers. I know. Hences for the 'in future someone can add support'. Cheers, Mezz This is an area where we have plans for dramatic changes with pkgng. We want to import a general solver mechanism so that a package can have a list of generic requirements: File /usr/local/bin/foo exists and is executable Shared library libfoo.so.3 is installed Perl Module Foo::Bar 1.23 is available Package foo-0.99 has option BLURFL enabled etc. etc. Packages will similarly have a list of facilities they provide. The job of the solver will be to find a set of packages such that there is a provider for every requirement constrained by the user requirement that their required package set is installed. However, making this mechanism workable implies significant changes to the ports -- introducing sub-packages in particular -- which are basically incompatible with the existing pkg_tools. So we need to pkgng 1.0 in place to be able to proceed with further changes. Also a generic solver is in itself a substantial piece of code to introduce. Which is why it hasn't happened yet. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP CFT] pkg 1.0rc1 and schedule
On Sun, Jul 15, 2012 at 10:32 PM, Peter Jeremy pe...@rulingia.com wrote: On 2012-Jul-12 10:01:10 +, Baptiste Daroussin b...@freebsd.org wrote: What is pkg --- pkg is a new package manager for FreeBSD. It is designed as a replacement for the pkg_* tools, and as a full featured binary package manager. A couple of specific questions that I haven't seen answered during this thread or in the wiki: - Can pkgng cope with parallel installs? What happpens if I simultaneously (attempt to) install conflicting packages? IMO, the parallel install shouldn't be supported for that exactly reason. Not only that reason, it makes the dependencies get complicate too. - If I use pkg delete -f, what happens to packages that depended on the forcibly-deleted package? - What happens if I delete a package where I've modified one of the files managed by the package? - What facilities does it have for auditing and repairing the package database? (ie checking for inconsistencies between installed files and the content of the package database) - How does it handle the situation where I install a package that depends on foo version 1.2.3 but have foo version 1.2.4 (or 1.2.2) installed? What about if I have bar version 1.3, which is ABI- compatible with foo version 1.2.3, installed? It's one of reason why I do not agree to remove the shared library version from the LIB_DEPENDS, so that way in future someone can add support in the package to check on shared library version then prevent package to install because it's not ABI compatible. Unless someone prefer to do it in the different way than putting shared library version in the LIB_DEPENDS is good to me either. Cheers, Mezz - Will it detect that a package install would overwrite an existing file? What does it do in this case? - I gather it handles update package more intelligently than uninstall old package, install new package. Will it avoid replacing an old file with an identical one in the new package? If so, what happens to the file metadata (particularly uid, gid and mtime)? - Can it track user-edited configuration files that are associated with packages? - Can it do 2- or 3-way merges of package configuration files? - The README states Directory leftovers are automatically removed if they are not in the MTREE. How does this work for directories that are shared between multiple packages? Does this mean that if I add a file to a directory that was created by a package, that file will be deleted automatically if I delete the package? -- Peter Jeremy -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADS-UP] BSD sort is the default sort in -CURRENT
On Wed, Jun 27, 2012 at 9:56 AM, Doug Barton do...@freebsd.org wrote: On 06/27/2012 07:30 AM, Pedro Giffuni wrote: --- Mer 27/6/12, Doug Barton do...@freebsd.org ha scritto: ... I believe we do not make this kind of work with any vendor code that is being updated in the base; Au contraire, we frequently avoid updating the old versions of things we have in the base precisely because they are not bug-for-bug compatible with existing behaviors that we count on. Really?? I guess you are speaking for bind, Nope. because the idea behind updating and piece of software is precisely shaking bugs. Nope. I would think only the maintainer of the package has the authority to make any request in the lines of being bug-for-bug compatible You have a seriously wrong idea of maintainer. The community owns the software, it's up to the community to decide how it should work. Historically we have looked at the maintainer as the person who volunteers to take care of code, not the person who has the exclusive lock on it. and in the case of GNU sort and GNU grep they are both unmaintained and replacements are welcome. Actually both are maintained, it's just that we don't want to import the new GNU versions. And yes, having BSD versions of these core tools is a nice goal, but it's not one we should pursue for its own sake. Please let's stop being an obstacle towards people bringing real progress to FreeBSD! In the case of grep, there were a fairly large number of people who agreed that a BSD grep with orders of magnitude worse performance than the previous version was not something we, as a project, were willing to stomach. Sufficiently such that the default was switched back. So can we please stop pretending that it's me who's the problem, and start looking at these things rationally? Doug, I think you need to give it a chance. I do not see any problem for anyone to switch the default and if the problems discover then switch the default back. It's a bleeding edge branch where more people can test it. The issue with grep was very harmeless and it was not difficult to switch the default between GNU and BSD. It's not like they threw GNU grep/sort away quickly. How come that I haven't heard anything from you about the jemalloc update? If you did then I must have missed it. It was very clearly that it was not test and he doesn't handle it very well, but got fixed evenly with the multi-commit. It was worst than grep/sort and other projects. If you are wondering why it's you. Because lately you are starting to whine a lot without give the things chance. If we are doing your way and nothing will moving on. Doug -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFT] Automatic load of USB kernel modules
On Fri, Jun 24, 2011 at 5:23 PM, Hans Petter Selasky hsela...@c2i.net wrote: On Saturday 25 June 2011 00:15:17 Warner Losh wrote: Hey Hans, Given that all this stuff is really new and shiny, and we're really close to the feature freeze, I'm not sure enabling it by default is the prudent action. Yes, you might be right. I'm not saying it should be enabled by default. BTW: How can we disable a .conf file from being picked up by devd? Or do I need to delete it from svn ? Maybe move it to src/etc/defaults/? Cheers, Mezz --HPS -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: licq KSE
On Tue, 2 Dec 2003 15:58:07 -0500 (EST), Daniel Eischen [EMAIL PROTECTED] wrote: On Tue, 2 Dec 2003, Alexander Motin wrote: Daniel Eischen wrote: On Tue, 2 Dec 2003, Alexander Motin wrote: Alexander Motin wrote: If I use libkse I get: kernel: Warning: pid 25341 used static ldt allocation. kernel: See the i386_set_ldt man page for more info in my messages. When I use libc_r I do not get this messages. I'm sorry. Messages seems to be independent from library. I get messages with both libraries but not every time. Some times I get two messages on one licq launching. But with libc_r it works and with libkse is not. It is not libkse that is causing the messages. It is some library or driver that licq is using. The kernel spews these messages whenever something uses static LDT allocation. We know that nvidia drivers and/or their OpenGL library do this, and they have been notified of it (by me). If there is another library or application that is also using static LDT allocation, please help us find it so it can be fixed also. $ ldd /usr/local/bin/licq From which system is this? The nvidia or the ATI? We know nvidia has a problem with ldt/%gs usage. You still haven't told me if you are getting the same static LDT warnings from the ATI system. /usr/local/bin/licq: libssl.so.3 = /usr/lib/libssl.so.3 (0x28102000) libcrypto.so.3 = /lib/libcrypto.so.3 (0x28134000) libc_r.so.5 = /usr/lib/libc_r.so.5 (0x28242000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x28266000) libm.so.2 = /lib/libm.so.2 (0x28322000) libc.so.5 = /lib/libc.so.5 (0x2833b000) $ ldd ./licq_qt-gui.so ./licq_qt-gui.so: libqt-mt.so.3 = /usr/X11R6/lib/libqt-mt.so.3 (0x2828e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x288d) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x288d9000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x288f) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x289b8000) libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x289c7000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x289e5000) libm.so.2 = /lib/libm.so.2 (0x28aa1000) libmng.so.1 = /usr/local/lib/libmng.so.1 (0x28aba000) libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28b18000) libz.so.2 = /lib/libz.so.2 (0x28b3d000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x28b4b000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28bb2000) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x28bc8000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x28bd) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28be2000) libfontconfig.so.1 = /usr/X11R6/lib/libfontconfig.so.1 (0x28c4c000) liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28c74000) libGLcore.so.1 = /usr/X11R6/lib/libGLcore.so.1 (0x28c8f000) ^^ What is this? It's more like Nvidia driver issue as you have said previous. There has an option to build QT3 with OpenGL. Alexander, Nvidia driver and libkse don't play together very well; it's recommend to stick with libc_r if you want to use Nvidia driver. Cheers, Mezz libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x2912b000) libexpat.so.4 = /usr/local/lib/libexpat.so.4 (0x2917c000) This doesn't match mine: /usr/local/lib/licq/licq_qt-gui.so: . libqt-mt.so.3 = /usr/X11R6/lib/libqt-mt.so.3 (0x2828e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x2894c000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x28955000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x2896c000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x28a34000) libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x28a43000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x28a61000) libm.so.2 = /lib/libm.so.2 (0x28b1d000) libc_r.so.5 = /usr/lib/libkse.so.1 (0x28b36000) libmng.so.1 = /usr/local/lib/libmng.so.1 (0x28b5b000) libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28bb9000) libz.so.2 = /lib/libz.so.2 (0x28bde000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x28bec000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28c59000) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x28c6f000) libXrandr.so.2 = /usr/X11R6/lib/libXrandr.so.2 (0x28c77000) libXcursor.so.1 = /usr/X11R6/lib/libXcursor.so.1 (0x28c7b000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x28c84000) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28c96000) libfontconfig.so.1 = /usr/X11R6/lib/libfontconfig.so.1 (0x28d0) liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28d28000) libc.so.5 = /lib/libc.so.5 (0x2808) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x28d43000) libexpat.so.4 = /usr/local/lib/libexpat.so.4 (0x28d94000) -- bsdforums.org 's moderator, mezz.
Re: HEADS-UP new statfs structure
On Sat, 15 Nov 2003 00:46:19 +0100, Sascha Holzleiter [EMAIL PROTECTED] wrote: On Fri, 2003-11-14 at 22:46, Bruce Cran wrote: Either the new statfs, or something in a recent change in -CURRENT (since last week), has broken the nvidia driver. I've been using it now for over half a year with no problems at all. I installed the new kernel and world, rebuilt x11/nvidia-driver and X11 hung before it had even switched to graphical mode. After a minute the system rebooted, and I got the same behavoir a few days ago BEFORE rebuilding the system, so i don't think it is due to the statfs change. The driver stopped working around the time the XFree86 ports were changed, I think that these are more likely the cause. But, all my apps are up to date so the Nvidia driver is still working. I haven't update -CURRENT yet, I am waiting for Gnome 2.5 to be out then I will update -CURRENT and stuff. # pkg_info | grep XFree86 XFree86-4.3.0,1 X11/XFree86 core distribution (complete, using mini/meta-po XFree86-FontServer-4.3.0_2 XFree86-4 font server XFree86-Server-4.3.0_12 XFree86-4 X server and related programs XFree86-clients-4.3.0_5 XFree86-4 client programs and related files XFree86-documents-4.3.0 XFree86-4 documentation XFree86-font100dpi-4.3.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.3.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontCyrillic-4.3.0 XFree86-4 Cyrillic fonts XFree86-fontDefaultBitmaps-4.3.0 XFree86-4 default bitmap fonts XFree86-fontEncodings-4.3.0 XFree86-4 font encoding files XFree86-fontScalable-4.3.0 XFree86-4 scalable fonts XFree86-libraries-4.3.0_6 XFree86-4 libraries and headers dri-4.3.0,1 OpenGL hardware acceleration drivers for XFree86 imake-4.3.0_1 Imake and other utilities from XFree86 wrapper-1.0_3 Wrapper for XFree86-4 server # pkg_info | grep nvidia nvidia-driver-1.0.4365 [...with non-offical patch...] Cheers, Mezz The odd thing is that this seems to be system dependent, on my P4 system at home the driver still works fine, on my Athlon system at work I have the same issues you describe here... I haven't done anything to debug or fix this because I need the failing system to work with rather then to play around with ;) But if anyone wants to look into that I'll provide every information needed. Greets, Sascha -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GNOME users should recompile gnomevfs2 after today update
On Thu, 13 Nov 2003 04:54:21 -0800, walt [EMAIL PROTECTED] wrote: I found that the new statfs changes cause nautilus to crash on startup. The fix is to recompile/reinstall devel/gnomevfs2. Thanks for let us know and add CC'ing to freebsd-gnome list.. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ALTQ support
On Mon, 10 Nov 2003 12:29:34 +0800, Michael Lee [EMAIL PROTECTED] wrote: Dear Sir, I don't know if I am posting this question to a wrong mailing list. I am looking for a solution to make QoS possible on my FreeBSD box. After searching for the internet, I found that there is a software called ALTQ that can do possibly what I want. However, I found that it is still not directly built into the kernel. Those who want to use it need to patch the kernel themselves. http://www.rofug.ro/projects/freebsd-altq/ I am not really sure which is better or difference, but there has another link: http://www.nipsi.de/altq/index.html Cheers, Mezz I wonder if any of the core team members has the plan to build it into the kernel since I was told that it is not a good way to patch the kernel myself. ( for the system stability concern. ) Thanks! Michael Lee PS: Please c.c me since I did not subscribe to this mailing list. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd block size
On Fri, 07 Nov 2003 10:10:40 +0100, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: I've been having a variety of problems burning CDs with atang: - burncd consistently failing in exactly the same spot in the ISO, and reporting only wrote 0 of 32768 bytes: Unknown error: 0 - burncd failing right at the start with only wrote -1 of 32768 bytes: Input/output error (this generally happens after a couple of the previous, and once it starts happening I have to reboot) Whew, glad that I am not only one.. I *just* have wasted two of my blank CD in like fifteen minutes ago, I keep wondering if I created the ISO files in the wrong way or was it burncd's fault.. Until now here.. I get like this: = # burncd -f /dev/acd0 -e -s 6 data NT2004.iso fixate next writeable LBA 0 writing from file NT2004.iso size 662576 KB written this track 410656 KB (61%) total 410656 KB only wrote 4096 of 32768 bytes: Unknown error: 0 fixating CD, please wait.. = I tried the another ISO and I get the same thing by stopped at 32768 bytes. I am going to use cdrecord for now, hope it will work ok. Cheers, Mezz - burncd getting stuck in acdcld for a long time while fixating - a *lot* of sensekey=ILLEGAL REQUEST error=4ABORTED; fixating a CD causes about half a dozen TEST_UNIT_READY failures, and I occasionally get READ_BIG, START_STOP, PREVENT_ALLOW and SET_SPEED failures as well, all of them with status=51READY,DSC,ERROR sensekey=ILLEGAL REQUEST error=4ABORTED I've discovered that reducing the buffer size in burncd fixes at least the first problem, and possibly the second, but not the third. I've attached a patch that adds a command-line option for that (the default will still be 16 blocks at a time, but you can specify anything from 1 to 64 on the command line) The drive is an LG 8400B with which I've previously had little or no trouble; prior to atang, it burned CDs just fine at 40x with a failure rate of precisely 0. # dmesg | grep acd acd0: CDRW HL-DT-ST GCE-8400B at ata1-master WDMA2 # atacontrol info ata1 Master: acd0 HL-DT-ST GCE-8400B/1.00 ATA/ATAPI rev 0 Slave: no device present # atacontrol cap ata1 0 ATA channel 1, Master, device acd0: ATA/ATAPI revision0 device model HL-DT-ST GCE-8400B serial number firmware revision 1.00 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no dma queued no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 DES -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd block size
On Fri, 7 Nov 2003 10:28:42 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] wrote: It seems Jeremy Messenger wrote: On Fri, 07 Nov 2003 10:10:40 +0100, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: I've been having a variety of problems burning CDs with atang: - burncd consistently failing in exactly the same spot in the ISO, and reporting only wrote 0 of 32768 bytes: Unknown error: 0 - burncd failing right at the start with only wrote -1 of 32768 bytes: Input/output error (this generally happens after a couple of the previous, and once it starts happening I have to reboot) Whew, glad that I am not only one.. I *just* have wasted two of my blank CD in like fifteen minutes ago, I keep wondering if I created the ISO files in the wrong way or was it burncd's fault.. Until now here.. This is fallout from getting atapi-cd under GEOM. GEOM wasn't designed to handle medias of size 0 and where the sizes can change during an open. I just committed a fix that has solved the issue here (and its ugly). Thanks! /me goes to update his -CURRENT... Cheers, Mezz -Søren -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd block size
On Fri, 7 Nov 2003 10:28:42 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] wrote: It seems Jeremy Messenger wrote: On Fri, 07 Nov 2003 10:10:40 +0100, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: I've been having a variety of problems burning CDs with atang: - burncd consistently failing in exactly the same spot in the ISO, and reporting only wrote 0 of 32768 bytes: Unknown error: 0 - burncd failing right at the start with only wrote -1 of 32768 bytes: Input/output error (this generally happens after a couple of the previous, and once it starts happening I have to reboot) Whew, glad that I am not only one.. I *just* have wasted two of my blank CD in like fifteen minutes ago, I keep wondering if I created the ISO files in the wrong way or was it burncd's fault.. Until now here.. This is fallout from getting atapi-cd under GEOM. GEOM wasn't designed to handle medias of size 0 and where the sizes can change during an open. I just committed a fix that has solved the issue here (and its ugly). It's fixed, now I am able to burn it full on CD. I get the new messages (see bottom) when it boot, but it seems to be harmless since I can use anything and work ok. Does this messages mean I need to give the SCSI_DELAY more time? == Nov 7 13:21:43 mezz kernel: acd0: CDRW CD-W516EB at ata0-master PIO4 Nov 7 13:21:43 mezz kernel: Waiting 5 seconds for SCSI devices to settle Nov 7 13:21:43 mezz kernel: GEOM: create disk cd0 dp=0xc2e44e00 Nov 7 13:21:43 mezz kernel: GEOM: create disk da0 dp=0xc2e36450 Nov 7 13:21:43 mezz kernel: da0 at ahc0 bus 0 target 0 lun 0 Nov 7 13:21:43 mezz kernel: da0: SEAGATE ST336706LW 0109 Fixed Direct Access SCSI-3 device Nov 7 13:21:43 mezz kernel: da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled Nov 7 13:21:43 mezz kernel: da0: 35003MB (71687370 512 byte sectors: 255H 63S/T 4462C) Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Recovered Sense Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): NOT READY asc:3a,0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Medium not present Nov 7 13:21:43 mezz kernel: cd0 at ata0 bus 0 target 0 lun 0 Nov 7 13:21:43 mezz kernel: cd0: TEAC CD-W516EB 1.0A Removable CD-ROM SCSI-0 device Nov 7 13:21:43 mezz kernel: cd0: 16.000MB/s transfers Nov 7 13:21:43 mezz kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Recovered Sense Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): NOT READY asc:3a,0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Medium not present Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Recovered Sense Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): NOT READY asc:3a,0 Nov 7 13:21:43 mezz kernel: (cd0:ata0:0:0:0): Medium not present Nov 7 13:21:43 mezz kernel: Mounting root from ufs:/dev/da0s1a == Cheers, Mezz -Søren -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld failure: don't know how to make thr_atfork.c
On Wed, 5 Nov 2003 17:17:05 +1030, Alex Wilkinson [EMAIL PROTECTED] wrote: CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails. $ make buildworld . snip === lib/libpthread make: don't know how to make thr_atfork.c. Stop *** Error code 2 snip It's already fixed, Daniel has missed this file so David has committed it for him. Cheers, Mezz - aW -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Was: More ULE bugs fixed. Is: Mouse problem?
On Tue, 4 Nov 2003 22:10:36 -0500 (EST), Jeff Roberson [EMAIL PROTECTED] wrote: On Wed, 5 Nov 2003, Eirik Oeverby wrote: Eirik Oeverby wrote: Just for those interested: I do *not* get any messages at all from the kernel (or elsewhere) when my mouse goes haywire. And it's an absolute truth (just tested back and forth 8 times) that it *only* happens with SCHED_ULE and *only* with old versions (~1.50) and the very latest ones (1.75 as I'm currently running). 1.69 for instance did *not* show any such problems. I will, however, update my kernel again now, to get the latest sched_ule.c (if any changes have been made since 1.75) and to test with the new interrupt handler. I have a suspicion it might be a combination of SCHED_ULE and some signal/message/interrupt handling causing messages to get lost along the way. Because that's exactly how it feels... Whee. Either the bump from sched_ule.c 1.75 to 1.77 changed something back to the old status, or the new interrupt handling has had some major influence. All I can say is - wow. My system is now more responsive than ever, I cannot (so far) reproduce any mouse jerkiness or bogus input or anything, and things seem smoother. As always I cannot guarantee that this report is not influenced by the placebo effect, but I do feel that it's a very real improvement. The fact that I can start VMWare, Firebird, Thunderbird, Gaim and gkrellm at the same time without having *one* mouse hickup speaks for itself. I couldn't even do that with ULE. So Jeff or whoever did the interrupt stuff - what did you do? This is wonderful news. I fixed a few bugs over the last couple of days. I'm not sure which one caused your problem. I'm very pleased to hear your report though. This SCHED_ULE (1.78) rocks! I don't get any mouse lag anymore in the 'cd /usr/src ; make clean ; make cleandir' and the beginner of 'portupgrade -ra'. I did the hard test; I have Gnome2, Opera 7 (linux version), several gvim, several gnome-terminal tabs, pan and even use totem to watch a movie (700mb) in full screen mode ;-).. While watching the movie and it doesn't get lag that much only while unpack the large tarballs like mozilla. While the build and clean, it only has very very little lag like one to two time(s) but the rest are pretty smooth. The mouse doesn't get any lag at all. Just let you know my experience with SCHED_ULE so far. In the command line, I can tell that I can 'feel' it's faster but I don't know about the real time (ie: benchmark). It's better than SCHED_4BSD because I will get mouse lag if I do the same thing as above with SCHED_4BSD. BTW: I don't use KSE because of Nvidia driver. Cheers, Mezz Cheers, Jeff /Eirik Greetings, /Eirik Morten Johansen wrote: On Tue, 4 Nov 2003, Sheldon Hearn wrote: On (2003/11/04 09:29), Eirik Oeverby wrote: The problem is two parts: The mouse tends to 'lock up' for brief moments when the system is under load, in particular during heavy UI operations or when doing compile jobs and such. The second part of the problem is related, and is manifested by the mouse actually making movements I never asked it to make. Wow, I just assumed it was a local problem. I'm also seeing unrequested mouse movement, as if the signals from movements are repeated or amplified. The thing is, I'm using 4BSD, not ULE, so I wouldn't trouble Jeff to look for a cause for that specific problem in ULE. Me too. Have had this problem since I got a Intellimouse PS/2 wheel-mouse. (It worked fine with previous mice (no wheel)). With any scheduler in 5-CURRENT and even more frequent in 4-STABLE, IIRC. Using moused or not doesn't make a difference. Get these messages on console: psmintr: out of sync, and the mouse freezes then goes wild for a few seconds. Can happen under load and sometimes when closing Mozilla (not often). It could be related to the psm-driver. Or maybe I have a bad mouse, I don't know. I will try another mouse, but it does work perfectly in Linux and Windogs... mj -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: opendchub compile problem
On Mon, 03 Nov 2003 01:13:54 +0100, Sebastijan Vacun [EMAIL PROTECTED] wrote: Helo! I wanna install opendchub on my FreeBSD server. My system is: 4.9-STABLE FreeBSD I have installed perl-5.6.1_14. But when I want to make net/opendchub I got this: # make === opendchub-0.7.12 needs at least perl 5.6.1 to build. # Can anybody help me, please? Check in the /usr/ports/lang/perl5/pkg-message, it explains what you need to do. Best regards, Sebastijan Btw: Is that ok, to post msg like this on this maillist? Yes it's ok, but you have sent to the wrong mailing list. ;-) You should have sent to freebsd-ports instead freebsd-current. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports and -current
On Sat, 20 Sep 2003 08:14:07 +0200, Harald Schmalzbauer [EMAIL PROTECTED] wrote: Well, for weeks now I couldn't compile (almost) any port. It seems that ports aren't tested against -current. Is that true? Not only the -pthread removement broke countless ports (some of them are easy to fix others aren't) also the entire new kde fails. Is there no aim to have ports running on -current? Check in the bottom at http://lists.freebsd.org/pipermail/freebsd-gnome/2003-September/002846.html .. I believe, we should be expect to see the many fixes for -CURRENT when the ports freeze lift. Cheers, Mezz I'm asking because my workstation has enough resources to track -current to help testing. But if I breake ports with -current I won't keep tracking it. Thanks, -Harry -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re:
Nevermind, I switched from slave to master of CD-RW; it boots just fine and function fine too. No more weird busy signal at all the time. Time to use my own kernel config.. Cheers, Mezz On Wed, 17 Sep 2003 11:59:46 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: Last night, I CVSup'ed and did the buildworld/kernel stuff. Then, I reboot and I get the busy signal like forever, it looks like the HD is spinning forever for no reason. Also, the ATAng can't find my Teac CD-RW.. Here are three attaches.. dmesg-ataog.txt is old kernel sometime before ATAng went in the 5.1-CURRENT tree. FreeBSD mezz.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 23 01:09:03 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 dmesg-atang.txt and pciconf.txt are from last night 5.1-CURRENT. Please, let me know if there is something else I can do.. Soon, I am going to boot into the yesterday -CURRENT, I think I saw more error with SCSI stuff and I will try to collect them. If I get them and I will reply in here with the more info. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Engineering Status Report
On Wed, 17 Sep 2003 10:57:58 +0200, Dag-Erling Smrgrav [EMAIL PROTECTED] wrote: Mike Jakubik [EMAIL PROTECTED] writes: Is there a specific problem with OpenSSH 3.5 which requires an update to 3.6.1? Or do you just want me to update it to make the numbers look pretty on your screen? Apparently, yes. No. 3.6.1 has the same bug, and 3.7 isn't out yet. http://www.mindrot.org/pipermail/openssh-unix-announce/2003-September/64.html Cheers, Mezz DES -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Yesterday -CURRENT doesn't work on my CD-RW and SCSI HD (Re: )
Err, for some reason the email client ate my subject.. On Wed, 17 Sep 2003 11:59:46 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: Last night, I CVSup'ed and did the buildworld/kernel stuff. Then, I reboot and I get the busy signal like forever, it looks like the HD is spinning forever for no reason. Also, the ATAng can't find my Teac CD-RW.. Here are three attaches.. dmesg-ataog.txt is old kernel sometime before ATAng went in the 5.1-CURRENT tree. FreeBSD mezz.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 23 01:09:03 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 dmesg-atang.txt and pciconf.txt are from last night 5.1-CURRENT. Please, let me know if there is something else I can do.. Soon, I am going to boot into the yesterday -CURRENT, I think I saw more error with SCSI stuff and I will try to collect them. If I get them and I will reply in here with the more info. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re:
On Wed, 17 Sep 2003 11:59:46 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: Last night, I CVSup'ed and did the buildworld/kernel stuff. Then, I reboot and I get the busy signal like forever, it looks like the HD is spinning forever for no reason. Also, the ATAng can't find my Teac CD-RW.. Here are three attaches.. dmesg-ataog.txt is old kernel sometime before ATAng went in the 5.1-CURRENT tree. FreeBSD mezz.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 23 01:09:03 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 dmesg-atang.txt and pciconf.txt are from last night 5.1-CURRENT. Please, let me know if there is something else I can do.. Soon, I am going to boot into the yesterday -CURRENT, I think I saw more error with SCSI stuff and I will try to collect them. If I get them and I will reply in here with the more info. Ok, I have collected them.. I get the errors when I copied many files to the different place.. === (da0:ahc0:0:0:0): tagged openings now 59 (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Queue Full (da0:ahc0:0:0:0): tagged openings now 50 (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Queue Full (da0:ahc0:0:0:0): tagged openings now 49 (da0:ahc0:0:0:0): Retrying Command [...goes on...] === Cheers, Mezz Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Yesterday -CURRENT doesn't work on my CD-RW and SCSI HD (Re: )
On Wed, 17 Sep 2003 13:27:28 -0500, Conrad J. Sabatier [EMAIL PROTECTED] wrote: On Wed, 17 Sep 2003 11:59:46 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: Last night, I CVSup'ed and did the buildworld/kernel stuff. Then, I reboot and I get the busy signal like forever, it looks like the HD is spinning forever for no reason. Also, the ATAng can't find my Teac CD-RW.. Strange, I cvsupped/rebuilt last night as well. I haven't been seeing the outright hangs on boot that people are talking about, but I am still having problems getting both of my ATAPI devices to attach properly. Well, it doesn't hangs but I can surf around and fireup Gnome2 while I get the crazy busy singal light on at all the time. There are no crazy CPU/Memory in the ps/top, but just 90%-100% idle. I am pretty clueless on this one, so I am stick to the old 5.1-CURRENT for now until someone know what's wrong with my problem. I have four kernels under /boot, two of them have debug enable and I am willing to do anything. I got a response from Soren re: my last dmesg report; sounded like maybe he had an idea what to do about the ATAPI problem at least crossing fingers. :-) I hope, -CURRENT will get stable sometime soon same as before. :-) Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. Cheers, Mezz # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 15:53:26 -0400 (EDT), Andre Guibert de Bruet [EMAIL PROTECTED] wrote: On Sun, 24 Aug 2003, Jeremy Messenger wrote: On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... I am pretty aware of it and I don't care of those are lost because I always backup my personal stuff daily. I run everything in bleed edge such as - CURRENT, Gnome 2.4, VIM-cvs and etc, so I know my risk. Cheers, Mezz Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error: ln: /usr/libexec/ld-elf.so.1: Operation not permitted
On Sun, 17 Aug 2003 13:41:17 -0500, dave [EMAIL PROTECTED] wrote: I'm getting a consistent error with cvsup from this morning during make installworld snip ln: /usr/libexec/ld-elf.so.1: Operation not permitted snip I've done make cleandir and re-cvsup etc. Same error. amd 2400 asus mb. running cvsup/makeworld almost daily for 4 months with minimal problems. Probably something simple I just don't see. gordon just fixed in the rev 1.22 of src/libexec/rtld-elf/Makefile, so CVSup and try it again. Cheers, Mezz cheers, dave -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSUP problems
On Thu, 31 Jul 2003 15:57:45 -0700 (PDT), Rus Foster [EMAIL PROTECTED] wrote: Hi all I'm trying to pull the 5.1 source with the following cvsup file *default host=cvsup8.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5 *default compress src-all Doing cvsup it just hangs...doesn't seem to be writing... Have I done something stupid? Kind of.. :-) Where did you learn that 5.x already have the -STABLE branch? We only have -RELEASE and -CURRENT branches right now, but should have - STABLE branch after 5.2 released. Cheers, Mezz Rus -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSUP problems
On Thu, 31 Jul 2003 16:09:56 -0700 (PDT), Rus Foster [EMAIL PROTECTED] wrote: Kind of.. :-) Where did you learn that 5.x already have the -STABLE branch? We only have -RELEASE and -CURRENT branches right now, but should have - STABLE branch after 5.2 released. So CURRENT_5? No, if you want -CURRENT branch then it's '.' w/out quote. Check the more info: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs- tags.html Cheers, Mezz Rus -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
Now, it has been fixed today with the new 6.2.040 patch. Cheers, Mezz On Fri, 18 Jul 2003 13:24:30 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette [EMAIL PROTECTED] wrote: On Thursday 17 July 2003 08:14, David O'Brien wrote: I'm willing to commit it as such, but I'd like to hear more people's opinion. What I found so far: - gvim 6.2.21 works under 'twm' - gvim 6.2.21 works under 'kde 3.1' with SESSION_MANAGER unset - gvim 6.2.21 works under 'kde 3.1' if running on a remote machine tunneled through ssh's X11-redirection as reported by others: - gvim 6.2.21 works without patch 015 I looked at patch 015 but I'm not familiar with X11 SessionManagerProtocol - perhaps some others are able to analyze the correctness of that patch... I have sent to the vim-dev mailing list yesterday, because I got the same problem. I gave them with info of vim ran under gdb and explained about that 6.2.015 patch cause the crash. The author of VIM uses FreeBSD as well, so hope he will look into this problem. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Memory Mangement Problem in 5.1-RELEASE
On Thu, 24 Jul 2003 15:53:21 -0400, Bill Moran [EMAIL PROTECTED] wrote: Ahmed Al-Hindawi wrote: Hi, I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I seem to have memory mangament problems. The BIOS indicates I have 160, so does the BSD bootstrap program. When I launch GNOME 2.2 everythings is good as gold untill I open the System monitor program. It says that I have 149 Mb of RAM which is fine ( 4Mb of video..and the rest...god knows). I open every program I have and after 107Mb the machine starts to swap with about 50Mb left unused!! I recompliled the GENERIC kernal for the sake of it really (Im still an amature) I didn't mess with the configuration files or anything (I just don't know how!!). Is this normal or mismanagement of memory in the 5.1 version of the excellent FreeBSD kernel?? The mistake is in the way the Gnome System Monitor display the free memory. I just watched both 'top' and the System Monitor as I opened program after program until the system started swapping, and System monitor reports almost 100M free while top reported less than 10M. To _always_ have a little memory free is A Good Thing(tm). FreeBSD has some pretty advanced memory management that will start swapping _before_ the system runs out of RAM. However, the System Monitor's display of this is simply inaccurate. There was NOT 100M free when it started swapping on my system. Well, the 5.0, old -CURRENT and 4.8 have never touch the swap, until 5.1- CURRENT. My system has 256mb ram and it's always touch swap now. If I compile some stuff, sometime it will get around 300mb swap. Current, I only have Gnome 2.3.x and Opera running, so what my top looks like this: Mem: 85M Active, 29M Inact, 51M Wired, 4496K Cache, 35M Buf, 73M Free Swap: 512M Total, 79M Used, 433M Free, 15% Inuse But, I will remove the Gnome System Monitor applet, then reboot and see how it goes for the whole afternoon. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Memory Mangement Problem in 5.1-RELEASE
On Thu, 24 Jul 2003 16:46:12 -0400, Bill Moran [EMAIL PROTECTED] wrote: Jeremy Messenger wrote: On Thu, 24 Jul 2003 15:53:21 -0400, Bill Moran [EMAIL PROTECTED] wrote: Ahmed Al-Hindawi wrote: Hi, I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I seem to have memory mangament problems. The BIOS indicates I have 160, so does the BSD bootstrap program. When I launch GNOME 2.2 everythings is good as gold untill I open the System monitor program. It says that I have 149 Mb of RAM which is fine ( 4Mb of video..and the rest...god knows). I open every program I have and after 107Mb the machine starts to swap with about 50Mb left unused!! I recompliled the GENERIC kernal for the sake of it really (Im still an amature) I didn't mess with the configuration files or anything (I just don't know how!!). Is this normal or mismanagement of memory in the 5.1 version of the excellent FreeBSD kernel?? The mistake is in the way the Gnome System Monitor display the free memory. I just watched both 'top' and the System Monitor as I opened program after program until the system started swapping, and System monitor reports almost 100M free while top reported less than 10M. To _always_ have a little memory free is A Good Thing(tm). FreeBSD has some pretty advanced memory management that will start swapping _before_ the system runs out of RAM. However, the System Monitor's display of this is simply inaccurate. There was NOT 100M free when it started swapping on my system. Well, the 5.0, old -CURRENT and 4.8 have never touch the swap, until 5.1-CURRENT. My system has 256mb ram and it's always touch swap now. If I compile some stuff, sometime it will get around 300mb swap. Current, I only have Gnome 2.3.x and Opera running, so what my top looks like this: Well, the old YMMV applies, but I'm not seeing this kind of behaviour. I'm also not running 5.1-CURRENT, but 5.1-RELEASE, so it may be a newly introduced problem. The original poster didn't specify whether he was using -CURRENT or 5.1-RELEASE. It's in the subject, he said that he has 5.1-RELEASE. Mine is... === # uname -a FreeBSD mezz.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Jul 18 18:43:42 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 === I am planning to CVSup and do the another update of -CURRENT sometime this weekend. Mem: 85M Active, 29M Inact, 51M Wired, 4496K Cache, 35M Buf, 73M Free Swap: 512M Total, 79M Used, 433M Free, 15% Inuse Did something use most of the memory up to start the system swapping? If it started using swap while there was still 73M free, then that's new to me. Well, it still should not touch the swap since I have very few stuff running with 256mb ram. I just reboot and start with Gnome 2.3.x and Opera, then doing the update (compile/install) gnome-panel. Now, it's already use the swap in minutes and later hours I will get more mbs or swap. === last pid: 69694; load averages: 0.30, 0.73, 0.54up 0+00:26:23 15:56:49 49 processes: 2 running, 47 sleeping CPU states: 25.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 75.0% idle Mem: 123M Active, 21M Inact, 41M Wired, 5776K Cache, 35M Buf, 53M Free Swap: 512M Total, 3M Used, 512M Free === Cheers, Mezz But, I will remove the Gnome System Monitor applet, then reboot and see how it goes for the whole afternoon. I'm not saying that Gnome System Monitor is causing the problem, I'm just saying that it reports inaccurate numbers. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vim: Caught deadly signal BUS (after -current update with newgcc)
On Fri, 18 Jul 2003 19:36:50 +0200, Matthias Schuendehuette [EMAIL PROTECTED] wrote: On Thursday 17 July 2003 08:14, David O'Brien wrote: I'm willing to commit it as such, but I'd like to hear more people's opinion. What I found so far: - gvim 6.2.21 works under 'twm' - gvim 6.2.21 works under 'kde 3.1' with SESSION_MANAGER unset - gvim 6.2.21 works under 'kde 3.1' if running on a remote machine tunneled through ssh's X11-redirection as reported by others: - gvim 6.2.21 works without patch 015 I looked at patch 015 but I'm not familiar with X11 SessionManagerProtocol - perhaps some others are able to analyze the correctness of that patch... I have sent to the vim-dev mailing list yesterday, because I got the same problem. I gave them with info of vim ran under gdb and explained about that 6.2.015 patch cause the crash. The author of VIM uses FreeBSD as well, so hope he will look into this problem. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc-3.3 issues
On 17 Jul 2003 22:07:37 +0200, Peter Kadau [EMAIL PROTECTED] wrote: Hi ! s/gcc-3.3/ports/ issues and we are in agreement. alright, `port compile issues raised with the adoption of gcc-3.3' Patches to fix broken ports are welcome. Looking at AbiWord2 I suspect this has to be pushed upstream in some cases. OK, here is a - ahem - patch for aspell: --- prog/checker_string.hpp.origTue Sep 24 03:34:52 2002 +++ prog/checker_string.hpp Thu Jul 17 20:02:58 2003 @@ -5,6 +5,7 @@ // it at http://www.gnu.org/. #include stdio.h +#include g++/cassert #include aspell.h It works on my colleague's and my current and my stable. But maybe it's not the right way (tm) (to 'do-it) :-) But should I post that on -ports, -current or send it to the ports maintainer ? I'd rather avoid tracking -ports... snip But, this patch doesn't work/fix to me on yesterday -CURRENT. Here's what I get error following: = In file included from check_funs.hpp:10, from aspell.cpp:25: checker_string.hpp:8:23: g++/cassert: No such file or directory gmake[1]: *** [aspell.o] Error 1 gmake[1]: Leaving directory `/usr/ports/textproc/aspell/work/aspell- 0.50.3/prog' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/textproc/aspell. = Without this patch, I get error following: = checker_string.cpp: In member function `void CheckerString::replace(acommon::ParmString)': checker_string.cpp:113: error: `assert' undeclared (first use this function) checker_string.cpp:113: error: (Each undeclared identifier is reported only once for each function it appears in.) gmake[1]: *** [checker_string.o] Error 1 gmake[1]: Leaving directory `/usr/ports/textproc/aspell/work/aspell- 0.50.3/prog' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop in /usr/ports/textproc/aspell. *** Error code 1 = I am willing to test the patches if one of you have any. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc-3.3 issues
On 17 Jul 2003 22:47:02 +0200, Peter Kadau [EMAIL PROTECTED] wrote: Hi ! Sorry for that... That was my pre-get-rid-of-g++-workaround - how embarrassing ! Alexander pointed out in private (thank you), that this was a failure. I am willing to test the patches if one of you have any. Try that instead: --- prog/checker_string.hpp.origTue Sep 24 03:34:52 2002 +++ prog/checker_string.hpp Thu Jul 17 22:37:38 2003 @@ -5,6 +5,7 @@ // it at http://www.gnu.org/. #include stdio.h +#include assert.h #include aspell.h And *please* don't ask why I didn't use assert.h in the first place. *flush* Yes, that did it.. Thanks!! :-) Cheers, Mezz Cheers anyway Peter -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysutils/daemontools can't be install by NFS mount?
On Wed, 9 Jul 2003 12:46:37 +0300, Peter Pentchev [EMAIL PROTECTED] wrote: On Wed, Jul 09, 2003 at 03:30:50AM -0500, Jeremy Messenger wrote: Here's how I install sysutils/daemontools folowing: client# mount server:/usr/ports /usr/ports client# cd /usr/ports/sysutils/daemontools client# make It builds and start to halt forever at: env - /bin/sh rts.tests 21 | cat -v rts So, I tried to build in the NFS server machine without mount and it works fine. It will not work if I do that the steps above by mount. Here are two attaches of rts.tests and rts in case if anyone want to check.. I am not sure if it's NFS bug, I might missed option or it's just normal. Yes, this is a known problem: the tests run by daemontools seem to hang forever due to some problems with locking files over NFS. Ok, thanks.. Look forward for someone to fix this issue and I am willing to test the patch if one of you want me to test. I guess I should add a WITHOUT_TESTS knob to disable the test run. That's good idea and add the comment to explain about known issue of NFS file lock. Cheers, Mezz G'luck, Peter -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld failure - BFD - targmatch.h
On Thu, 19 Jun 2003 08:05:38 -0400, Michael W. Oliver [EMAIL PROTECTED] wrote: Hello -CURRENT, nice to meet you. My name is Michael Oliver, and I have been running FreeBSD for a few years, and am a BIG fan. I have recently decided to run -CURRENT on my laptop (Gateway SOLO-9300cl), and on my most recent buildworld (past -CURRENT upgrades have worked), I am having trouble. The buildworld fails as shown below: ... cc -O -pipe -mcpu=pentiumpro -D_GNU_SOURCE -I. - I/usr/src/gnu/usr.bin/binuti ls/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd - I/usr/src/gnu/usr.bin /binutils/libbfd/../libbfd/i386 - I/usr/src/gnu/usr.bin/binutils/libbfd/../.. /../../contrib/binutils/include - DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd - DBF D_VERSION=\20021127\ -DBFD_VERSION_DATE=20021127 - DBFD_VERSION_STRING=\2 .13.2 [FreeBSD] 2002-11-27\ -DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec - DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -Wsystem-headers -Werror -Wall -Wno-format-y2k -W - Wst rict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized - c /usr/src/contrib/binutils/bfd/targets.c -o targets.o In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: targmatch.h:7:1: null character(s) ignored targmatch.h:12:1: null character(s) ignored . . . targmatch.h:2033:1: null character(s) ignored targmatch.h:2037:1: null character(s) ignored *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. $ uname -a FreeBSD cyclops.gargantuan.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jun 15 14:11:56 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CYCLOPS i386 The last CVSUP of the source was done just before the buildworld, at about 21:00EDT on 2003-06-18. If any other information is required to troubleshoot this problem, please ask. Thanks in advance for your help, it is much appreciated. You should read in the /usr/src/UPDATING, an answer is right there if you CVSup your source very recently. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: src/sys/kern sched_ule.c (fwd)
On Tue, 17 Jun 2003 02:45:18 -0400 (EDT), Jeff Roberson [EMAIL PROTECTED] wrote: My last few commits, including this one, went a long way towards improving ULE's interactive responsiveness under heavy load. I was just able to do a make -j32 of my kernel while browsing the web with mozilla and commiting this change. Mozilla, my shell, cvs, etc. were all as responsive as they are on an unloaded system. Don't you think, the mplayer, xine and sound stuff might be better apps to test? Like, play the video and sound to see if they won't skip the frames or lag behind. Cheers, Mezz This is on a 2ghz laptop so your mileage may not be exactly the same. This is a significant improvement over the old state of things. If the interactive perf was chasing you away before, ULE should be much better now. Cheers, Jeff -- Forwarded message -- Date: Mon, 16 Jun 2003 23:39:51 -0700 (PDT) From: Jeff Roberson [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/kern sched_ule.c jeff2003/06/16 23:39:51 PDT FreeBSD src repository Modified files: sys/kern sched_ule.c Log: - Add a new function sched_interact_update() that scales back the sleep and run time. - Scale the sleep and run time back via sched_interact_update() in more places. This is to keep the statistic more accurate. - Charge a parent one tick for forking a child. - Add only the run time and not the sleep time to the parents kg when a thread exits. This allows us to give a penalty for having an expensive thread exit but does not give a bonus for having an interactive thread exit. - Change the SLP_RUN_THROTTLE to limit us to 4/5th and not 1/2. - Change the SLP_RUN_MAX to two seconds. This keeps bursty interactive applications like mozilla and openoffice in the interactive range even through expensive tasks. - Recalculate the slice after every sleep. This ensures that once a task has been marked interactive it only has a slice of 1 at the risk of giving tasks that sleep for a very brief period a longer time slice. Revision ChangesPath 1.42 +20 -23src/sys/kern/sched_ule.c -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xft-2.1.2 fails to build under 5.1 release
On 17 Jun 2003 12:31:58 -0700, Eli K. Breen [EMAIL PROTECTED] wrote: Xft-2.1.2 fails to build under 5.1 release - Any hints or should I try and get a hold of the Xft port maintainer? I installed Xft/XFree86-4 on the very fresh 5.1-CURRENT (/usr/local/ and /usr/X11R6/ were empty) and they built success this morning. Are you sure, you have everything update such as freetype, XFree86 and etc? If no, then use the portupgrade. P.S. It's wrong list, which should be -ports and -gnome (this is maintainer) list, so I am cc'ing to -gnome list. Cheers, Mezz cd /usr/ports/x11-fonts/Xft make ...results in... [...] cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/X11R6/include -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -O -pipe -mcpu=pentiumpro -MT xftdpy.lo -MD -MP -MF .deps/xftdpy.Tpo -c xftdpy.c -fPIC -o .libs/xftdpy.o xftdpy.c: In function `XftDefaultSubstitute': xftdpy.c:484: `FC_RGBA_UNKNOWN' undeclared (first use in this function) xftdpy.c:484: (Each undeclared identifier is reported only once xftdpy.c:484: for each function it appears in.) gmake[1]: *** [xftdpy.lo] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-fonts/Xft/work/xft-2.1.2' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/x11-fonts/Xft. -EKB- -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld failing in /usr/src/gnu/usr.bin/binutils/libbfd
On 13 Jun 2003 15:42:20 -0400, Fish [EMAIL PROTECTED] wrote: Hello list, I'm sure I've done something naughty as I've been seeing errors for a few days, but I've done some troubleshooting and I can't seem to find the place I shot myself in the foot. My system is current, and about a week old right now. Source was checked out this morning at about 8:30 A.M. EST. The output of uname -a follows. FreeBSD current 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Thu Jun 5 10:34:30 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURRENT-TWO i386 Leading up to this build I explicitly ran the following commands. cd /usr/src chflags -R noschg /usr/obj/* rm -rf /usr/obj/* make cleandir make cleandir make buildworld The tail end of the build error is below. I have the full build output if anyone would like to see it. Repeated builds, even in single-user mode, all show the same error. I have tried to ensure that nothing in /etc/make.conf is biting me, only a few things are defined, primarily CPUTYPE=i686. I usually run at CPUTYPE=p3 (as p4 builds broken code last I heard) but downgraded here to remove a possible source of error. CFLAGS and CXXFLAGS are not defined. cc -O -pipe -march=pentiumpro -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386 - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include -DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd - DBFD_VERSION=\20021127\ -DBFD_VERSION_DATE=20021127 - DBFD_VERSION_STRING=\2.13.2 [FreeBSD] 2002-11-27\ - DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec -DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -std=iso9899:1999 -Wsystem-headers -Werror -Wall - Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Wno-uninitialized -c /usr/src/contrib/binutils/bfd/stab-syms.c -o stab-syms.o cc -O -pipe -march=pentiumpro -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386 - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include -DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd - DBFD_VERSION=\20021127\ -DBFD_VERSION_DATE=20021127 - DBFD_VERSION_STRING=\2.13.2 [FreeBSD] 2002-11-27\ - DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec -DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -std=iso9899:1999 -Wsystem-headers -Werror -Wall - Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Wno-uninitialized -c /usr/src/contrib/binutils/bfd/stabs.c -o stabs.o cc -O -pipe -march=pentiumpro -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386 - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include -DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd - DBFD_VERSION=\20021127\ -DBFD_VERSION_DATE=20021127 - DBFD_VERSION_STRING=\2.13.2 [FreeBSD] 2002-11-27\ - DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec -DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -std=iso9899:1999 -Wsystem-headers -Werror -Wall - Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Wno-uninitialized -c /usr/src/contrib/binutils/bfd/syms.c -o syms.o cc -O -pipe -march=pentiumpro -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386 - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include -DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec - I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd - DBFD_VERSION=\20021127\ -DBFD_VERSION_DATE=20021127 - DBFD_VERSION_STRING=\2.13.2 [FreeBSD] 2002-11-27\ - DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec -DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -std=iso9899:1999 -Wsystem-headers -Werror -Wall - Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer- arith -Wno-uninitialized -c /usr/src/contrib/binutils/bfd/targets.c -o targets.o In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: targmatch.h:7:1: null character(s) ignored targmatch.h:12:1: null character(s) ignored targmatch.h:16:1: null character(s) ignored targmatch.h:20:1: null character(s) ignored targmatch.h:24:1: null character(s) ignored hundreds of lines between here have been snipped targmatch.h:2024:1: null character(s) ignored
Re: Interest in nvidia-driver debugging on 5-*
On 13 Jun 2003 05:11:34 +, Samy Al Bahra [EMAIL PROTECTED] wrote: Hey, I believe the fix is as simple as saving and restoring %gs in the nVidia driver, and/or not letting the nVidia use %gs at all (segment registers generally belong to the OS, in any case, and stealing a CPU register of any kind for exclusive use of a driver is a pig trick). Please take a look at http://www.minion.de/ Christian Zander has written a patch to deal with the gs restoration problem and other issues. It is well tested and adopted. Maxime Henrion has also written several patches which may be found in the ports system (x11/nvidia-driver). The %gs register issue patch for linux_sysvec.c has been committed in the source tree like a month ago or so, btw. :-) Cheers, Mezz I think Terry is jumping to conclusions on what Evan's problem could be. I have this seen this cause application to crash at exit (if using OpenGL) but never a crash in kernel-space from the nVidia drivers. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Buildworld failed by binutils/bfd/targets.c:1092..
I just CVSup'ed at the phk's lastest committed on UPDATING/CDD stuff. I did the buildworld and it has been failed. == /usr/src/contrib/binutils/bfd/targets.c -o targets.o In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: targmatch.h:7:1: null character(s) ignored targmatch.h:12:1: null character(s) ignored targmatch.h:16:1: null character(s) ignored targmatch.h:20:1: null character(s) ignored targmatch.h:24:1: null character(s) ignored targmatch.h:28:1: null character(s) ignored targmatch.h:32:1: null character(s) ignored targmatch.h:36:1: null character(s) ignored targmatch.h:40:1: null character(s) ignored targmatch.h:44:1: null character(s) ignored targmatch.h:48:1: null character(s) ignored targmatch.h:51:1: null character(s) ignored targmatch.h:55:1: null character(s) ignored targmatch.h:58:1: null character(s) ignored targmatch.h:62:1: null character(s) ignored [...] targmatch.h:2024:1: null character(s) ignored targmatch.h:2028:1: null character(s) ignored targmatch.h:2033:1: null character(s) ignored targmatch.h:2037:1: null character(s) ignored *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 == Any hint? Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia driver problems
On 09 Jun 2003 23:22:55 +0200, Sascha Holzleiter [EMAIL PROTECTED] wrote: Hello, just got these messages with a today -CURRENT and the nvidia driver compiled with FREEBSD_AGP: snip Is this just a the nvidia driver isn't officially for the 5.x series issue or shouldn't this happen at all? If I compile the module without FREEBSD_AGP and use it with the debugging kernel the system core-dumps. Without debugging activated in the kernel this is running quite stable... Disable the debug is always the solution to me so far. Let me quote it from http://www.minion.de/nvidia.html : = Potential FreeBSD specific sources of instabilities are such kernel configurations that enable debugging or aggressive optimizations. You should keep this in mind if you are seeing seemingly random panics. = Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld failed by binutils/bfd/targets.c:1092..
On Mon, 9 Jun 2003 14:45:01 -0700, Marcel Moolenaar [EMAIL PROTECTED] wrote: On Mon, Jun 09, 2003 at 04:18:46PM -0500, Jeremy Messenger wrote: I just CVSup'ed at the phk's lastest committed on UPDATING/CDD stuff. I ^^^I mean, CCD.. did the buildworld and it has been failed. == /usr/src/contrib/binutils/bfd/targets.c -o targets.o In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: targmatch.h:7:1: null character(s) ignored targmatch.h:12:1: null character(s) ignored targmatch.h:16:1: null character(s) ignored targmatch.h:20:1: null character(s) ignored targmatch.h:24:1: null character(s) ignored targmatch.h:28:1: null character(s) ignored targmatch.h:32:1: null character(s) ignored targmatch.h:36:1: null character(s) ignored targmatch.h:40:1: null character(s) ignored targmatch.h:44:1: null character(s) ignored targmatch.h:48:1: null character(s) ignored targmatch.h:51:1: null character(s) ignored targmatch.h:55:1: null character(s) ignored targmatch.h:58:1: null character(s) ignored targmatch.h:62:1: null character(s) ignored [...] targmatch.h:2024:1: null character(s) ignored targmatch.h:2028:1: null character(s) ignored targmatch.h:2033:1: null character(s) ignored targmatch.h:2037:1: null character(s) ignored *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 == Any hint? Broken sed(1), I think. Has been fixed last week. Yes, I remember it's fixed but I didn't remember/know that broke sed caused this.. If you did a -DNOCLEAN build, don't. Otherwise, build and install sed first. Build and install sed first did the trick. Thanks! Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression: Playing QT files from mplayer stopped working in 5.1
On Sat, 7 Jun 2003 22:28:29 +0200, Arjan van Leeuwen [EMAIL PROTECTED] wrote: Hi, Since a short time (don't know exactly when it happened) it's not possible anymore to play Quicktime files (.mov) with mplayer on 5.1- CURRENT. It has to be a change in -CURRENT, I haven't updated mplayer. When trying to play a QT file, mplayer outputs: It happened on me too, so to other users over at bsdforums.org.. I don't have the problem with 5.0-CURRENT, until I upgraded to 5.1-CURRENT and now xine and mplayer will not work with the quicktime anymore. They both will crash with the dump core. I will have to turn on the debug and post the info of run them under gdb to see if it will help. I am cc'ing to the maintainer of xine and mplayer here, btw.. Cheers, Mezz win32 libquicktime loader (c) Sascha Sommer Standard init done you may now call supported functions loader_init DONE??? loader_init DONE! External func COMCTL32.dll:17 External func COMCTL32.dll:16 QuickTime5 DLLs found QuickTime.qts patched!!! old entry=0x62924c30 theQuickTimeDispatcher catched - 0x62924c30 Win32 Warning: Accessed uninitialized Critical Section (0x62b7fcd0)! WARNING! Invalid Ptr handle! Win32 Warning: Accessed uninitialized Critical Section (0x62b7fcb8)! MPlayer interrupted by signal 11 in module: init_audio_codec - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. For details, see DOCS/bugreports.html#crash.b. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug. Best regards, Arjan -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA ACPI power management controller
On Thu, 5 Jun 2003 16:14:25 +0200, Alexander Leidinger [EMAIL PROTECTED] wrote: Hi, is there a way to teach our ACPI implementation about [EMAIL PROTECTED]:7:4: class=0x068000 card=0x chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class= bridge subclass = PCI-unknown I own the same chipest here, which it is support in 4.x and no longer in 5.x.. :-( Note that, I only check in the 5.x's NOTES and haven't tried to put some opinion from 4.x to 5.x yet. I don't know if it will work. In 4.x, you just add in the kernel config following: === # VT82C686A/B ACPI Power Management Controller device smbus device viapm device iicbus device iicbb device ic device iic device iicsmb === I would like to see someone to bring 4.x drivers to 5.x as well. Too bad, I know nothing with C, but just a hello world. Cheers, Mezz Bye, Alexander. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA ACPI power management controller
On Thu, 05 Jun 2003 13:10:35 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: On Thu, 5 Jun 2003 16:14:25 +0200, Alexander Leidinger [EMAIL PROTECTED] wrote: Hi, is there a way to teach our ACPI implementation about [EMAIL PROTECTED]:7:4: class=0x068000 card=0x chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class= bridge subclass = PCI-unknown Oh, it seems to be little different but I have the same 'VT82C686A/B ACPI Power Management Controller'.. === [EMAIL PROTECTED]:7:4: class=0x0c0500 card=0x30571106 chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class= serial bus -- diff here.. subclass = SMBus -- diff here.. === Cheers, Mezz I own the same chipest here, which it is support in 4.x and no longer in 5.x.. :-( Note that, I only check in the 5.x's NOTES and haven't tried to put some opinion from 4.x to 5.x yet. I don't know if it will work. In 4.x, you just add in the kernel config following: === # VT82C686A/B ACPI Power Management Controller device smbus device viapm device iicbus device iicbb device ic device iic device iicsmb === I would like to see someone to bring 4.x drivers to 5.x as well. Too bad, I know nothing with C, but just a hello world. Cheers, Mezz Bye, Alexander. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA ACPI power management controller
On Thu, 5 Jun 2003 20:56:50 +0200, Michael Nottebrock [EMAIL PROTECTED] wrote: On Thursday 05 June 2003 20:10, Jeremy Messenger wrote: I own the same chipest here, which it is support in 4.x and no longer in 5.x.. :-( Note that, I only check in the 5.x's NOTES You didn't check in the right NOTES then. 5-CURRENT has different NOTES files, one general, machine independent and several smaller others for each platform. The machine independent is in /usr/src/sys/conf, the others are in /usr/src/sys/ARCH/conf. Do'h! You are right that I didn't check in /usr/src/sys/conf/.. It does exist and I am doing the rebuild kernel right now.. Thanks.. It's only thing that I dislike about 5.x is example configure files move to the different places (ie: NOTES, make.conf and etc).. I will get use to them, thought.. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA ACPI power management controller
On Thu, 05 Jun 2003 13:56:15 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: On Thu, 5 Jun 2003 20:56:50 +0200, Michael Nottebrock [EMAIL PROTECTED] wrote: On Thursday 05 June 2003 20:10, Jeremy Messenger wrote: I own the same chipest here, which it is support in 4.x and no longer in 5.x.. :-( Note that, I only check in the 5.x's NOTES You didn't check in the right NOTES then. 5-CURRENT has different NOTES files, one general, machine independent and several smaller others for each platform. The machine independent is in /usr/src/sys/conf, the others are in /usr/src/sys/ARCH/conf. Do'h! You are right that I didn't check in /usr/src/sys/conf/.. It does exist and I am doing the rebuild kernel right now.. Thanks.. Here's the result: # dmesg | grep via viapropm0: SMBus I/O base at 0x5000 viapropm0: VIA VT82C686A Power Management Unit port 0x5000-0x500f at device 7.4 on pci0 viapropm0: failed to enable port mapping! viapropm0: could not allocate bus space device_probe_and_attach: viapropm0 attach returned 6 [EMAIL PROTECTED]:7:4: class=0x0c0500 card=0x30571106 chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class= serial bus subclass = SMBus I don't know what the errors mean.. Cheers, Mezz It's only thing that I dislike about 5.x is example configure files move to the different places (ie: NOTES, make.conf and etc).. I will get use to them, thought.. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Wed, 4 Jun 2003 08:54:07 -0400 (EDT), Matthew N. Dodd [EMAIL PROTECTED] wrote: On Tue, 3 Jun 2003, Jeremy Messenger wrote: # ./test-libmap /usr/X11R6/bin/ggv libc_r.so.5 Lookup of libc_r.so.5 for /usr/X11R6/bin/ggv - libc_r.so.5 Looks like its working to me. # ./test-libmap /usr/X11R6/bin/ggv libthr.so.1 [...etmpy...] Right, there was on mapping found. So this isn't a libmap.conf issue. I don't understand, so how do you explain about ldd? If I change the main library and the ldd of ggv will change corrrect the link. If I put ggv point to a library by use [] and the ldd shows incorrect. Also, the ggv will crash at all the time, because it needs to be libc_r; not libthr. So, are you suggest that there's something wrong in somewhere beside libmap.conf? Thanks! Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Wed, 04 Jun 2003 13:05:26 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: On Wed, 4 Jun 2003 08:54:07 -0400 (EDT), Matthew N. Dodd [EMAIL PROTECTED] wrote: On Tue, 3 Jun 2003, Jeremy Messenger wrote: # ./test-libmap /usr/X11R6/bin/ggv libc_r.so.5 Lookup of libc_r.so.5 for /usr/X11R6/bin/ggv - libc_r.so.5 Looks like its working to me. # ./test-libmap /usr/X11R6/bin/ggv libthr.so.1 [...etmpy...] Right, there was on mapping found. So this isn't a libmap.conf issue. I don't understand, so how do you explain about ldd? If I change the main library and the ldd of ggv will change corrrect the link. If I put ggv point to a library by use [] and the ldd shows incorrect. Also, the ggv will crash at all the time, because it needs to be libc_r; not libthr. So, are you suggest that there's something wrong in somewhere beside libmap.conf? Nevermind, I think you are right it does work. Because, I did the test on mplayer by install it. It does link mplayer to libc_r correct, while not ggv. Looks like I will have to chase on ggv to find what ggv is depending on and get them link to libc_r.. This must be reason why it doesn't work. Thanks! Cheers, Mezz Thanks! Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Wed, 4 Jun 2003 16:55:35 -0400 (EDT), Matthew N. Dodd [EMAIL PROTECTED] wrote: On Wed, 4 Jun 2003, Jeremy Messenger wrote: Nevermind, I think you are right it does work. Because, I did the test on mplayer by install it. It does link mplayer to libc_r correct, while not ggv. Looks like I will have to chase on ggv to find what ggv is depending on and get them link to libc_r.. This must be reason why it doesn't work. Thanks! 'ldd -a' is usefule for finding this out. Sweet, thanks! This is what I need, which it made easier to locate the library that use libc_r.. I have found two that need to be link to libc_r instead libthr so far.. /usr/X11R6/lib/libgnomeui-2.so.300 /usr/local/lib/libgthread-2.0.so.200 -- This one, I might need to report at -threads. Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
libmap.conf has the bug or not work correct?
I am trying to get ggv link against libc_r instead libthr, but it doesn't work as expect.. Maybe, I must have done something wrong? # cat /etc/libmap.conf libc_r.so.5 libthr.so.1 libc_r.so libthr.so [/usr/X11R6/bin/ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so # uname -a FreeBSD personal.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Jun 2 20:23:45 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 I even rebuilt rtld-elf (WITH_LIBMAP=yes in /etc/make.conf) and ggv then reinstall them, but no luck. The ggv is still linking to libthr instead libc_r.. Also, ggv isn't only one app that I tried. I did tried with gst- register and no luck to change the link to libc_r. # ldd /usr/X11R6/bin/ggv | grep libc libc.so.5 = /usr/lib/libc.so.5 (0x28a68000) libc_r.so.5 = /usr/lib/libthr.so.1 (0x28b49000) Do anyone have any hint? Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Tue, 3 Jun 2003 18:01:52 -0700, David P. Reese Jr. [EMAIL PROTECTED] wrote: On Tue, Jun 03, 2003 at 03:50:00PM -0500, Jeremy Messenger wrote: I am trying to get ggv link against libc_r instead libthr, but it doesn't work as expect.. Maybe, I must have done something wrong? Make sure that you have rev 1.6 of src/libexec/rtld-elf/libmap.c. It fixes a bug in the libmap.conf parsing code. I downgrade from 1.7 - 1.6 and the problem is still there. I CVSup'ed yesterday around 30 to 45 minutes before my 'uname -a' in the bottom. Cheers, Mezz # cat /etc/libmap.conf libc_r.so.5 libthr.so.1 libc_r.so libthr.so [/usr/X11R6/bin/ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so # uname -a FreeBSD personal.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Jun 2 20:23:45 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 I even rebuilt rtld-elf (WITH_LIBMAP=yes in /etc/make.conf) and ggv then reinstall them, but no luck. The ggv is still linking to libthr instead libc_r.. Also, ggv isn't only one app that I tried. I did tried with gst-register and no luck to change the link to libc_r. # ldd /usr/X11R6/bin/ggv | grep libc libc.so.5 = /usr/lib/libc.so.5 (0x28a68000) libc_r.so.5 = /usr/lib/libthr.so.1 (0x28b49000) Do anyone have any hint? Cheers, Mezz -- bsdforums.org 's moderator, mezz. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Tue, 03 Jun 2003 21:04:11 -0500, Jeremy Messenger [EMAIL PROTECTED] wrote: On Tue, 3 Jun 2003 18:01:52 -0700, David P. Reese Jr. [EMAIL PROTECTED] wrote: On Tue, Jun 03, 2003 at 03:50:00PM -0500, Jeremy Messenger wrote: I am trying to get ggv link against libc_r instead libthr, but it doesn't work as expect.. Maybe, I must have done something wrong? Make sure that you have rev 1.6 of src/libexec/rtld-elf/libmap.c. It fixes a bug in the libmap.conf parsing code. I downgrade from 1.7 - 1.6 and the problem is still there. I CVSup'ed yesterday around 30 to 45 minutes before my 'uname -a' in the bottom. Here's more info It works if my libmap.conf looks like: # cat /etc/libmap.conf libc_r.so.5 libc_r.so.5 # Before was libthr libc_r.so libc_r.so # ^ [/usr/X11R6/bin/ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so Result: # ldd /usr/X11R6/bin/ggv | grep libc libc.so.5 = /usr/lib/libc.so.5 (0x28a68000) libc_r.so.5 = /usr/lib/libc_r.so.5 (0x28b49000) It seems like the [/path/to/exec] and [exec] don't work? Cheers, Mezz # cat /etc/libmap.conf libc_r.so.5 libthr.so.1 libc_r.so libthr.so [/usr/X11R6/bin/ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so # uname -a FreeBSD personal.mezzweb.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Jun 2 20:23:45 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDRULZ i386 I even rebuilt rtld-elf (WITH_LIBMAP=yes in /etc/make.conf) and ggv then reinstall them, but no luck. The ggv is still linking to libthr instead libc_r.. Also, ggv isn't only one app that I tried. I did tried with gst-register and no luck to change the link to libc_r. # ldd /usr/X11R6/bin/ggv | grep libc libc.so.5 = /usr/lib/libc.so.5 (0x28a68000) libc_r.so.5 = /usr/lib/libthr.so.1 (0x28b49000) Do anyone have any hint? Cheers, Mezz -- bsdforums.org 's moderator, mezz. -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libmap.conf has the bug or not work correct?
On Tue, 3 Jun 2003 22:51:59 -0400 (EDT), Matthew N. Dodd [EMAIL PROTECTED] wrote: On Tue, 3 Jun 2003, Jeremy Messenger wrote: It seems like the [/path/to/exec] and [exec] don't work? ftp://ftp.jurai.net/users/winter/libmap-test.tar Untar that in src/libexec/rtld-elf/ cd test/ make ./test-libmap /path/to/exec library-name # ./test-libmap /usr/X11R6/bin/ggv libc_r.so.5 Lookup of libc_r.so.5 for /usr/X11R6/bin/ggv - libc_r.so.5 # ./test-libmap /usr/X11R6/bin/ggv libthr.so.1 [...etmpy...] # cat /etc/libmap.conf libc_r.so.5 libthr.so.1 libc_r.so libthr.so [/usr/X11R6/bin/ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [ggv] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so Cheers, Mezz -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
