Keep seeing this annoying message on FreeBSD, even though back on December 20th, 2013....I had set
"security.bsd.unprivileged_mlock=1" in /etc/sysctl.conf to try to finally address this problem.
The default RLIMIT_MEMLOCK resource limit is 64k, which I would think is more than sufficient.
So, it was time to research this problem in more depth.
Found that there's a DEBUG_SECURE_MEMORY define to see how much memory its trying to allocate. Which its trying to allocate some multiple of 16k blocks, which it later refers as pages. Which I seem to recall is Windows?, Solaris is 8k and most other systems are 4k (my FreeBSD system, its 4k). Well, its only trying (and failing) to mlock 16k. So, I tried overriding the constant to 4k. But, this also failed.
I had skimmed the man page, where it says:
Since physical memory is a potentially scarce resource, processes are limited in how much they can lock down. A single process can mlock() the minimum of a system-wide ``wired pages'' limit vm.max_wired and the per-process RLIMIT_MEMLOCK resource limit.
If security.bsd.unprivileged_mlock is set to 0 these calls are only available to the super-user.
Well, on my system vm.max_wired defaults to 1323555 and RLIMIT_MEMLOCK (ulimit -l) is 64.....so limit is 64k, right?
Wrong...delving into the Kernel source...I found that it first checks that the requested amount + the amount it already has doesn't exceed RLIMIT_MEMLOCK, and then that the requested amount + the amount wired system wide (
"vm.stats.vm.v_wire_count") is not greater than
Well, when I looked at
vm.stats.vm.v_wire_count it was 2020311....its already got more than
I feel a PR coming on....
1323555 (which is about 5GB) is said to be 1/3 of some maximum. I have a 16GB system, probably not contiguous...and there's probably some amount reserved....but 2020311 is about 7.7GB.
I did a
"sysctl vm.max_wired=2097152", and it took it (so put that into
/etc/sysctl.conf, too.) and now gnome-keyring-daemon can start without that message.
So, having returned from a morning trip to the UPS store to pick up some packages and with my knee bothering me more than yesterday...I didn't feel like going out again today. It seemed that there was a good moment do the upgrades I was planning to do.
First upgrade was to 'orac'. It is to upgrade the machine to its 8GB max, from it's current 6GB. So, I popped out the original 2GB the machine came with, and popped in a pair of 2GB DIMMs that I had purchased for this.
At first nothing special to report about it....
So, then took 'gumby' down...so that I could put that 2GB of memory into 'gumby' to take it to 4GB, knowing of course that it is running 32-bit Windows XP. And, while it was open I set in the other upgrade for 'gumby', swap out its DVD-ROM drive for a DVD burner.
No surprise....it didn't see all the memory. Though first thing I noticed was that FreeRAM XP pegged out at 2GB. Guess that's something for the future when I get around to replacing 'tardis'...where I plan to have a 64-bit Windows and tons of memory, etc. Perhaps.
But, checking more...it knows that there's 4GB of RAM in the machine, but it seems to only be letting me use 3GB. I then set about to install the software for the DVD burner. I purchased a retail kit, because I wanted the limited version of software that comes with it. Rather than dig around for the ancient version of software I used to have back then. The limited version is much newer version of Roxio than I had (formerly known as Easy CD Creator). The other computer has a dated version of Nero...I haven't done much in the way of burning in a long time, so it wasn't really a major need to get a new full blown package.
Pretty much just burn the occasional ISO here and there. I wanted to see what this lightscribe stuff is. And, at least have the option...since 'gumby' being more, seems to suggest that I might get back into some of that stuff at some point. Some day I'll buy some blank media to use....other than the spindle of blank CD-Rs that I have nearby (first thing I did burn was the restore iso for 'gumby').
Anyways, while I was using the Plextor software, I checked for updates....first no firmware update, but it found a plexutil update...so I updated it. Running that update, it found a firmware update....so then I did update the firmware. It then reported that it wanted to reboot, so I did that.
The reboot took longer than I expected, partly because I had forgotten that I had scheduled a boot-time defrag of the drives and then it hung during the boot. Not sure if the Plextor stuff has something to do with it (there seems to be something added that does something)...but when I switched to 'orac' to go online to see if I had broken something...I found 'orac' acting a big odd. It eventually locked up completely. But, while I was on 'orac'....'gumby' eventually booted, though with all the shared drives disconnected.
I did notice that after the upgrade, while poking around in the BIOS...that the new PC2-5300 (PNY) memory's SPD was being reported as 800MHz, rather than the expected 667MHz. I wondered if it being in the first bank to the older PC2-5300 (Crucial) in the second bank might be causing some problems....I didn't really feel like undoing the memory upgrades to both systems.
So, I switched the memory around (making sure that it really is alternating sockets, unlike the 'gumby' where they weren't...though the original memory was installed as if it were)
So far 'orac' seems happier....guess we'll see. Did notice that the new memory seems hotter than the old memory....but could just be the difference in packaging.
I then had to reboot 'gumby' after installing the Roxio 10 CE, but it was still slow to boot....did seem it flash some kind of window that I hadn't seen before, so it could be something the Plextor install added to my startup that is contributing to the slowdown in boot.
Guess time will tell....
The process did distract me from the other reboot that I was going to do.... Thought I saw the "Your CPU is lacking expected security protection" while logging into 'box' the other day, and was going to see if there was something I needed to change in its BIOS. Of course, I could've just been confused and confused that from the message that shows when logging into my lucid server VM running in VirtualBox...maybe I'll try that now....
A couple of days ago, I got a second stick of 1GB PC3200 DDR memory...and last night I finally got around to upgrading 'box' to 2GB. I had previously throwing a 1GB stick into a geeks.com order to bring 'box' to 1.5GB.
Nothing special of note happened with either upgrade. Just that I now have the maximum for this system, and it should allow it to better run BOINC work.
Though the current RNA World work assignments are calling for memory that I only have one machine that has at least that much memory....but it has 4 cores, so it can't run more than one RNA World at a time...and if I mix in other work with RNA World....the RNA World jobs always miss their deadline, because the estimation perpetually wrong.
Anyways....after I had done this...it occurred to me that I had done something odd....my main desktop (known as 'tardis') is suffering with low memory (firefox keeps consuming more and more memory...sometimes its consuming over 800MB....not to mention all my CPU....and then I made that mistake of upgrading to Thunderbird 3....plus Tweetdeck is pretty big too) Why am I not upgrading the memory in there....it has 4 slots, currently filled with 512MB PC3200 DDR memory. And, I should be able to change two of the slots for 1GB PC3200 DDR memory and everything should work. Could do 4GB, but don't think it'll see it all.
Though that computer was pretty temperamental on what kind of PC3200 memory it got....though when I do get around to finally replacing that computer, the 1GB sticks would probably go well in to 'box'....had I thought about this process better
Wonder if there'll be hardware upgrades to my main desktop between now and when I finally get around to replacing it. Think the machine turns 7 soon.
Now the reason I was on TigerDirect in the first place. I was ordering upgrade memory to take the Lenovo 3000 v200 that I had gotten from them from its stock 2GB to 4GB (max).
It had said that the 32-bit Vista on the machine wasn't going to see it all, but I blew that away immediately...so I didn't care.
I probably should've shutdown down (turned off) laptop before I swapped the memory...instead of doing it while it was in its suspended state. But, I had a brain fart.
Booting up, I saw that it was 4GB in the BIOS...but then only 3GB in Ubuntu. After a quick search, I found that the desktop kernel is config'd that way. And, the solution was to install the server kernel.
I did that, and now it sees all 4GB. I had gone 32-bit because of certain repos...namely Boxee....didn't support 64-bit.
After booting up, I tested a few key apps to make sure there wasn't any issue in the installing the server kernel. Namely, VirtualBox (booting my XP VM), Boxee (clicked the wrong shortcut), Skype+Webcam (sudo modprobe gspca_m5602 and then starting skype with the v4lcompat1.so PRELOAD). And, then confirm that it'll suspend when I close the lid, and resume when I open it.
Now off to stir up some other trouble....
Latest Poopli Updaters -- http://lkc.me/poop
|<< <||> >>|
boxee cpap «windows 7» «amazon prime» woot prescription lhaven netflix dsl replaytv box mdadm raid1 linux «instant streaming» appletv upgrade backuppc zen tivo twitter «hd movie» ebay «windows xp» boinc «sans digital» ups «air purifier» raid virtualbox progressive 10.04lts b2evolution «watch instantly» «doctor who» ubuntu cox tardis batteries «powersource 400» «chicago tardis» tv «tivo hd» orac amazon.com dvd eyeglasses usb freebsd cfengine3