Re: Time jumping on both 4.x and 5.x ...
On Saturday 29 November 2003 11:43, Kris Kennaway wrote: > > I didn't think 4.x SMP kernels could run on a UP machine. It's a pretty decent Pentium4 Mobo, I guess it meets the requirements for an SMP-Board running one CPU. From dmesg: Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2421.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 536805376 (524224K bytes) avail memory = 515989504 (503896K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 17 -> irq 10 IOAPIC #0 intpin 18 -> irq 3 IOAPIC #0 intpin 19 -> irq 5 FreeBSD/SMP: Multiprocessor motherboard: 1 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 Warning: Pentium 4 CPU: PSE disabled bktr_mem: memory holder loaded Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00f7c80 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: Time jumping on both 4.x and 5.x ...
On Saturday 29 November 2003 09:19, Kris Kennaway wrote: > > Are all affected machines multi-processor? None. Both are i386 UP (although the 4.9-RELEASE box is running an SMP-enabled kernel). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: Time jumping on both 4.x and 5.x ...
On Saturday 29 November 2003 05:57, Dag-Erling Smørgrav wrote: > "Marc G. Fournier" <[EMAIL PROTECTED]> writes: > > as to ntpd/timed ... don't run either ... run ntpdate twice a day (11:59 > > and 23:59) > > Don't Do That. It will lead to all kinds of trouble that will take > you ages to figure out. Really, ntpd is so ridiculously easy to set > up (especially if you already have ntpdate working) that there is no > reason not to use it. FWIW, it can reproduce this on two machines (one 4.9-RELEASE, one 5.1-RELEASE) which both run ntpd. Takes some 10 minutes on both before the first steps backwards turn up. Unfortunately, both machines aren't very good datapoints because both have pretty customized kernels and have -Os and -march optimized worlds/kernels... Both have kern.timecounter.hardware: ACPI-fast, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: HEADS UP: /bin and /sbin are now dynamically linked
On Friday 28 November 2003 21:03, Tim Kientzle wrote: > David O'Brien wrote: > > On Wed, Nov 26, 2003 at 10:37:48AM -0800, Tim Kientzle wrote: > >>and [/usr/bin/ftp] doesn't support HTTP. > > > > $ /usr/bin/ftp http://www.theregister.co.uk/content/6/32524.html > > Requesting http://www.theregister.co.uk/content/6/32524.html > > 100% |*| 22559 35.32 KB/s > > 00:00 ETA 22559 bytes retrieved in 00:00 (35.28 KB/s) > > Wow! Learn something new every day around here. Well, it's a rather new ftp(1), this feature came with lukemftp replacing the former ftp. I believe Microsoft Windows still ships the old ftp client thought. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: if_tun failed to register
On Wednesday 05 November 2003 23:47, Antoine Jacoutot wrote: > On Wednesday 05 November 2003 23:25, Brian Lynn wrote: > > will be run at startup if you have any ifconfig_tun* lines in rc.conf. > > You can see if ifconfig is the culprit by booting single-user and doing > > ifconfig tun0 (it is only the first attempt that gives the error message > > in question). If so, the following (Untested!) patch would presumably > > But I don't have any "ifconfig_tun*" in rc.conf; although I do have the > ppp_enable set on. ppp will bring up a tun interface. Btw, what I was trying to say earlier is that this all really isn't a problem. If you compile tun into the kernel, this is what will be used and if you don't, the autoloaded module will be used. This is probably the reason nobody bothered to fix this yet. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: if_tun failed to register
On Wednesday 05 November 2003 20:52, Antoine Jacoutot wrote: > On Wednesday 05 November 2003 18:37, you wrote: > > It's been there for quite a while, I see that behaviour in 5.1-RELEASE, > > too. > > Thanks, I'm happy I'm not the only one seeing this :) > It looks like ppp does not get compiled in the kernel either... :( FWIW, tun _is_ in the kernel if you compile it in, but gets loaded a second time. The module which gets loaded isn't actually used. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: if_tun failed to register
On Tuesday 04 November 2003 15:32, Antoine Jacoutot wrote: > Matteo Riondato wrote: > >>Well, it did not change anything :( > >>What is really strange is that "tun" is compiled in the kernel, but the > >>module is started anyway ??? > > > > I had the same problem last year and solved it by removing > > device tun > > from the kernel configuration file. > > Yes, I though about it. But still, it is a strange bug and I cannot > believe I (well, and you :) ) am the only one seeing this. It's been there for quite a while, I see that behaviour in 5.1-RELEASE, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: Forward: HEADS UP! Default value of ip6_v6only changed
I wrote: I find the notion of making people "fix" their software to not rely on RFC-defined behaviour problematic. I'm actually glad to see NetBSD reversed their unfortunate decision regarding the default (and OpenBSD's stunt of not even providing a knob is very evil indeed). I understand that itojun would like to see this aspect of RFC2553 amended. I don't know what the prospects of this happening are on the IETF level. FWIW, I wonder if the publication of http://bulk.fefe.de/scalability/, especially the paragraph: "OpenBSD also caused a lot of grief on the IPv6 front. The OpenBSD guys intentionally broke their IPv6 stack to not allow IPv4 connections to and from IPv6 sockets using the IPv4 mapped addresses that the IPv6 standard defines for thus purpose. I find this behaviour of pissing on internet standards despicable and unworthy of free operating systems." has inspired NetBSD's move. :-) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: PGP signature
Re: Forward: HEADS UP! Default value of ip6_v6only changed
Christian Weisgerber wrote: If we ship with a default of v6only off, then people will not fix software to open two sockets. This in turn means that turning v6only on will break this software. I find the notion of making people "fix" their software to not rely on RFC-defined behaviour problematic. I'm actually glad to see NetBSD reversed their unfortunate decision regarding the default (and OpenBSD's stunt of not even providing a knob is very evil indeed). I understand that itojun would like to see this aspect of RFC2553 amended. I don't know what the prospects of this happening are on the IETF level. Not too bad, IMHO. The IETF really is the place for this decision to be made and the knob should reflect current standards. Flipping the default when a revised RFC is published would be the right thing to do. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: PGP signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 22:52, Mike Makonnen wrote: > As far as I know text attachments are still accepted. So, if the > attachment is being stripped either you are sending gziped/uuencoded > attachments or your MUA is not describing it as text. Well, it was described as text/x-diff. Not an officially IANA registered MIME-type, but text/* nonetheless... perhaps the mailing list manager should be configured to be a little less anal. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: Initial list of ports that fail due to -pthread
On Wednesday 24 September 2003 19:36, Bruce M Simpson wrote: > On Wed, Sep 24, 2003 at 06:14:52PM +0200, Michael Nottebrock wrote: > Content-Description: signed data > > > On Wednesday 24 September 2003 04:18, Kris Kennaway wrote: > > > icecast-1.3.12_1 > > > > I don't have a -CURRENT machine to test with. I don't mind the port > > marked BROKEN, since it's unsupported abandonware and due for deorbit > > anyway. > > I object. The Icecast team have barely even documented how to configure > Icecast 2 nor have they provided a means of cleanly migrating to the new > XML configuration format. > > SPC is one organization who make a lot of use of this particular port, I > am sure there are others. > > If you must kill it off at least give us time to bury it properly. Don't worry, a port deorbit takes a very long time and right now I'm merely thinking out loud, there's no countdown started yet. But keep in mind that this doesn't change the facts: Icecast 1 _is_ unsupported abandonware, and it is by any means not too early to start investigating the migration to other software. That said, if you have a fix going for the -pthread issue on -CURRENT, I'd appreciate (and commit). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: Initial list of ports that fail due to -pthread
On Wednesday 24 September 2003 04:18, Kris Kennaway wrote: > icecast-1.3.12_1 I don't have a -CURRENT machine to test with. I don't mind the port marked BROKEN, since it's unsupported abandonware and due for deorbit anyway. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: HEADSUP: PFIL_HOOKS/ipfilter changes
Sam Leffler wrote: It was not "due for 5.0" or any subsequent release. It was requested by certain developers and I requested that they demonstrate that adding it to the GENERIC system would not noticeably impact non-PFIL_HOOKS users. I intend to convert certain network subsystems to use PFIL_HOOKS instead of their (current) adhoc techniques. This will mean that PFIL_HOOKS will be a necessary part of the system and so will be in the GENERIC kernel. PFIL_HOOKS has been necessary in order to use the ipfilter kernel module, since 5.0-R and before, IIRC. The fact that a kernel customization and recompile was needed because of the missing PFIL_HOOKS in GENERIC for two releases in a row is a bug, and it ought to be fixed. (On a related note, the ipfilter kernel module itself is still built without IPV6 support - is there a particular reason for this?) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: PFIL_HOOKS/ipfilter changes
Sam Leffler wrote: Could we add PFIL_HOOKS to GENERIC, while we're at it? Please? Eventually this will happen. Almost certainly in time for 5.2. It was due for 5.0-RELEASE, it hasn't made it in for 5.1-RELEASE and post 5.1-R reminders have been ignored on this list as well. This is starting to become rather ridiculous. Why not just do it? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: PFIL_HOOKS/ipfilter changes
Sam Leffler wrote: FreeBSD src repository Modified files: sys/net bridge.c pfil.h pfil.c sys/netinet ip_input.c ip_output.c ip_var.h sys/netinet6 ip6_forward.c ip6_input.c ip6_output.c ip6_var.h ip6protosw.h sys/sys param.h protosw.h sys/modules/bridge Makefile Log: o update PFIL_HOOKS support to current API used by netbsd o revamp IPv4+IPv6+bridge usage to match API changes o remove pfil_head instances from protosw entries (no longer used) o add locking o bump FreeBSD version for 3rd party modules Heavy lifting by: "Max Laier" <[EMAIL PROTECTED]> Supported by: FreeBSD Foundation Obtained from: NetBSD (bits of pfil.h and pfil.c) Could we add PFIL_HOOKS to GENERIC, while we're at it? Please? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)
Daniel Eischen wrote: I feel that a FreeBSD that manages to break so many existing configure-scripts and build systems is degraded in usefulness. Please, this is -current. If you want less pain then stick with -stable and you won't be annoyed by the -pthread removal. Perhaps I should make it clear that, personally, I'm NOT very much annoyed. I know my way around in ports@, I actually do know what -CURRENT means and I have no problem with using the ports-collection exclusively instead of quickly compiling my own stuff right there in my user-account. The problem is just that this -CURRENT is supposed to be -STABLE rather soon, as we all know (I think the RE status for HEAD is 'Semi-Frozen', too). There are many users out there with 5.1-Release installed which have at best only a very distant clue about the fact they're running an "early adopter's release" and they won't be upgrading to 4.9-R or 4.10-R when the time arrives. For someone coming from 5.0-R or 5.1-R, the new "necessary evil behaviour" of cc/c++, be it -pedantic or -pthread, will be totally unexpected. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)
Steve Kargl wrote: Why? The portmgr can tag the ports collection at any point in time before or after the -pthread deprecation date. Steve, ports-freeze dates are set and published ahead of time just as dates for releases are. It's obviously not a good thing to have to try and be very conservative with commits to ports (in order to have a maximum number of them working for the next 4.x release) while at the same time there is loud demand for fixing a big number of them for -CURRENT. Don't bother telling me I'm whining, pointing at the handbook again and saying "don't expect anything to work on -CURRENT at any given time", you're shooting the messenger. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)
Steve Kargl wrote: I have no problems in building the traditional C "hello world" program with "cc -pedantic". You're right about that, you'll need a C++ hello world (, cout). This is in the archives anyway and (should be) well known. (why could this change not have been made _after_ 4.9 is out the door, btw.? Or before 5.0-R FWIW.) 4.9 and 5.0-R are independent branch. By your logic we should wait to 4.10 or 4.11 or 4.12 or ... before any substantial change can be made to -CURRENT. The point is that is isn't wise to commit a change like the -pthread deprecation that breaks many ports just before a ports-freeze. The reason gcc-3.3.1 was committed before 5.0-R should be fairly obvious. I was concerned with the -pthread deprecation. I feel that a FreeBSD that manages to break so many existing configure-scripts and build systems is degraded in usefulness. Please see the Handbook for the distinction between -CURRENT and -STABLE. Oh please. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Quo vadis, -CURRENT? (recent changes to cc & compatibility)
Sorry if this sounds a bit flame-ish, but the way I see it we now have a system compiler in -CURRENT that doesn't even compile a hello world if -pedantic is specified and breaks with lots of existing software out there that tries to use a threads library because -pthread errors out (why could this change not have been made _after_ 4.9 is out the door, btw.? Or before 5.0-R FWIW.) Are we expecting people to be able to compile software directly from the commandline at all these days and in the future on a (stable) FreeBSD-5? Is the decision criterion for making acceptable changes to core system components that we can somehow make 3rd party software compiling via ports-collection hacks? I feel that a FreeBSD that manages to break so many existing configure-scripts and build systems is degraded in usefulness. - ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 18:03, Daniel Eischen wrote: > On Sat, 23 Aug 2003, Larry Rosenman wrote: > > Prior to Thursday, it worked just fine. > > I can't explain it. Someone is going to have to debug konsole and > figure out what is going on. Done. Turns out this change ( http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/gethostname.c.diff?r1=1.3&r2=1.4&f=h ) was the cause for Konsole to abort(). The case of gethostbyname returning ENOMEM is caught, ENAMETOOLONG isn't. A fix will go into the kdebase port in the next few days, along with a bunch of other fixes. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Sunday 24 August 2003 00:13, Simon L. Nielsen wrote: > FYI, this is actually documented: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#E > RESOURCES-MAILFILTERING Thanks! > If you think 'text/x-diff' should be allowed, you can ask [EMAIL PROTECTED] > (If get it added to the allowed list, please let me or -doc know so the > handbook can be updated.) Will do. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 16:52, I wrote: > Incidentally, Adriaan de Groot just dug up a set of patches for konsole & > konsole_grantpty, I quickly adapted those for the kdebase port. They apply, > but I'm still compiling kdebase with those myself, so beware, they might > turn konsole into a Teletubbie FWIW (although Adriaan says they work okay > for him, so there). Find the patch attached to this message. Or rather, find it at http://lofi.dyndns.org/~lofi/patch-konsole , the attachment has been stripped. BTW: Is there a place or a person that has a list of which mailing lists will actually accept mails with attachments these days? And which of the lists is subscriber only or not? It used to be very easy (outside-posts work everywhere, attachments work everwhere), but I guess times have changed. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 16:52, Michael Nottebrock wrote: > Incidentally, Adriaan de Groot just dug up a set of patches for konsole & > konsole_grantpty, I quickly adapted those for the kdebase port. They apply, > but I'm still compiling kdebase with those myself Just finished. They work fine on my 4.8-STABLE machine here. When I make konsole_grantpty suid root as advised, the chownpty succeeds: [EMAIL PROTECTED]:0:~ > konsole konsole: cannot chown /dev/ttyp2. Reason: Operation not permitted [EMAIL PROTECTED]:0:~ > ls -l /dev/ttyp2 crw--- 1 lofi tty5, 2 23 Aug 18:23 /dev/ttyp2 I'm going to test them on a 5.1-RELEASE box next. Please test on -CURRENT as well. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 16:27, Daniel Eischen wrote: > On Sat, 23 Aug 2003, Larry Rosenman wrote: > > --On Saturday, August 23, 2003 15:22:35 +0200 Michael Nottebrock > > > > <[EMAIL PROTECTED]> wrote: > > > On Saturday 23 August 2003 14:51, Larry Rosenman wrote: > > >> I'm not sure how to switch to a libkse'd world. > > > > > > You have to explicitly make and install both libkse and libthr: > > > > > > cd /usr/src/lib/libpthread && make && make install (will give you > > > libkse) cd /usr/src/lib/libthr && make && make install (will give you > > > libthr) > > > > > > Then, create /etc/libmap.conf to map libc_r to either libthr or libkse, > > > globally or just for single executables. Look at the libmap.conf > > > manpage, is has a nice example and all the information. > > > > libkse and libthr are built by default now. > > > > konsole crashes with all 3 (libc_r, libthr, libkse). > > > > How can I help figure this out? > > We (threads guys) think it's a problem with konsole. It is trying > to change ownership of the pty and is failing to do so. We don't > know why. Sometimes it works, sometimes it doesn't. Actually, it should never work. This bug has been long standing, there is additional information about it here: http://bugs.kde.org/show_bug.cgi?id=42986 Incidentally, Adriaan de Groot just dug up a set of patches for konsole & konsole_grantpty, I quickly adapted those for the kdebase port. They apply, but I'm still compiling kdebase with those myself, so beware, they might turn konsole into a Teletubbie FWIW (although Adriaan says they work okay for him, so there). Find the patch attached to this message. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 16:08, Larry Rosenman wrote: > libkse and libthr are built by default now. > > konsole crashes with all 3 (libc_r, libthr, libkse). Just to make sure, have you tried rebooting between changing stuff? > How can I help figure this out? No idea really. I don't use -CURRENT myself. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Friday 18 July 2003 21:16, Alexander Kabaev wrote: > On Fri, Jul 18, 2003 at 07:07:55PM +0200, Michael Nottebrock wrote: > Content-Description: signed data > > > On Friday 18 July 2003 18:14, Alexander Kabaev wrote: > > > Configure ailing due to warnings is a real bug. > > > > What do you mean now? Configure is not failing because of warnings, it is > > failing because of _ERRORS_, errors occur in gcc's libstdc++ bits. They > > _used to be warnings_ before the import. > > Then configure runs gcc with wrong parameters. In GCC 3.3 -pedantic implies > -pedantic-error, unless -fpermissive is specified too. That's perfectly fine for configure to do, since it would work if gcc wouldn't shoot its own foot by failing in libstdc++. What's the rationale of changing around these commandline parameters anyway I'm asking myself. But that's offtopic. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Friday 18 July 2003 19:23, Jacques A. Vidrine wrote: > Even when libstdc++ is updated, we'll still be left with warnings from > C-derived headers, such as the `long long' stuff. Warnings are perfectly fine with me, since they don't break anything. Putting bandaid around ports to avoid _errors_ in libstdc++ on the other hand doesn't strike me as productive. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Friday 18 July 2003 18:14, Alexander Kabaev wrote: > Configure ailing due to warnings is a real bug. What do you mean now? Configure is not failing because of warnings, it is failing because of _ERRORS_, errors occur in gcc's libstdc++ bits. They _used to be warnings_ before the import. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Friday 18 July 2003 17:37, Alexander Kabaev wrote: > On Fri, 18 Jul 2003 10:33:58 -0500 > > "Jacques A. Vidrine" <[EMAIL PROTECTED]> wrote: > > I also recall lots of missing `typename's in the system headers that > > were resolved in the actual GCC distribution. > > > > Alexander, do the STL headers et. al. get updated with the rest of the > > compiler chain? > > Yes. But libstdc++ itself lags a bit behind GCC features. The reason why > GCC ports are not reporting any errors is because by default GCC > suppresses warnings from system headers, and C++ headers are considered > system. We disable this suppression in imported compiler. I guess the next question is whether this is fixable, maybe even by enabling said supression, at least for a short while. It seems the better fix than to go and remove -pedantic from all the helloworlds that may linger in the ports-tree. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: [kde-freebsd] Re: gcc-3.3 issues
On Friday 18 July 2003 10:32, I wrote: > Now, if I compile this on 5.1-RELEASE with > > c++ -Wnon-virtual-dtor -Wno-long-long -Wall -pedantic -W -Wpointer-arith > -Wmissing-prototypes -Wwrite-strings -DNDEBUG -DNO_DEBUG -O -pipe > -mcpu=pentiumpro -fno-check-new -L/usr/local/lib -I/usr/local/include > -I/usr/local/include -I/usr/X11R6/include -D_GETOPT_H -o helloworld > helloworld.cc This commandline is copy-paste from the failing configure checks, however, just 'c++ -pedantic -O -pipe -o helloworld helloworld.cc' should probably do the trick just as well. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Thursday 17 July 2003 22:50, Mikhail Teterin wrote:
> Here is how to reproduce the problem, Michael is talking about. Simply
> try to build the kdelibs3 (or kdegraphic3, or kdenetwork3) port.
I've tried to come up with a less obscure testcase:
#include
#include
using namespace std;
int main ()
{
string astring="Hello World";
cout << astring << endl;
}
Now, if I compile this on 5.1-RELEASE with
c++ -Wnon-virtual-dtor -Wno-long-long -Wall -pedantic -W -Wpointer-arith
-Wmissing-prototypes -Wwrite-strings -DNDEBUG -DNO_DEBUG -O -pipe
-mcpu=pentiumpro -fno-check-new -L/usr/local/lib -I/usr/local/include
-I/usr/local/include -I/usr/X11R6/include -D_GETOPT_H -o helloworld
helloworld.cc
I get a plethora of warnings:
In file included from /usr/include/g++/memory:55,
from /usr/include/g++/string:48,
from helloworld.cc:1:
/usr/include/g++/bits/stl_alloc.h:979: warning: ISO C++ forbids the use of `
extern' on explicit instantiations
/usr/include/g++/bits/stl_alloc.h:980: warning: ISO C++ forbids the use of `
extern' on explicit instantiations
/usr/include/g++/bits/stl_alloc.h:981: warning: ISO C++ forbids the use of `
extern' on explicit instantiations
/usr/include/g++/bits/stl_alloc.h:981: warning: ISO C++ forbids the use of `
extern' on explicit instantiations
/usr/include/g++/bits/stl_alloc.h:981: warning: ISO C++ forbids the use of `
extern' on explicit instantiations
[and many, many more]
but it will compile. If I omit -pedantic, none of these warnings occur. The
thing is, in -CURRENT with the new gcc, all these warnings for some reason
become errors. The other thing is, if I try this with with a ports-compiled
g++32 on 4-STABLE, I don't get warnings at all, no matter if -pedantic is
specified or not.
So here's the questions for the experts:
- Why errors instead of warnings?
- Why do gcc's own bits seem to not conform to some kind of standard that it
tries to adhere to in 5-CURRENT but not in 4-STABLE?
- Who's to blame?
--
Michael Nottebrock \KDE on FreeBSD\,ww
\--- \ ,wWWCybaWW_)
\ http://freebsd.kde.org \ `WSheepW'free
\II II node
pgp0.pgp
Description: signature
Re: gcc-3.3 issues
On Thursday 17 July 2003 22:11, Alexander Kabaev wrote: > -Werror? As doctor said: if it hurts, DON'T DO THAT. In the kdelibs case, it's definitely _not_ -Werror (I wouldn't complain about that, obviously). Mikhail, can you recap which combinations exactly trigger what? -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: gcc-3.3 issues
On Wednesday 16 July 2003 17:07, Alexander Kabaev wrote: > s/gcc-3.3/ports/ issues and we are in agreement. > > Patches to fix broken ports are welcome. Kris is doing a fine job > generating a list of what needs to be fixed with his cluster packabe > building runs. There was one report of kdelibs' configure failing because of "the weirdness of the new cc (3.3), that leads to errors instead of warnings with certain combinations of -W* and -pedantic options." Is something like this expected, i.e., certain combinations of -W* and -pedantic to produce errors when they didn't before? -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: 5.1-CURRENT 23.06.2003: the floppy has ceased to work
On Wednesday 25 June 2003 17:43, Andy Fawcett wrote: > For what it's worth, I get the same with 5.1-RELEASE: > > [EMAIL PROTECTED] mp3]$ uname -a > FreeBSD vimes.int.athame.co.uk 5.1-RELEASE FreeBSD 5.1-RELEASE #7: Sat > Jun 14 23:09:29 EEST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VIMES i386 > > [EMAIL PROTECTED] mp3]$ dmesg | grep fdc > fdc0: cmd 3 failed at out byte 1 of 3 > fdc0: cmd 3 failed at out byte 1 of 3 > fdc0: cannot reserve I/O port range (6 ports) Very quick guess: ACPI problems (bad BIOS) ... Worksforme, FWIW: [EMAIL PROTECTED]:0:~ > uname -a FreeBSD lofi.dyndns.org 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Wed Jun 11 13:51:19 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LOFI i386 [EMAIL PROTECTED]:0:~ > dmesg | grep fdc fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 I tested mounting something in the 3.5" drive, works (I'm willing to test the 5.25" drive as well if someone mails me media for it ;). -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: 8MB install
On Wednesday 25 June 2003 11:44, Terry Lambert wrote: > Alternately, you could find a FreeBSD 1.1.5.1 distribution on the > net somewhere, and install that, instead; I have personally run > that version of FreeBSD on a 4M 386SX, to use it as an X Terminal. > 8-). FWIW, the last FreeBSD release I managed to install on an 8mb machine from CD-ROM+bootfloppies was 4.1.1. -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: ReiserFS
On Sunday 22 June 2003 18:17, Simon Watson wrote: > Maybe I should have clarified this, I'm only after readonly support - just > enough to be able to successfully move my data over to UFS. If you can live with creating UFS1 filesystems, you can just mount them read-write in Linux and move your data over that way. Or you wait a little while longer until Linux' UFS implementation can mount UFS2 (shouldn't be to difficult to hacked up anyway). -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: reviving rp-pppoe
Matthias Andree schrieb: Hi, as a band-aid fix, because 5.1-CURRENT's ppp or netgraph or whatever is spoiled and PPPoE no longer works Isn't this supposed to be fixed by the backouts of the c-standard related changes to bsd.sys.mk? -- Michael Nottebrock ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OK, how about now? PFIL_HOOKS
Now that 5.0 has been released, can we please make PFIL_HOOKS the default? 5.1 released, still not committed. How about now? :) -- Michael Nottebrock "And the reasons? There are no reasons." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: adsl/pppoe no longer connecting on 5.1
On Wednesday 11 June 2003 13:53, T. Muddletin wrote: > On my previous FreeBSD version (5.0 April 21 snapshot), my ADSL/pppoe > setup worked fine... as it always has all the way back to 4.x. Now > having installed 5.1-RELEASE, with no other changes, ppp no longer can > seeming no longer connect to my adsl modem. I've been struggling with > this for days. Are you sure you really have 5.1-RELEASE and not 5-CURRENT shortly after -RELEASE? There have been many other reports on pppoe related breakage with ppp in -CURRENT, but 5.1-RELEASE should work (at least it works fine for me). -- Michael Nottebrock \ KDE on FreeBSD \ ,ww \ --- \ ,wWWCybaWW_) \ http://freebsd.kde.org\ `WSheepW'free \ II II node pgp0.pgp Description: signature
Re: Serious ppp failure on 5.1
On Tuesday 10 June 2003 18:06, Farid Hajji wrote: > Ugh, I was just planning to switch to 5.1-RELEASE and cvsup > to CURRENT. Now, I'm reluctant to do this for my DSL router > -STABLE box. FWIW, RELENG_5_1 works fine. -- | Michael Nottebrock| KDE on FreeBSD | ,ww | | [EMAIL PROTECTED] | --- | ,wWWCybaWW_) | | --- | http://freebsd.kde.org | free `WSheepW'| | http://tigress.com/lofi | --- | node II II | ___ [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 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//conf. -- | Michael Nottebrock| KDE on FreeBSD | ,ww | | [EMAIL PROTECTED] | --- | ,wWWCybaWW_) | | --- | http://freebsd.kde.org | free `WSheepW'| | http://tigress.com/lofi | --- | node II II | pgp0.pgp Description: signature
Re: Polishing touch
On Sunday 01 June 2003 18:45, [EMAIL PROTECTED] wrote: > > module_register: module if_tap already exists! > > Module if_tap failed to register: 17 > > can't re-use a leaf (if_tap_debug)! FWIW, same thing happens for if_tun. -- | Michael Nottebrock| KDE on FreeBSD | ,ww | | [EMAIL PROTECTED] | --- | ,wWWCybaWW_) | | --- | http://freebsd.kde.org | free `WSheepW'| | http://tigress.com/lofi | --- | node II II | pgp0.pgp Description: signature
Re: /stand/sysinstall with upgraded 5.1-BETA
On Saturday 31 May 2003 13:55, Vitalis wrote: > * So what > do I have to do with /stand/sysinstall? It's probably safe to delete it, complete with the whole /stand directory. -- | Michael Nottebrock| KDE on FreeBSD | ,ww | | [EMAIL PROTECTED] | --- | ,wWWCybaWW_) | | --- | http://freebsd.kde.org | free `WSheepW'| | http://tigress.com/lofi | --- | node II II | pgp0.pgp Description: signature
Re: libm problem
On Sunday 23 March 2003 20:22, Till Riedel wrote: > I think no one should simply use the sse2 stuff at the moment, > because you will notice problems too late. My > mp3s sounded horrible and gv didn't display pdf files correctly. > if there hadn't been libvorbis though that had a division by zero,however, > i probably never would have located the bug. Scary. You might want to summarize what you've found (or going to find, if you continue investigating) in a big mean PR in gcc's GNATS... (I've filed one as of date, and they actually fixed the issue three months later, it seems, unlike FreeBSD, the GCC folks actually process their PR queue). -- Regards, Michael Nottebrock pgp0.pgp Description: signature
Re: libm problem
On Sunday 23 March 2003 19:24, Till Riedel wrote: > On Sun, Mar 23, 2003 at 06:43:16PM +0100, Michael Nottebrock wrote: > > Just out of curiousity, have you tried using -mfpmath=sse? I remember > > someone on this list claiming that the SSE fpa-code works much better > > than the i387 code which is used by default (even with -march=pentium4). > > seems to be equally fast with whetstone benchmark , Actually, when I said "better", I really meant "doesn't break -O(ptimized) code" rather than "faster". :) -- Regards, Michael Nottebrock pgp0.pgp Description: signature
Re: libm problem
On Sunday 23 March 2003 18:02, Till Riedel wrote: > why not > +_CPUCFLAGS = -march=pentium4 -mno-sse2 > > > choose, and in the case of pentium4 producing broken code the > > obvious fallback would be pentium3... > > above would be in fact the same because only the SSE2 code differs from > march=pentium3 which in turn only defines SSE additionally (which > probably generates the slower code compared to pentiumpro) as i see it. > code generation for all x86 uses the same rules (i386.md) > except that some rules only apply if TARGET_SSE2 is defined. Just out of curiousity, have you tried using -mfpmath=sse? I remember someone on this list claiming that the SSE fpa-code works much better than the i387 code which is used by default (even with -march=pentium4). -- Regards, Michael Nottebrock pgp0.pgp Description: signature
Re: Need ALSA [was: Re: MIDI on SB Live! ?]
On Saturday 22 March 2003 16:15, Peter Schultz wrote: > OSS is on the outs. New applications that are ALSA only will soon be > common, won't they? No. In fact, there is quite an explosion in multimedia middleware projects right now and people are having heated discussions in other places which one is the most promising. :) Don't expect many audio apps in the future to be talking directly to some API exported by a kernel. -- Regards, Michael Nottebrock pgp0.pgp Description: signature
Re: MIDI on SB Live! ?
On Friday 21 March 2003 21:01, [EMAIL PROTECTED] wrote:
> Hello,
>
> just out of curiosity: Is someone working in MIDI support for Creative
> EMU10K1 based sound cards (aka Soundblaster Live!) ?
On and off, as far as I can tell. If you want MIDI right now, take a look at
what 4Front Technologies offers in their commercial OSS package.
--
Regards,
Michael Nottebrock
pgp0.pgp
Description: signature
Re: Need ALSA [was: Re: MIDI on SB Live! ?]
On Saturday 22 March 2003 14:52, Peter Schultz wrote: > [EMAIL PROTECTED] wrote: > > Hello, > > > > just out of curiosity: Is someone working in MIDI support for Creative > > EMU10K1 based sound cards (aka Soundblaster Live!) ? > > > > Regards, > > Julian Stecklina > > Having a port of ALSA would sure round out 5.2 nicely, and would get you > MIDI support: http://www.alsa-project.org/ I think you wouldn't really do anyone a favour, including the ALSA folks, if you went and made a port right now. The ALSA project is still not at 1.00 status and still quite in-flux. > This can easily happen if we get behind a developer. ALSA has been > sponsored by SuSE for the benefit of Linux, and there's no reason we > can't pull together our resources to do the same for our OS. I'm sure > someone will step forward to do the port if we have the cash for them to > comfortably sit in front of their computer until the port is complete. I'd appreciate sponsoring somebody to work on our existing newpcm stuff and add the missing bits and pieces much more. Donating hardware (soundcards and MIDI-devices) would probably help very much already. -- Regards, Michael Nottebrock pgp0.pgp Description: signature
Re: maildrop/tmpfile breakage on 5.0-RELEASE (?)
On Tuesday 04 February 2003 23:34, David Wolfskill wrote:
> I haven't seen that particular issue, but there was a time in -CURRENT
> when my "make -j8 buildworld" runs were failing: I was using an md
> device for /tmp, and it was running out of inodes.
I had not thought of that, but /tmp is just a subdirectory of / on this
particular machine and %iused for / is just 7%.
--
Regards,
Michael Nottebrock
msg51777/pgp0.pgp
Description: signature
maildrop/tmpfile breakage on 5.0-RELEASE (?)
I noticed a growing queue of undelivered messages today and after some digging
I found out that maildrop, which I use as a local delivery agent for sendmail
in order to deliver to Maildirs, would fail on some messages bigger than its
message-buffer with "Unable to create temporary file.".
I traced that error message back in the sourcecode - it's emitted if tempfile
generation via tmpfile(3) fails. Since permissions on /tmp were nominal and I
couldn't think of anything else, I recompiled the port with an additional
--enable-tempdir=.tmp in order to disable usage of tmpfile and that solved
the problem.
My question is: Does anybody with a similar configuration see any similar
behaviour, i.e. growing queues of undelivered mail and maildrop-errors in
/var/log/maillog? It may perfectly well be just my box being screwed up in a
weird way, but the thought of more mail servers out there silently loosing
mail is somewhat scary...
--
Regards,
Michael Nottebrock
msg51776/pgp0.pgp
Description: signature
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Am Dienstag, 28. Januar 2003 21:52 schrieb Martin Blapp: > Hi, > > > Can this please be committed to or at least prepared as a patch for > > RELENG_5_0? I myself consider fixing automount access to 5.0-RELEASE nfs > > Feel free to add this patch: > > http://people.freebsd.org/~mbr/patches/committed/patch-rpc_oldreply.diff I'm sorry to have to bother you further, but this patch does not solve the problem completely. Amd works partially now, but I still get 'mountd rpc failed: RPC: Unable to receive' errors when I try to access /host// (nfsd on hostname exports / -alldirs,/usr -alldirs,/var -alldirs) and I can only access the / export. /host//usr or /host//var, where is the ip-address of the same machine as above, works as expected. -- Regards, Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Martin Blapp wrote: Hi, Can this please be committed to or at least prepared as a patch for RELENG_5_0? I myself consider fixing automount access to 5.0-RELEASE nfs Feel free to add this patch: http://people.freebsd.org/~mbr/patches/committed/patch-rpc_oldreply.diff Ah, thank you ever so much, a quick recompile of libc and things are working again! :) -- Regards, Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Can this please be committed to or at least prepared as a patch for RELENG_5_0? I myself consider fixing automount access to 5.0-RELEASE nfs servers a critical bugfix, but should RE's mileage vary, I'd really like a patch that I can apply on my server. There is also a PR open about this which could be closed, it's bin/47496. -- Regards, Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Masafumi NAKANE wrote: > On Mon, 20 Jan 2003 09:15:40 +0100, > Michael Nottebrock <[EMAIL PROTECTED]> wrote: > >>Yes, that's exactly what I'm experiencing here... uhoh. First >>errata-topic discovered 2 hours after the release? :} > > > Well, not so quick. I took another -CURRENT box and the problem was > not reproduceable on this box. I can't quite figure out what the > differences between these two boxes are, though. Could others check this please with 5.0-RELEASE? I was (and still am) willing to continue running RELENG_5_0 on that server, but I would rather not try and run -CURRENT. If this a common problem with 5.0-R, it would surely warrant a 'critical bugfix'. -- Regards, Michael Nottebrock msg50713/pgp0.pgp Description: PGP signature
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Masafumi NAKANE wrote: | I've been encountering the exact same problem past a few days. My | -CURRENT box is -CURRENT as of 01/18. | | Another thing is that, I can mount filesystems via NFS from a -CURRENT | box if I execute the mount command manually. But it fails to mount | them via AMD. Yes, that's exactly what I'm experiencing here... uhoh. First errata-topic discovered 2 hours after the release? :} - -- Regards, Michael Nottebrock -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE+K7AsXhc68WspdLARAgfpAJ9ddiC6Zwax3yUBqBZvAoihHIgEDwCgofgt DeUt46hpyszh5tA77Pu6dGs= =YP02 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.7-amd cannot mount exports from 5.0-RELEASE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have upgraded a box from 4.7-p1 to 5.0-RELEASE. It exports all its filesystems ( /, /usr, /var ) via NFS. A 4.7-STABLE client used to mount in those exports on demand with amd, with the default amd-map and /net and /host. Since the upgrade to 5.0-RELEASE on the server, amd cannot mount the exports anymore. It hangs and after a while throws an error similar to amd[345]: mountd rpc failed: RPC: Timed out in the syslog. Let me stress that the configurations of both the server and client have not changed at all and are almost factory defaults - yet it just ceased working. The most peculiar thing is that the 4.7-STABLE client also mounts in /usr/ports/distfiles from the server statically - and that still works. .. (not subscribed to list - please CC me) - -- Regards, Michael Nottebrock -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE+KvxZXhc68WspdLARAm/ZAJ99pJMyz/PjM6bx5Uuc7nLFhHg5yQCbBg3a IaiXOMjN0iBiuCOQElnnxM4= =FYbe -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cdrtools doesn't build on -current
Long, Scott wrote: All I'm asking is that ports maintainers make an effort to maintain their ports. Will's accertation that it's an all or nothing issue is certainly not productive, and neither is the 'us versus them' inuendo here. The single one -CURRENT vs. -STABLE difference that causes many easy to fix breakages is really gcc. Port-maintainers are quite the pigs in the middle when ports break because of gcc3's pickyness, the original authors of the ported software might not use (or care) gcc3 themselves and not every port-maintainer has access to a -CURRENT machine to provide selfmade patches. -- Michael Nottebrock "And the reasons? There are no reasons." msg44924/pgp0.pgp Description: PGP signature
Re: KDE 3.0 broken in current??
Alex Zepeda wrote: > On Wed, Oct 09, 2002 at 10:17:01PM -0700, Terry Lambert wrote: > > >>FWIW: Thanks. It sometimes feels like people intentionally go >>out of their way to put Linux-isms (or whatever-isms) into code >>to make it not run on BSD platforms. > > > I'm quite suprised how this managed to avoid detection for so long > (webcvs.kde.org indicated that the last commit to this branch was > 12 > months ago). Becaused it all used to compile just fine until a very short time ago. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg44478/pgp0.pgp Description: PGP signature
Re: i386 tinderbox failure
David O'Brien wrote: > I'm hoping for another 3.2.1 import soon. I raised some hell on the GCC > lists last week about the quality of 3.2.1; and actually got some Athlon > and p4 optimization PR's taken care of. Great, maybe I'll be able to use -march athlon again quite soon then. :) Today in my mailbox: -- Synopsis: ICE with gcc 3.1, happens only with -march athlon State-Changed-From-To: open->closed State-Changed-By: hubicka State-Changed-When: Wed Oct 9 10:13:46 2002 State-Changed-Why: * i386.c (athlon_cost): Fix the move costs. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg44421/pgp0.pgp Description: PGP signature
Re: tcsh hang in -current (kse bug?)
Michael Nottebrock wrote: > Kris Kennaway wrote: > >> Can anyone else reproduce this in tcsh? > > > Yup. My -CURRENT here is two weeks old. ... reproducible in -STABLE, too. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg44136/pgp0.pgp Description: PGP signature
Re: tcsh hang in -current (kse bug?)
Kris Kennaway wrote: > Can anyone else reproduce this in tcsh? Yup. My -CURRENT here is two weeks old. -- Michael Nottebrock | After years of using email, I'm still to dumb to hit Reply-All | msg44132/pgp0.pgp Description: PGP signature
Re: sym disabling controller LED?
Christian Weisgerber wrote: > Actually, that's a case of sym(4) failing to actuate the LED rather > than shutting it off. Later sym chips control the LED in hardware, > but the '875 doesn't and the driver has to blink the LED. Oh shucks, and I thought this was decent hardware. :) I'll still have the acoustic feedback from the harddisk anyway. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg44011/pgp0.pgp Description: PGP signature
sym disabling controller LED?
I have a Dawicontrol 2975U SCSI controller, which is handled by the sym driver: sym0: <875> port 0xac00-0xacff mem 0xe3201000-0xe3201fff,0xe3203000-0xe32030ff irq 10 at device 8.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking I have connected the controller's LED-connector to the case hdd-LED and it works fine (for example during loading the kernel) until sym takes over the controller, then it remains dark. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
Kenneth Culver wrote: > Oh ok, wierd... I've only tried (unsuccessfully, the compiler errors out) > kde3, and some make worlds and stuff. I guess that's not strenuous enough. kde3 compiled okay for me with Alexander Kabaev's gcc patch posted to this ML. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg42906/pgp0.pgp Description: PGP signature
Re: updated to August 5th kernel broke mozilla
Michael Nottebrock wrote: > Brooks Davis wrote: > >> I recently updated my laptop's kernel to an August 5th version from an >> July 23rd one and mozilla started getting connection refused from >> everything. Lynx worked fine as did other network services like cvsup >> and ssh. Upgrading mozilla from 1.0_rc? to the latest version corrected >> the problem, but so did booting with an old kernel so something weird is >> going on. > > > The ipv6_ipv4mapping variable in rc.conf has been changed to "NO" And the default value of net.inet6.ip6.v6only to 1. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41738/pgp0.pgp Description: PGP signature
Re: updated to August 5th kernel broke mozilla
Brooks Davis wrote: > I recently updated my laptop's kernel to an August 5th version from an > July 23rd one and mozilla started getting connection refused from > everything. Lynx worked fine as did other network services like cvsup > and ssh. Upgrading mozilla from 1.0_rc? to the latest version corrected > the problem, but so did booting with an old kernel so something weird is > going on. The ipv6_ipv4mapping variable in rc.conf has been changed to "NO", which broke mozilla (mozilla's fault). A patch for the mozilla port has been added to the port to work around the problem. Other people reported this before, see the archives. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41737/pgp0.pgp Description: PGP signature
Re: Compiler error XFree86-Server
David O'Brien wrote:
>>>I've got suggests that it's still present in all branches. I get the
>>>impression that not too many people really use gcc3 with heavy
>>>optimization on big stuff like XFree86 yet ... Of course, updating the
>>
>>XFree86 works like a charm built with -march=athlon-xp .
>
>
> I do know that compiling XFree86 with a June 2002 GCC 3.1.1 prerelease
> works fine on AMD x86-64 running SuSE with -O2 and -march specifying the
> Hammer.
You might want to try the attached code-snippet I grabbed from the gcc
GNATS. It manages to ICE 3.1 and 3.2 with a lot of optimizations,
including pentium2/3/4 and athlon-* and is believed to trigger the same
bug that borks XFree86 here.
Compile with gcc -O -march= -c clacrt.c
Regards,
--
Michael Nottebrock
"And the reasons? There are no reasons."
void foo ()
{
struct { float x, y; } c, *cp;
static float z;
while (1)
{
c.y = cp->y + cp->y;
z = c.y + 1.0;
}
}
Re: Comments on Release Building for -current
David O'Brien wrote: >>>If someone could find the small segment of code where the optimizer >>>screws up, and write a small program to demonstrate the problem, we >>>would have a good chance of it getting fixed. >> >>Er, someone (Dan Lukes) has already done this. See PR 40209. > > > It looks like this PR is against the system GCC 3.1. As such it isn't a > very interesting bug report. Someone needs to test to see if this bug > exists when using the gcc31 (gcc 3.1.1 release) port. df seems to be a rather nice & quick testcase (thanks perky). Compiling libc with -O2, then compiling df with it yields output like this: Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 252M<5M:7M54%/ devfs 1.0K 1.0K 0B:0%/dev /dev/da0s1f 3.2G 2.2G 757M75%/usr /dev/da0s1e 252M28M 204M <%/var procfs 4.0K 4.0K 0B:0%/proc linprocfs 4.0K 4.0K 0B:0% The system gcc3 and all versions of gcc3 in our ports do this. gcc295 does not. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41726/pgp0.pgp Description: PGP signature
Re: Compiler error XFree86-Server
David O'Brien wrote: > On Wed, Aug 07, 2002 at 03:59:47PM +0200, Michael Nottebrock wrote: > >>>Please submit a full bug report, >>>with preprocessed source if appropriate. >>>See http://www.gnu.org/software/gcc/bugs.html> for instructions. >>>*** Error code 1 >>> >>>Stop in >>>/usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/PEX5/ddpex/mi/level2. >>> >>>Anyone have a suggestion? >> >>1.) Submit that bugreport. > > > Why? We have a useless compiler code base for submitting bug reports > from. GCC 3.1 and 3.1.1 have been released since we imported our > compiler sources. GCC 3.2 should be released next week. Because chances are good that the bugs still aren't fixed. I reported a bug related to optimization with -march=athlon recently and the reply I've got suggests that it's still present in all branches. I get the impression that not too many people really use gcc3 with heavy optimization on big stuff like XFree86 yet ... Of course, updating the system compiler would make bug reports from -CURRENT users even more useful. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41707/pgp0.pgp Description: PGP signature
Re: Comments on Release Building for -current
Michael Nottebrock wrote: > Bruce Evans wrote: >> Er, someone (Dan Lukes) has already done this. See PR 40209. I'm sorry >> I haven't found time to look at it in detail. > > > O2-compiling -CURRENT (and -march=athlon ...) still manages to break > DCCs in xchat And, through __vnprintf, nawk too, which then breaks world. Sheesh. gawk to the rescue... Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41691/pgp0.pgp Description: PGP signature
Re: Comments on Release Building for -current
Bruce Evans wrote: > On Sat, 3 Aug 2002, Mike Barcroft wrote: > > >>Andrew Kolchoogin <[EMAIL PROTECTED]> writes: >> >>>... >>>sorry, but some time ago I read here that gcc -O2 breaks our printf() in >>>libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, >>>as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code, >>>this compiler is broken. Isn't it? >>> >>>Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer >>>code. :) >> >>If someone could find the small segment of code where the optimizer >>screws up, and write a small program to demonstrate the problem, we >>would have a good chance of it getting fixed. > > > Er, someone (Dan Lukes) has already done this. See PR 40209. I'm sorry > I haven't found time to look at it in detail. O2-compiling -CURRENT (and -march=athlon ...) still manages to break DCCs in xchat, like: Program received signal SIGBUS, Bus error. 0x286b3220 in __vfprintf () from /usr/lib/libc.so.5 (gdb) bt #0 0x286b3220 in __vfprintf () from /usr/lib/libc.so.5 #1 0x286b20ca in __vfprintf () from /usr/lib/libc.so.5 #2 0x286ad622 in snprintf () from /usr/lib/libc.so.5 #3 0x08066036 in fe_dcc_update_recv () #4 0x08086ee0 in dcc_check_timeouts () #5 0x0809dd83 in lag_check () #6 0x2825c496 in g_timeout_dispatch () from /usr/local/lib/libglib12.so.3 #7 0x2825b658 in g_main_dispatch () from /usr/local/lib/libglib12.so.3 #8 0x2825bbf9 in g_main_iterate () from /usr/local/lib/libglib12.so.3 #9 0x2825bd86 in g_main_run () from /usr/local/lib/libglib12.so.3 #10 0x2844fa38 in gtk_main () from /usr/X11R6/lib/libgtk12.so.2 #11 0x08069311 in fe_main () #12 0x0809e950 in main () #13 0x080638c1 in _start () Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg41682/pgp0.pgp Description: PGP signature
Re: kernel panic on boot, acpica related?
Terry Lambert wrote: > Michael Nottebrock wrote: > >>I tweaked my BIOS to assign a different irq (9) to >>the NIC and now the kernel boots and runs my old userland quite nicely. >>The old kernel ran perfectly well with the NIC on irq10 ... strange. > > > None of your other postings identified the devices also on > IRQ10. If I had to guess... USB? Almost everything. sym0, csa0, bktr0, atapci1, drm0 ... and USB, but since I can only change IRQs per 'pin', fxp0 still shares its IRQ with USB now. :] Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41610/pgp0.pgp Description: PGP signature
Re: kernel panic on boot, acpica related?
Michael Nottebrock wrote: > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > Timecounters tick every 10.000 msec > > Fatal trap 9: general protection fault while in kernel mode > instruction pointer= 0x8:0xc4109ac1 > stack pointer= 0x10:0xd6855ce4 > frame pointer= 0x10:0xd6855d0c > code segment= base0x0, limit 0xf, type 0x16 > = DPL 0, pres 1, def 32, gran 1 > processor eflags= interrupt enabled, resume, IOPL=0 > current process= 21 (irq10:fxp0 sn0+++*) I tweaked my BIOS to assign a different irq (9) to the NIC and now the kernel boots and runs my old userland quite nicely. The old kernel ran perfectly well with the NIC on irq10 ... strange. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41607/pgp0.pgp Description: PGP signature
Re: nmbd receiving strange SIGHUPs
Galen Sampson wrote: > I started seeing this on a -current machine about 5 months ago. The -current > was pre gcc3.1 and pre KSE. Samba was 2.2.3. Updating -current solved the > problem for me. It has been kinda on and off here. With some -CURRENT builds it would happen, with some it wouldn't. ATM I'm running a Kernel&Userland where it happens all the time (Jul 16) and it seems I'm stuck with it. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41605/pgp0.pgp Description: PGP signature
Re: kernel panic on boot, acpica related?
Mitsuru IWASAKI wrote: >>sc0: at flags 0x100 on isa0 >>sc0: VGA <16 virtual consoles, flags=0x300> >>vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 >>Timecounters tick every 10.000 msec >> >>Fatal trap 9: general protection fault while in kernel mode >>instruction pointer = 0x8:0xc4109ac1 >>stack pointer = 0x10:0xd6855ce4 >>frame pointer = 0x10:0xd6855d0c >>code segment = base0x0, limit 0xf, type 0x16 >> = DPL 0, pres 1, def 32, gran 1 >>processor eflags = interrupt enabled, resume, IOPL=0 >>current process = 21 (irq10:fxp0 sn0+++*) > > > >>kernel: type 9 trap, code=0 >>Stopped at0xc4109ac1: lcall $0xc410,0xa040c410 >>db> trace >>_end (c158d300,d6855d48,c04897b1,356,0) at 9xc4109ac1 >>fork_exit (c02ae2c0,c158d300,d6855d48) at fork_exit+0xaf >>fork_trampoline () at fork_trampoline+0x1a > > > Hmmm, I don't think so. How about typing > unset acpi_load > in loader prompt, and see if this panic disappear or still happen? Hm, right, doesn't go away, slightly different panic now ... Fatal trap 1, but basically same spot. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41575/pgp0.pgp Description: PGP signature
kernel panic on boot, acpica related?
sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc4109ac1 stack pointer = 0x10:0xd6855ce4 frame pointer = 0x10:0xd6855d0c code segment= base0x0, limit 0xf, type 0x16 = DPL 0, pres 1, def 32, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 21 (irq10:fxp0 sn0+++*) kernel: type 9 trap, code=0 Stopped at 0xc4109ac1: lcall $0xc410,0xa040c410 db> trace _end (c158d300,d6855d48,c04897b1,356,0) at 9xc4109ac1 fork_exit (c02ae2c0,c158d300,d6855d48) at fork_exit+0xaf fork_trampoline () at fork_trampoline+0x1a -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41572/pgp0.pgp Description: PGP signature
nmbd receiving strange SIGHUPs
On startup (being run from the rc.d-script), nmbd (from samba-2.2.5) sometimes receives a sighup (and dumps its workgrouptable), sometimes not. This has been going on for at least a month now here, does anybody else see this? Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41556/pgp0.pgp Description: PGP signature
AMD low power hacks
I've been wondering lately why my AthlonTB runs at a quite high idle-temperature and I came across this page: http://vcool.occludo.net/VC_Theory.html Does someone feel like getting something similar into our kernel? Regards, -- Michael Nottebrock msg41473/pgp0.pgp Description: PGP signature
gcc going ICE on XFree86 with -march athlon
JFYI, I submitted a bug report to the gcc GNATS, the PR-Number is 7390. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41295/pgp0.pgp Description: PGP signature
Re: 5.0-DP2 coming up..
John Baldwin wrote: > Of course, bug fixes can be merged from current back into the > DP2 branch before DP2 goes out if needed, but we'd like to try and get > it as close to right as possible the first time. :) A working fsck would surely be a good thing for DP2. :) See thread on current@. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg41166/pgp0.pgp Description: PGP signature
Re: Update to the DRM
Eric Anholt wrote: > On Wed, 2002-07-10 at 17:17, Eric Anholt wrote: > >>I've posted a diff to the DRM at >>http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta > > > Evolution's "send" button is way too big. > > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.diff > is the file. The patch brings the current DRM from DRI CVS into the > system. It includes PCI Rage 128 support and support for "transform, > clipping, & lighting" (TCL) hardware on Radeons. I have just compiled a world with the 20020711.diff. It sure runs fast, but the quality isn't very good. I tested with glxgears and gltron and in both there is a lot of flashing and lighting errors. Do you have any recommendations what other tests I could run? Hardware: drm0@pci1:0:0: class=0x03 card=0x008a1002 chip=0x51441002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Radeon 7200 / Radeon' class= display subclass = VGA Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40985/pgp0.pgp Description: PGP signature
Re: Update to the DRM
Stanislav Grozev wrote:
> On Fri, Jul 12, 2002 at 09:56:50AM +0200, Stanislav Grozev wrote:
>
>
>>>Missed the N on my cvs diff -uN. New patch is uploaded, including not
>>>stripping FreeBSD ID tags.
>>>http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff
>>
>>thanks, i'll try it now
>
>
> ok, it compiles and runs fine...
> but my card isn't recognized. here's what pciconf -l -v shows:
>
> none6@pci0:13:0:class=0x03 card=0x80af104d chip=0x4c521002 rev=0x64
>hdr=0x00
> vendor = 'ATI Technologies'
> device = 'Rage P/M Mobility PCI'
> class= display
> subclass = VGA
>
> so I just added the chipid to r128_drv.c (hoping that it will work;-):
>
> {0x1002, 0x4c52, __REALLY_HAVE_SG, "ATI Rage 12m Mobility P/M (PCI)"},
>
> and the driver now detects it:
>
> drm0: port 0x1400-0x14ff mem
>0xfc00c000-0xfc00cfff,0xfd00-0xfdff irq 9 at device 13.0 on pci0
> [drm:r128_init]
> [drm:r128_agp_init] agp_available = 0
> [drm:r128_ctxbitmap_next] drm_ctxbitmap_next bit : 0
> [drm:r128_ctxbitmap_init] drm_ctxbitmap_init : 0
> info: [drm] Initialized r128 2.2.0 20010917 on minor 0
>
> but, glxinfo still says 'Direct rendering: no' (i have load "dri" in my
> x config, do i need something else?).
Load "glx"
and something like
Section "DRI"
Mode 0666
EndSection
See http://www.xfree86.org/current/DRI6.html#10 for details.
Regards,
--
Michael Nottebrock
"The circumstance ends uglily in the cruel result." - Babelfish
msg40941/pgp0.pgp
Description: PGP signature
Re: fsck hosed?
Doug Barton wrote: > I brought the fsck_y_enable stuff in, I'll try to take a look at it this > week. Just to avoid misunderstandings: That all worked fine a few weeks ago... that was the second to last time I needed it (because I accidentally pulled the wrong plug). Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40688/pgp0.pgp Description: PGP signature
Re: fsck hosed?
Georg-W. Koltermann wrote: > Yes, I see that as well. Another symptom is that fsck -p now always > announces "unexpected inconsistencies" and drops back to singleuser when > it indeed was able to fix the problems, i.e. it marks the filesystem > clean and a manual fsck does not report anything unusual. Metoo: I have fsck_y_enable="YES" set and sometimes it'd announce "unexpected inconsistencies", sometimes it'd not, but it will always bail out to single user after it processes the first unclean filessystem. I then need to run fsck as many times as I have dirty filesystems (because it'll exit after it has cleaned one of them). Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40672/pgp0.pgp Description: PGP signature
[Fwd: Re: Post-KSE disaster with libc_r]
Somehow this thread slipped into privmail. Original Message Subject: Re: Post-KSE disaster with libc_r Date: Mon, 1 Jul 2002 14:23:23 -0700 (PDT) From: Julian Elischer <[EMAIL PROTECTED]> To: Michael Nottebrock <[EMAIL PROTECTED]> > [Applied 'thediff' to pre-KSE CURRENT and rebuilt world, things > break, things remain broken when booting the old kernel with the > new world.] THANKS!!! ok so it's libc_r for sure.. now we have two possibilities: 1/ It's ingherrently broken because of a recent change. if so, checking out 1 month old sources to libc_r and compiling it should yield a working libc_r. 2/ Something I've committed is polluting the compile. e.g. a namespace clash or similar in a new include file. In this case, teh new compile of old sources should yield a bad libc_r. can someone test this? msg40222/pgp0.pgp Description: PGP signature
Re: Post-KSE disaster with libc_r
Andrey A. Chernov wrote: > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > >>the question is: >>did you update both kernel and userland? > > > This bug is not related to in-kernel KSE code (but, maybe related to > header files compiled in). I got it even with updated userland and old > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > old about month ago helps. I applied "thediff" to a -CURRENT box as of June 25th and it promptly shows the symptoms, so I still think it's somewhere in the KSE-code. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40232/pgp0.pgp Description: PGP signature
Re: Post-KSE desaster
Bill Huey wrote: > Try "info threads" in gdb and then progressively walking through the thread > list with "thread N", N being the thread number. (...) Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread 3 Process 14606, Thread 3 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 2 Process 14606, Thread 2 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 * 1 Process 14606, Thread 1 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) thread 1 [Switching to thread 1 (Process 14606, Thread 1)]#0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () (gdb) thread 2 [Switching to thread 2 (Process 14606, Thread 2)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc502 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #2 0x281ced1d in pthread_cond_timedwait () from /usr/lib/libc_r.so.5 #3 0x281c58f2 in _thread_gc () from /usr/lib/libc_r.so.5 #4 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 (gdb) thread 3 [Switching to thread 3 (Process 14606, Thread 3)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc49d in _thread_kern_sched_state () from /usr/lib/libc_r.so.5 #2 0x281c60ff in _write () from /usr/lib/libc_r.so.5 #3 0x281c6187 in write () from /usr/lib/libc_r.so.5 #4 0x2828ccc2 in ao_plugin_play () from /usr/local/lib/ao/plugins-2/liboss.so #5 0x280b4f8d in ao_play () from /usr/local/lib/libao.so.3 #6 0x08049bed in free () #7 0x0804a9a1 in free () #8 0x0804a066 in free () #9 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 As a comparison, artsd: [lofi@kiste]:0:~ > gdb artsd GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... (no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/artsd (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... unix_connect: can't connect to server (unix:/tmp/mcop-lofi/kiste_localdomain-01c2-3d1fe3ca) There are already artsd objects registered, looking if they are active... ... cleaned 5 unused mcop global references. (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread * 1 Process 15847, Thread 1 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x284242e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40172/pgp0.pgp Description: PGP signature
Post-KSE desaster
Everything that links to libc_r is now completely hosed here, this includes all of KDE. Since KDE is a tad too big to make a handy test, here comes ogg123 from the vorbis-tools port: [lofi@kiste]:1:~ > gdb ogg123 GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... (no debugging symbols found)... (gdb) run /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02Ordinary_World.ogg Starting program: /usr/local/bin/ogg123 /home/lofi/mp3/Duran_Duran/The_Wedding_A lbum/02Ordinary_World.ogg (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Device: OSS audio driver output Author: Aaron Holtzman <[EMAIL PROTECTED]> Comments: Outputs audio to the Open Sound System driver. Playing: /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02Ordinary_World.ogg Title: Ordinary World Artist: Duran Duran Album: The Wedding Album (no debugging symbols found)...(no debugging symbols found)...ffer 6.2% Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40170/pgp0.pgp Description: PGP signature
buildworld errors
- One in usr.bin/gcore/gcore.c (open #ifndef, lost the errorlog, commit-accident?) - Another: cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /usr/src/lib/libkvm/kvm_proc.c:271: invalid operands to binary != /usr/src/lib/libkvm/kvm_proc.c:310: invalid operands to binary != /usr/src/lib/libkvm/kvm_proc.c:324: invalid operands to binary != *** Error code 1 Stop in /usr/src/lib/libkvm. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg40137/pgp0.pgp Description: PGP signature
Re: [kde-freebsd] [3.0.1] gcc/g++ 3.1 problems
Ollivier Robert wrote: > Hello, > > I've upgraded my CURRENT system to a post gcc 3.1 world and I'm now unable > to compile any C++ program that use the STL (incl. KDE 3.0.1). I happens > with the system g++ 3.1 and the ports g++ 3.1.1 and with both a clean > /usr/include/g++ and the old one (which has lots of older files due to > CURRENT evolution). The weird thing is that my laptop, also running > CURRENT, is fine. You need a clean /usr/include. Remove the old one and 'make includes' in /usr/src. Please make also sure your ports-tree is up to date. I think you're using an old bsd.kde.mk. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg39953/pgp0.pgp Description: PGP signature
Re: [OT] ACPI based support for suspend to disk?
Fischer, Oliver wrote: > You are right. My PC supports this via BIOS too. The > disadvantage is, that the bios handle it. I like W2K's > feature to do it ACPI based (?). This gives my the freedom > to suspend my W2K to disk and to reboot with FBSD. Later I > reboot again and choose W2K and it restores it previous > state. If the bios does it, it restores always the last > suspended OS. AFAIR, the Win2k-Suspend2Disk is not ACPI-based. -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg39760/pgp0.pgp Description: PGP signature
Re: konqueror 3.0.1 eats all CPU
Ollivier Robert wrote: > According to Michael Nottebrock: > >>At least on -CURRENT, this stems from QT being compiled with the >>system-gcc3, which breaks the gif-loader of QT. Here is a patch for the > > > I've seen that mentionned a few times but what did we changed in gcc31 in the > system that makes it generate bad code ? Actually the system-gcc31 is older than the ports-gcc31, so the question is rather "What did the gcc-developers change during those weeks?". :) Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg39749/pgp0.pgp Description: PGP signature
Re: C++ problems
Wesley Morgan wrote: > I cleaned up my /usr/lib and /usr/include file of stale headers/libs left > after the libstdc++ upgrade (maybe this should be in src/UPDATING??), and > now any port that uses C++ & autoconf fails to configure... > > checking if STL implementation is SGI like... no > checking if STL implementation is HP like... no > configure: error: "no known STL type found - did you forget to install > libstdc++-devel ?" > > However, the configure script WILL succeed if I manually run configure > with the same options (grabbed from ps). Weird... Anyone have some > thoughts on this? It's a little annoying :) I just hit the same problem while trying to compile KDE stuff. In my case it stems from bsd.kde.mk adding -I/usr/include to CPPFLAGS, causing gcc to change its include search order. Lacking further insight, I don't know the proper fix there, but I got around it by simply removing -I/usr/include from bsd.kde.mk. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish msg39676/pgp0.pgp Description: PGP signature
Re: buildworld failure in libfetch
David Wolfskill wrote: > Were you running with -j ? 'cause the error appears to be with libssl, > not libfetch. Nope. > > And I built OK, both with -j8 (on 2x866 PII) & -j4 (on laptop), though > I didn't use the "athlon" specification I tried unsetting CPUTYPE, no change. > You might try a combination of no -j & clearing /usr/obj/usr/src to > see if you can make it recur in a "pristine" environment. I rm -rf /usr/obj before every build. Regards, -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in libfetch
Michael Nottebrock wrote: > Error attached. Correctly this time. Regards, -- Michael Nottebrock ===> lib/libfetch cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/fetch.c -o fetch.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/common.c -o common.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/ftp.c -o ftp.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/http.c -o http.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/file.c -o file.o building static fetch library ranlib libfetch.a cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/fetch.c -o fetch.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/common.c -o common.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/ftp.c -o ftp.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/http.c -o http.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/file.c -o file.So make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libssl.a. Stop
buildworld failure in libfetch
I'm trying to upgrade from a 2002.05.10-CURRENT, with a fresh cvsup. Error attached. Regards, -- Michael Nottebrock --- error Description: application/java-vm
libstdc++-v3
First: It's great to see gcc3 in -CURRENT, a round of cheers for obrien@! :) So, please, don't misread this question as some kind of "hurry, hurry!", but: Is libstdc++-v3 already on anyone's schedule, and if so, when can we expect it to hit the tree? -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sftp troubles
[[EMAIL PROTECTED]]:/usr/home/lofi > sftp [user]@[host] Connecting to [host]... [user]@[host]'s password: sftp> get nonexistentfile Couldn't stat remote file: No such file or directory Segmentation fault (core dumped) --- snip Anyone else seeing this? Yesterday's current with base-system openssh. -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Assertion faild at kern_mutex.c
David Wolfskill wrote: >>Date: Fri, 01 Mar 2002 10:47:09 +0900 >>From: Jun Kuriyama <[EMAIL PROTECTED]> >> > >>At Fri, 1 Mar 2002 01:34:17 + (UTC), >>John Baldwin wrote: >> >>>That's bad juju panic. :) Are you using witness? If so, did you get a printf >>>about sleeping with a lock held? >>> > >>I think I did not get lock warning just before this assertion >>failure. But on my environment, I got this lock order reversal >>everytime I booted. >> > >>lock order reversal >>1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 >>2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 >> > > Although I did not get the reported panic, I have also had a very > similar lock order reversal reported since (at least) the -CURRENT of > 22 Feb. (which as far back as I presently keep the message log). I reported that particular LOR on this list on Feb 7th. -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
