Re: 9.2-RC4 amd64 panic: vm_page_unwire
On Fri, Sep 27, 2013 at 10:07:28AM +1000, John Marshall wrote: > I'm running 9.2-RC4 on a handful of desktop and server machines (both > i386 and amd64). I have seen three panics (all vm_page_unwire) on one > of those systems only (amd64 server) during the past week. > > The first two panics were triggered when shutting down the ntpd daemon > (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a > later release (p388) has not triggered the panic. The system panicked > again overnight, this time while acting as an sftp server receiving > large (GB) files from another system. > > Fri Sep 20 16:48:34 2013 +1000 > ozsrv04# kgdb kernel.debug /var/crash/vmcore.0 > ... > panic: vm_page_unwire: page 0xfe0233510578's wire count is zero > cpuid = 3 > KDB: stack backtrace: > #0 0x80490268 at kdb_backtrace+0x68 > #1 0x8045630a at panic+0x21a > #2 0x8068bbc2 at vm_page_unwire+0x102 > #3 0x80678702 at vm_fault_unwire+0xd2 > #4 0x80680841 at vm_map_delete+0x171 > #5 0x80680abf at vm_map_remove+0x5f > #6 0x80683ee9 at vmspace_exit+0xc9 > #7 0x8041f3ad at exit1+0x72d > #8 0x804203ae at sys_sys_exit+0xe > #9 0x806afd6f at amd64_syscall+0x3bf > #10 0x8069a817 at Xfast_syscall+0xf7 > Uptime: 2d0h35m3s > > Fri Sep 20 17:49:57 2013 +1000 > ozsrv04# kgdb kernel.debug /var/crash/vmcore.1 > ... > panic: vm_page_unwire: page 0xfe022f5fc238's wire count is zero > cpuid = 2 > KDB: stack backtrace: > #0 0x80490268 at kdb_backtrace+0x68 > #1 0x8045630a at panic+0x21a > #2 0x8068bbc2 at vm_page_unwire+0x102 > #3 0x80678702 at vm_fault_unwire+0xd2 > #4 0x80680841 at vm_map_delete+0x171 > #5 0x80680abf at vm_map_remove+0x5f > #6 0x80683ee9 at vmspace_exit+0xc9 > #7 0x8041f3ad at exit1+0x72d > #8 0x804203ae at sys_sys_exit+0xe > #9 0x806afd6f at amd64_syscall+0x3bf > #10 0x8069a817 at Xfast_syscall+0xf7 > Uptime: 59m51s > > Fri Sep 27 01:51:44 2013 +1000 > ozsrv04# kgdb kernel.debug /var/crash/vmcore.2 > ... > panic: vm_page_unwire: page 0xfe0239ecfc48's wire count is zero > cpuid = 5 > KDB: stack backtrace: > #0 0x80490268 at kdb_backtrace+0x68 > #1 0x8045630a at panic+0x21a > #2 0x8068bbc2 at vm_page_unwire+0x102 > #3 0x804d857e at vfs_vmio_release+0x10e > #4 0x804dadc8 at getnewbuf+0x468 > #5 0x804dbb2f at getblk+0x5df > #6 0x80632bb1 at ffs_balloc_ufs2+0x15c1 > #7 0x8065a8d6 at ffs_write+0x246 > #8 0x8070a18f at VOP_WRITE_APV+0x11f > #9 0x80505e77 at vn_write+0x1f7 > #10 0x80503b51 at vn_io_fault+0xb1 > #11 0x804a387c at dofilewrite+0x9c > #12 0x804a3b54 at kern_writev+0x54 > #13 0x804a3bf5 at sys_write+0x65 > #14 0x806afd6f at amd64_syscall+0x3bf > #15 0x8069a817 at Xfast_syscall+0xf7 > Uptime: 6d7h46m14s > > Is this a known problem? Should I file a PR? What additional > information should I provide? > > I have made the core.txt.[0-2] files available in the following > directory. The directory is not browsable. > > http://www.riverwillow.net.au/~john/92rc4/ This might be fixed by r254087-r254090 on stable/9. pgpOt4VaRzMw2.pgp Description: PGP signature
Re: FreeBSD 9.1 ix driver vlan problem
On 25/09/2013 22:10, Dmitry Morozovsky wrote: On Wed, 25 Sep 2013, Rumen Telbizov wrote: Thanks for the heads-up Oleg, although not the news that I was hoping for. So what I am going to do right now is reinstall with 9.2 and recompile the driver with your patch. I'll come back to the list with my results. FWIW, we're (with oleg@, yeah) using this patch on stable/9, so you're welcome to test this on your 9 It's supposedly way too late to try to include this fix into 9.2-R, but maybe it's worth the errata notice... This happens on several other intel chipsets as well, no previous errata was ever noted (legacy em, for example) :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: lock order reversal in 10-alpha2
On Fri, 27 Sep 2013 05:57:45 +0200, Shane Ambler wrote: After booting from a 10-alpha2 disk I am seeing "lock order reversal" messages show up from time to time. Current logs have 35 entries. FreeBSD 10-ALPHA is still being build with kernel option WITNESS on. This gives more diagnostics of internal state of the kernel. A lot of these LORs (Lock Order Reverals) should be fixed some day, but are harmless for the continues working of the machine. If you compile FreeBSD 9 with WITNESS on, you will some LORs also. Ronald. The machine normally is running 9.1 from zfs root and I have setup a separate disk (eSATA case connected through backplane port to onboard SATA port) that I have installed 10-alpha amd64 onto a ufs partition to test port building with. I started by building 10 alpha1 and installing onto the new disk. I have since done svn up (last revision is 255868) then rebuilt and installed kernel and world while running 10 and still see these messages. I mentioned the existing 9.1 on zfs which I am not importing while running 10 from ufs as I noticed zfs mentioned in one of the entries. Initially I built with an empty src.conf but the last build I used the following - WITH_BSD_GREP=yes WITH_CLANG_EXTRAS=yes WITH_CTF=yes WITHOUT_LIB32=yes WITH_LLDB=yes Hardware is ASUS P8H61-M LE/USB3 corei5 8GB RAM nvidia GT520 I can provide full copy of log/messages or dmesg if required. A few samples -- messages:Sep 26 02:01:27 leader kernel: lock order reversal: messages-Sep 26 02:01:27 leader kernel: 1st 0xfe01eebd07f8 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3059 messages-Sep 26 02:01:27 leader kernel: 2nd 0xf800122f8200 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 messages-Sep 26 02:01:27 leader kernel: KDB: stack backtrace: messages-Sep 26 02:01:27 leader kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0238a8f270 messages-Sep 26 02:01:27 leader kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe0238a8f320 messages-Sep 26 02:01:27 leader kernel: witness_checkorder() at witness_checkorder+0xd23/frame 0xfe0238a8f3b0 messages-Sep 26 02:01:27 leader kernel: _sx_xlock() at _sx_xlock+0x75/frame 0xfe0238a8f3f0 messages-Sep 26 02:01:27 leader kernel: ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xfe0238a8f430 messages-Sep 26 02:01:27 leader kernel: ufs_direnter() at ufs_direnter+0x688/frame 0xfe0238a8f4f0 messages-Sep 26 02:01:27 leader kernel: ufs_makeinode() at ufs_makeinode+0x573/frame 0xfe0238a8f6b0 messages-Sep 26 02:01:27 leader kernel: VOP_CREATE_APV() at VOP_CREATE_APV+0xea/frame 0xfe0238a8f6e0 messages-Sep 26 02:01:27 leader kernel: vn_open_cred() at vn_open_cred+0x300/frame 0xfe0238a8f830 messages-Sep 26 02:01:27 leader kernel: kern_openat() at kern_openat+0x261/frame 0xfe0238a8f9a0 messages-Sep 26 02:01:27 leader kernel: amd64_syscall() at amd64_syscall+0x265/frame 0xfe0238a8fab0 messages-Sep 26 02:01:27 leader kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe0238a8fab0 messages-Sep 26 02:01:27 leader kernel: --- syscall (5, FreeBSD ELF64, sys_open), rip = 0x80185baca, rsp = 0x7fffd168, rbp = 0x7fffd1a0 --- messages.0:Sep 23 10:08:11 leader kernel: lock order reversal: messages.0-Sep 23 10:08:11 leader kernel: 1st 0xf801ba2e65f0 ufs (ufs) @ /usr/src/sys/kern/vfs_syscalls.c:3435 messages.0-Sep 23 10:08:11 leader kernel: 2nd 0xfe01ef93c1c0 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:262 messages.0-Sep 23 10:08:11 leader kernel: 3rd 0xf801ba2e6240 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2099 messages.0-Sep 23 10:08:11 leader kernel: KDB: stack backtrace: messages.0-Sep 23 10:08:11 leader kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe02397c2300 messages.0-Sep 23 10:08:11 leader kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe02397c23b0 messages.0-Sep 23 10:08:11 leader kernel: witness_checkorder() at witness_checkorder+0xd23/frame 0xfe02397c2440 messages.0-Sep 23 10:08:11 leader kernel: __lockmgr_args() at __lockmgr_args+0x6f2/frame 0xfe02397c2570 messages.0-Sep 23 10:08:11 leader kernel: ffs_lock() at ffs_lock+0x84/frame 0xfe02397c25c0 messages.0-Sep 23 10:08:11 leader kernel: VOP_LOCK1_APV() at VOP_LOCK1_APV+0xf5/frame 0xfe02397c25f0 messages.0-Sep 23 10:08:11 leader kernel: _vn_lock() at _vn_lock+0xab/frame 0xfe02397c2660 messages.0-Sep 23 10:08:11 leader kernel: vget() at vget+0x70/frame 0xfe02397c26b0 messages.0-Sep 23 10:08:11 leader kernel: vfs_hash_get() at vfs_hash_get+0xf5/frame 0xfe02397c2700 messages.0-Sep 23 10:08:11 leader kernel: ffs_vgetf() at ffs_vgetf+0x41/frame 0xfe02397c2790 messages.0-Sep 23 10:08:11 leader kernel: softdep_sync_buf() at softdep_sync_buf+0x8fa/frame 0xfe02397c2840 messages.0-Sep 23 10:08:11 leader kernel: ffs_syncvnode() at ffs_syncvnode+0x258/frame 0xfff
Running a script via PHP
Hello there, It's quite off-topic, but I'm using freebsd-stable,so The priblem is - running a script that requires root privileges via PHP (or probably CGI - I do not care, just want it to be secure and working). It's all about minidlna service (I use upnp to so mediatomb and other are no options). On FreeBSD it should be resync-ed manually, so I've got a simple script placed in /etc/periodic/daily: more 957.dlna_update #!/bin/sh #Script to daily update minidlna DB a="$*" if (/usr/local/etc/rc.d/minidlna stop 1>/dev/null);then sleep 10 if /usr/local/etc/rc.d/minidlna rescan;then /usr/bin/logger -t minidlna "DB updated." exit 0 else /usr/bin/logger -t minidlna "Error. Failed to update DB." exit 1 fi else /usr/bin/logger -t minidlna "Error. Failed to update DB." exit 1 fi And it's working fine to me. But it uses service infrastructure. So when I'm trying to run via PHP it fails. For example running under unprivileged user: id uid=1001(amd_miek) gid=0(wheel) groups=0(wheel),5(operator) -rwsr-sr-x 1 root wheel 394 27 сен 10:58 957.dlna_update* sh -x 957.dlna_update + a='' + /usr/local/etc/rc.d/minidlna stop kill: 10786: Operation not permitted + /usr/bin/logger -t minidlna 'Error. Failed to update DB.' + exit 1 What is the best way to run it via WEB? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running a script via PHP
On Fri, 27 Sep 2013 11:18:40 +0200, Michael BlackHeart wrote: Hello there, It's quite off-topic, but I'm using freebsd-stable,so The priblem is - running a script that requires root privileges via PHP (or probably CGI - I do not care, just want it to be secure and working). It's all about minidlna service (I use upnp to so mediatomb and other are no options). On FreeBSD it should be resync-ed manually, so I've got a simple script placed in /etc/periodic/daily: more 957.dlna_update #!/bin/sh #Script to daily update minidlna DB a="$*" if (/usr/local/etc/rc.d/minidlna stop 1>/dev/null);then sleep 10 if /usr/local/etc/rc.d/minidlna rescan;then /usr/bin/logger -t minidlna "DB updated." exit 0 else /usr/bin/logger -t minidlna "Error. Failed to update DB." exit 1 fi else /usr/bin/logger -t minidlna "Error. Failed to update DB." exit 1 fi And it's working fine to me. But it uses service infrastructure. So when I'm trying to run via PHP it fails. For example running under unprivileged user: id uid=1001(amd_miek) gid=0(wheel) groups=0(wheel),5(operator) -rwsr-sr-x 1 root wheel 394 27 сен 10:58 957.dlna_update* sh -x 957.dlna_update + a='' + /usr/local/etc/rc.d/minidlna stop kill: 10786: Operation not permitted + /usr/bin/logger -t minidlna 'Error. Failed to update DB.' + exit 1 What is the best way to run it via WEB? You can't setuid a shell script. The executable actually is '/bin/sh' which just reads the shell script. So you should setuid /bin/sh which is a security problem. You can use sudo to do this. (/usr/ports/security/sudo) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [SOLVED] Only one CPU core detected on Supermicro E3-1240 v3
Marian Cerny wrote: > I am trying to install FreeBSD 9.2-RC4 on Supermicro server with Intel Xeon > E3-1240 v3 processor. The processor has 4 cores with 8 threads. However only > one core is detected (with two threads): > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > > The motherboard is Supermicro X10SLM-F. All cores are enabled in BIOS and the > latest firmware is installed (version 1.1a, Build Date 08/20/2013). I have contacted Supermicro support and they have advised me to flash the latest BIOS but set the JPME2 jumper (Manufacturing Mode Select) and move it back after flashing. Now the all the cores are detected: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads Marian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running a script via PHP
Hi-- On Sep 27, 2013, at 2:18 AM, Michael BlackHeart wrote: > Hello there, > It's quite off-topic, but I'm using freebsd-stable,so > > The priblem is - running a script that requires root privileges via PHP (or > probably CGI - I do not care, just want it to be secure and working). Unfortunately the combination of PHP, doing something which needs root, and security are inherently contradictory. The least risky approach would be to invoke the needed command via sudo, or possibly a small setuid-root C wrapper program which launches only the needed script with root permissions. Use sudo unless your C wrapper is careful enough to use exec() and not system(), sanitizes $PATH and other env variables, and guards against games with $IFS, shell metachars, and such. Regards, -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 21.09.2013 12:40, Matthew Seaman wrote: > On 21/09/2013 11:31, O. Hartmann wrote: >> I'd like to switch off this silly "Nakatomi Socrates" message which >> reminds me on Linux and their childish naming schemes. >> >> It is only cosmetics, but it bothers me whenever I switch on the laptop. >> >> I guess there is a switch already prsent to have in the bootloader >> config? > > It's turned off by default in more recent 9.2-STABLE > > Otherwise: > > loader_logo="orb" > > in /boot/loader.conf -- see loader.conf(5) > > Cheers, > > Matthew > Hi, I have loader_logo="orb" and I still have a message at the right bottom with that stupid joke. It's really pisses me off *now*. I already said it was okay to add a new logo for that stupid joke. But now, I have orb set and I still see that in my bootloader. How can I disable this forever ?! Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Sep 27, 2013, at 3:06 PM, David Demelier wrote: > On 21.09.2013 12:40, Matthew Seaman wrote: >> On 21/09/2013 11:31, O. Hartmann wrote: >>> I'd like to switch off this silly "Nakatomi Socrates" message which >>> reminds me on Linux and their childish naming schemes. >>> >>> It is only cosmetics, but it bothers me whenever I switch on the laptop. >>> >>> I guess there is a switch already prsent to have in the bootloader >>> config? >> >> It's turned off by default in more recent 9.2-STABLE >> >> Otherwise: >> >> loader_logo="orb" >> >> in /boot/loader.conf -- see loader.conf(5) >> >> Cheers, >> >> Matthew >> > > Hi, > > I have loader_logo="orb" and I still have a message at the right bottom > with that stupid joke. > I already responded to this once. loader_version="" See version.4th(8). > It's really pisses me off *now*. Why *now*? I already answered this... (link to archives below) http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html If you say that you tried this and it didn't work, then by all means... come back (pissed off or not) and we'll debug the situation. The person that recommended loader_logo was incorrectly thinking you were talking about the ARTWORK that you get by default in RC1-RC3 which is now non-default (requiring loader_logo="tribute" to enable beyond RC3). The "named releases" however are staying enabled by default. And as I answered in the archives... loader_version="whatever you want to name your release" or loader_version="" is how you customize the text which seems to piss you off so much. > I already said it was okay to add a new > logo for that stupid joke. But now, I have orb set and I still see that > in my bootloader. > > How can I disable this forever ?! > http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html > Also in the future you can just forgot that crappy ideas as you can see, > nobody liked it. > Uh... I'm ignoring that. -- Devin P.S. You're not winning any friends here. We answered your question and you came back hostile. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Sep 27, 2013, at 3:06 PM, David Demelier wrote: > On 21.09.2013 12:40, Matthew Seaman wrote: >> On 21/09/2013 11:31, O. Hartmann wrote: >>> I'd like to switch off this silly "Nakatomi Socrates" message which >>> reminds me on Linux and their childish naming schemes. >>> >>> It is only cosmetics, but it bothers me whenever I switch on the laptop. >>> >>> I guess there is a switch already prsent to have in the bootloader >>> config? >> >> It's turned off by default in more recent 9.2-STABLE >> >> Otherwise: >> >> loader_logo="orb" >> >> in /boot/loader.conf -- see loader.conf(5) >> >> Cheers, >> >> Matthew >> > > Hi, > > I have loader_logo="orb" and I still have a message at the right bottom > with that stupid joke. > "Named Releases" is far from a joke. Maybe you'd like something a bit more boring like "9.2-RELEASE" The fact is... there is (and only ever will be) one iteration of FreeBSD 9.2. I assume that you have had no clue up until this point that there was yet another BSD 9.2. A fictitious version of BSD in a 1980's film, named... Nakatomi Socrates Yeah, we could have decided to let the opportunity pass; to show that we're the first BSD to ever hit 9.2 out of all the flavors, producing the first ever non-fictitious BSD 9.2... But where would the fun be in that? Rest assured... I've not seen *any* hollywood films with a number higher than 9.2... so our future looks pretty darn boring. The "name" for 10.0-RELEASE could very well be NULL or boring ol' 10.0-RELEASE But one thing is clear. There is a real tangible benefit to seeing the version on the boot screen. As we move to integrate BE's into the Forth boot screen, it may become paramount to know what version of loader(8) you're using. So please try not to be so judge-mental about these things. This is a real tangible improvement and simply because you've heard that those crazy people in Linux-land are naming their releases... That had zero bearing on why we did it. We may never name another release ever again. I personally would like to see loader(8) set the value to include an SVN revision so that everytime you rebuild loader(8), the version info updates; displayed prominently in the bottom right corner (which of course... you'll again be free to override it if you don't like it... just as you are free to completely disable the entire menu by adding beastie_disable=YES to loader.conf(8)). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 28.09.2013 00:12, Teske, Devin wrote: > > On Sep 27, 2013, at 3:06 PM, David Demelier wrote: > >> On 21.09.2013 12:40, Matthew Seaman wrote: >>> On 21/09/2013 11:31, O. Hartmann wrote: I'd like to switch off this silly "Nakatomi Socrates" message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? >>> >>> It's turned off by default in more recent 9.2-STABLE >>> >>> Otherwise: >>> >>> loader_logo="orb" >>> >>> in /boot/loader.conf -- see loader.conf(5) >>> >>> Cheers, >>> >>> Matthew >>> >> >> Hi, >> >> I have loader_logo="orb" and I still have a message at the right bottom >> with that stupid joke. >> > > I already responded to this once. > > loader_version="" > > See version.4th(8). > > >> It's really pisses me off *now*. > > Why *now*? I already answered this... (link to archives below) > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html > > If you say that you tried this and it didn't work, then by all means... > come back (pissed off or not) and we'll debug the situation. > I already asked a few weeks ago what was this strange artwork on my boot loader and I was told to use loader_logo to completely disable it. I've first said that it's funny but I would not recommend to enable it by default because it's really not serious and the artwork was really immature in the scope of the FreeBSD project. Then I was "happy" because I get my orb as usual. And today, I've updated to 9.2-RELEASE SVN tag and saw there was again a message about this stupid "Nakatomi Socrates" version in green. So I needed to check again *why* this has been enabled by default and that's why it was starting to get my nerves. I personally think (but you may totally disagree with) that an operating system *is* an operating system. And I really hate easter eggs or anything else not serious being integrated into the system. I think about a new user installing FreeBSD 9.2, I would not imagine his reaction front of this kind of "tribute" or whatever you call that. For me it stands for "that's not serious, it looks like a toy". Fortunately now it's just a "version" but I would really not imagine when the screen was looking with the "tribute" loader_logo. Seriously, I don't understand why people waste time to create jokes like that instead of working on serious issues. You may think I'm putting to much significance on this kind of matter but I like (and I'm not the only one) serious, clean things. And the real reason that made me yell like that was that I needed to ask / complain a second time to remove that "tribute" thing again. > The person that recommended loader_logo was incorrectly thinking you > were talking about the ARTWORK that you get by default in RC1-RC3 which > is now non-default (requiring loader_logo="tribute" to enable beyond RC3). > > The "named releases" however are staying enabled by default. > > And as I answered in the archives... > > loader_version="whatever you want to name your release" > > or > > loader_version="" > > is how you customize the text which seems to piss you off so much. > Thanks. > > >> I already said it was okay to add a new >> logo for that stupid joke. But now, I have orb set and I still see that >> in my bootloader. >> >> How can I disable this forever ?! >> > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html > > >> Also in the future you can just forgot that crappy ideas as you can see, >> nobody liked it. >> > > Uh... I'm ignoring that. > Check again in the lists, I'm not the only one complaining on that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 28.09.2013 00:32, Teske, Devin wrote: > > On Sep 27, 2013, at 3:06 PM, David Demelier wrote: > >> On 21.09.2013 12:40, Matthew Seaman wrote: >>> On 21/09/2013 11:31, O. Hartmann wrote: I'd like to switch off this silly "Nakatomi Socrates" message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? >>> >>> It's turned off by default in more recent 9.2-STABLE >>> >>> Otherwise: >>> >>> loader_logo="orb" >>> >>> in /boot/loader.conf -- see loader.conf(5) >>> >>> Cheers, >>> >>> Matthew >>> >> >> Hi, >> >> I have loader_logo="orb" and I still have a message at the right bottom >> with that stupid joke. >> > > "Named Releases" is far from a joke. > > Maybe you'd like something a bit more boring like "9.2-RELEASE" > > The fact is... there is (and only ever will be) one iteration of FreeBSD 9.2. > > I assume that you have had no clue up until this point that there was yet > another BSD 9.2. A fictitious version of BSD in a 1980's film, named... > > Nakatomi Socrates Yes I know that, I've already seen the image a lot a few weeks ago. > > Yeah, we could have decided to let the opportunity pass; to show that we're > the first BSD to ever hit 9.2 out of all the flavors, producing the first ever > non-fictitious BSD 9.2... > > But where would the fun be in that? > FreeBSD is not Linux, I (and again, I'm not the only one) thought the idea of naming Linux 3.11 "Linux for workgroups" very stupid. In the Linux world we like to add funny messages / easter eggs directly in the kernel source, but I think this silly and not serious. So I don't really want to bring these Linux manners into our FreeBSD world. > Rest assured... I've not seen *any* hollywood films with a number higher > than 9.2... so our future looks pretty darn boring. > > The "name" for 10.0-RELEASE could very well be NULL or boring ol' > > 10.0-RELEASE > > But one thing is clear. > > There is a real tangible benefit to seeing the version on the boot screen. > > As we move to integrate BE's into the Forth boot screen, it may become > paramount to know what version of loader(8) you're using. > > So please try not to be so judge-mental about these things. > > This is a real tangible improvement and simply because you've heard > that those crazy people in Linux-land are naming their releases... > > That had zero bearing on why we did it. We may never name another release > ever again. > > I personally would like to see loader(8) set the value to include an SVN > revision > so that everytime you rebuild loader(8), the version info updates; displayed > prominently in the bottom right corner (which of course... you'll again be > free to > override it if you don't like it... just as you are free to completely > disable the > entire menu by adding beastie_disable=YES to loader.conf(8)). > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Fri, Sep 27, 2013 at 2:57 PM, David Demelier wrote: > > >> I have loader_logo="orb" and I still have a message at the right bottom > >> with that stupid joke. I know that you're passionate about this topic, but if you could drop the subjective parts and focus on the facts, that would be more constructive. > Seriously, I don't understand why people waste time to create jokes like > that instead of working on serious issues. Because we're not robots. We need to occasionally shift gears to avoid burning out. Taking a break to do something playful can actually improve overall productivity. Especially if you're pushing hard to get a world-class OS out the door in your copious free time. > >> Also in the future you can just forgot that crappy ideas as you can see, > >> nobody liked it. I actually thought that it was pretty cool. It may have needed an easier off switch, but I think that it was harmless. > Check again in the lists, I'm not the only one complaining on that. This depends on which lists. I'm not the only one who thought it was cool. People were passing it around and appreciating the reference. I'm honestly mystified by the backlash on this. Did people panic because they thought they'd been hacked? If so, future logo humor could be adjusted to account for this. I understand leaving out true code-based easter eggs, to keep code clean and simple. But this was a humorous logo change for an alpha release. It seems harmless to me. Royce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Sep 27, 2013, at 3:57 PM, David Demelier wrote: > On 28.09.2013 00:12, Teske, Devin wrote: >> >> On Sep 27, 2013, at 3:06 PM, David Demelier wrote: >> >>> On 21.09.2013 12:40, Matthew Seaman wrote: On 21/09/2013 11:31, O. Hartmann wrote: > I'd like to switch off this silly "Nakatomi Socrates" message which > reminds me on Linux and their childish naming schemes. > > It is only cosmetics, but it bothers me whenever I switch on the laptop. > > I guess there is a switch already prsent to have in the bootloader > config? It's turned off by default in more recent 9.2-STABLE Otherwise: loader_logo="orb" in /boot/loader.conf -- see loader.conf(5) Cheers, Matthew >>> >>> Hi, >>> >>> I have loader_logo="orb" and I still have a message at the right bottom >>> with that stupid joke. >>> >> >> I already responded to this once. >> >> loader_version="" >> >> See version.4th(8). >> >> >>> It's really pisses me off *now*. >> >> Why *now*? I already answered this... (link to archives below) >> >> https://urldefense.proofpoint.com/v1/url?u=http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=z7tFMIIWxpbu4NUJ6O%2BFBM29y7x%2BpF%2Bsj9kfA1f0JxU%3D%0A&s=f2e6eb61a04c40db454a365487d050393168dfb0d53318972e79c38283de3a50 >> >> If you say that you tried this and it didn't work, then by all means... >> come back (pissed off or not) and we'll debug the situation. >> > > I already asked a few weeks ago what was this strange artwork on my boot > loader and I was told to use loader_logo to completely disable it. > > I've first said that it's funny but I would not recommend to enable it > by default because it's really not serious and the artwork was really > immature in the scope of the FreeBSD project. > > Then I was "happy" because I get my orb as usual. And today, I've > updated to 9.2-RELEASE SVN tag and saw there was again a message about > this stupid "Nakatomi Socrates" version in green. So I needed to check > again *why* this has been enabled by default and that's why it was > starting to get my nerves. > The artwork and the name are separate. The artwork is an RC/Beta easter-egg that disappears at release time. The ability to display a loader_version however stays. > I personally think (but you may totally disagree with) that an operating > system *is* an operating system. And I really hate easter eggs or > anything else not serious being integrated into the system. I think > about a new user installing FreeBSD 9.2, I would not imagine his > reaction front of this kind of "tribute" or whatever you call that. For > me it stands for "that's not serious, it looks like a toy". > Only people downloading an RC or a BETA will see the artwork. This very well could: 1. Drive more people to test RC/BETA cycles 2. Not be an impact to anybody because serious people don't deploy RC or BETA builds to an enterprise. 3. It makes it very clear when you're using an RC or a BETA versus final > Fortunately now it's just a "version" but I would really not imagine > when the screen was looking with the "tribute" loader_logo. > Some folks have told me that they've permanently enabled the artwork. Not everybody that uses FreeBSD uses it in a corporate setting. Naturally, those in a corporate setting will be thankful that final releases won't ever enable a tribute artwork by-default. > Seriously, I don't understand why people waste time to create jokes like > that instead of working on serious issues. > Actually... I flip that on its head. If you work seriously on serious issues long enough... you'll become burned- out. Let me just come right out and say it... I coded it. And after 8 years of "always serious" coding on "always serious" projects has made me a dull boy. This little mini-project gave me something to work on that lifted my spirits. > You may think I'm putting to much significance on this kind of matter > but I like (and I'm not the only one) serious, clean things. > Well, maybe the middle ground is that the code is a "seriously clean" thing. It may not be "serious" but it is indeed "seriously clean." Cleanliness allows you to add two lines to loader.conf(5) to kill it: loader_logo="orb" loader_version="" But if you look closer, you'll see that it's really designed to give you or anybody else a way to brand the OS. PC-BSD changes brand.4th(8) So does NuOS -- self-purported "FreeBSD Distro" (not fork, distro) At $work, we change beastie.4th(8) and brand.4th(8) The tribute -- disabled by default -- could be yet another entry-point for corporate customers to brand their boxen for customers. Example? Leaving brand.4th(8) alone and just adding a set of tribute functions to produce the custom boot screen if-and-ony-if loader_logo=tribute. If NuOS had done that
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 09/28/2013 08:06, David Demelier wrote: [..] Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. I beg to differ. cheers, gja ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
Quoth David Demelier : > > I personally think (but you may totally disagree with) that an operating > system *is* an operating system. And I really hate easter eggs or > anything else not serious being integrated into the system. I think > about a new user installing FreeBSD 9.2, I would not imagine his > reaction front of this kind of "tribute" or whatever you call that. For > me it stands for "that's not serious, it looks like a toy". Personally I thoroughly approve of a joke every now and then, as long as it doesn't get out of hand. It reassures me there are actual human people working on this who care about what they're doing, rather than some faceless humourless corporation only interested in profit margins. This in turn reassures me that standards will be kept high and bugs will be taken seriously, because that's what people who care do. > Fortunately now it's just a "version" but I would really not imagine > when the screen was looking with the "tribute" loader_logo. While I like the idea of release names in general, I think it's important not to make them more prominent than the real version numbers. I've had to deal with Ubuntu users (I know very little about Ubuntu) in other open-source contexts, and they tend to talk about 'hardy heron' or 'constipated koala' or what-have-you, which just leaves me thinking 'yes, but which is *more recent*?'. So I might rather the default version string was something more like 'FreeBSD 9.2-RELEASE (Nakatomi Socrates)'. Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Sep 27, 2013 5:05 PM, "grenville armitage" wrote: > > > > On 09/28/2013 08:06, David Demelier wrote: > [..] > >> Also in the future you can just forgot that crappy ideas as you can see, >> nobody liked it. > > > I beg to differ. I know it's not a poll, but myself and the 5 people in my office all thought it was awesome, and will be leaving it enabled for as long as 9.2 is installed on our servers. That definitely puts it above "nobody liked it". Lighten up. Go outside, take a deep breath of fresh air. Move on. Life is too short for this. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 9/27/13 7:14 PM, Freddie Cash wrote: On Sep 27, 2013 5:05 PM, "grenville armitage" wrote: On 09/28/2013 08:06, David Demelier wrote: [..] Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. I beg to differ. I know it's not a poll, but myself and the 5 people in my office all thought it was awesome, and will be leaving it enabled for as long as 9.2 is installed on our servers. That definitely puts it above "nobody liked it". Lighten up. Go outside, take a deep breath of fresh air. Move on. Life is too short for this. :) Agreed. When it stop being fun, then it will see a decline in participation. -Alfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-RC4 amd64 panic: vm_page_unwire
On Fri, 27 Sep 2013, 11:12 +0300, Konstantin Belousov wrote: > On Fri, Sep 27, 2013 at 10:07:28AM +1000, John Marshall wrote: > > I'm running 9.2-RC4 on a handful of desktop and server machines (both > > i386 and amd64). I have seen three panics (all vm_page_unwire) on one > > of those systems only (amd64 server) during the past week. > > The first two panics were triggered when shutting down the ntpd daemon > > (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a > > later release (p388) has not triggered the panic. The system panicked > > again overnight, this time while acting as an sftp server receiving > > large (GB) files from another system. > > I have made the core.txt.[0-2] files available in the following > > directory. The directory is not browsable. > > > > http://www.riverwillow.net.au/~john/92rc4/ > > This might be fixed by r254087-r254090 on stable/9. Thank you. Those patches applied cleanly to releng/9.2 so I rebuilt a patched 9.2. I double-checked and verified that the following patched files in my releng/9.2@255904 working copy were identical to the same files in stable/9@254090, then I removed /usr/obj/* and built a fresh system. M /usr/src/sys/vm/vm_fault.c M /usr/src/sys/vm/vm_map.c M /usr/src/sys/vm/vm_map.h M /usr/src/sys/vm/vm_object.c M /usr/src/sys/vm/vm_object.h M /usr/src/sys/vm/vm_page.c The system panicked as follows during shutdown after its first boot. The corresponding core.txt.3 file is available at the same location previously posted. Fri Sep 27 22:32:18 2013 +1000 ozsrv04# kgdb kernel.debug /var/crash/vmcore.3 ... Unread portion of the kernel message buffer: . <118>Stopping watchdogd. <118>Waiting for PIDS: 1297 panic: vm_page_unwire: page 0xfe023743eb50's wire count is zero cpuid = 1 KDB: stack backtrace: #0 0x80490278 at kdb_backtrace+0x68 #1 0x8045630a at panic+0x21a #2 0x8068bac2 at vm_page_unwire+0x102 #3 0x80678732 at vm_fault_unwire+0xd2 #4 0x80680851 at vm_map_delete+0x171 #5 0x80680acf at vm_map_remove+0x5f #6 0x80683ea9 at vmspace_exit+0xc9 #7 0x8041f3ad at exit1+0x72d #8 0x804203ae at sys_sys_exit+0xe #9 0x806afc6f at amd64_syscall+0x3bf #10 0x8069a717 at Xfast_syscall+0xf7 Uptime: 7m24s I have now seen this panic on a second server as well (also amd64 but different hardware vendor). This second (unpatched) system also panicked during shutdown as follows. Corresponding file named core.txt.0.system2 is available at the same location as above. Sat Sep 28 06:19:59 2013 +1000 panic: vm_page_unwire: page 0xfe0429aa5d18's wire count is zero cpuid = 1 KDB: stack backtrace: #0 0x804e7398 at kdb_backtrace+0x68 #1 0x804ad43a at panic+0x21a #2 0x80717d42 at vm_page_unwire+0x102 #3 0x80704882 at vm_fault_unwire+0xd2 #4 0x8070c9c1 at vm_map_delete+0x171 #5 0x8070cc3f at vm_map_remove+0x5f #6 0x80710069 at vmspace_exit+0xc9 #7 0x804764dd at exit1+0x72d #8 0x804774de at sys_sys_exit+0xe #9 0x8073d7cf at amd64_syscall+0x3bf #10 0x80728277 at Xfast_syscall+0xf7 Uptime: 5m31s -- John Marshall pgpRkG1L5L96E.pgp Description: PGP signature
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 28/09/2013 12:17 PM, Alfred Perlstein wrote: > On 9/27/13 7:14 PM, Freddie Cash wrote: >> On Sep 27, 2013 5:05 PM, "grenville armitage" >> wrote: >>> >>> >>> On 09/28/2013 08:06, David Demelier wrote: >>> [..] >>> Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. >>> >>> I beg to differ. >> I know it's not a poll, but myself and the 5 people in my office all >> thought it was awesome, and will be leaving it enabled for as long as 9.2 >> is installed on our servers. >> >> That definitely puts it above "nobody liked it". >> >> Lighten up. Go outside, take a deep breath of fresh air. Move on. Life is >> too short for this. :) >> > Agreed. When it stop being fun, then it will see a decline in > participation. > > -Alfred > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Both of you have it *right* on the money :) A more discerning question is *why* you thought it was awesome. Poeple might think its obvious, but the answer is *not* a cool logo, nor any Nakatomi reference. The real answer is deeper than that, and goes to the heart of why we feel affinities toward one individual, group, organisation or another. The purpose is entirely non-technical, and *precisely* to be active in honing FreeBSD's brand identity, personality and culture moving forward. If the outcomes are a perception of a community that is approachable and lighthearted, and encouraging participation, so much the better. To those who read this thread, ask yourself first: What message do YOU want to communicate to the world about who we are? Now make your decisions follow from that :) -- Kubilay "koobs" Kocak ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
