Experience using httpd in production on busy machines?
I am in the process of deploying an updated version of a PHP web application that has been running on Apache and Nginx on Linux. This time I have done all the development running the webserver on OpenBSD httpd+PHP. The setup is so much simpler and I am used to running OpenBSD boxes as gateways/firewall so I am familiar. However, before I take the final step and deploy the new application on OpenBSD httpd in production I would like to hear if anyone has any experience to share regarding performance compared to running Apache or Nginx on Linux? Any caveats to look out for? Kind regards! Sent with [ProtonMail](https://protonmail.com/) Secure Email. I never deployed it in the real world, but made a version of my web server using httpd. To test it I beat the crap out of it with three other OpenBSD systems running wget scripts and programs simulating hordes of users. It worked well, saturating a 100mb test network. I have never cared for "speed", because a faster less secure site only leads to a notice of breakins or worse. Regardless of the software you use, you should always be really mean to it Try to crash it--multiple machines on your test network will really, really test it. --STeve Andre' Ps: if you do find weirdness, report it! Sent with Aqua Mail for Android https://www.mobisystems.com/aqua-mail
Re: Filling a 4TB Disk with Random Data
Even easier, have stty status set to ^T, and run dd . When you want to know where you are in the process hit ^T. Lots (most?) of programs will respond to a SIGINFO request. --STeve Andre' On Jun 10, 2020, 12:48, at 12:48, Luke Small wrote: >if you have access to packages, you could "pkg_add pv" > >and: > >"dd if=/dev/random | pv | dd of=/dev/rsdXc bs=1m" > >It will show you in real time how much random > >data has been written to disk. > >-Luke > > >On Wed, Jun 10, 2020 at 11:43 AM Luke Small >wrote: > >> I mean: "dd if=/dev/random | pv | dd of=/dev/rsdXc bs=1m" >> >> -Luke >> >> >> On Wed, Jun 10, 2020 at 11:41 AM Luke Small >wrote: >> >>> if you have access to packages, you could "pkg_add pv" >>> >>> and: >>> >>> "dd if=/dev/random | pv | of=/dev/rsdXc bs=1m" >>> >>> It will show you in real time how much random >>> >>> data has been written to disk. >>> >>> -Luke >>> >>
Re: Filling a 4TB Disk with Random Data
The speed of writing is dependent on the rotational speed of the disk, and the i/o bandwidth of the system. You want to do dd if=/dev/zero of=/dev/rsd1c bs=1m Note that this writes to the sd1 disk! Carefully, carefully look at your disks and write to the correct one. Writing to sd0 is likely to be disastrous. Do this on a test system. dd is as efficient as it is ruthless. You can irrevocably damage a system with it. ---STeve Andre' Sent from BlueMail On Jun 1, 2020, 09:58, at 09:58, Justin Noor wrote: >Hi Misc, > >Has anyone ever filled a 4TB disk with random data and/or zeros with >OpenBSD? > >How long did it take? What did you use (dd, openssl)? Can you share the >command that you used? > >Thank you so much
Re: OpenBSD: Not Free Not Fuctional and Definetly Not Secure and BSD, the truth blog
If you look at the titles of some of the other "articles" You will see a trend of unhappiness. The author has the right to write such things, just as everyone else has the right to ignore it. --STeve Andre' On May 28, 2020, 00:16, at 00:16, Quantum Robin wrote: >Hi, > >While surfing on the Google to learn more about OpenBSD, I encountered >this >one: "OpenBSD: Not Free Not Fuctional and Definetly Not Secure ( >https://aboutthebsds.wordpress.com/2013/01/25/20/) > >Is the author telling the truth? Or just yet another anti-BSD thing?
Re: openbsd.org down?
The proper people know already. It's useless to make further comments. --STeve Andre' On Apr 13, 2020, 03:14, at 03:14, Ilya Mitrukov wrote: >Hi, >flushing the caches doesn't help and it's still unavailable. > >Does anybody know where to report the issue? >(I'd look at openbsd.org but ... ) > >- Ilya > >On 2020-04-13 05:00, zeurk...@volny.cz wrote: >> "Durial EB" wrote: >>> Still down for me. >> Appears intermittent. Cc'ing webmaster@ (assuming it exists). >> >> --zeurkous. >> >>> On Sun, Apr 12, 2020 at 5:44 PM wrote: >>> >>>>> Hello. >>>>> >>>>> What happened to the openbsd.org? >>>>> I seems to be down for 10+ hours for now. >>>> WFM. Empty your name swerver cache, it might help. >>>> >>>>> Regards, >>>>> >>>>> Roman >>>> --zeur. >>>> >>>> -- >>>> Friggin' Machines!
Re: Tools for writers
On 2019-11-02 15:07, Antoine Jacoutot wrote: On Sat, Nov 02, 2019 at 03:04:34PM -0400, STeve Andre' wrote: On 2019-11-02 11:00, Oliver Leaver-Smith wrote: Hello, What tools do people find useful for writing on OpenBSD? By writing I mean long form such as novels and technical books, including plot and character development, outlining, and formatting for publishing (not all the same application necessarily) I have found a number which boast Linux support, but not really anything that stands out which supports OpenBSD (aside from the obvious LaTeX et al.) Mich appreciated ~ols -- Oliver Leaver-Smith +44(0)114-360-1337 TZ=Europe/London /usr/bin/vi You obviously never wrote a book. At least not with the requirements OP asked for. > Actually, I am, right now. I've found that "formatting" is an annoyance, when writing material. Get it written, *then* worry about how it looks. I've done this for more than 40 years when creating documents, reports and such for work. --STeve Andre'
Re: Tools for writers
On 2019-11-02 11:00, Oliver Leaver-Smith wrote: Hello, What tools do people find useful for writing on OpenBSD? By writing I mean long form such as novels and technical books, including plot and character development, outlining, and formatting for publishing (not all the same application necessarily) I have found a number which boast Linux support, but not really anything that stands out which supports OpenBSD (aside from the obvious LaTeX et al.) Mich appreciated ~ols -- Oliver Leaver-Smith +44(0)114-360-1337 TZ=Europe/London /usr/bin/vi
Nobody said it yet...
Happy birthday to OpenBSD!
Re: When will OpenBSD become a friendly place for bug reporters?
On 7/8/19 10:57 PM, mazoc...@disroot.org wrote: Hi! We all know that bugs don't get fixed without backtraces. After few years of using OpenBSD I am annoyed to get mocked for not sending backtraces, but why I don't send them? The answer is: OpenBSD doesn't provide software packages with debugging symbols. Do I look like a Gentoo user? It's not cool to leave no choice to bug reporters but to make them rebuild all ports they use with: $ env CFLAGS='-pipe -g' DEBUG=-g make -j $(sysctl -n hw.ncpu) reinstall The current OpenBSD is definetely not friendly to bug reporters, so don't blame me when I refuse to send backtraces, I am simply not in mood to rebuild software when it shouldn't be necessary, I value my time. For heavens sake, why don't you compile the code with symbols? If you have the ability to go inside and look for problems, you can compile stuff yourself. If you're going to submit a patch you have to build to test the fix! --STeve Andre'
Re: Blind OpenBSD users
On 5/14/19 5:02 AM, Marc Espie wrote: As far as I know, the only software we have for blind people (and not just people with very poor eye sight) is misc/brltty. misc/screen also has support in the form of the shm flavor, which hooks to misc/brltty The main issue for this kind of thing is of course testing. This was done over 10 years ago. I have zero idea if this still works, or if there are better tools these days. We also have (had?) a speech synthesis system in audio/festival Unfortunately, this is research code that predates the C++ standard by years, and thus is thoroughly rotten through. I don't think we have any other speech synthesis open source software in the ports tree. There is flite which works but isn't great. --STeve Andre'
Re: Code of Conduct location
On 4/28/19 3:58 AM, Strahil Nikolov wrote: Hello All, can someone point me to the link of the OpenBSD code of Conduct ? It seems that I can't find it even with the help of google. Best Regards, Strahil Nikolov There isn't one that I have ever seen. But the code of conduct here is really the same as in life: be honest and fair, try to help and not harass. Deal with others as you would wish others would do to you. A formal Code of Conduct is a rabbit hole, with no bottom. The very people who might need it will be its abusers, and how do you enforce it on open mailing list? --STeve Andre'
Can't boot up on -current of thursday
For the first time in 14+ years I cant boot up. I compiled -current yesterday but didnt reboot then. Rebooting today after the probe line Spkr0 at pcppi0 I get Usbd_free_xfer: xfer=0xff087bb44c30 not free And hangs. So, I booted the previous kernel and got the same message. Other kernels give the same message. Bsd.rd did come up however. This is a w541 thinkpad. I'm going to install on an external disk, but have others seen this? Given multiple kernel failures I fear hardware problems. And of course I dont have other working hardware with me so I have to deal with that to get comparison systems up. Thanks for any clues. --STeve Andre'
Re: TypeO
On 10/19/18 6:29 PM, david long wrote: I'm the first to admit I don't know anything about anything. Should it be iwn or iwm for the wireless firmware drivers. Because I get an error say unable to load iwm. I thought the wireless drivers for the Intel chipset are iwn David, I would suggest reading https://www.openbsd.org/mail.html. Actually, reading the entire FAQ is a good idea for newcomers. Both iwn and iwm are wireless drivers, for different species of Intel wireless chips. Reading is a really good thing when delving into a new op system. Fortunately OpenBSD is great docs. In addition, https://undeadly.org/ is good reading, as is http://daemonforums.org/forumdisplay.php?f=11 There are others but that should get you started. --STeve Andre'
Re: Going nuts
Thanks very much to Stewart and Josh. My new little beast is on the net now and everything seems to work. Now the W541 can go to the hospital as I leave mine. (-; STeve Andre' On Sep 11, 2018, 06:16, at 06:16, Stuart Henderson wrote: >On 2018-09-11, STeve Andre' wrote: >> My main laptop is going south on me and I'm trying to get an >alternate thinkpad working. Adding to my joy is that I'm in the >hospital currently. >> >> I have a stock X220. What firmware file do I want for -current? >Sorry for the question but I plead antibiotics! Most frustrating not >having access to normal items. >> >> Thank you all... >> >> STeve Andre' >> > >Files for -current are at >http://firmware.openbsd.org/firmware/snapshots/, >"fw_update -i" will tell you which ones you need. > >If you need to load them from USB stick or similar to get wlan working, >you can use fw_update -p /path/to/files.
Going nuts
My main laptop is going south on me and I'm trying to get an alternate thinkpad working. Adding to my joy is that I'm in the hospital currently. I have a stock X220. What firmware file do I want for -current? Sorry for the question but I plead antibiotics! Most frustrating not having access to normal items. Thank you all... STeve Andre'
Re: Lesser evil
On 09/04/18 20:04, Heinz Kampmann wrote: -- *Gesendet:* Dienstag, 04. September 2018 um 23:00 Uhr *Von:* "STeve Andre'" *An:* "Kevin Chadwick" , misc@openbsd.org *Betreff:* Re: Lesser evil On 09/04/18 09:09, Kevin Chadwick wrote: Um, maybe I'm not writing well. I'm talking about a dual-boot Windows OpenBSD system, which gets a Windows virus, which wipes out the disk. Effectively asleep, OpenBSD gets creamed. That's what I mean about dual-booting being a risk. Hi, I understand you in that way, but I thougt win10 can´t read/write ufs-partitions. Maybe I´am wrong. I use Windows for one program (PsyPrax), cause I won´t run it in an emulation. I only trust in OpenBSD. Lean and clean code shifts security - plus the extra work like pledge, KARL, w^x etc. ... and the most reviews praise the high quality code of OpenBSD. Sometimes I use win10 or mac high sierra for amazon prime. best wishes, Heinz Heinz, Think disk, not partitions. Smash the raw disk and it matters not what was on it; it will be obliterated. That's what some Win viri do. --STeve Andre'
Re: Lesser evil
On 09/04/18 09:09, Kevin Chadwick wrote: On Mon, 3 Sep 2018 18:03:06 -0400 I would not try to dual boot Windows and OpenBSD. There are too many disgusting viri out that smash parts of partitions. OpenBSD or anything else on the disk is a sitting duck once not active. Don't do it. The AV situation on Windows is out of control--a conservative estimate is that there are 4M pieces of malware out for Windows. Personally I feel this is a red herring. If you are finding viri on your system then OpenBSD helps but could be hacked too. Viri are unlikely with a security conscious OpenBSD user. You are doing something wrong or need to silo your actions. Um, maybe I'm not writing well. I'm talking about a dual-boot Windows OpenBSD system, which gets a Windows virus, which wipes out the disk. Effectively asleep, OpenBSD gets creamed. That's what I mean about dual-booting being a risk. --STeve Andre'
Re: Lesser evil
On 09/03/18 14:42, - - wrote: Hello all, I am running OpenBSD on my desktop, which is suitable for 99% of my needs. However I have to run certain proprietary software, which is available on Linux, Mac OSX and Windows. I cannot decide which of the three would be a "lesser evil" to run in respect with security and privacy. The software (video and photo editing) runs best on Windows, almost as good on OSX and it runs on Linux with some compromises. Does it make sense to accept such compromises and run Linux for security and privacy OR is the better security and privacy of Linux more or less a myth and running Windows would be almost the same in that respect? I understand that any response is to be just an opinion. Thank you Jan I would not try to dual boot Windows and OpenBSD. There are too many disgusting viri out that smash parts of partitions. OpenBSD or anything else on the disk is a sitting duck once not active. Don't do it. The AV situation on Windows is out of control--a conservative estimate is that there are 4M pieces of malware out for Windows. If your AV software knows how to deal with 98%, that means 80K things aren't dealt with. Ugh! I know of a dual booting Win/Obsd laptop that was damaged by a viri and afterwards the owner could not find the OpenBSD partition at all. Pity I was never able to see it to do analysis. Here in the US, you can get used thinkpads for an astonishing small amount of money. My wife just got a T430 with 8G ram, 500G disk, 2.6GHz I5, 1366x768 display, 2 USB 3 ports, for $167. The battery is even decent. This is at Newegg. Used macs look like $400. For that money I would advocate that a separate machine is best, AND you have an emergency OpenBSD backup system. --STeve
Re: Installed current on top of FAT32 flash, Recover old filesystem??
On 07/14/18 15:16, Chris Bennett wrote: I very carefully and surely tested which flash drive to use and then pulled out the wrong one. I stopped the install with halt and done nothing else. Should I have yanked it, halted it or just said goodbye? ddrescue or something else or nothing else? Thanks, I hope, Chris Bennett https://www.r-studio.com/ This is software I have used in the past to deal with disk disasters. It's about $80 the last time I used it but it worked pretty well. Good luck. If you find some other method, let misc@ know. --STeve Andre'
Re: Hard disk controller not recognized
On 02/12/18 12:07, Xianwen Chen wrote: Dear OpenBSD users, I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The installation was done by taking out the hard drive and hook it through a USB reader to another machine. I boot the hard drive through Legacy Boot menu. The boot process stops with root device: It is possible to boot through bsd.rd. However, the hard drive is not recognized there. Here is the dmesg from bsd.rd: [snip] Xianwen, Obviously the best thing is for IT to release the BIOS control to you, but if they won't, get a USB SATA disk interface, and try to use that. Your IT department might have figured out how to interfere with that too, but that might be a solution. You'd have to keep that external disk and its interface with you, but at least you could use OpenBSD. --STeve Andre'
Re: Writing "ones" instead of "zeroes" when wiping disk
Don't bother. Wiping the disk twice is enough. If you are storing state secrets melt the disk. Back in the days of sub 1G disks it might have been possible to get inter track gap data that was usable. Maybe. But not multi T disks. Sectors mapped out are a problem though, and multiple writes aren't going to touch those. If you encrypt the disk I question how much value a few encrypted sectors would be to anyone. Worry far more over lost usb sticks or portable usb disks. That's a far bigger problem. STeve Andre' Sent with AquaMail for Android http://www.aqua-mail.com On January 11, 2018 9:46:25 AM Andreas Thulin <andreasthu...@gmail.com> wrote: Hi! Again, an ignorant question (as usual): How might I do something similar to # dd if=/dev/one of=/dev/sd0 bs=1M as a complement to the usual and well-described # dd if=/dev/zero of=/dev/sd0 bs=1M followed by # dd if=/dev/urandom of=/dev/sd0 bs=1M in order to achieve paranoid disk-wiping? BR Andreas
Re: fsck: CANNOT READ: BLK 4235468160
When you enter the realm of hardware errors, anything can happen. If you are lucky you will see the same hard and soft errors every time you cross a bad sector, but I have seen many cases wildly varying block numbers on really sick disks. And yes, bad cables and USB interfaces can be a problem too. Try wiggling the cable disk the disk stable and see if you can produce errors. Try doing a read with that USB hardware on another disk, too. That will tell you something. I'll bet that the disk is bad. If it stops producing errors, don't forgive it! Get a new one. --STeve Andre' On 01/06/18 21:45, Maximilian Pichler wrote: Hi, I'm running fsck on an external USB hard drive, using OpenBSD 6.2 inside VirtualBox on MacOS. On each run it gives a handful of "CANNOT READ: BLK ..." messages, but the block numbers reported are different (!) each time. If the disk is damaged, shouldn't the problematic blocks be consistent? Does this point to a communication problem with the disk (e.g. faulty USB cable)? Or is this a hopelessly unstable situation given the general screwiness of USB over VirtualBox/Mac OS...? Also, does answering "y" to "CANNOT READ" modify the disk contents? Thanks for any insights! Max xhci0 at pci0 dev 12 function 0 "Intel 7 Series xHCI" rev 0x00: apic 2 int 20 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 umass0 at uhub0 port 9 configuration 1 interface 0 "Seagate Expansion" rev 3.00/0.00 addr 2 umass0: using SCSI over Bulk-Only scsibus4 at umass0: 2 targets, initiator 0 sd0 at scsibus4 targ 1 lun 0: <Seagate, Expansion, 9300> SCSI4 0/direct fixed sd0: 3815447MB, 512 bytes/sector, 7814037167 sectors $ doas fsck /dev/sd0a ** /dev/rsd0a ** Last Mounted on /home/max/mnt ** Phase 1 - Check Blocks and Sizes CANNOT READ: BLK 4235468160 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4128081280 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4194986880 CONTINUE? [Fyn?] y CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: ** Phase 2 - Check Pathnames CANNOT READ: BLK 4195146384 CONTINUE? [Fyn?] y CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 614222 files, 408012667 used, 76524122 free (3658 frags, 9565058 blocks, 0.0% fragmentation) MARK FILE SYSTEM CLEAN? [Fyn?] y * FILE SYSTEM WAS MODIFIED * $ doas fsck -f /dev/sd0a ** /dev/rsd0a ** File system is already clean ** Last Mounted on /home/max/mnt ** Phase 1 - Check Blocks and Sizes CANNOT READ: BLK 4236615424 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: ** Phase 2 - Check Pathnames CANNOT READ: BLK 3732315520 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4161885792 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4201995728 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4202008160 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: CANNOT READ: BLK 4202013680 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups CANNOT READ: BLK 5011229824 CONTINUE? [Fyn?] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 614222 files, 408012667 used, 76524122 free (3658 frags, 9565058 blocks, 0.0% fragmentation)
Guess what today is
Happy birthday to OpenBSD--22 years old!
Trying to burn a 4.5G dvd
Doing my usual growisofs -dvd-compat -Z /dev/rcd0c=image.iso results in the error mkisofs: Value too large to be stored in data type. File 4P4WFA00_W10x64ROW_proDL.iso is too large for current mkisofs settings - ignoring So far I do not see what needs to be changed in order to do this and a scan of marc.info and faq aren't helping. Clues? I'm pinched for time. Thanks... --STeve Andre'
Re: Limits on OBSD amd64
On 05/26/17 10:28, Stuart Henderson wrote: On 2017-05-26, Friedrich Locke <friedrich.lo...@gmail.com> wrote: Hi folks, i wonder what is the maximum file system size OBSD supports using different file systems like FFS afaik, this is 1TB FFS2 "as much as you have RAM to fsck"... and ZFS ? 0 bytes. On a 10T disk I created an 8T file with dd=/dev/zero of=bff. I didn't test it, but saw that I had the correct amount of space left. --STeve Andre'
Re: list all system users, eg. _x11
On 05/06/17 14:27, Luke Small wrote: Is there a way to determine all users on a system that the users command doesn't seem to show? like _x11 and _ntpd What's a user? Maybe you want to look at /etc/passwd. The first four lines are root:*:0:0:Charlie &:/root:/bin/ksh daemon:*:1:1:The devil himself:/root:/sbin/nologin operator:*:2:5:System &:/operator:/sbin/nologin bin:*:3:7:Binaries Commands and Source:/:/sbin/nologin You can parse that with awk and do stuff. Read about passwd(5) to understand the format. A login shell of /sbin/nologin means it isn't interactive. That might get you started? --STeve Andre'
Re: Etnernal & infernal browser woes
On 04/28/17 09:00, David Coppa wrote: On Fri, Apr 28, 2017 at 2:18 PM, Jyri Hovila [iki.fi] <jyri.hov...@iki.fi> wrote: Dear everyone, With the above disclaimer said, and still knowing the potential for a war, I must say this: There is not much hope for OpenBSD to ever become a desktop (or laptop) OS if the nightmarish sluggishness of ALL modern web browsers can not be solved. Have you properly configured your user? What I usually do is: 1) be sure my user has the "staff" class: # grep dcoppa /etc/master.passwd dcoppa:***:1000:1000:staff:0:0:David Coppa:/home/dcoppa:/bin/ksh 2) I have this at the top of my ~/.profile: ---8<--- # bump limits ulimit -S -d $(ulimit -H -d) ulimit -S -n $(ulimit -H -n) ulimit -S -p $(ulimit -H -p) ulimit -S -s $(ulimit -H -s) ---8<--- With chromium or iridium it's not as bad as you have described. Personally I use iridium on a daily basis. Ciao! David I agree with David. It's manageable. I switched from Firefox to chrome some time ago, along with otter and Iridium--the three browser lifestyle. Firefox causes my wife to snarl all too often, so it isn't the case that FF on Windows is so great. Gone are the days of a 2G web browsing system, mostly. I have a 32G thinkpad and make sure limits are ramped up to absurd limits. Is is slower? Sure, but I'll take that over a faster, diseased system any time. OpenBSD will improve. Windows will not. --STeve Andre'
Re: Load average changed in 6.1?
On 04/24/17 04:42, Christoph Borsbach wrote: Hello everyone, first off: I know that the topic of "load" has been discussed numerous times, and been a topic on undeadly [1]. I know that this number is not that important. However: After upgrading 3 of my systems to 6.1 (from 6.0) I noticed the load average (15min value) has gone up by roughly 1.0, both in the output of daily(8) over some days now and when checking manually with w, top, or uptime. The systems in question differ a bit: - amd64 MP (KVM-Guest, dmesg [2], load-example [3]) - amd64 SP (VMware Guest, dmesg and examples not handy right now) - i386 SP (Alix, dmesg [4], load examples [5]) All were upgraded last week with bsd.rd to 6.1-RELEASE. The systems perform as well as ever and nothing was changed aside from upgrading system and packages. I'm just interested what could change the behavior. A quick check of src/sys/uvm/uvm_meter.c does not show me any changes recently. Has anybody observed this as well and has an explanation for this? Thanks, Christoph Christoph, What has changed 6.0 - 6.1 is the entire operating system. uvm_meter.c may not have changed but the other sub-systems have, which effects the way things works. It's the same with playing mp3's and you get stutter (or not) when disk I/O or other things are in play. Any OS is a city; largely invisible to us, interactions go on that can have ripple effects in how things work. The concept of a load average is nebulous at best. You can spike the system averages any number of ways so using it to determine how busy the system is at any point in time is not great. Better to see how fast the system delivers web pages or files, or ... Perhaps the uptime / w documentation should explicitly say that comparing load avs on different versions is a bit like comparing apples to spark plugs. --STeve Andre'
Can't install -current on a Dell precision t3500
I'm puzzled and am asking for help. I'm attempting to install the -current snapshot (feb 12) on a Dell precision t3500. The install formats a 6T disk very quickly, like in 25 seconds. Hmm. After installing the tar files, installboot fails with a "Bad magic number in superblock". If I mount the a partition I see real data. Changing to a 160G disk everything works & boots, but not with the 6T disk. The t3500 is a sata 2 machine, as is the 160G disk. The 6T disk is sata 3, but since I see the OS written to the 6T disk it's been written out OK so thats not it. I'm missing something with regards the size of the disk? Probably I'm forgetting to include something relevant but I've been dealing with this last night and am tired. Clues? Thanks to all -- STeve Andre' dmesg OpenBSD 6.0-current (RAMDISK_CD) #164: Sun Feb 12 14:02:22 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD RTC BIOS diagnostic error 11 real mem = 12865998848 (12269MB) avail mem = 12472324096 (11894MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0450 (77 entries) bios0: vendor Dell Inc. version "A17" date 05/28/2013 bios0: Dell Inc. Precision WorkStation T3500 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET TCPA SLIC SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU W3680 @ 3.33GHz, .73 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 731530 Hz cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins acpiprt0 at acpi0: bus 1 (PCI1) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 4 (PCI4) acpiprt4 at acpi0: bus 5 (PCI5) acpiprt5 at acpi0: bus 6 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu at acpi0 not configured "PNP0C0C" at acpi0 not configured "*pnp0c14" at acpi0 not configured "PNP0401" at acpi0 not configured "PNP0501" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel X58 Host" rev 0x22 ppb0 at pci0 dev 1 function 0 "Intel X58 PCIE" rev 0x22: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 3 function 0 "Intel X58 PCIE" rev 0x22: msi pci2 at ppb1 bus 2 vga1 at pci2 dev 0 function 0 "ATI FirePro V4800" rev 0x00 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "ATI Radeon HD 5600 Audio" rev 0x00 at pci2 dev 0 function 1 not configured ppb2 at pci0 dev 7 function 0 "Intel X58 PCIE" rev 0x22: msi pci3 at ppb2 bus 3 "Intel X58 Misc" rev 0x22 at pci0 dev 20 function 0 not configured "Intel X58 GPIO" rev 0x22 at pci0 dev 20 function 1 not configured "Intel X58 RAS" rev 0x22 at pci0 dev 20 function 2 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801JI USB" rev 0x00: apic 8 int 16 uhci1 at pci0 dev 26 function 1 "Intel 82801JI USB" rev 0x00: apic 8 int 17 uhci2 at pci0 dev 26 function 2 "Intel 82801JI USB" rev 0x00: apic 8 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801JI USB" rev 0x00: apic 8 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1ppb3 at pci0 dev 28 function 0 "Intel 82801JI PCIE" rev 0x00: msi pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 5 "Intel 82801JI PCIE" rev 0x00 pci5 at ppb4 bus 5 bge0 at pci5 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1 (0x5761100): msi, address b8:ac:6f:96:76:63 brgphy0 at bge0 phy 1: BCM5761 10/100/1000baseT PHY, rev. 0 uhci3 at pci0 dev 29 function 0 "Intel 82801JI USB" rev 0x00: apic 8 int 23 uhci4 at pci0 dev 29 function 1 "Intel 82801JI USB" rev 0x00: apic 8 int 17 uhci5 at pci0 dev 29 function 2 "Intel 82801JI USB" rev 0x00: apic 8 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801JI USB" rev 0x00: apic 8 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x90 pci6 at ppb5 bus 6 "Intel 82801JIR LPC" rev 0x00 at pci0 dev 31 function 0 not configured ahci0 at pci0 dev 31 function 2 "Intel 82801JI AHCI" rev 0x00:
Re: Laptop Recommendations?
On 11/10/16 00:47, Nathan Koch wrote: Greetings Fair BSD Wizards, I am new to the lists. I am currently shopping for a new Xmas present for myself and am looking for a laptop that's portable and lightweight. Preferably fast, cheap (close to free), light, and secure. If you have any recommendations before the stormy winter hits the prairies please let me know. Thank you. Nate Sailing the South Saskatchewan. I have used ThinkPads with great success: - T60p: everything worked - W500: everything worked - W541: camera and SDHC cards wern't working last time I checked, which was a while ago. Everything else is fine. Well, maybe the docking adaptor is still problematic. - A31p: which is now long obsolete, but it worked well. W500's can be had on ebay in the $280 class range, then add extra mem and a large disk, etc. --STeve Andre
Re: Dell R930 server
On 11/06/16 20:35, Philip Guenther wrote: On Sun, Nov 6, 2016 at 4:42 PM, Friedrich Locke <friedrich.lo...@gmail.com> wrote: ... Does OBSD "see" all the 96*128G memory available ? We only allocate a single PML4 slot for the direct map on amd64, so it's currently limited to seeing 2^39 == 512GB. To expand that, the size and base-slot/address of the direct map really need to be made variable, based on the number of physical address bits supported by the CPU (as found by CPUID), preferably then clamped by the range of the actual memory installed, and then set up in locore.S and pmap.c Philip Guenther Thanks for the explanation of the memory limit. I'm not needing a system with more than 512G yet, but how much of a project would it be to dynamically expand to whatever? --STeve Andre'
Happy Birthday
Happy Birthday to OpenBSD. Hey, it's 21. It can drink in Michigan now!
Re: i386 or amd64?
On 09/20/16 19:38, Jeff Ross wrote:
Hi all,
I've had a server with corenetworks for quite a few years now but after
changes at corenetworks (their recent name change after acquisition by
another company, no current servers available, no communication about
the change of ownership with existing customers and an email exchange
with sales@), I've decided it is best jump ship now rather than wait for
a hard and possibly immediate deadline.
I've just rented a server with 8GB of ram from m5hosting (based in large
part from the many recommendations I read while searching misc@ on
marc.info). Now the question is: i386 which is what I've always run on
my 2 GB ram server, or amd64? http://www.openbsd.org/amd64.html and
http://www.openbsd.org/i386.html are curiously silent on the amount of
ram that can be accessed. If I have 8GB, I for sure want to use it all.
I know there was a time when i386 was limited to the amount of ram it
can access (32 bit) but now amd64 has this caveat: "(Some Intel
processors lack support for important PAE NX bit, which means those
machines will run without any W^X support -- it is thus safer to run
those machines in i386 mode)." How does this fit with the recent work
in 6.0+? How can I tell if the Xeon 3220 processor has the PAE NX bit?
I see nothing in the tech sheet about PAE NX.
http://ark.intel.com/products/28034/Intel-Xeon-Processor-X3220-8M-Cache-2_40-GHz-1066-MHz-FSB
I have a little less than 2 weeks to make the transition so not a lot of
time for install and try.
Thanks in advance for any suggestions--dmesgs supplied once I get access.
Jeff Ross
Open Vistas Networking
AMD64. There isn't a real future in 32-bit stuff. I have some great
old Dells ("white optiplex") that I'll eventually get rid of but have
kept because of their quality. But they do have the 3G problem. So
look forwards at 65-bit. I don't think you'll look back.
--STeve Andre'
Re: Building OpenBSD 6.0 -stable - Error
On 09/03/16 11:32, Harald Dunkel wrote: On 09/03/16 12:40, Ted Unangst wrote: Teno Deuter wrote: installed a fresh 6.0 AMD64 and tried to build 'stable' from source. Here is what I did as 'root' (as described in: http://www.openbsd.org/stable.html): export CVSROOT=anon...@anoncvs1.ca.openbsd.org:/cvs cd /usr; cvs checkout -P -rOPENBSD_6_0 src there's some repo surgery in progress. it should be fixed eventually. What exactly does this mean? It means that something went wrong, and steps were being taken to fix it. Not very often, cvs has problems and getting good copies of stuff doesn't work. This is always noticed and repaired fairly quickly. Also, if a repository is down, people have noticed it and are working on it, so messages to @misc such as "I can't update from xxx" are somewhat useless. The ecosystem for distributing software is not perfect. When you find a problem, wait, and try again. Repeat if needed. --STeve Andre'
Strange problem with symlink usage in apache2 / wordpress-4.5.3
I write this having solved the problem I was having, but I feel weird about my solution for it. This is an amd64 -current system compiled on Aug 8th, with packages from Aug 9th. An Optiplex 745 at 2.4GHz, 8G ram using the stock GENERIC kernel. A vanilla system for Wordpress 4.53 using PHP-5.6.23 and Maria 10.0.26v1 with apache 2.4.23. /etc/login.conf had limits raised to infinity. The system was updated just before the wx changes. Under a light load Wordpress worked as expected. But every once in a while, an ah00037 ( Symbolic link not allowed or link target not accessible) error popped up. The client would see a page not accessible message. Under a heavy load of wget scripts the error was just about constant. Going back in the browser would get things working after a page denial, at least for a bit. Pages that once worked came up with the error often. After a period of time pages would generally not work at all. The fix to get apache working again was to restart it, but lots of wget scripts would ramp the problem up again. My "fix" was to get rid of the symlink of /var/www/htdocs to /u, and making /var/www/htdocs the main code area. In a 4 hour test with multiple wget scripts, it served about 113,000 pages without error, about 8 per second. After that test I was convinced the "fix" worked. But why? The basic apache/system setup was correct I pretty sure, or wordpress would have never worked. The problem seems like it's load related. If anyone can say "idiot--you forgot N Q and Z" I'd like top hear it, but I think I have found a bug either in Apache or OpenBSD. Ideas on the best way to test symlinks? I haven't found any comments on a symlink problem in apache or wrodpress. All the ah00037 comments talk of stuff I already verified. I'm certainly willing to do more work on this--I'd appreciate any ideas on what to test. I've never seen an error like this before... Right now I feel uncomfortably dumb. Thanks for ideas... --STeve Andre'
Re: Recent package archives?
On 08/21/16 17:29, Stuart Henderson wrote:
On 2016-08-21, STeve Andre' <and...@msu.edu> wrote:
Does anyone have archives of recent amd64 snapshot packages?
I blew my aug-09 set away and I'd like libreoffice back. Anyone?
(And yes, I know it's always a gamble to mismatch packages and the OS)
Thanks, STeve Andre'
The last snapshot package built for libreoffice is against old X
libraries so if you run them you get symbol conflicts (old package
wanting libfreetype.so.25.0 but *also* pulling in X libraries linked
against libfreetype.so.26.0).
libreoffice builds from ports are currently failing due to W^X enforcement
("uno.bin(39666): mprotect W^X violation" when running code which is produced
during the build as part of the build). I'm hoping that the recently
committed change to ports gcc will let us work around this for now (I'll
be testing this shortly) and then once we've got a working build of libreoffice
again it will hopefully be simpler to track down the libreoffice code that
currently needs W+X mappings - we can set kern.wxabort=1 sysctl and
get some kind of coredump.
Thanks Stuart. I figured that was the general problem.
--STeve Andre'
Re: Recent package archives?
On 08/21/16 01:01, bytevolc...@safe-mail.net wrote: STeve Andre' wrote: Does anyone have archives of recent amd64 snapshot packages? I blew my aug-09 set away and I'd like libreoffice back. Anyone? (And yes, I know it's always a gamble to mismatch packages and the OS) Thanks, STeve Andre' You won't get it from the original *.openbsd.org mirrors but try it from the other mirrors; sometimes they have versions back to the good old days. Heh. I've been trawling the list of mirrors on the download page, and I'm impressed--the oldest I've yet seen is the 18th. I'd say that the mirrors are more up to date than 5+ years ago. I'm mostly done trawling, hence this query. --STeve Andre'
Recent package archives?
Does anyone have archives of recent amd64 snapshot packages? I blew my aug-09 set away and I'd like libreoffice back. Anyone? (And yes, I know it's always a gamble to mismatch packages and the OS) Thanks, STeve Andre'
Re: problem trying to import a 3.4m database with phpmyadmin
Well guess what--I fixed it. In /etc/php5-6.ini, a semi-colon is used for comment lines. I used a colon. It misparses things when you do that. Silently. I need to clean my eyeballs now... Sorry for the noise, but at least you can remember this. (reason 416 to not be crazy about php...) --STeve Andre' On 08/15/16 05:41, STeve Andre' wrote: This is on an amd64 -current system updated/compiled as of Aug 8 7am; using the 8/13 packages. I'm trying to use phpMyAdmin to import a database into maria. in /etc/php-5.6ini I've set memory_limit to 256m, post_max_size to 16m and upload_max_filesize to 8m. The db I'm trying to import is 3.4m. Under import in phpmyadmin it says (max 2,048k) for importing, hence my doing what php faq 1.16 said about the above three params in php.ini. Now I notice that suhosin says in /var/log/messages ALERT - script tried to disable memory_limit by setting it to a negative value -1 bytes which is not allowed (attacker '10.0.0.5', file '/u/php/www/import.php', line 296) So, I am wondering how suhosin is seeing this, and how one gets phpmyadmin to deal with > 2M files. That is always says 2,048K says I'm not changing things correctly? I've restarted apache and even rebooted but I always get the 2M max notice. Any ideas? I'm pressed for time on this, sigh. Pointers would be much appreciated. --STeve Andre'
problem trying to import a 3.4m database with phpmyadmin
This is on an amd64 -current system updated/compiled as of Aug 8 7am; using the 8/13 packages. I'm trying to use phpMyAdmin to import a database into maria. in /etc/php-5.6ini I've set memory_limit to 256m, post_max_size to 16m and upload_max_filesize to 8m. The db I'm trying to import is 3.4m. Under import in phpmyadmin it says (max 2,048k) for importing, hence my doing what php faq 1.16 said about the above three params in php.ini. Now I notice that suhosin says in /var/log/messages ALERT - script tried to disable memory_limit by setting it to a negative value -1 bytes which is not allowed (attacker '10.0.0.5', file '/u/php/www/import.php', line 296) So, I am wondering how suhosin is seeing this, and how one gets phpmyadmin to deal with > 2M files. That is always says 2,048K says I'm not changing things correctly? I've restarted apache and even rebooted but I always get the 2M max notice. Any ideas? I'm pressed for time on this, sigh. Pointers would be much appreciated. --STeve Andre'
Interesting error message from disk testing
I am testing some new 8TB disks. I've taken to doing dd if=/dev/zero of=/dev/rsd3c bs=64k and dd if=/dev/rsd3c of=/dev/null bs=64k as a first test. It's depressing how often I've found problems on big disks. Today, the read test produced an error in the messages file I've not seen before: Jun 28 16:17:39 paladin /bsd: sd3(umass0:1:0): Check Condition (error 0x70) on opcode 0x28 Jun 28 16:17:39 paladin /bsd: SENSE KEY: Aborted Command Jun 28 16:17:39 paladin /bsd: ASC/ASCQ: Information Unit iuCRC Error Detected So it isn't a soft read error -- what is it? It might be useful to indicate where the error occurred? This is the second of three disks to be tested. It's connected to a Thermaltake USB 3.0 disk enclosure. Thanks for any pointers. --STeve Andre'
Re: Is it possible and not unadvisable to make /src with the -O3 option?...
Go for it. The beauty of open source is that you are free to try things. I would submit your first step of learning is how to figure out where all the -O2's are. You will learn a lot about things if you really dig into the weird problems you will hit. Probably you won't get much help here, but that shouldn't stop you. Hint: start reading about compilers. --STeve Andre' On 06/16/16 11:12, Luke Small wrote: Eh, I run it on a VM. I could copy one and somehow locate all the -O2's and replace them with -O3's in the files. I'd probably have to write a program to do it, unless there are easy to find, centrally located ones? On Thu, Jun 16, 2016 at 9:54 AM Janne Johansson <icepic...@gmail.com> wrote: Do you have the skills to detect and handle if gcc miscompiles something at -O3? If not, then don't. Noone else will help you getting a zomg-fast -O3 system working after a slight miscompile gets a few bad instructions stuffed into some lib somewhere, so if you break your system, you get to keep all the pieces. Short version: "if you had to ask, then the answer was no". 2016-06-16 15:42 GMT+02:00 Luke Small <lukensm...@gmail.com>: -- May the most significant bit of your life be positive.
Mod_rewrite.so use
Sorry not my usual mail program Sent with AquaMail for Android http://www.aqua-mail.com --- Forwarded message --- From: STeve Andre' <and...@msu.edu> Date: May 17, 2016 4:16:13 PM Subject: Mod_rewrite.so use I am creating a Web server using apache2. For the moment I need to use it. To enable mod_rewrite.so you simply uncomment it in httpd2.conf and restart apache, correct? I haven't used a2 before. This is a -current system with amd64 packages of may 15. Verifying that what I think is correct. This is using WordPress 4.5.2. Cough... Thanks for any clue bats. STeve Andre' Sent with AquaMail for Android http://www.aqua-mail.com
Re: support new
On 02/09/16 07:41, Ingo Schwarze wrote: Hi, William Mimart wrote on Mon, Feb 08, 2016 at 08:36:59PM +0100: 0 C FRANCE P Normandie T Rouen Z 76000 O mimart.info Sorry, but this doesn't make any sense to me. This entry wouldn't be related to OpenBSD at all. It seems to be something about kittens... Consequently, entry not added. Yours, Ingo Perhaps they can assist with kitten cake? I William Mimart A 63 rue des Hallettes M will...@mimart.info B +33 6 86 11 19 43 N Almost 30 years of experience in Unix systems including more than 10 on OpenBSD with a specialty in firewalls. Consulting, installation, maintenance, formation and support. Presque 30 ans d'exprience dans les systmes Unix dont plus de 10 sur OpenBSD avec une spcialit?? dans les pare-feu. Consulting, installation, maintenance, training and support.
Re: Pledge problem in tsort?
On 01/09/16 07:46, Sebastien Marie wrote: On Sat, Jan 09, 2016 at 03:40:08AM -0500, STeve Andre' wrote: I got the following error below after updating my tree about 02:42 am Jan 9 EST. Amd64 -current. I don't see anything special the the -current update faq. Are others seeing this? --STeve Andre' [...] tsort: pledge: Invalid argument cc: no input files Well, maybe we should document that in -current update faq. Several things occurs at near same time: - tsort was using the 2nd argument of pledge(2) : it has been corrected in tsort.c rev 1.35 (3 days old) - for preparing 5.9 release, we turn off this specific argument in rev 1.143 of sys/kern/kern_pledge.c (2 days old) So your "old" tsort (which use whitepaths in pledge) is incompatible with the "new" kernel you just compiled and booted (as it don't allow using whitepaths in pledge). And as tsort is used during building... "paf". You should be able to recompile and reinstall tsort, before rerun your make build. Something like: cd /usr/src/usr.bin/tsort && make clean && make obj && make depend && make && doas make install Thanks. Yes, my pea brain figured this out just about the time that Theo said to do this. It worked.Thanks to all.. --STeve Andre'
Pledge problem in tsort?
I got the following error below after updating my tree about 02:42 am Jan 9 EST. Amd64 -current. I don't see anything special the the -current update faq. Are others seeing this? --STeve Andre' building shared crypto library (version 37.0) cc -shared -fpic -o libcrypto.so.37.0 `lorder cryptlib.so malloc-wrapper.so mem_dbg.so cversion.so ex_data.so cpt_err.so o_time.so o_str.so o_init.so mem_clr.so aes_misc.so aes_ecb.so aes_cfb.so aes_ofb.so aes_ctr.so aes_ige.so aes_wrap.so a_object.so a_bitstr.so a_time.so a_int.so a_octet.so a_print.so a_type.so a_dup.so a_d2i_fp.so a_i2d_fp.so a_enum.so a_utf8.so a_sign.so a_digest.so a_verify.so a_mbstr.so a_strex.so x_algor.so x_val.so x_pubkey.so x_sig.so x_req.so x_attrib.so x_bignum.so x_long.so x_name.so x_x509.so x_x509a.so x_crl.so x_info.so x_spki.so nsseq.so x_nx509.so d2i_pu.so d2i_pr.so i2d_pu.so i2d_pr.so t_req.so t_x509.so t_x509a.so t_crl.so t_pkey.so t_spki.so t_bitst.so tasn_new.so tasn_fre.so tasn_enc.so tasn_dec.so tasn_utl.so tasn_typ.so tasn_prn.so ameth_lib.so f_int.so f_string.so n_pkey.so f_enum.so x_pkey.so a_bool.so x_exten.so bio_asn1.so bio_ndef.so asn_mime.so asn1_gen.so asn1_par.so asn1_lib.so asn1_err.so a_bytes.so a_strnid.so evp_asn1.so asn_pack.so p5_pbe.so p5_pbev2.so p8_pkey.so asn_moid.so a_set.so a_time_tm.so bf_skey.so bf_ecb.so bf_cfb64.so bf_ofb64.so bio_lib.so bio_cb.so bio_err.so bss_mem.so bss_null.so bss_fd.so bss_file.so bss_sock.so bss_conn.so bf_null.so bf_buff.so b_print.so b_dump.so b_posix.so b_sock.so bss_acpt.so bf_nbio.so bss_log.so bss_bio.so bss_dgram.so bn_add.so bn_div.so bn_exp.so bn_lib.so bn_ctx.so bn_mul.so bn_mod.so bn_print.so bn_rand.so bn_shift.so bn_word.so bn_blind.so bn_kron.so bn_sqrt.so bn_gcd.so bn_prime.so bn_err.so bn_sqr.so bn_recp.so bn_mont.so bn_mpi.so bn_exp2.so bn_gf2m.so bn_nist.so bn_depr.so bn_const.so bn_x931p.so buffer.so buf_err.so buf_str.so cmll_cfb.so cmll_ctr.so cmll_ecb.so cmll_ofb.so c_skey.so c_ecb.so c_enc.so c_cfb64.so c_ofb64.so chacha.so cmac.so cm_ameth.so cm_pmeth.so comp_lib.so comp_err.so c_rle.so c_zlib.so conf_err.so conf_lib.so conf_api.so conf_def.so conf_mod.so conf_mall.so conf_sap.so cbc_cksm.so cbc_enc.so cfb64enc.so cfb_enc.so ecb3_enc.so ecb_enc.so enc_read.so enc_writ.so fcrypt.so ofb64enc.so ofb_enc.so pcbc_enc.so qud_cksm.so rand_key.so set_key.so xcbc_enc.so str2key.so cfb64ede.so ofb64ede.so ede_cbcm_enc.so dh_asn1.so dh_gen.so dh_key.so dh_lib.so dh_check.so dh_err.so dh_depr.so dh_ameth.so dh_pmeth.so dh_prn.so dsa_gen.so dsa_key.so dsa_lib.so dsa_asn1.so dsa_vrf.so dsa_sign.so dsa_err.so dsa_ossl.so dsa_depr.so dsa_ameth.so dsa_pmeth.so dsa_prn.so dso_dlfcn.so dso_err.so dso_lib.so dso_null.so dso_openssl.so ec_lib.so ecp_smpl.so ecp_mont.so ecp_nist.so ec_cvt.so ec_mult.so ec_err.so ec_curve.so ec_check.so ec_print.so ec_asn1.so ec_key.so ec2_smpl.so ec2_mult.so ec_ameth.so ec_pmeth.so eck_prn.so ecp_nistp224.so ecp_nistp256.so ecp_nistp521.so ecp_nistputil.so ecp_oct.so ec2_oct.so ec_oct.so ech_lib.so ech_key.so ech_err.so ecs_lib.so ecs_asn1.so ecs_ossl.so ecs_sign.so ecs_vrf.so ecs_err.so eng_err.so eng_lib.so eng_list.so eng_init.so eng_ctrl.so eng_table.so eng_pkey.so eng_fat.so eng_all.so tb_rsa.so tb_dsa.so tb_ecdsa.so tb_dh.so tb_ecdh.so tb_rand.so tb_store.so tb_cipher.so tb_digest.so tb_pkmeth.so tb_asnmth.so eng_openssl.so eng_cnf.so eng_dyn.so err.so err_all.so err_prn.so encode.so digest.so evp_enc.so evp_key.so e_des.so e_bf.so e_idea.so e_des3.so e_camellia.so e_rc4.so e_aes.so names.so e_xcbc_d.so e_rc2.so e_cast.so m_null.so m_md4.so m_md5.so m_sha1.so m_wp.so m_dss.so m_dss1.so m_ripemd.so m_ecdsa.so p_open.so p_seal.so p_sign.so p_verify.so p_lib.so p_enc.so p_dec.so bio_md.so bio_b64.so bio_enc.so evp_err.so e_null.so c_all.so evp_lib.so evp_pkey.so evp_pbe.so p5_crpt.so p5_crpt2.so e_old.so pmeth_lib.so pmeth_fn.so pmeth_gn.so m_sigver.so e_aes_cbc_hmac_sha1.so e_rc4_hmac_md5.so e_chacha.so evp_aead.so e_chacha20poly1305.so e_gost2814789.so m_gost2814789.so m_gostr341194.so m_streebog.so gost2814789.so gost89_keywrap.so gost89_params.so gost89imit_ameth.so gost89imit_pmeth.so gost_asn1.so gost_err.so gostr341001.so gostr341001_ameth.so gostr341001_key.so gostr341001_params.so gostr341001_pmeth.so gostr341194.so streebog.so hmac.so hm_ameth.so hm_pmeth.so i_cbc.so i_cfb64.so i_ofb64.so i_ecb.so i_skey.so krb5_asn.so lhash.so lh_stats.so md4_dgst.so md4_one.so md5_dgst.so md5_one.so cbc128.so ctr128.so cts128.so cfb128.so ofb128.so gcm128.so ccm128.so xts128.so o_names.so obj_dat.so obj_lib.so obj_err.so obj_xref.so ocsp_asn.so ocsp_ext.so ocsp_ht.so ocsp_lib.so ocsp_cl.so ocsp_srv.so ocsp_prn.so ocsp_vfy.so ocsp_err.so pem_sign.so pem_seal.so pem_info.so pem_lib.so pem_all.so pem_err.so pem_x509.so pem_xaux.so pem_oth.so pem_pk8.so pem_pkey.so pvkfmt.so p12_add.so p12_asn.so p12_attr.so p12_crpt.so p12_crt.so p12_decr.so p12_init.so p12_key.so p12_kiss.so
Re: Is OpenSMTPD worthy of OpenBSD inclusion?
You obviously never lived through the sendmail era. The smtpd code is very good. Bugs happen, and how the creators of a program react to them is what matters. The qualsys results were promptly dealt with. I don't think there is much to discuss other than diffs that further the project. STeve Andre' On October 5, 2015 12:47:18 PM EDT, "Jason A. Donenfeld" <ja...@zx2c4.com> wrote: >Hi folks, > >Like many others, when I learned that OpenBSD was creating from >scratch an SMTP daemon, I was thrilled. The OpenBSD name has for a >long time been connected with security, stability, and reliability. I >was excited to see an extremely easy to configure yet powerful SMTP >daemon coming from such a venerable project as OpenBSD. Overtime, >OpenSMTPD has replaced all other mail daemons for me, and I've been >pleased to use another OpenBSD project as part of my critical >infrastructure. Code from OpenBSD is code that the community has >learned to trust, a reputation matched by few other projects. > >It has been, therefore, to my extreme dismay to discover in recent >months the sheer number of critical security vulnerabilities - in some >cases, remotely exploitable - in OpenSMTPD. Just this past week, >Qualys has reported an impressive audit result [1], with a scary >remote code execution vulnerability among others, and last night I >discovered a remotely exploitable buffer overflow that was being >triggered in the wild [2]. If you comb through the OpenSMTPD misc >mailing list, you'll find scattered reports of other similar bugs -- >buffer overflows, remote denial of service vectors, and a host of >other nasty glitches and security vulnerabilities -- and if you look >at the CVS repository or git repository, you'll see other such goodies >baked in there; most of them haven't been publicly revealed as >security vulnerabilities and were not assigned CVEs, which is an >irreverent point for most reasonably skilled malicious actors. > >The fact is, OpenSMTPD has suffered a disproportionately high number >of security issues, especially for a daemon as important as it. It is >not living up to OpenBSD's reputation, and it threatens the >OpenBSD.org frontpage security claim. I do not any longer believe >OpenSMTPD to be software that is trustable for use in critical >infrastructure at this point in time. > >Personally, I am very attached to OpenSMTPD. I have contributed to its >development in, what I think to be, significant ways, and I maintain >both distribution packages for it (Gentoo), as well as my entire >infrastructure, which is based on OpenSMTPD. I've "bet the farm" on >the project, so to speak. > >But I think it's time we take a step back and reassess the situation. >There are some critical questions that need to be answered. What >accounts for the high proportion of security vulnerabilities in a >project renowned for its brilliant developers and stringent review >processes? Do the OpenSMTPD developers have time -- and have they >displayed a presence of necessary free time -- to keep the project >healthy and moving toward stability at an acceptable pace? Have the >correct standards of releases been applied to the OpenSMTPD release >process? > >And most importantly: should OpenSMTPD continue to be a part of the >core OpenBSD project? Or should it rather spend some time maturing and >securing commitments from developers for maintaining it in a >consistent manner, before being accepted by such a reputable >organization as OpenBSD? > >Finally, if OpenSMTPD does continue to exist as a part of core >OpenBSD, I would strongly recommend some effort is organized to bring >top quality code reviewers and auditors to the source code, in order >to give the project the eyeballs it deserves. It would be a great >boost in confidence for many who use - or hoped to someday use - >OpenSMTPD to see that intelligent minds, capable of securing large >codebases, have put their efforts into making it secure. > >I hope this can begin some discussion on the best way forward toward >making OpenSMTPD a piece of infrastructure we can trust. My best >wishes for the project. > >Regards, >Jason > > >[1] http://seclists.org/oss-sec/2015/q4/17 >[2] http://seclists.org/oss-sec/2015/q4/25
Package for taking a picture
I'm looking in the ports tree for something to test a camera that shows up as uvideo0. It looks like uvideo0 at uhub0 port 12 configuration 1 interface 0 8SSC20F26960L1GZ52304E9 Integrated Camera rev 2.00/10.04 addr 4 video0 at uvideo0. I'm sure I used something several years ago. It's great that the ports tree has gotten so big that you can't remember it all. ;-) Something to take a pic and put it in a file would be OK. --STeve Andre'
Re: hp laptop with nvidia - slow X11
On 06/15/15 17:19, Riccardo Mottola wrote: Hi, for the same laptop for which I just posted a full dmesg about the battery problem, which reports this video card: vga1 at pci1 dev 0 function 0 NVIDIA GeForce 8400M GS rev 0xa1 I get a super-slow X11. Dragging an xterm may take half a second, up to the point where X11 looses track of the mouse move events. Scrolling XTerm is unusably slwo too. Using a larger editor like Emacs or Firefox... even worse. It looks totally unacelercated. [snip] Sadly, Nvidia video cards are to be avoided. I think it would be fair to say that Nvidia is the most open-source hostile company out there. Because of this there is no Nvidia specific driver in OpenBSD. You are using it in vga compatible mode. Things work, but hardly with the speed that it delivers on Windows. There is a reverse engineered driver called nouveau. Look at https://en.wikipedia.org/wiki/Nouveau_(software) for more info. While theoretically portable to OpenBSD, it involves work, and when I looked at it a bit it was under constant change, such that a port dated Monday might be outdated by Saturday. I have a LOT of respect for the people doing this. It's hard. I did a little hardware poking on the 286, a long time ago. It's isn't simple. I also hope it was written under a reasonable license. Once nouveau stabilizes (I have no idea of its current state), someone may get the interest to port it. Maybe. But as of right now, it ought to be avoided. --STeve Andre'
Major improvement in CPU temperatures for -current
I just did a build of the world after seeing Philip Guenther's post on better using C-states in ACPI for cooler CPU temperatures. This is a *significant* improvement. I'm using a new ThinkPad, a w541. During my first world build I saw temperatures as high as 94C. It did not hit the fatal temperature to force a reboot but it was pretty hot. This was at 3.3GHz. After booting with the new kernel I wondered what the results would be. Keeping track of hw.sensors.acpithinkpad0.temp3 on my older w500 would typically be in the 86 - 92C range and then reboot if I was wasn't careful. This build the temperature was typically 78 - 80C, with one spike at 82C during the latter part of the xenocara build. My script checked every 17 seconds. I can say from this one test that there is a huge difference--10C, at least! The last time I saw such a significant change to OpenBSD was when soft deps came into the tree. If you can run -current on your laptop, you should consider it. It really is amazing. Later I will try to get a test jig in place such that I can measure current draw and compare, but heat == power, so I'm sure it's a success. Thank you Philip, et al! --STeve Andre' ps: more on the w541 later and a description to dm...@openbsd.org. -- original email Date: Sat, 13 Jun 2015 15:15:59 -0700 Subject: Re: CPU power consumption on thinkpad x201 From: Philip Guenther guent...@gmail.com To: Jingcheng Zhang dio...@gmail.com Cc: Shaun Reiger srei...@sprmail.net, misc@openbsd.org misc@openbsd.org On Thu, May 28, 2015 at 6:53 AM, Jingcheng Zhang dio...@gmail.com wrote: Another x201 user here, suffering from the same problem. Any news/solutions on this issue? I just committed support for using the deeper C-states advertised by ACPI, which in testing dropped the temperature on most laptops. Don't forget to send a dmesg to dm...@openbsd.org some time after you upgrade, so we can check for any problems found by the code! Philip Guenther -- w541 dmesg OpenBSD 5.7-current (GENERIC.MP) #0: Mon Jun 8 20:49:25 EDT 2015 r...@paladin.home.network:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33950375936 (32377MB) avail mem = 32917573632 (31392MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (68 entries) bios0: vendor LENOVO version GNET72WW (2.20 ) date 02/26/2015 bios0: LENOVO 20EGCTO1WW acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCP A UEFI MSDM ASF! BATB FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-4940MX CPU @ 3.10GHz, 798.31 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR, SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID, SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4940MX CPU @ 3.10GHz, 798.15 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR, SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID, SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,IT SC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4940MX CPU @ 3.10GHz, 798.15 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR, SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID, SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,IT SC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4940MX CPU @ 3.10GHz, 798.15 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR, SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID, SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C
Re: New LibreSSL mailing lists
On 06/03/15 22:23, Doug Hogan wrote: We have two new lists for LibreSSL: libre...@openbsd.org - public list for technical discussion about LibreSSL on any operating system. libressl-secur...@openbsd.org - private list for reporting severe vulnerabilities in OpenSSL or LibreSSL to the core LibreSSL team. See http://www.openbsd.org/mail.html for more details. libressl-security gives me an error: The libressl-security mailing list is not supported at OpenBSD Mailing List Server.
Re: OpenBSD on Dell m4800 -- Anybody tried it?
I would like to believe that, but OEMs are constantly changing hardware. Since everyone runs Windows, all they have to do is make sure the new frotzel works, and ship it. Over time, the parts that don't work will likely get drivers, but if you need a laptop that just runs right now, I would find a way to test it. --STeve Andre' On 04/15/15 14:28, Shaun Reiger wrote: Hi Ray, I haven't used a Dell Precision M4800 with OBSD yet, but I found that under PCBSD it should work. Given OBSD has very good laptop support I believe everything should be detected. I have included a link to the PCBSD site where I found the your laptop listed. http://wiki.pcbsd.org/index.php/Hardware Cheers, Shaun On Tue, Apr 14, 2015 at 6:17 PM, Raymond Lillard r...@prosysmeg.com wrote: I am considering the purchase of a Dell Precision M4800 laptop with the intention of installing OpenBSD on it. Has anyone here ran OBSD on one of these? I will configure it with an AMD FirePro M5100. Google has fail to find anyone who has tried this. Thanks Ray
Suggestion for the 5.7 page
It might be good to include R under the highlights section. It's growing in popularity; I know I've gotten questions about it being in OpenBSD. It's really cool to show the ports tree now. Most all the important things are there now, at least for non-technical people. R is a useful addition to that, I think. --STeve Andre'
Re: What's wrong with script(1)?
On 01/29/15 18:16, openda...@hushmail.com wrote: Hi Marc / Otto! On 29. januar 2015 at 7:07 PM, Marc Espie es...@nerim.net wrote: And it shouldn't ! script(1) is often used for debugging purposes, and that noise becomes paramount to figuring out what's going on. Thanks, I had no idea. Would it be possible though to mention some use cases where the noise is necessary? Many thanks! O.D. When you want to know exactly what a process is spewing out. CR's and all. Really, script(1) says that it catches everything printed onto the terminal in the first line. I've used script to find out escape sequences from programs, to figure out how cursor movement worked. I've also caught programs with many gigs of output, so I could look for weird little things it said (not my code, but I had to figure it out). Having the line breaks in there let me see each individual line which was useful. Lastly if you don't want to see them make an alias of cat/more with output going through tr(1) and you'll never see them again. That's the beauty of this world--you have little tools to make stuff happen the way you want. --STeve Andre'
Re: Following Current / Flag Day
On 01/26/15 19:34, Kurt Miller wrote: We narrowed the definition of what a static pie binary is in the kernel. This change is a flag day where newer kernels will not recognize older pie binaries making upgrading via source hard. If you are running an older version of -current, upgrade via snapshots prior to building a new kernel from source to get over this flag day. -Kurt Is the below the change that is the flag day? Or, when is the FD? Modified files: sys/kern : exec_elf.c Log message: Require EFT shared objects have a PT_PHDR entry to be considered a pie binary. The kernel will now reject executing a typical shared library with EINVAL. This breaks compatibility with initial static pie binaries and requires a recent user-land prior to upgrading. In addition, more fine grained errors can be returned from execve(2) when errors occur while attempting to execute ELF objects. okay guenther@, kettenis@, deraadt@ --STeve Andre'
Re: Following Current / Flag Day
On 01/27/15 00:16, Theo de Raadt wrote: On 01/26/15 19:34, Kurt Miller wrote: We narrowed the definition of what a static pie binary is in the kernel. This change is a flag day where newer kernels will not recognize older pie binaries making upgrading via source hard. If you are running an older version of -current, upgrade via snapshots prior to building a new kernel from source to get over this flag day. -Kurt Is the below the change that is the flag day? Or, when is the FD? Modified files: sys/kern : exec_elf.c Log message: Require EFT shared objects have a PT_PHDR entry to be considered a pie binary. The kernel will now reject executing a typical shared library with EINVAL. This breaks compatibility with initial static pie binaries and requires a recent user-land prior to upgrading. In addition, more fine grained errors can be returned from execve(2) when errors occur while attempting to execute ELF objects. okay guenther@, kettenis@, deraadt@ Look, you'll be fine. There is approximately a 3-4 day window about a 4 weeks or a month back, depending on architecture. Use snapshots, if in doubt. OK, already did that. The tense of the message is what made me question this. Thanks. --STeve Andre'
Re: AMD64 packages
On 12/11/14 05:59, FRIGN wrote: On Wed, 10 Dec 2014 21:27:46 -0500 STeve Andre' and...@msu.edu wrote: You might want to subscribe to the ports-changes changes list, which will show you what's been changed. The source-changes list will show you all the other cvs commits. Look at http://www.openbsd.org/mail.html Btw, now that the topic has come up. Is there a way to view the diffs quickly on a source- or port-change? Just reading the titles is not very helpful and I also don't feel like pulling the entire OpenBSD CVS-tree just to view the recent code-changes. I'm subscribed to numerous mailing lists, and all of them provide diff-data in the mail itself. I'm sure more people would subscribe to such a list if it actually encouraged to read and check the source. Cheers FRIGN Have you looked at http://cvsweb.openbsd.org/cgi-bin/cvsweb/ ? You can get a diff of the change of any revision, which should help out. --STeve Andre'
Re: AMD64 packages
On 12/10/14 20:51, Stan Gammons wrote: When will new packages be built for AMD64? I'm getting library errors with the latest snapshot and the current packages. Stan They come out frequently, but not on a set schedule. Since the last set came out on the 6th, I would expect the next set in the next several days -- unless some change caused a cascade of non-compiles in which case the problem will be worked on before the next release. You might want to subscribe to the ports-changes changes list, which will show you what's been changed. The source-changes list will show you all the other cvs commits. Look at http://www.openbsd.org/mail.html
intermittent problems compiling kdrive in xenocara
So, I am dumb. Problem is, I don't know what it is that I don't know. Every once in a while compiling xenocara, I get a fatal error when dealing with kdrive. I've looked for emails talking about this and haven't found anything. I've gone over release(8) and think I'm OK. What's frustrating is that this error comes and goes. Sometimes for months at a time things are OK. I've resorted to getting a new copy of xenocara when this happens, which is dumb. I'm using the anoncvs server at spacehopper.org. Since others aren't complaining about this it must be me. So then, how am I shooting myself (this time) ? Clue sticks? Error below. tnx, STeve Andre' === kdrive cd /usr/xenocara/kdrive exec make -f Makefile.bsd-wrapper cleandir cd /usr/xenocara/kdrive exec make -f Makefile.bsd-wrapper depend no dependencies here yet cd /usr/xenocara/kdrive exec make -f Makefile.bsd-wrapper all PKG_CONFIG_LIBDIR=/usr/lib/pkgconfig:/usr/X11R6/lib/pkgconfig CONFIG_SITE=/usr/xenocara/etc/config.site CFLAGS=-O2 -pipe MAKE=make PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin exec sh /usr/xenocara/kdrive/../xserver/configure --prefix=/usr/X11R6 --sysconfdir=/etc --mandir=/usr/X11R6/man --cache-file=/usr/xobj/xorg-config.cache.amd64 --localstatedir=/var --sysconfdir=/etc/X11 --with-xkb-path=/usr/X11R6/share/X11/xkb --with-xkb-output=/var/db/xkb --with-default-xkb-rules=base --disable-xorg --enable-xcsecurity --enable-kdrive --disable-dmx --disable-xnest --disable-xvfb --without-fop --without-xmlto --without-xsltproc --disable-silent-rules configure: loading site script /usr/xenocara/etc/config.site configure: creating cache /usr/xobj/xorg-config.cache.amd64 /usr/xenocara/kdrive/../xserver/configure[3569]: cannot create /usr/xobj/xorg-config.cache.amd64: No such file or directory checking for a BSD-compatible install... (cached) /usr/bin/install -p checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) awk checking whether make sets $(MAKE)... (cached) yes configure: error: source directory already configured; run make distclean there first *** Error 1 in kdrive (/usr/X11R6/share/mk/bsd.xorg.mk:179 'config.status') *** Error 1 in kdrive (/usr/X11R6/share/mk/bsd.xorg.mk:211 'build') *** Error 1 in . (bsd.subdir.mk:48 'realbuild') *** Error 1 in /usr/xenocara (Makefile:36 'build')
Re: Non-functional battery stuck at 55% on ThinkPad T420 upgrade since 5.6-stable upgrade
On 11/05/14 11:40, Peter wrote: Hello all, Since upgrading to 5.6-stable my ThinkPad T20 battery doesn't work. The OS recognizes the battery but it's stuck at 55% and won't recharge. It won't boot without AC power. I'm running apmd(8) without modifications. Did I forget some option when I reinstalled? Any help would be greatly appreciated. Thanks, Peter [snip] I had a Windows user on a Txxx thinkpad last year that had the same kind of problem. Sometimes things get weird with tp batteries. Three suggestions: 1. Take the battery out, unplugged from AC and try to start it. This drains whatever capacitive storage it might have. Leave it alone for an hour then plug it together and try it. 2. Boot anything else, like a live CD and see if the battery problem is the same. 3. kill apmd and see if that changes anything. --STeve Andre'
nobody spoke up, about today?
Happy birthday, OpenBSD!
Re: Trying to create softraid crypto part
So The partition has to be raid, vs 4.2 BSD Onward to my new disk... --STeve Andre' Sent with AquaMail for Android http://www.aqua-mail.com On October 6, 2014 12:22:25 AM STeve Andre' and...@msu.edu wrote: So I am missing something, or being dumb. sd0j is a 128g piece of disk. Doing bioctl -c C -l /dev/sd0j softraid0 Gives softraid0: invalid metadata format What am I missing? This is an amd64 snap of Oct 4th. The vnconfig way of encryption has worked till I decided to do things the new way. Thanks for clues, STeve Andre' Sent with AquaMail for Android http://www.aqua-mail.com
Trying to create softraid crypto part
So I am missing something, or being dumb. sd0j is a 128g piece of disk. Doing bioctl -c C -l /dev/sd0j softraid0 Gives softraid0: invalid metadata format What am I missing? This is an amd64 snap of Oct 4th. The vnconfig way of encryption has worked till I decided to do things the new way. Thanks for clues, STeve Andre' Sent with AquaMail for Android http://www.aqua-mail.com
W540 Thinkpads
Is anyone using one with OpenBSD? Email me directly if you are willing to talk. Thanks, STeve Andre'
Re: problem with sound card
On 08/16/14 19:30, Long Wind wrote: does that really help? OpenBSD 5.5 (GENERIC) #276: Wed Mar 5 09:57:06 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Celeron (GenuineIntel 686-class, 128KB L2 cache) 435 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR,PERF real mem = 335036416 (319MB) avail mem = 317255680 (302MB) [snip] Yes, it can at times. I have seen cases where something you wouldn't have expected causing problems elsewhere. Also, things like bios levels can impact things. Given how big the dmesg data is, it's always reasonable to post it. --STeve Andre'
Re: 5.4 (GENERIC) box has begun to randomly reboot
On 08/05/14 10:02, Craig R. Skinner wrote: Hi, A reliable box has begun to randomly reboot in the last couple of days. There's nothing obviously unusual in /var/log/* $ ls -ld /var/crash drwxrwx--- 2 root wheel 512 Dec 24 2013 /var/crash/ $ ls -lA /var/crash total 4 -rw-r--r-- 1 root wheel 5 Jul 30 2013 minfree I set up a 1 min cron job of sysctl | fgrep hw.sensors.lm1.temp uptime The last one before a reboot was: hw.sensors.lm1.temp0=34.00 degC hw.sensors.lm1.temp2=33.50 degC 2:53PM up 31 mins, 2 users, load averages: 0.13, 0.19, 0.23 I'm guessing some bit of hardware is on it's way out, but which? $ ls -l /var/run/dmesg.boot -rw-r--r-- 1 root wheel 3612 Aug 5 14:58 /var/run/dmesg.boot OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class, 128KB L2 cache) 635 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR,SSE,PERF real mem = 535228416 (510MB) avail mem = 515035136 (491MB) So, a nice venerable P III.. I have several Dell's of that vintage all running well, after 10+ years. Me, I'd get the memtest CD and use that for a start. Easy. In decreasing order I'd say 5) motherboard problem, 4) power supply, 3) memory, 2) cabling failure, 1) disk controller. I did once have a really strange problem of crashing, which turned out to be the on-board IDE controller. I put a Siig sata controller in it and still works today. So a varient on )5. Don't forget about dust and around the fans. I'd take it outside and use compressed air of some kind to clean it. Good luck... --STeve Andre'
Re: Package installation
On 08/02/14 07:17, Gustav Fransson Nyvell wrote: On 08/02/14 13:13, Gustav Fransson Nyvell wrote: On 08/02/14 12:54, Marc Espie wrote: On Sat, Aug 02, 2014 at 12:26:06PM +0200, Gustav Fransson Nyvell wrote: Hi, there, I wanted to run something by you, mkay. About package management. I wonder if this has been shouted at already. I remember from SunOS that packages are installed in a different manner than let's say Red Hat and of course OpenBSD. They install it in the form /pkgs/PROGRAM/VERSION, example /pkgs/gimp/1.0. GoboLinux does this. I think this has some advantages over installing /usr/local/bin/gimp1.1 and /usr/local/bin/gimp2.0. What do you think? What have you said? Ready to be shouted at; This puts more strain on the file system actually, which is probably the main reason we don't do it. Also, there is generally a lot of churning to do to make the package self-contained. As far as policy goes, having stuff set up like that looks more flexible, but it is a fallacy. Instead of having the distribution solve issues concerning incompatible versions and updates, the toll falls instead on the individual sysadmin, to make sure things they have work together. It can lead to security nightmares, because it's so simple to have the newer version alongside the old version that sticky points of updating take much longer to resolve. It's a bit like having mitigation measures that you can turn on and off... if it's possible to turn these off, there's not enough incentive to actually fix issues. Likewise for packages. By making it somewhat LESS convenient to install several versions of the same piece of software, we make it more important to do timely updates. Also, we don't have the manpower to properly manage lots of distinct versions of the same software. So this kind of setup would be detrimental to actually testing stuff. I guess there could be both. But I think that if there's a security issue with one version of a software then there quite possibly are multiple ways of limiting the impact of that issue. Disallowing multiple versions to force people to upgrade is not really a good reason, from how I see it. Old software will always have more holes, because they're older and more well observed, but they have qualities, too, like speed. GIMP-1.0 is amazing on Lenovo X41 from 2005, but probably has bugs. Of course none of these systems will stop someone who wants to run version x of a software. Maybe something entirely different is needed? Okay, maybe I should complain about the status quo... thing is when packages install in /var, /usr, /etc and /opt they're so spread out it's hard to know what is what. This might be because I'm new but/and scripts can find orphan files in this structures, but you need the scripts for that. Having everything in /pkgs/PKG/VER would not cause this splatter. Programs without dependees (i.e. non-libs, non-utilprograms) could fit in this structure without any extra filesystem magic. Well, the grass is always greener. BTW, you create multiple versions by your mere existence. There are lots of old versions laying around, but they can't be installed together right now. No, I have multiple versions by experience and usage of a package. If I want multiple versions of something, I'll take the older version of and modify it to call the older version of it's libraries, etc. I have done this on one occasion. It wasn't fun but it was doable, for the period I wanted both around. OpenBSD's philosophy of packages bound together, with a specific version of the OS is entirely reasonable. You don't want to have versions of the same thing running, or at least you shouldn't. If you do, virtualizing might be a more sane way to go. This is all open source, and you have the freedom to change, or mangle things as you wish.. --STeve Andre'
Re: fxp driver - bsd.rd vs bsd
First guess is do you have /etc/mygate ? --STeve Andre' On June 24, 2014 3:47:27 PM EDT, Stefan Olsson stur...@hotmail.com wrote: Hi, My colleague is after trying to install Current onto an old Dell PC several times now. -She can go through the install without problem, she gets connected with dhcp and can download the filesets, so obviously she has network connection. -However, after rebooting into the freshly installed system (still set to dhcp), the machine will just not appear on the network. -While it was installing it could be pinged, but as soon as it restarts into the installed Current, it will not reply to ping anymore, it is not accessible over ssh and it is impossible to connect from it as well. -ifconfig fxp0 tells me that the state is active and it appears to have kept the same ip-address as it had when it was being installed. -Cables have been changed and it was connected to ports on other switches to no avail. -I was just wondering what would be the difference between being booted into bsd.rd vs bsd - in the latter fxp seems to have some kind of issue while it is working fine while in install-mode?-We will work around this issue by using a different machine, but I am still curious, how come it works fine while installing, but not when it is actually installed? Any clue-sticks to hit me with? Cheers
Re: Vision 2020: Making OpenBSD the world's fastest OS
On 06/10/14 01:17, Amit Kulkarni wrote: Lastly, I will remind you that the fastest OS compared to OpenBSD is very likely less than 15%. Say its 25% even, and you could get faster hardware to accomedate that. Come on, that is a false assertion. OpenBSD does have its warts, like everybody else out there. They are different warts compared to others. But IMHO running it slow with security is better than running it fast, and not paying attention to secuirty. It's false? You think OpenBSD is slower than 15%? I don't, based on a few tests run against some version of Debian. It was faster, both in terms of disk i/o and the running of a program that did a lot of computations with little output. It seemed to me to be less than 6%, using stopwatches but small enough to make me stop testing. But I think you agree with the general tone of this? --STeve Andre'
Re: Vision 2020: Making OpenBSD the world's fastest OS
On 03/05/14 10:08, openda...@hushmail.com wrote: Anybody have any thoughts on how to achieve this? Thanks. O.D. Lots of others have replied to this, but I'm going to jump in with a few comments. Probably the biggest reason OpenBSD will never be the fastest OS around is the simple fact that when optimizing for speed, you sacrifice other things. Like security. Security, or correctness, means you are looking for the most reliable way to do something, not the fastest. Mechanisms like pro-police (or a new name for it?) are going to slow things down a little. I think Theo said that all the security systems slow a system down by less than 5%. I believe that. The effect isn't huge but some would call that too much. Oh Well. When something can be done more efficiently, it is. But not at the cost of potential security problems. The MP code is a classic case of something written that strives to avoid race conditions at all costs. Me, I'd rather lose a few percent rather than have a hole. Lastly, I will remind you that the fastest OS compared to OpenBSD is very likely less than 15%. Say its 25% even, and you could get faster hardware to accomedate that. In an era of ever increasing hardware speed, optimizing on anything other than security and stability is foolish. --STeve Andre'
Problem compiling kde4/libs
Trying to compile kde4's libs I get the below error. I see it's related to the recent ssl changes, but I don't see what I need to do to get around this. The system is 5.5-current, compiled on June 4th. I love the GNU messasge, too. ;-) What am I missing here? I haven't found anything about this. Thanks, STeve Andre' /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: strcpy() is almost always misused, please use strlcpy() /usr/local/lib/qt4/libQtCore.so.9.0: warning: rand_r() isn't random; consider using arc4random() /usr/local/lib/qt4/libQtCore.so.9.0: warning: rand() isn't random; consider using arc4random() /usr/local/lib/qt4/libQtCore.so.9.0: warning: srand() seed choices are invariably poor /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: strcat() is almost always misused, please use strlcat() /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: sprintf() is often misused, please use snprintf() /usr/local/lib/libglib-2.0.so.4000.0: warning: stpcpy() is dangerous GNU crap; don't use it /usr/local/lib/libglib-2.0.so.4000.0: warning: vsprintf() is often misused, please use vsnprintf() /usr/lib/libkrb5.so.20.0: undefined reference to `RAND_egd_bytes' collect2: ld returned 1 exit status ninja: build stopped: subcommand failed. *** Error 1 in . (/usr/ports/devel/cmake/cmake.port.mk:31 'do-build': @cd /usr/ports/pobj/kdelibs-4.11.5/build-amd64 exec /usr/bin/env -i...) *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2691 '/usr/ports/pobj/kdelibs-4.11.5/build-amd64/.build_done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1890 '/usr/ports/packages/amd64/all/kdelibs-4.11.5p8.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2443 '_internal-package') *** Error 1 in /usr/ports/x11/kde4/libs (/usr/ports/infrastructure/mk/bsd.port.mk:2423 'package')
Re: Problem compiling kde4/libs
On 06/08/14 20:45, Nigel Taylor wrote: On 06/09/14 01:16, STeve Andre' wrote: Trying to compile kde4's libs I get the below error. I see it's related to the recent ssl changes, but I don't see what I need to do to get around this. The system is 5.5-current, compiled on June 4th. I love the GNU messasge, too. ;-) What am I missing here? I haven't found anything about this. Thanks, STeve Andre' /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: strcpy() is almost always misused, please use strlcpy() /usr/local/lib/qt4/libQtCore.so.9.0: warning: rand_r() isn't random; consider using arc4random() /usr/local/lib/qt4/libQtCore.so.9.0: warning: rand() isn't random; consider using arc4random() /usr/local/lib/qt4/libQtCore.so.9.0: warning: srand() seed choices are invariably poor /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: strcat() is almost always misused, please use strlcat() /usr/ports/pobj/kdelibs-4.11.5/build-amd64/lib/libkdecore.so.50.1: warning: sprintf() is often misused, please use snprintf() /usr/local/lib/libglib-2.0.so.4000.0: warning: stpcpy() is dangerous GNU crap; don't use it /usr/local/lib/libglib-2.0.so.4000.0: warning: vsprintf() is often misused, please use vsnprintf() /usr/lib/libkrb5.so.20.0: undefined reference to `RAND_egd_bytes' collect2: ld returned 1 exit status ninja: build stopped: subcommand failed. *** Error 1 in . (/usr/ports/devel/cmake/cmake.port.mk:31 'do-build': @cd /usr/ports/pobj/kdelibs-4.11.5/build-amd64 exec /usr/bin/env -i...) *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2691 '/usr/ports/pobj/kdelibs-4.11.5/build-amd64/.build_done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1890 '/usr/ports/packages/amd64/all/kdelibs-4.11.5p8.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2443 '_internal-package') *** Error 1 in /usr/ports/x11/kde4/libs (/usr/ports/infrastructure/mk/bsd.port.mk:2423 'package') See current 2014/04/22 - kerberosV removed libkrb5 should have been removed ha! of course! I will do that. Thank you, Nigel. --STeve Andre'
Re: CPU power consumption on thinkpad x201 on openbsd current
On 06/05/14 04:53, Johan Svensson wrote: On 06/05/14 00:53, STeve Andre' wrote: On 06/04/14 17:08, Johan Svensson wrote: I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201). The first problem that i came across was that the Cpu fanspeed was running constantly at 3500RPM. After the acpithinkpad.c patch from jcs (and i modified to make it work on the openbsd-current(link: http://exclude.se/patch/jcs_mod_by_js.diff) Another thing that i noticed is that the battery lifetime is really bad. In Linux i get around ~5,5 hours. In OpenBSD i get around 2 hours. when i ran : sysctl hw.sensors | grep -i consumption. the output of the cpu was 6W. in Linux it's around 1,5W. with: apmd -C and apmd -L it's the same. dmesg: http://exclude.se/openbsd/dmesg.txt Is there anyway to fix this? Regards Johan Svensson Take a look at hw.setperf in sysctl. I think you are running at the maximum cpu speed? On my 2.8GHz W500 I can run at 800, 1600, 2133 and 2801. 800MHz makes a huge difference. You have to try different values for setperf to see what happens. sysctl will also tell you the speed in hw.cpuspeed. --STeve Andre' This my output from sysctl and apm when running on the lowest clockspeed: # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption hw.sensors.acpithinkpad0.fan0=1959 RPM hw.sensors.itherm0.power0=6.00 W (CPU power consumption) hw.cpuspeed=1199 hw.setperf=0 # apm Battery state: high, 70% remaining, 111 minutes life estimate A/C adapter state: not connected Performance adjustment mode: manual (1199 MHz) This is the output when i use apm -H: # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption hw.sensors.acpithinkpad0.fan0=1972 RPM hw.sensors.itherm0.power0=6.00 W (CPU power consumption) hw.cpuspeed=2666 hw.setperf=100 # apm Battery state: high, 68% remaining, 107 minutes life estimate A/C adapter state: not connected Performance adjustment mode: manual (2666 MHz) The energy consumption is the same which is odd. --Johan Hmmm. Smells like a bug, to me. But by changing hw.setperf your self you should be able to go to other speeds(?). And of course, the real test is to see if you get longer life at setperf 0. --STeve Andre'
Re: Weird disk problem
On 06/05/14 17:38, Christian Weisgerber wrote: I have a 3TB disk here... sd1 at scsibus1 targ 1 lun 0: ATA, Hitachi HUA72303, MKAO SCSI3 0/direct fixed naa.5000cca225c5fbeb sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors ... that's serving as a general media dump with a single FFS2 file system on it. Filesystem SizeUsed Avail Capacity Mounted on /dev/sd1d 2.7T2.5T 63.7G98%/export Yesterday, I experienced the odd effect that reading some files, or parts of files, from that disk became excruciatingly slow. We're talking a few kB/s here. Other files were fine. There were no kernel errors/warnings whatsoever. There were no read errors, the disk was just 100% busy and appeared to be returning data drip by drip. # atactl sd1 smartstatus No SMART threshold exceeded No change on reboot. dd(1) from the raw device was initially fast, then slowed to a crawl as it progressed. I eventually fixed it all by powering off the machine, jiggling the SATA connectors (all fine), and powering the machine back up. Tonight the problem is back. Something is very wrong. Given that dd if=/dev/rsd1c also seems affected, the filesystem layer can be excluded. I won't cry too much over a dying disk, but why the heck are there no error indications of any kind? Any other ideas? I think you are relying on the smart system too much. Certainly try what David said, but it's obvious that the disk is sick despite what the smart system may say. I've had about seven disk failures in the last several years. Three or four of them the smart system was absolutely correct, with the others being less informative. I've also had a false notice that a disk was bad, but worked for several years, till it got too small for its task. Smart is good, but it has its limitations. It best deals with gradual errors, not fast catastrophic ones. --STeve Andre'
Re: CPU power consumption on thinkpad x201 on openbsd current
On 06/04/14 17:08, Johan Svensson wrote: I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201). The first problem that i came across was that the Cpu fanspeed was running constantly at 3500RPM. After the acpithinkpad.c patch from jcs (and i modified to make it work on the openbsd-current(link: http://exclude.se/patch/jcs_mod_by_js.diff) Another thing that i noticed is that the battery lifetime is really bad. In Linux i get around ~5,5 hours. In OpenBSD i get around 2 hours. when i ran : sysctl hw.sensors | grep -i consumption. the output of the cpu was 6W. in Linux it's around 1,5W. with: apmd -C and apmd -L it's the same. dmesg: http://exclude.se/openbsd/dmesg.txt Is there anyway to fix this? Regards Johan Svensson Take a look at hw.setperf in sysctl. I think you are running at the maximum cpu speed? On my 2.8GHz W500 I can run at 800, 1600, 2133 and 2801. 800MHz makes a huge difference. You have to try different values for setperf to see what happens. sysctl will also tell you the speed in hw.cpuspeed. --STeve Andre'
Re: Calgary, this Tuesday
On 05/26/14 09:21, dera...@cvs.openbsd.org wrote: I'm sorry for the late public announcement... Tomorrow (Tuesday) Bob Beck will be hurtling down the Highway from Edmonton to Calgary. Then in the evening, he and I will present at the local calgary unix group meeting about recent changes in LibreSSL, OpenBSD, and how the OpenBSD Foundation fits into this. http://www.cuug.ab.ca/ I hope a video or audio transcript can be made available. Doesn't have to be great, to be valuable. Thanks... --STeve Andre'
panic: softdep_deallocate_dependencies
Twice now in three or so weeks, I've gotten a panic on my -current_amd64
W500 laptop. I've updated my tree several times during this time, and have
not seen other problems besides the known acpi heat problem.
I have both firefox and chrome running but I'm getting the feeling that
things
get more weird as I use lots of tabs in chrome.
I don't think it matters but my boot disk is a 960g Crucial SSD.
--STeve Andre'
panic: softdep_deallocate_dependencies: dangling deps
Stopped at Debugger+0x5: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} ddb{1} Debugger() at Debugger+0x5
panic() at panic+0xfe
softdep_deallocate_dependencies() at softdep_deallocate_dependencies+0x1b
brelse() at brelse+0x61
ffs_write() at ffs_write+0x419
VOP_WRITE() at VOP_WRITE+0x3f
uvn_io() at uvn_io+0x1a0
uvm_pager_put() at uvm_pager_put+0x92
uvmpd_scan_inactive() at uvmpd_scan_inactive+0x5a3
uvmpd_scan() at uvmpd_scan+0x6e
uvm_pageout() at uvm_pageout+0x5b
end trace frame: 0x0, count: -11
ddb{1} CPU not specified
ddb{1} Stopped at Debugger+0x5: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} Stopped at Debugger+0x5: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} Debugger() at Debugger+0x5
panic() at panic+0xfe
softdep_deallocate_dependencies() at softdep_deallocate_dependencies+0x1b
brelse() at brelse+0x61
ffs_write() at ffs_write+0x419
VOP_WRITE() at VOP_WRITE+0x3f
uvn_io() at uvn_io+0x1a0
uvm_pager_put() at uvm_pager_put+0x92
uvmpd_scan_inactive() at uvmpd_scan_inactive+0x5a3
uvmpd_scan() at uvmpd_scan+0x6e
uvm_pageout() at uvm_pageout+0x5b
end trace frame: 0x0, count: -11
ddb{1} Debugger() at Debugger+0x5
end trace frame: 0x80002207cab0, count: 0
ddb{1}PID PPID PGRPUID S FLAGS WAIT COMMAND
27484 1 27484 0 30x80 poll ftpd
11680 15813 11680 1000 30x83 ttyin ksh
15813 6621 3503 1000 30xb2 select xterm
16802 4523 16802 1000 30x83 ttyin ksh
4523 6621 3503 1000 30xb2 select xterm
27410 18597 3503 1000 30x82 thrsleep chrome
7576 18597 3503 1000 3 0x482 kqread chrome
16218 18597 3503 1000 3 0x482 thrsleep chrome
658 18597 3503 1000 3 0x482 thrsleep chrome
7989 18597 3503 1000 3 0x482 thrsleep chrome
11847 18597 3503 1000 3 0x482 thrsleep chrome
20010 18597 3503 1000 2 0x482 chrome
15059 18597 3503 1000 3 0x482 kqread chrome
27259 18597 3503 1000 3 0x482 thrsleep chrome
20832 18597 3503 1000 3 0x482 thrsleep chrome
26369 18597 3503 1000 3 0x482 thrsleep chrome
4610 18597 3503 1000 3 0x482 thrsleep chrome
13262 18597 3503 1000 3 0x482 thrsleep chrome
8575 18597 3503 1000 3 0x482 netio chrome
7173 18597 3503 1000 2 0x4000482 chrome
29279 18597 3503 1000 3 0x482 thrsleep chrome
17470 18597 3503 1000 2 0x4000482 chrome
28899 18597 3503 1000 3 0x482 thrsleep chrome
29261 18597 3503 1000 30x82 thrsleep chrome
10383 18597 3503 1000 3 0x482 kqread chrome
26250 18597 3503 1000 3 0x482 thrsleep chrome
29984 18597 3503 1000 3 0x482 thrsleep chrome
1661 18597 3503 1000 3 0x482 thrsleep chrome
26874 18597 3503 1000 3 0x482 thrsleep chrome
18381 18597 3503 1000 2 0x482 chrome
22068 18597 3503 1000 3 0x482 kqread chrome
5164 18597 3503 1000 3 0x482 thrsleep chrome
3419 18597 3503 1000 3 0x482 thrsleep chrome
11293 18597 3503 1000 3 0x482 thrsleep chrome
14060 18597 3503 1000 3 0x482 thrsleep chrome
15908 18597 3503 1000 30x82 thrsleep chrome
22526 18597 3503 1000 3 0x482 kqread chrome
3139 18597 3503 1000 3 0x482 thrsleep chrome
16815 18597 3503 1000 3 0x482 thrsleep chrome
9024 18597 3503 1000 3 0x482 thrsleep chrome
21044 18597 3503 1000 3 0x482 thrsleep chrome
21241 18597 3503 1000 30x82 thrsleep chrome
14538 18597 3503 1000 3 0x482 kqread chrome
2642 18597 3503 1000 3 0x482 thrsleep chrome
25772 18597 3503 1000 3 0x482 thrsleep chrome
8110 12981 18597 3503 1000 3 0x482 thrsleep chrome
2271
Re: panic: softdep_deallocate_dependencies
On 05/08/14 22:43, Philip Guenther wrote:
On Thu, May 8, 2014 at 2:59 PM, STeve Andre' and...@msu.edu wrote:
Twice now in three or so weeks, I've gotten a panic on my -current_amd64
W500 laptop. I've updated my tree several times during this time, and have
not seen other problems besides the known acpi heat problem.
Uh, what was the date of the cvs update of your kernel build when they
started? What was the cvs update date of your kernel before *that*? (I.e,
what's your best estimate of the window in which the change to the kernel
which triggered the panic occurred?
(What, you don't keep a log of the timestamps of your kernel
updates+builds? Doesn't everyone?)
Actually, I do keep past kernels so I have the build date for them.
I *thought* I had some notes on when this started but I am
ashamed to see that I didn't put them in a safe place.
I have both firefox and chrome running but I'm getting the feeling that
things
get more weird as I use lots of tabs in chrome.
You're pushing the vm subsystem enough to page. Since you have 8GB, I
wonder if you've raised yourkern.bufcachepercent, thus pushing on it harder.
Nope, I try to avoid the knobs when possible. It's been at 20%
ever since (bob?) raised it to 20%.
I don't think I'm swapping? At least I haven't seen top tell me that.
...In the past (like a year+) ago, there were times when chrome
went crazy with memory and I did swap. But chrome has gotten
better--I don't think I've seen it do that for some time now.
panic: softdep_deallocate_dependencies: dangling deps
Stopped at Debugger+0x5: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} ddb{1} Debugger() at Debugger+0x5
panic() at panic+0xfe
softdep_deallocate_dependencies() at softdep_deallocate_dependencies+0x1b
brelse() at brelse+0x61
ffs_write() at ffs_write+0x419
VOP_WRITE() at VOP_WRITE+0x3f
uvn_io() at uvn_io+0x1a0
uvm_pager_put() at uvm_pager_put+0x92
uvmpd_scan_inactive() at uvmpd_scan_inactive+0x5a3
uvmpd_scan() at uvmpd_scan+0x6e
uvm_pageout() at uvm_pageout+0x5b
This is *likely* to be a bug in the don't cache pages being paged out
commit, but it would be nice to be sure it didn't start before then...
Philip Guenther
I'm not sure how well I can pin this down. If I go too far back with
an older kernel I'll be out of sync with userland. Any suggestions
on how to test this more?
Thanks!
--STeve Andre'
Re: panic: softdep_deallocate_dependencies
On 05/08/14 23:41, Philip Guenther wrote: On Thu, May 8, 2014 at 8:14 PM, STeve Andre' and...@msu.edu wrote: On 05/08/14 22:43, Philip Guenther wrote: On Thu, May 8, 2014 at 2:59 PM, STeve Andre' and...@msu.edu wrote: Twice now in three or so weeks, I've gotten a panic on my -current_amd64 W500 laptop. I've updated my tree several times during this time, and have not seen other problems besides the known acpi heat problem. Uh, what was the date of the cvs update of your kernel build when they started? What was the cvs update date of your kernel before *that*? (I.e, what's your best estimate of the window in which the change to the kernel which triggered the panic occurred? (What, you don't keep a log of the timestamps of your kernel updates+builds? Doesn't everyone?) Actually, I do keep past kernels so I have the build date for them. I *thought* I had some notes on when this started but I am ashamed to see that I didn't put them in a safe place. Well, make your best, but conservative estimate of the window in which it started. (Certainly after _that_ kernel; not sure if before _this_ kernel but certainly before this+1...) This first occurred after I created an April 16th kernel. I'm pretty sure of that. I have both firefox and chrome running but I'm getting the feeling that things get more weird as I use lots of tabs in chrome. You're pushing the vm subsystem enough to page. Since you have 8GB, I wonder if you've raised yourkern.bufcachepercent, thus pushing on it harder. Nope, I try to avoid the knobs when possible. It's been at 20% ever since (bob?) raised it to 20%. Ok. I guess it's just memory pressure from chrome. I don't think I'm swapping? At least I haven't seen top tell me that. ...In the past (like a year+) ago, there were times when chrome went crazy with memory and I did swap. But chrome has gotten better--I don't think I've seen it do that for some time now. Heh, the backtrace starts from uvm_pageout so yes, it decided to page *DUH*. sigh. Still recovering from Penguicon or something. Well, that would be consistent with chrome's rabbid usage of memory from time to time. I'm going to test stuff after a rebuild of the world, re Ted's comments. something out. :-) I'm not sure how well I can pin this down. If I go too far back with an older kernel I'll be out of sync with userland. Any suggestions on how to test this more? I don't recall any kernel ABI changes in the window, but hold off for now. Eyes more familiar with the involved subsystem may consider the backtrace you gave (thanks!) enough. Philip Guenther --STeve
Re: panic: softdep_deallocate_dependencies
On 05/09/14 00:05, Ted Unangst wrote: On Thu, May 08, 2014 at 17:59, STeve Andre' wrote: Twice now in three or so weeks, I've gotten a panic on my -current_amd64 W500 laptop. I've updated my tree several times during this time, and have not seen other problems besides the known acpi heat problem. Thanks, I think we've fixed this. Really! I'll update/compile and start beating on stuff with ff and chrome tonight. --STeve
Re: Updating sets
On 05/07/14 19:01, Stuart Henderson wrote: My advice is: stick to releases for now on important systems that you mustn't break, but also setup on a spare machine or VM that you don't mind breaking from time to time, use base os + package snapshots, maybe play with compiling a few things yourself - basically play around and find out what works and what doesn't. Breaking this type of system from time to time is a good thing. :-) It gives you a good opportunity to work out how to recover from various problems without too much stress. System running -current kernel with snapshots are even less stable than one running -current and using fully compiled userspace from ports source tree. Generally: -current is not meant to be unstable in terms of operation, it's more that it's subject to more rapid change and you may occasionally have things like package breakage until new packages are available following API/ABI changes. If you're running much from ports, snapshots are usually a lot easier to get on with than compiling from scratch. At hackathon times and at some other times when there are major changes in the tree this often gets a bit more fragile. Recently we've been in a bit more fragile than usual sort of stage. It is still important that people run new code in this situation and report on problems, but use common sense as to where you run this :) The reverse applies as we approach lock for release and changes are much more conservative. If you're following -current then I strongly recommend reading the source-changes mailing list (or some alternative) to get a feel for what's going on in the OS, and when is a good or bad time to upgrade. If I may add to the excellent comments here, a bit: -Current is incredibly stable. Commits that break the tree are fairly rare and get repaired quickly. Before using a -current system in something important you want to test it, but you want to test a stock -stable system before using it for your applications, too. Most of my systems that I use for real are -current. I've not had a problem in 12 years--but I test stuff before using it! I've screwed myself twice with -current: once when I didn't pay attention to a flag day and gotten myself a broken compiler, and once during a hackathon when commits were coming in every 90 seconds or so, and my eagerness to try something new made a system which went BOOM. But these kinds of errors are good practice for dealing with a real-world broken system. ;-) If you want to use -current you *really* want to pay close attention to the source change mailing list. Your mirror of choice updates itself every N hours. There will be times when the latest update to the mirror will not include all the physical parts of a logical commit, so attempting to compile stuff will result in an error (think code change that uses a new #define in a .h that you didn't get), or really subtle stuff because you got *part* of a change. And of course, caution during a hackathon. I'll update my tree during one, but will stay away from using it, as the tree of 45 minutes ago might not be right by the time your mirror gets its update. --STeve Andre'
Where can I find a list of error codes in smtpd?
So far, I'm not finding them. I'm interested in learning more about 150 IO error and 442 i/o error 5, but a general list of them would be good. I know I'm missing something... Thanks, STeve Andre'
Re: Help troubleshooting performance problem
On 11/30/13 20:04, Shawn K. Quinn wrote: On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote: On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote: OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013 j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/ GENERIC.MP Try 5.4 or -current. Issues with non-home-compiled kernels are more interesting. I thought as long as it was an unmodified GENERIC or GENERIC.MP that the issue was still valid. Is this no longer the case? You want to use the latest release whenever possible for things. If you find a specific problem in 5.3 it might have been touched upon for some other reason. If there were an infinite number of developers it might be different, but there aren't. So the latest release (and -current is even better) should be used if possible. Looking at http://openbsd.org/plus54.html shows quite a few changes. --STeve Andre'
Re: UEFI
On 11/06/13 10:53, sven falempin wrote: On Wed, Nov 6, 2013 at 10:44 AM, Peter N. M. Hansteen pe...@bsdly.netwrote: On Wed, Nov 06, 2013 at 09:49:44AM -0500, Mayuresh Kathe wrote: just install another 'os' like ubuntu-desktop on your laptop first. openbsd will install on it flawlessly after that, it did on mine. and yes, there was no need to change any options anywhere. On my daughter's brand spanking new Lenovo Ideapad $something Touch, we needed to set the BIOS to 'legacy mode' in order to have it boot into the Ubuntu installer and then choose some obscure linux kernel parameter for it to switch to a usable graphics mode for the installer to complete. For some reason she wanted her laptop on Ubuntu and to use it herself from that point on. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. Why you people are talking about your Lenovo experience ? are you salesman ? *facepalm* Sven, Thinkpads are still the best laptops out there. I have dealt with many others in the the last year, and thinkpads still rule. This W500 I bought 5 years ago is still running. None of the non-TP laptops friends bought in that time frame are still work. The quality of ALL laptops has gone downhill, but the thinkpads are still at the top of the list (even with the new wretched keyboards they have). Add the UEFI horror for non-Windows users and giving exact details becomes important. --STeve Andre' ps: Has anyone run OpenBSD on a System76 laptop?
Problem with dhcp requests on --current of Nov 2-4
Sometime between Oct 18th and now I've lost the ability to do a dhcp request at boot time. Dropping back to the Oct 18 kernel fixes things so I don't have hardware problems. When I attempt to do a dhclient em0 I get DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 (00:1a:70:f8:07:38) and thats it. This is a thinkpad W500 running -current oct 18th that works, Nov 2-today kernels that do not work. Has anyone else seen this? --STeve Andre' OpenBSD 5.4-current (GENERIC.MP) #0: Fri Oct 18 22:38:59 EDT 2013 root@paladin:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8499433472 (8105MB) avail mem = 8265060352 (7882MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version 6FET92WW (3.22 ) date 12/14/2011 bios0: LENOVO 4061CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.46 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 265MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4619 serial 5701 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 2793 MHz: speeds: 2801, 2800, 2133, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 ppb0 at pci0 dev 1 function 0 Intel GM45 PCIE rev 0x07: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Mobility Radeon HD 3650 rev 0x00: apic 1 int 16 drm0 at radeondrm0 Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured puc0 at pci0 dev 3 function 3 Intel GM45 KT rev 0x07: ports: 1 com com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com4: probed fifo depth: 0 bytes em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: msi, address 00:22:68:1b:3c:c7 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: msi azalia0: codecs: Conexant CX20561, Conexant/0x2c06, using Conexant CX20561 audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: msi pci3 at ppb2 bus 3 iwn0 at pci3 dev 0 function 0 Intel WiFi Link 5300 rev 0x00: msi, MIMO 3T3R, MoW, address 00:21:6a:01:d0:b6 ppb3 at pci0 dev 28 function 3 Intel 82801I PCIE rev 0x03: msi pci4 at ppb3 bus 5 ppb4 at pci0 dev 28 function 4 Intel 82801I PCIE rev 0x03: msi pci5 at ppb4 bus 13 uhci3 at pci0 dev 29 function 0 Intel 82801I USB rev 0x03: apic 1 int 16 uhci4 at pci0 dev 29 function 1 Intel 82801I USB rev 0x03: apic 1 int 17 uhci5 at pci0 dev 29 function 2 Intel 82801I USB rev 0x03: apic 1 int 18 ehci1 at pci0 dev 29 function 7 Intel 82801I USB rev 0x03: apic 1 int 19 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel
Re: Problem with dhcp requests on --current of Nov 2-4
AARGH! I missed that completely! I did look at following -current, but my eyes glazed over the part that said a dhcp would hang. OK, off to finish building the world. Thanks for the clue, all. --STeve Andre' On 11/04/13 19:48, Brad Smith wrote: On 04/11/13 6:22 PM, STeve Andre' wrote: Sometime between Oct 18th and now I've lost the ability to do a dhcp request at boot time. Dropping back to the Oct 18 kernel fixes things so I don't have hardware problems. When I attempt to do a dhclient em0 I get DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 (00:1a:70:f8:07:38) and thats it. This is a thinkpad W500 running -current oct 18th that works, Nov 2-today kernels that do not work. Has anyone else seen this? Yes.. as Tobias mentioned, make sure your kernel and userland are in sync. From current.html.. 2013/10/31 - new routing message version
Re: A suggestion for snapshots
On 09/06/13 23:13, Theo de Raadt wrote: On Fri, Sep 6, 2013 at 7:14 AM, Lars Engblom lars.engb...@kimitotelefon.fiwrote: Quite often the snapshot of the packages and the base system are out of sync, because naturally, the base has to be built before packages. For example in this moment, as I write this, Firefox can not be installed in a new system installed from snapshots, as the packages are compiled against an older snapshot (amd64) If there are just space on the ftp servers, I would suggest keeping two snapshots: one complete with both base and packages (always in sync) and one with just the newest base. This would make life easier for people following snapshots. Regards, Lasse The problem with ports is that even with a build farm, the ports guy has to make sure dpb runs to the end. In the best case, a dpb run WITHOUT problems to the end takes atleast a day with a fast quad core machine. gcc4, JDK 1.6 + 1.7, GTK+2, GTK+3, Qt4, Webkit, Firefox are some of the worst ports in terms of build time and the largest offender Libreoffice which alone takes 4-6 hrs of all quad cores (Xeon E3-1230v2 3.3GHz). I might have missed some offenders, I just built a subset, experienced porters who handle the whole tree know better than me which ones are also worthy candidates. Finding and fixing port problems takes a minimum of 2 and I am guessing typically 4 days to pump out a wholly built ports tree, on a extremely fast arch like amd64. By which time the userland, kernel and xenocara have changed a lot underneath. Hence, you get these mismatches from time to time. It is not catastrophic, solution is to wait for the next snap. Even if the ports build machine untars userland, kernel, xenocara, running dpb again may force rebuilds or sometimes not. Anyone want to pay for a faster network link? Step up -- then we can solve this problem easily. OK. How much would it cost per month for faster access? Do you have several options for increased speeds? I smell a fundraiser here--paying for a year's costs in advance. Perhaps then others would come up with larger chunks for future costs. It would certainly be bad to not be able to come up with the funds for the future net costs. I think it should be thought of as another cost, just like new hardware. --STeve Andre'
Selecting new motherboards in the era of uefi
I'm shopping around for new server hardware. Unless someone has a reason to think of something else, I'm planing on a i7-4770K. The more interesting question is what motherboard to get. I have my eye on the Asus Sabertooth Z87, but I see that it talks of uefi. What I do not yet see, is whether the system can boot in a non- uefi mode or not. Given that the motherboard is at least a little OS agnostic, I have some hope that it will work. But I don't know, and in general I think it might be worth talking of strategies for motherboard selection given the size of the marketplace. I wonder if this might make a new section Thoughts? --STeve Andre'
Re: How to mark a block as invalid ?
On 08/18/13 08:00, Mik J wrote: Hello, Thank you all for your answers. First I would like to understand better what's happening. According to what I read, there are no block in the disk itself, they refer to the word sector. Then, the OS, here OpenBSD format it with a block size. So from a physical point of view I have faulty sectors on my disk right ? I bought this disk about a year ago. And ok, I write in a few files (~1000 rrd files) every minute all year long. I'm surprise that you guys ask me to throw the disk away because a few blocks out of thousands are faulty. Smartmontools doesn't complain about my disk [snip] Once a disk sprouts an error, it cannot be trusted. This has always been true, but in an era of multi hundred G disks, any tiny particles floating around in a disk resembles large rocks pummeling the insides of a disk. You MAY be OK and have just a few bad sectors but the uneasy question is, will you get more, how many, and where? Not to mention all the other failures that can happen. I have had disks with bad sectors that I mapped out by never touching files where the bad spots were, and had the disk live for five years. I've also seen a case where a friend showed me a disk that had one bad sector on it, and tens of thousands the next day. You are dancing on a volcano. I hope it doesn't erupt on you. Make backups. Rsync is a good friend. Really. --STeve Andre'
Re: Default software in the base
On 07/30/13 18:15, Alexandre Ratchov wrote: On Mon, Jul 29, 2013 at 10:48:11PM +0400, h...@riseup.net wrote: I realize that everything has its pros and cons (like URXVT is GPL-licensed, st is pretty much hackish for an ordinary user and Clang is not, well, mature yet). But ain't pros of the programs above not enough to actually make it in the base? (replacing XTerm and GCC) there seem to be many pros, but nobody did the work yet (hint ;) -- Alexandre Hub, If the software is GPL'd, it won't go into base, period. However, making this stuff available as a port seems a reasonable thing to do. The more ports the better. I can't speak to things like urxvt so I don't know how much of a pain they'd be to incorporate into OpenBSD but making them available is reasonable from a user point of view. --STeve Andre'
Any other ThinkPad W500 users out there?
If so, I'd like to know if you are running a recent 5.3-current. Mail me off list so we don't pollute misc@. Thanks... --STeve Andre'
Re: OpenBSD Doesn't Support 64-Bit Intel
On 07/01/13 00:06, Jash Sefferson wrote: Hi guys. I’m a civil engineer by day and use OpenBSD at night, but I’m trying to do high-end CAD on my home PC and OpenBSD doesn’t support 64-bit Intel chips. Don't believe me? It says very clearly at the OpenBSD/amd64 page: “All versions of the AMD Athlon 64 processors and their clones are supported.” But does not mention or list any Intel chips. Not one. Wtf? I can do CAD on my i7-980X under Windows 7 SP 1, but I’d rather use something secure and responsibly coded like OpenBSD. Except that I can't. Why for the life of this platform are we not on the only future direction for the platform? And I mean that literally. Neither AMD nor Intel sells 32-bit chips anymore. If OpenBSD remains stuck at 32 bits, people will stop using and developing for it. Who makes the decision to keep OpenBSD off of 64-bit Intel? And why the hell are they doing so? -jash Um I'm writing this on an amd64 Thinkpad W500 which has a 2.8GHz core two duo. So I don't understand what you mean. --STeve Andre'
Re: Severe problem with amd64 -current as of June 13
On 06/16/13 01:05, Philip Guenther wrote: On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre' and...@msu.edu wrote: On June 13 I updated my tree from anoncvs.usa.openbsd.org, and the new -current failed shortly after running it. Things would get *very* slow, with continuous disk activity. It was sort of possible to switch between screens, albeit after a few minutes. Processes would be shown as in a disk wait (D). Eventually the system freezes completely with the continuous disk activity as evidenced by my disk LED. Hmm, once it gets into this state, can you go to the console, then break into ddb (you'll need to add ddb.console=1 to your /etc/sysctl.conf and reboot for that to work), and then do show uvm and report the results? Philip Guenther I will try that, but I doubt I can get to a console. It's very quick from slow to hung. But I'll umount everything I can and see what transpires. Thanks. --STeve Andre'
Re: Severe problem with amd64 -current as of June 13
On 06/16/13 01:05, Philip Guenther wrote: On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre' and...@msu.edu wrote: On June 13 I updated my tree from anoncvs.usa.openbsd.org, and the new -current failed shortly after running it. Things would get *very* slow, with continuous disk activity. It was sort of possible to switch between screens, albeit after a few minutes. Processes would be shown as in a disk wait (D). Eventually the system freezes completely with the continuous disk activity as evidenced by my disk LED. Hmm, once it gets into this state, can you go to the console, then break into ddb (you'll need to add ddb.console=1 to your /etc/sysctl.conf and reboot for that to work), and then do show uvm and report the results? Philip Guenther Well, that worked. As soon as it got slow I flipped to the console and got: current uvm status: pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12 2020005 vm pages: 444603active, 5144inactive, -29733wired, 1340021free min 10% (25) anon, 10% (25) vnode, 5% (12) vtext pages0anon, 0vnode, 0vtext freemin=67333, free-target=89777, inactive-target=0, wired-max=673335 faults=1649483, traps=1771874, intrs=88809, ctxswitch=8541333 fpuswitch=6 softint=200628, syscalls=36792232, kmapent=13 faultcounts: noram=0, noanon=0 pgwait=0, pgrele=0 ok relocks(total)=52922(53361), anget(retries)=179277(0), amapcopy=208087 neighbor anon/obj pg=20425/253589, gets(lock/unlock)=155928/53361 cases: anon=160496, anoncow=18781, obj=131739, prcopy=23750, przero=1309640 daemon and swap counts: woke=0, revs=0, scans=0, obscans=0, anscans=0 busy=0, freed=0, reactivate=0, deactivate=0 pageouts=0, pending=0, nswget=0 nswapdev=1, nanon=0, nanonneeded=0, nfreeanon=0 swpages=1050240, swpginuse=0, swpgonly=0, paging=0 kernelpointers: objs(kern)=0x81c96c00 --STeve
Severe problem with amd64 -current as of June 13
amd64-current seems rather wounded at the moment. I've been running -current since June 5th with no problems. This is a W500 thinkpad. On June 13 I updated my tree from anoncvs.usa.openbsd.org, and the new -current failed shortly after running it. Things would get *very* slow, with continuous disk activity. It was sort of possible to switch between screens, albeit after a few minutes. Processes would be shown as in a disk wait (D). Eventually the system freezes completely with the continuous disk activity as evidenced by my disk LED. Going back to the June 5th kernel with the June 13th userland seems to be working. Looking at the FAQ there are things for -current which had no relevance to this problem. I then got a new copy of src and xenocara with the same results. Seeing memmove and similar changes, and a fix for at least one arch makes me wonder if amd64 has a problem. Suggestions? ---dmesg of the 'good' kernel of June 5th Jun 15 00:28:58 paladin /bsd: OpenBSD 5.3-current (GENERIC.MP) #0: Wed Jun 5 21:33:29 EDT 2013 Jun 15 00:28:58 paladin /bsd: root@paladin:/usr/src/sys/arch/amd64/compile/GENERIC.MP Jun 15 00:28:58 paladin /bsd: real mem = 8499433472 (8105MB) Jun 15 00:28:58 paladin /bsd: avail mem = 8265461760 (7882MB) Jun 15 00:28:58 paladin /bsd: mainbus0 at root Jun 15 00:28:58 paladin /bsd: bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) Jun 15 00:28:58 paladin /bsd: bios0: vendor LENOVO version 6FET92WW (3.22 ) date 12/14/2011 Jun 15 00:28:58 paladin /bsd: bios0: LENOVO 4061CTO Jun 15 00:28:58 paladin /bsd: acpi0 at bios0: rev 2 Jun 15 00:28:58 paladin /bsd: acpi0: sleep states S0 S3 S4 S5 Jun 15 00:28:58 paladin /bsd: acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT Jun 15 00:28:58 paladin /bsd: acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) Jun 15 00:28:58 paladin /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits Jun 15 00:28:58 paladin /bsd: acpiec0 at acpi0 Jun 15 00:28:58 paladin /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat Jun 15 00:28:58 paladin /bsd: cpu0 at mainbus0: apid 0 (boot processor) Jun 15 00:28:58 paladin /bsd: cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.45 MHz Jun 15 00:28:58 paladin /bsd: cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF Jun 15 00:28:58 paladin /bsd: cpu0: 6MB 64b/line 16-way L2 cache Jun 15 00:28:58 paladin /bsd: cpu0: smt 0, core 0, package 0 Jun 15 00:28:58 paladin /bsd: cpu0: apic clock running at 266MHz Jun 15 00:28:58 paladin /bsd: cpu1 at mainbus0: apid 1 (application processor) Jun 15 00:28:58 paladin /bsd: cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz Jun 15 00:28:58 paladin /bsd: cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF Jun 15 00:28:58 paladin /bsd: cpu1: 6MB 64b/line 16-way L2 cache Jun 15 00:28:58 paladin /bsd: cpu1: smt 0, core 1, package 0 Jun 15 00:28:58 paladin /bsd: ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins Jun 15 00:28:58 paladin /bsd: ioapic0: misconfigured as apic 2, remapped to apid 1 Jun 15 00:28:58 paladin /bsd: acpimcfg0 at acpi0 addr 0xe000, bus 0-63 Jun 15 00:28:58 paladin /bsd: acpihpet0 at acpi0: 14318179 Hz Jun 15 00:28:58 paladin /bsd: acpiprt0 at acpi0: bus 0 (PCI0) Jun 15 00:28:58 paladin /bsd: acpiprt1 at acpi0: bus 1 (AGP_) Jun 15 00:28:58 paladin /bsd: acpiprt2 at acpi0: bus 2 (EXP0) Jun 15 00:28:58 paladin /bsd: acpiprt3 at acpi0: bus 3 (EXP1) Jun 15 00:28:58 paladin /bsd: acpiprt4 at acpi0: bus -1 (EXP2) Jun 15 00:28:58 paladin /bsd: acpiprt5 at acpi0: bus 5 (EXP3) Jun 15 00:28:58 paladin /bsd: acpiprt6 at acpi0: bus 13 (EXP4) Jun 15 00:28:58 paladin /bsd: acpiprt7 at acpi0: bus 21 (PCI1) Jun 15 00:28:58 paladin /bsd: acpicpu0 at acpi0: C3, C2, C1, PSS Jun 15 00:28:58 paladin /bsd: acpicpu1 at acpi0: C3, C2, C1, PSS Jun 15 00:28:58 paladin /bsd: acpipwrres0 at acpi0: PUBS Jun 15 00:28:58 paladin /bsd: acpitz0 at acpi0: critical temperature is 127 degC Jun 15 00:28:58 paladin /bsd: acpitz1 at acpi0: critical temperature is 100 degC Jun 15 00:28:58 paladin /bsd: acpibtn0 at acpi0: LID_ Jun 15 00:28:58 paladin /bsd: acpibtn1 at acpi0: SLPB Jun 15 00:28:58 paladin /bsd: acpibat0 at acpi0: BAT0 model 42T4619 serial 5701 type LION oem SANYO Jun 15 00:28:58 paladin /bsd: acpibat1 at acpi0: BAT1 not present Jun 15 00:28:58 paladin /bsd: acpiac0 at acpi0: AC unit online Jun 15 00:28:58 paladin /bsd: acpithinkpad0 at acpi0 Jun 15 00:28:58 paladin /bsd: acpidock0 at acpi0: GDCK not docked (0) Jun 15 00:28:58
Re: Severe problem with amd64 -current as of June 13
On 06/16/13 00:23, Amit Kulkarni wrote: On Sat, Jun 15, 2013 at 9:19 PM, STeve Andre' and...@msu.edu mailto:and...@msu.edu wrote: amd64-current seems rather wounded at the moment. I've been running -current since June 5th with no problems. This is a W500 thinkpad. On June 13 I updated my tree from anoncvs.usa.openbsd.org http://anoncvs.usa.openbsd.org, and the new -current failed shortly after running it. Things would get *very* slow, with continuous disk activity. It was sort of possible to switch between screens, albeit after a few minutes. Processes would be shown as in a disk wait (D). Eventually the system freezes completely with the continuous disk activity as evidenced by my disk LED. Going back to the June 5th kernel with the June 13th userland seems to be working. Looking at the FAQ there are things for -current which had no relevance to this problem. I then got a new copy of src and xenocara with the same results. Seeing memmove and similar changes, and a fix for at least one arch makes me wonder if amd64 has a problem. Suggestions? i just updated a desktop PC with the 15th June snap and things were working fine... and the June 10th packages. Interesting. I updated my tree this afternoon, and built a new kernel which finally had the same problem. It ran for a while fine, but then got very slow and finally froze. This was after 10 or 15 minutes, long enough for me to think that things were OK. Running on the June 5th kernel right now and all is well. I'll try the June 10th snaps, but I think that's missing png? --STeve Andre'
Re: how can I get a dmesg (without a floppy or serial console port)?
On 05/27/13 19:52, Heptas Torres wrote: Is there any way (physical settings / cables) to get a dmesg from a laptop that has neither a floppy nor a serial console port (no ssh either)? 10x -h You have two options: 1) video tape it and transcribe it, or 2) take the disk out of the machine and put it on another, so you can grab the dmesg output. --STeve Andre'
Re: ACPI hack for temperature control
On 05/02/13 02:40, Vadim Zhukov wrote: 2013/5/2 STeve Andre' and...@msu.edu mailto:and...@msu.edu Can someone point me to the proper patch for ACPI so I don't reboot any more? Thanks. Do you mean disabling acpitz(4) when it does the Wrong Thing, or ThinkPad-specific patch I was posting some time ago (and still want to incorporate but after 64-bit time_t)? -- WBR, Vadim Zhukov Sorry -- I mean the acpitz(4) hack to let my W500 get past 79C without rebooting. Time_t I can wait for. ;-) Thanks, STeve Andre'
ACPI hack for temperature control
Can someone point me to the proper patch for ACPI so I don't reboot any more? Thanks. --STeve Andre'
Re: How many rounds to use for a pbkdf2 encrypted disk?
On 04/21/13 23:57, Ted Unangst wrote: On Sun, Apr 21, 2013 at 19:00, and...@msu.edu wrote: The example in vnconfig shows 20,000. I picked 30K. This is a 2.8G core2 duo machine, encrypting mail and other stuff. I haven't found sources on the net that have explained what low security is, up to total paranoia with regards # of rounds. Ideas? URLs for good places to read? As many as don't annoy you. 100k will be about half a second on a CPU. The problem is the bad guys aren't going to be using CPUs. A single computer with a few high end graphics cards can do somewhere in the neighborhood of 3 billion hashes in one second. 1000 rounds (the bare minimum for pbkdf2) turns that into 3 million/s. 100k turns it into 30k/s. The work factor and time required scale linearly for both you and the attacker, the attacker just has somewhere ranging from 15000 to many more times more computing resources at his disposal. It's hard to directly equate time you spend waiting with time it will cost some unknown attacker. Your best bet is a longer password. Nothing will save you if your password is a word from a dictionary, or some 3lit3 spelling thereof. An interesting read: http://www.tarsnap.com/scrypt/scrypt.pdf There is a table at the top of page 14 that compares hypothetical hardware cracking costs. If you suspect somebody with a million dollars, access to chip fabrication facilities, and a year to wait will be interested in reading your email, you should use at least 100k rounds and and a ten character random password. Thank you, Ted. Well said and confirmed some thoughts I'd had. Something like this ought to go into the FAQ, perhaps Thanks again! --STeve Andre'
