Hang in VOP_LOCK1_APV on 8-STABLE with NFS.
Hi, OpenOffice hangs on NFS when I try to save a file or even when I try to open the save dialog in this case. $ 17:25:35 ron...@ronald [~] procstat -kk 85575 PIDTID COMM TDNAME KSTACK 85575 100322 soffice.bin initial thread mi_switch+0x176 sleepq_wait+0x3b __lockmgr_args+0x655 vop_stdlock+0x39 VOP_LOCK1_APV+0x46 _vn_lock+0x44 vget+0x67 vfs_hash_get+0xeb nfs_nget+0xa8 nfs_lookup+0x65e VOP_LOOKUP_APV+0x40 lookup+0x48a namei+0x518 kern_statat_vnhook+0x82 kern_statat+0x15 lstat+0x22 syscallenter+0x186 syscall+0x40 85575 100502 soffice.bin -mi_switch+0x176 sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _sleep+0x1a0 do_cv_wait+0x639 __umtx_op_cv_wait+0x51 syscallenter+0x186 syscall+0x40 Xfast_syscall+0xe2 85575 100576 soffice.bin -mi_switch+0x176 sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _sleep+0x1a0 do_cv_wait+0x639 __umtx_op_cv_wait+0x51 syscallenter+0x186 syscall+0x40 Xfast_syscall+0xe2 85575 100577 soffice.bin -mi_switch+0x176 sleepq_catch_signals+0x309 sleepq_wait_sig+0xc _sleep+0x25d kern_accept+0x19c accept+0xfe syscallenter+0x186 syscall+0x40 Xfast_syscall+0xe2 85575 100578 soffice.bin -mi_switch+0x176 sleepq_catch_signals+0x309 sleepq_wait_sig+0xc _cv_wait_sig+0x10e seltdwait+0xed poll+0x457 syscallenter+0x186 syscall+0x40 Xfast_syscall+0xe2 85575 100579 soffice.bin -mi_switch+0x176 sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _cv_timedwait_sig+0x11d seltdwait+0x79 poll+0x457 syscallenter+0x186 syscall+0x40 Xfast_syscall+0xe2 $ 17:25:35 ron...@ronald [~] uname -a FreeBSD ronald.office.base.nl 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #6: Mon Dec 27 23:49:30 CET 2010 r...@ronald.office.base.nl:/usr/obj/usr/src/sys/GENERIC amd64 It is not possible to exit or kill soffice.bin. I had a slighty different procstat stack before, but that was fixed a couple of days ago. Any thoughts? Enabling local locks in NFS doesn't fix it. The nfs server is an up-to-date Linux Debian 5 with kernel 2.6.26. If more info is needed. I can easily reproduce this. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.
On Fri, 07 Jan 2011 20:52:57 +0100, Kostik Belousov wrote: On Fri, Jan 07, 2011 at 02:37:25PM -0500, Rick Macklem wrote: > Hi, > > OpenOffice hangs on NFS when I try to save a file or even when I try > to > open the save dialog in this case. > > > $ 17:25:35 ron...@ronald [~] > procstat -kk 85575 > PID TID COMM TDNAME KSTACK > 85575 100322 soffice.bin initial thread mi_switch+0x176 > sleepq_wait+0x3b __lockmgr_args+0x655 vop_stdlock+0x39 > VOP_LOCK1_APV+0x46 > _vn_lock+0x44 vget+0x67 vfs_hash_get+0xeb nfs_nget+0xa8 > nfs_lookup+0x65e > VOP_LOOKUP_APV+0x40 lookup+0x48a namei+0x518 kern_statat_vnhook+0x82 > kern_statat+0x15 lstat+0x22 syscallenter+0x186 syscall+0x40 > 85575 100502 soffice.bin - mi_switch+0x176 > sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _sleep+0x1a0 > do_cv_wait+0x639 __umtx_op_cv_wait+0x51 syscallenter+0x186 > syscall+0x40 > Xfast_syscall+0xe2 > 85575 100576 soffice.bin - mi_switch+0x176 > sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 _sleep+0x1a0 > do_cv_wait+0x639 __umtx_op_cv_wait+0x51 syscallenter+0x186 > syscall+0x40 > Xfast_syscall+0xe2 > 85575 100577 soffice.bin - mi_switch+0x176 > sleepq_catch_signals+0x309 sleepq_wait_sig+0xc _sleep+0x25d > kern_accept+0x19c accept+0xfe syscallenter+0x186 syscall+0x40 > Xfast_syscall+0xe2 > 85575 100578 soffice.bin - mi_switch+0x176 > sleepq_catch_signals+0x309 sleepq_wait_sig+0xc _cv_wait_sig+0x10e > seltdwait+0xed poll+0x457 syscallenter+0x186 syscall+0x40 > Xfast_syscall+0xe2 > 85575 100579 soffice.bin - mi_switch+0x176 > sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12 > _cv_timedwait_sig+0x11d seltdwait+0x79 poll+0x457 syscallenter+0x186 > syscall+0x40 Xfast_syscall+0xe2 > > $ 17:25:35 ron...@ronald [~] > uname -a > FreeBSD ronald.office.base.nl 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE > #6: > Mon Dec 27 23:49:30 CET 2010 > r...@ronald.office.base.nl:/usr/obj/usr/src/sys/GENERIC amd64 > I think all the above tells us is that the thread is waiting for a vnode lock. The question then becomes "what is holding a lock on that vnode and why?". > It is not possible to exit or kill soffice.bin. I had a slighty > different > procstat stack before, but that was fixed a couple of days ago. Yea, it will be in an uniterruptible sleep when waiting for a vnode lock. > Any thoughts? Enabling local locks in NFS doesn't fix it. Here's some things you could try: 1 - apply the attached patch. It fixes a known problem w.r.t. the client side of the krpc. Not likely to fix this, but I can hope:-) 1a - Look around of other processes in the uninterruptible sleep state, quite possible, one of them also owns the lock the openoffice is waiting for. Also see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html Of the particular interest are the witness output and backtraces for all threads that are reported by witness as owning the vnode locks. 2 - If #1 doesn't fix the problem: - before making it hang, start capturing packets via: # tcpdump -s 0 -w xxx host server - then make it hang, kill the above and # procstat -ka # ps axHlww and capture the output of both of these. Hopefully these 2 commands will indicate what is holding the vnode lock and maybe, why. The "xxx" file can be looked at in wireshark to see what/if any NFS traffic is happening. If you aren't comfortable looking at the above, you can email them to me and I'll take a stab at them someday. 3 - Try the experimental client to see if it behaves differently. The mount command is: # mount -t newnfs -o nfsv3, server:/path /mntpath (This might ideantify if the regular client has an infrequently executed code path that forgets to unlock the vnode, since it uses a somewhat different RPC layer. The buffer cache handling etc are almost the same, but the RPC stuff is fairly different.) > The nfs server is an up-to-date Linux Debian 5 with kernel 2.6.26. > I'm afraid I can't blame Linux (at least not until we have more info;-). > If more info is needed. I can easily reproduce this. See above #2. Good luck with it and let us know how it goes, rick Hi, I have got the first steps set up. No solution yet. 1. With the patch OpenOffice opens my homedir (yeah!), but it gives an I/O error when saving a file and everything hangs after that. 2. I have dumps and stuff. I will mail some links in private e-mail. 3. Didn't work. It mount, but ls -l /home gives "Operation not permitted". I didn't see other processes in uninterruptable state. But maybe you guys see more than I do. If you don't see anything in wireshark I will try WITNESS and friends later this week. Already 2 hours busy with this during work hours. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Change in behavior to stat(1)
On Mon, 28 Feb 2011 23:39:10 +0100, jhell wrote:
On Mon, 28 Feb 2011 12:15, stephen@ wrote:
I had a little script that would remove broken links. I used to do it
like this:
if ! stat -L $link > /dev/null; then rm $link; fi
But recently (some time in February according to the CVS records) stat
was changed so that stat -L would use lstat(2) if the link is broken.
So I had to change it to
if stat -L $link | awk '{print $3}' | grep l > /dev/null;
then rm $link; fi
but it is a lot less elegant.
What is the proper accepted way to remove broken links?
Stephen
You might find sysutils/symlinks interesting. I have been using it a
long time and have not had to consider adjusting much in the way of
shell scripting to remove dirty links.
-c == change absolute/messy links to relative
-d == delete dangling links
-o == warn about links across file systems
-r == recurse into subdirs
-s == shorten lengthy links
-t == show what would be done by -c
-v == verbose (show all symlinks)
Quite interesting though how such a little tweak has caused a massive
expansion of your command line and required utils.
Good luck,
Find has some voodoo for handling links also.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Dell 850 Panic on boot
On Sat, 12 Mar 2011 21:06:38 +0100, Mark Felder wrote: On Sat, 12 Mar 2011 12:30:14 -0600, Andriy Gapon wrote: do you get exactly the same panic message with 8.2 or a slightly more informative one? If the latter, then could please provide a screenshot of that? Yeah, the 8.x seemed to have more details. That happens to be a screenshot from the 7.4 disc. I don't have access to the machine until Monday but I'll post an update then. You can also boot 'verbose'. This gives more information. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-kernel.html Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Backup tool fot ZFS with all "classic dump(8)" fetatures -- what should I use? (or is here any way to make dump -L works well on large FFS2+SU?)
Looked at rsync or tarsnap? On Mon, 28 Mar 2011 09:20:07 +0200, Lev Serebryakov wrote: Hello, Freebsd-stable. Now I'm backing up my HOME filesystem with dump(8). It works perfectly for 80GiB FS with many features: snapshot for consistency, levels, "nodump" flag (my users use it a lot!), ability to extract only one removed file from backup without restoring full FS, simple sctipy wrap-up for levels schedule, etc. On new server I have huge HOME (500GiB). And even if it is filled up only with 25GiB of data, creating snapshot takes about 10 minutes, freeze all I/O, and sometimes FAILS (!!!). I'm thinking to transfer GOME filesystem to ZFS. But I can not find appropriate tools for backing it up. Here is some requirements: (1) One-file (one-stream) backup. Not directory mirror. I need to store it on FTP server and upload with single command. (2) Levels & increment backups. Now I have "Monthly (0) - Weekly (1,2,3) - daily (4,5,6,7,8,9)" scheme. I could afford other schemes, but if they doesn't store full backup every day and doesn't need full backup more often than weekly. (3) Minimum of local metadata. Storing previous backups locally to calculate next one is not appropriate solution. "zfs send" needs previous snapshots for incremental backup, for example. (4) Working with snapshot (I think, it is trivial in case of ZFS). (5) Backup exclusions should be controlled by users (not super-user) themselves, like "nodump" flag in case of FFS/dump(8). "zfs send" can not provide this. I have very responsible users, so full backup now takes only up to 10GiB when all HOME FS is about 25GiB, so it is big help when backup is sent over Internet to other host. (6) Storing of ALL FS-specific information -- ACLs, etc. (7) Free :) Is here something like this for ZFS? "zfs send" looks promising, EXCEPT item (5) and, maybe, (3) :( gnu tar looks like everything but (6) :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: System extremely slow under light load
On Wed, 13 Apr 2011 14:28:03 +0200, Bartosz Fabianowski wrote: Hi list I am having problems with my 8.2-STABLE laptop. At times, even a very light load makes the system grind to a halt. Once an application is in the foreground, I can interact with it just fine. But when I click on a long-unused menu item or try to switch applications, I have to wait dozens of seconds or even minutes. It feels as if things were being swapped in very slowly. However, top says otherwise: The box has 4 GB of RAM with only 680 MB used. On top of that, 69 MB of swap are in used. That last number does not seem to be changing, so nothing is being swapped in or out. The load that seems to cause the worst problems is an import of OpenStreetMap data into a PostgreSQL 9 database. This does not exercise the CPU (a Core i7 Quad) much as CPU load hovers around the 20% mark most of the time and powerd is happy to reduce the operating frequency down to a few hundred MHz. There also does not seem to be much disk activity. So, memory, CPU and disk all seem fine. And still, whenever I try to switch applications, I have to wait minutes for them to appear. I am having a hard time figuring out what is going on. Any tips would be greatly appreciated. I am including the outputs of vmstat -c 2 and iostat -c 2 in the hope that these may shed some light on this. Thanks, - Bartosz Fabianowski vmstat -c 2 procs memory pagedisks faultscpu r b w avmfre flt re pi pofr sr ad0 cd0 in sy cs us sy id 0 1 20 21376M 203M 1652 2 1 1 2993 289 0 0 90 949 2764 5 2 93 0 0 20 21378M 197M 1332 0 5 1 2165 0 58 0 208 7875 3614 2 2 96 iostat -c 2 ttyada0 cd0pass0cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 188 2367 51.73 22 1.12 0.00 0 0.00 0.00 0 0.00 3 1 2 0 93 1 991 18.06 49 0.86 0.00 0 0.00 0.00 0 0.00 3 0 2 0 94 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Just for an experiment, try to disable powerd and look if things improve. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [poll] hyperthreading_allowed, hlt_logical_cpus, mp_watchdog
On Tue, 24 May 2011 18:27:47 +0200, Josh Carroll wrote: Whatever you do, please leave at least some way (at least a tunable) to enable/disable HTT - some workloads are better with, and some without it, and some BIOSes are unreliable in enabling/disabling it :) I noticed that disabling HTT via the machdep.hyperthreading_allowed tunable resulted in worse performance than disabling HTT via the BIOS. I'm not sure if that is to be expected due to how the scheduler ignores those cores or what, but just an observation I found while testing my i7 2600k to see if I should leave HTT on or off for my particular workloads. I was expecting only certain workloads to perform better with HTT on and others better with it off. However, I haven't found a task that performed better with HTT off. Some are almost equal (within a margin of error), but most are faster with HTT enabled (see below for the testing I did). For the tests below, I used an mdmfs for /usr/obj for all buildworld/buildkernel tests and they were all performed after caching the contents of /usr/src. I also ran each test 5 times and for each data point, I took the best run time. For the ffmpeg tests, I used -threads 0 to let it pick the number of threads to use. It seems hyperthreading on the Sandy Bridge i7 may be worth leaving enabled, though of course what I've tested below is just a small sample of possible tasks. So as with any benchmark, the only relevant tests are the things you use your machine for :) My workloads happen to all benefit from having HTT enabled. Josh buildworld (w/o HTT=-j5, w/HTT=-j11) === HTT off: 558.65 seconds HTT on: 501.01 seconds buildkernel (w/o HTT=-j5, w/HTT=-j7) === HTT off: 188.80 seconds HTT on: 187.03 seconds ffmpeg (10 min SD input - xvid/mp3) === HTT off: 7.75 seconds HTT on: 6.28 seconds ffmpeg (5 min 720p input - h264/aac) === HTT off: 20.08 seconds HTT on: 12.97 seconds ffmpeg (1 min 1080p input - h264/aac) === HTT off: 38.91 seconds HTT on: 30.79 seconds ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" I ones read about progress Intel made with HTT in newer cpu's. So it might very well depend on cpu type if the rumors about worse performance with HTT are true or not. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: OS X Lion time machine => (afpd|iSCSI) => ZFS question
On Thu, 21 Jul 2011 23:56:17 +0200, Bakul Shah wrote: I am in no hurry to upgrade my MBP to OS X Lion but given Lion time machine and netatalk issues, I got wondering if iSCSI on FreeBSD is stable enough for time machine use. How much duct tape and baling wire are needed to make it work?! A friend of mine posted this on twitter this morning. http://www.alexanderwilde.com/2011/04/os-x-lion-connection-error-with-afp-and-workaround/ Apparently some hash algorithm or something like that is disabled in Lion, but not in a lot of NAS's. Ronald/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS directory with a large number of files
Not an in depth solution for ZFS, but maybe a solution for you. mkdir images2 mv images/* images2 rmdir images Ronald. On Tue, 02 Aug 2011 09:39:03 +0200, seanr...@gmail.com wrote: Hi there, I Googled around and checked the PRs and wasn't successful in finding any reports of what I'm seeing. I'm hoping someone here can help me debug what's going on. On my FreeBSD 8.2-S machine (built circa 12th June), I created a directory and populated it over the course of 3 weeks with about 2 million individual files. As you might imagine, a 'ls' of this directory took quite some time. The files were conveniently named with a timestamp in the filename (still images from a security camera, once per second) so I've since moved them all to timestamped directories (/MM/dd/hh/mm). What I found though was the original directory the images were in is still very slow to ls -- and it only has 1 file in it, another directory. To clarify: % ls second [lots of time and many many files enumerated] % # rename files using rename script % ls second [wait ages] 2011 dead % mkdir second2 && mv second/2011 second2 % ls second2 [fast!] 2011 % ls second [still very slow] dead % time ls second dead/ gls -F --color 0.00s user 1.56s system 0% cpu 3:09.61 total (timings are similar for /bin/ls) This data is stored on a striped ZFS pool (version 15, though the kernel reports version 28 is available but zpool upgrade seems to disagree), 2T in size. I've run zpool scrub with no effect. ZFS is busily driving the disks away; my iostat monitoring has all three drives in the zpool running at 40-60% busy for the duration of the ls (it was quiet before). I've attached truss to the ls process. It spends a lot of time here: fstatfs(0x5,0x7fffe0d0,0x800ad5548,0x7fffdfd8,0x0,0x0) = 0 (0x0) I'm thinking there's some old ZFS metadata that it's looking into, but I'm not sure how to best dig into this to understand what's going on under the hood. Can anyone perhaps point me the right direction on this? Thanks, Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
zpool doesn't upgrade - Re: ZFS directory with a large number of files
On Tue, 02 Aug 2011 12:55:43 +0200, seanr...@gmail.com wrote: On Tue, Aug 2, 2011 at 11:10 AM, Daniel Kalchev wrote: If it is a limitation in ZFS it would be nice to know that, perhaps it truly, really is a bug that can be avoided (or it's inherent in the way ZFS handles such things) It is possible that there is not enough memory in ARC to cache that large directory. Other than that, perhaps in ZFS it would be easier to prune the unused directory entries, than it is in UFS. It looks like this is not implemented. Another reason might be some FreeBSD specific implementation issue for fstatfs. In any case, the data available is not sufficient. More information would help, like how much RAM this system has, how much ARC uses, some ARC stats. Which sysctl's would you like? I grabbed these to start: kstat.zfs.misc.arcstats.size: 118859656 kstat.zfs.misc.arcstats.hdr_size: 3764416 kstat.zfs.misc.arcstats.data_size: 53514240 kstat.zfs.misc.arcstats.other_size: 61581000 kstat.zfs.misc.arcstats.hits: 46762467 kstat.zfs.misc.arcstats.misses: 1607 The machine has 2GB of memory. What made me wonder is .. how exactly the kernel and zpool disagree on zpool version? What is the pool version in fact? % dmesg | grep ZFS ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version 5 ZFS storage pool version 28 % zpool get version tank NAME PROPERTY VALUESOURCE tank version 15 local % zpool upgrade tank This system is currently running ZFS pool version 15. Pool 'tank' is already formatted using the current version. Sean I think this zpool upgrade thing is weird. Can you try 'zpool upgrade -a'? Mine says: zpool get version zroot NAME PROPERTY VALUESOURCE zroot version 28 default Mind the SOURCE=default vs. SOURCE=local. Is it possible you did 'zpool set version=15 tank' in the past? You can check that with 'zpool history'. NB: if you upgrade the boot pool, don't forget to upgrade to boot loader. (See UPDATING) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zpool doesn't upgrade - Re: ZFS directory with a large number of files
On Tue, 09 Aug 2011 10:38:01 +0200, seanr...@gmail.com wrote: On Tue, Aug 2, 2011 at 8:59 PM, Ronald Klop wrote: On Tue, 02 Aug 2011 12:55:43 +0200, seanr...@gmail.com wrote: I think this zpool upgrade thing is weird. Can you try 'zpool upgrade -a'? Mine says: zpool get version zroot NAME PROPERTY VALUESOURCE zroot version 28 default Mind the SOURCE=default vs. SOURCE=local. Is it possible you did 'zpool set version=15 tank' in the past? You can check that with 'zpool history'. NB: if you upgrade the boot pool, don't forget to upgrade to boot loader. (See UPDATING) % sudo zpool upgrade -a Password: This system is currently running ZFS pool version 15. All pools are formatted using this version. I checked zpool history and I never set the version explicitly. My 'world' is from the 8th of March; it's possible my tree is sufficiently old (my kernel was built on the 12th of June; I'm fairly sure its from the same tree as the world, but it's also possible my kernel and userland have been out of sync for 2 months). I'll upgrade this machine sometime soon and see if that fixes the issue. Sean You can set the property to 28 and upgrade after that. zpool set version=28 zroot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
portsnap doesn't update INDEX-9?
Hi, I just upgraded to -CURRENT two weeks ago (and did a clean install at work last week). Is it normal if /usr/ports/INDEX-9 doesn't update after running portsnap? INDEX-7 and INDEX-8 are updated automatically. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portsnap doesn't update INDEX-9?
On Sat, 27 Aug 2011 18:21:43 +0200, Ronald Klop wrote: Hi, I just upgraded to -CURRENT two weeks ago (and did a clean install at work last week). Is it normal if /usr/ports/INDEX-9 doesn't update after running portsnap? INDEX-7 and INDEX-8 are updated automatically. Ronald. http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 --- Crap. First search, then search again, then post to the mailinglist. Not the other way around. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
/usr/bin/script eating 100% cpu with portupgrade and xargs
Hi,
I'm running portupgrade in screen to update all the ports for
9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
Because portupgrade -fa crashed I'm running this command to update the
remaining non-updates ports.
find /var/db/pkg -name +DESC -mtime +2 |cut -d / -f 5 | xargs time nice -n
20 portupgrade -f
The output of truss -p `pgrep script` is this:
clock_gettime(13,{1316301104.0 })= 0 (0x0)
select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
read(0,0x7fffcdf0,1024) = 0 (0x0)
write(4,0x7fffcdf0,0)= 0 (0x0)
clock_gettime(13,{1316301104.0 })= 0 (0x0)
select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
read(0,0x7fffcdf0,1024) = 0 (0x0)
write(4,0x7fffcdf0,0)= 0 (0x0)
clock_gettime(13,{1316301104.0 })= 0 (0x0)
select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
read(0,0x7fffcdf0,1024) = 0 (0x0)
write(4,0x7fffcdf0,0)= 0 (0x0)
clock_gettime(13,{1316301104.0 })= 0 (0x0)
select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
read(0,0x7fffcdf0,1024) = 0 (0x0)
write(4,0x7fffcdf0,0)= 0 (0x0)
So it is really fast in reading and writing 0 bytes most of the time.
I also found http://web.archiveorange.com/archive/v/6ETvLvjo60Gj9geAUAb6
and I think I am better of by rewriting my command so stdin/stdout is
still the terminal. Although the link is a couple of years old.
Is this known? Can somebody explain me why my xargs command is not working
well?
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /usr/bin/script eating 100% cpu with portupgrade and xargs
On Sun, 18 Sep 2011 07:39:01 +0200, Jeremy Chadwick
wrote:
On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
> Hi,
>
> I'm running portupgrade in screen to update all the ports for
> 9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
> Because portupgrade -fa crashed I'm running this command to update the
> remaining non-updates ports.
> find /var/db/pkg -name +DESC -mtime +2 |cut -d / -f 5 | xargs time
nice -n
> 20 portupgrade -f
>
> The output of truss -p `pgrep script` is this:
> clock_gettime(13,{1316301104.0 })= 0 (0x0)
> select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
> read(0,0x7fffcdf0,1024) = 0 (0x0)
> write(4,0x7fffcdf0,0)= 0 (0x0)
> clock_gettime(13,{1316301104.0 })= 0 (0x0)
> select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
> read(0,0x7fffcdf0,1024) = 0 (0x0)
> write(4,0x7fffcdf0,0)= 0 (0x0)
> clock_gettime(13,{1316301104.0 })= 0 (0x0)
> select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
> read(0,0x7fffcdf0,1024) = 0 (0x0)
> write(4,0x7fffcdf0,0)= 0 (0x0)
> clock_gettime(13,{1316301104.0 })= 0 (0x0)
> select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
> read(0,0x7fffcdf0,1024) = 0 (0x0)
> write(4,0x7fffcdf0,0)= 0 (0x0)
>
> So it is really fast in reading and writing 0 bytes most of the time.
>
> I also found
http://web.archiveorange.com/archive/v/6ETvLvjo60Gj9geAUAb6
> and I think I am better of by rewriting my command so stdin/stdout is
> still the terminal. Although the link is a couple of years old.
>
> Is this known? Can somebody explain me why my xargs command is not
working
> well?
>
Are you absolutely sure that its script(1) causing this ? 100% CPU usage
has been a known side effect of screen(1) for quite some time. Rebuild
it and try again.
Jason's referring to this, I believe:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.55
To clarify the what the commit message means: it does not mean "when the
package is installed the installation takes up 100% CPU". It means
"once the package is installed and screen is used, screen takes up 100%
CPU". I know because I've seen this behaviour in the past (one of the
many, many reasons I build ports from source).
However:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.78
So: If a binary package is being installed through your above
portupgrade command, and you're seeing this problem, then it sounds to
me like commit revision 1.78 is a regression and NO_PACKAGE should be
put back into place + packages removed from all mirrors.
There are many reasons to not use GNU screen at all, or if you must have
something like it, use tmux. I recently had to provide an analysis of
how GNU screen destroys one's terminal[1]; so if the above problem turns
out to be caused by GNU screen as well, I'll just add it to my
ever-growing list of reasons the software should be nuked from orbit.
Otherwise, if this turns out to be a problem with portupgrade (which you
found some evidence supporting such), then the solution is simple: stop
using portupgrade, use portmaster (if it lacks things you need ask Doug
Barton, he's incredibly receptive to adding new features/fixing things).
Two databases that aren't compatible, ruby shims, and other crap = not
worth it. Think the database ordeal is long over with/fixed/whatever?
It isn't[2].
[1]:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/063052.html
[2]:
http://www.dslreports.com/forum/r26304856-FreeBSD-defining-portmaster-alias
I have a repeatable test. Run top in a window and this command in another.
$ echo test | script /tmp/script-test sleep 1000
Script started, output file is /tmp/script-test
test
PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU
COMMAND
29656 ronald 1 1030 12324K 1244K CPU44 1:03 100.00%
script
So it has nothing to do with portupgrade or screen. The output of truss
-p29656 is the same as posted previously.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /usr/bin/script eating 100% cpu with portupgrade and xargs
On Sun, 18 Sep 2011 12:58:32 +0200, Mikolaj Golub
wrote:
On Sun, 18 Sep 2011 08:47:13 +0200 Ronald Klop wrote:
RK> On Sun, 18 Sep 2011 07:39:01 +0200, Jeremy Chadwick
RK> wrote:
>> On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
>>> On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
>>> > Hi,
>>> >
>>> > I'm running portupgrade in screen to update all the ports for
>>> > 9-BETA2/9-CURRENT on amd64. While doing this script eats 100% cpu.
>>> > Because portupgrade -fa crashed I'm running this command to
update the
>>> > remaining non-updates ports.
>>> > find /var/db/pkg -name +DESC -mtime +2 |cut -d / -f 5 | xargs
>>> time nice -n
>>> > 20 portupgrade -f
>>> >
>>> > The output of truss -p `pgrep script` is this:
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> >
>>> > So it is really fast in reading and writing 0 bytes most of the
time.
>>> >
>>> > I also found
>>> http://web.archiveorange.com/archive/v/6ETvLvjo60Gj9geAUAb6
>>> > and I think I am better of by rewriting my command so
stdin/stdout is
>>> > still the terminal. Although the link is a couple of years old.
>>> >
>>> > Is this known? Can somebody explain me why my xargs command is
>>> not working
>>> > well?
>>> >
>>>
>>> Are you absolutely sure that its script(1) causing this ? 100% CPU
usage
>>> has been a known side effect of screen(1) for quite some time.
Rebuild
>>> it and try again.
>>
>> Jason's referring to this, I believe:
>>
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.55
>>
>> To clarify the what the commit message means: it does not mean "when
the
>> package is installed the installation takes up 100% CPU". It means
>> "once the package is installed and screen is used, screen takes up
100%
>> CPU". I know because I've seen this behaviour in the past (one of
the
>> many, many reasons I build ports from source).
>>
>> However:
>>
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.78
>>
>> So: If a binary package is being installed through your above
>> portupgrade command, and you're seeing this problem, then it sounds
to
>> me like commit revision 1.78 is a regression and NO_PACKAGE should be
>> put back into place + packages removed from all mirrors.
>>
>> There are many reasons to not use GNU screen at all, or if you must
have
>> something like it, use tmux. I recently had to provide an analysis
of
>> how GNU screen destroys one's terminal[1]; so if the above problem
turns
>> out to be caused by GNU screen as well, I'll just add it to my
>> ever-growing list of reasons the software should be nuked from orbit.
>>
>> Otherwise, if this turns out to be a problem with portupgrade (which
you
>> found some evidence supporting such), then the solution is simple:
stop
>> using portupgrade, use portmaster (if it lacks things you need ask
Doug
>> Barton, he's incredibly receptive to adding new features/fixing
things).
>> Two databases that aren't compatible, ruby shims, and other crap =
not
>> worth it. Think the database ordeal is long over
with/fixed/whatever?
>> It isn't[2].
>>
&
usbus is seen as network interface - Fwd: sjakie.klop.ws daily run output
Hello, Why is usbus seen as a network interface since some time? I'm running 9-CURRENT on amd64. At boot devd recognizes these devices and the failure to configure them makes booting take longer. This is from an older console.log (still 8-STABLE), but I see the same today on 9-CURRENT. Jun 2 13:25:35 sjakie kernel: Starting devd. Jun 2 13:25:35 sjakie kernel: usbus0: not found Jun 2 13:25:35 sjakie kernel: Jun 2 13:25:35 sjakie kernel: exiting. Jun 2 13:25:35 sjakie kernel: Starting Network: usbus0. Jun 2 13:25:35 sjakie kernel: usbus1: not found Jun 2 13:25:35 sjakie kernel: Jun 2 13:25:35 sjakie kernel: exiting. Jun 2 13:25:35 sjakie kernel: Starting Network: usbus1. Jun 2 13:25:35 sjakie kernel: usbus2: not found Jun 2 13:25:35 sjakie kernel: Jun 2 13:25:35 sjakie kernel: exiting. Ronald. --- Forwarded message --- From: "Charlie Root" To: r...@klop.ws Cc: Subject: sjakie.klop.ws daily run output Date: Tue, 20 Sep 2011 03:18:03 +0200 Removing stale files from /var/preserve: Cleaning out old system announcements: Removing stale files from /var/rwho: Backup passwd and group files: Verifying group file syntax: /etc/group is fine Backing up package db directory: Rotating accounting logs and gathering statistics: Checking status of zfs pools: all pools are healthy Network interface status: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll em01500 00:21:70:46:6c:da 1129338 0 0 861443 0 0 em01500 192.168.1.0 sjakie.home1128004 - - 862309 - - usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 usbus 00 0 0 0 0 0 lo0 16384 16 0 0 16 0 0 lo0 16384 localhost ::1 8 - - 8 - - lo0 16384 fe80::1%lo0 fe80::1 0 - - 0 - - lo0 16384 your-net localhost8 - - 8 - - Security check: (output mailed separately) Checking for denied zone transfers (AXFR and IXFR): -- End of daily output -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-BETA3 and ports db
On Wed, 28 Sep 2011 23:36:13 +0200, George Kontostanos wrote: Hi everyone, Today I upgraded one of my servers from 8.2-STABLE to 9.0-BETA3. I noticed that after the upgrade portsnap does not fetch Index-9 and I had to manually issue the "make fetchindex" command. I remember that this was something I had to do when I was running 9-CURRENT a few months ago in my desktop PC but I thought that it would be solved by now. Am I doing something wrong or is this an expected behavior ? Thanks It is known. But I don't know when it will be fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /usr/bin/script eating 100% cpu with portupgrade and xargs
On Tue, 04 Oct 2011 13:15:24 +0200, Mikolaj Golub
wrote:
On Sun, Sep 18, 2011 at 1:58 PM, Mikolaj Golub
wrote:
On Sun, 18 Sep 2011 08:47:13 +0200 Ronald Klop wrote:
RK> On Sun, 18 Sep 2011 07:39:01 +0200, Jeremy Chadwick
RK> wrote:
>> On Sun, Sep 18, 2011 at 12:54:13AM -0400, Jason Hellenthal wrote:
>>> On Sun, Sep 18, 2011 at 01:49:15AM +0200, Ronald Klop wrote:
>>> > Hi,
>>> >
>>> > I'm running portupgrade in screen to update all the ports for
>>> > 9-BETA2/9-CURRENT on amd64. While doing this script eats 100%
cpu.
>>> > Because portupgrade -fa crashed I'm running this command to
update the
>>> > remaining non-updates ports.
>>> > find /var/db/pkg -name +DESC -mtime +2 |cut -d / -f 5 | xargs
>>> time nice -n
>>> > 20 portupgrade -f
>>> >
>>> > The output of truss -p `pgrep script` is this:
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> > clock_gettime(13,{1316301104.0 })= 0 (0x0)
>>> > select(5,{0 4},0x0,0x0,{30.00 }) = 1 (0x1)
>>> > read(0,0x7fffcdf0,1024) = 0 (0x0)
>>> > write(4,0x7fffcdf0,0)= 0 (0x0)
>>> >
>>> > So it is really fast in reading and writing 0 bytes most of the
time.
>>> >
>>> > I also found
>>> http://web.archiveorange.com/archive/v/6ETvLvjo60Gj9geAUAb6
>>> > and I think I am better of by rewriting my command so
stdin/stdout is
>>> > still the terminal. Although the link is a couple of years old.
>>> >
>>> > Is this known? Can somebody explain me why my xargs command is
>>> not working
>>> > well?
>>> >
>>>
>>> Are you absolutely sure that its script(1) causing this ? 100% CPU
usage
>>> has been a known side effect of screen(1) for quite some time.
Rebuild
>>> it and try again.
>>
>> Jason's referring to this, I believe:
>>
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.55
>>
>> To clarify the what the commit message means: it does not mean
"when the
>> package is installed the installation takes up 100% CPU". It means
>> "once the package is installed and screen is used, screen takes up
100%
>> CPU". I know because I've seen this behaviour in the past (one of
the
>> many, many reasons I build ports from source).
>>
>> However:
>>
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile#rev1.78
>>
>> So: If a binary package is being installed through your above
>> portupgrade command, and you're seeing this problem, then it sounds
to
>> me like commit revision 1.78 is a regression and NO_PACKAGE should
be
>> put back into place + packages removed from all mirrors.
>>
>> There are many reasons to not use GNU screen at all, or if you must
have
>> something like it, use tmux. I recently had to provide an analysis
of
>> how GNU screen destroys one's terminal[1]; so if the above problem
turns
>> out to be caused by GNU screen as well, I'll just add it to my
>> ever-growing list of reasons the software should be nuked from
orbit.
>>
>> Otherwise, if this turns out to be a problem with portupgrade
(which you
>> found some evidence supporting such), then the solution is simple:
stop
>> using portupgrade, use portmaster (if it lacks things you need ask
Doug
>> Barton, he's incredibly receptive to adding new features/fixing
things).
>> Two databases that aren't compatible, ruby shims, and other crap =
not
>> worth it. Think the database ordeal is long over
Re: FreeBSD 9.0-BETA3 Available...
On Tue, 04 Oct 2011 18:41:50 +0200, Arnaud Lacombe wrote: Hi, On Tue, Oct 4, 2011 at 12:24 PM, Chris Rees wrote: On 4 October 2011 16:35, Chris Rees wrote: On 4 Oct 2011 16:26, "Arnaud Lacombe" wrote: On Mon, Oct 3, 2011 at 7:50 PM, Arnaud Lacombe wrote: On Wed, Sep 28, 2011 at 9:42 PM, Ken Smith wrote: The third BETA build of the 9.0-RELEASE release cycle is now available. Since this is the first release of a brand new branch I cross-post the announcements on both -current and -stable. But just so you know most of the developers active in head pay more attention to the -current mailing list. If you notice problems you can report them through the normal Gnats PR system or on the -current mailing list. The 9.0-RELEASE cycle will be tracked here: http://wiki.freebsd.org/Releng/9.0TODO could you please update that page ? It's wayy out of date... The page is immutable, so I guess a lambda user cannot edit it. Could you please give me the credential to update it ? Providing an out-of-date status update page in a release is really amateurish; the only real use of that page being during the release process... What is your Wiki name? Just to clarify, I will fix you up with access, but the re page should not be edited without re approval! Not when re@'s guys are not doing their job. With privilege comes responsibility. - Arnaud Yeah! I'm not the only one who looks at that page sometimes and wonders why it is there. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ports index on FreeBSD 9
On Sat, 15 Oct 2011 11:24:32 +0200, George Kontostanos wrote: On Thu, Oct 13, 2011 at 2:54 AM, George Kontostanos wrote: On Wed, Oct 12, 2011 at 3:01 PM, Matthew Seaman wrote: On 12/10/2011 11:24, Sergey V. Dyatko wrote: On Wed, 12 Oct 2011 13:12:55 +0300 George Kontostanos wrote: On Wed, Oct 12, 2011 at 8:52 AM, Sergey V. Dyatko wrote: On Tue, 11 Oct 2011 14:31:12 +0300 George Kontostanos wrote: Hi everyone, I was wondering if there is any progress regarding the http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 . svn log -v -r226274 wbr, tiger Do you mean this: http://svnweb.freebsd.org/base?view=revision&revision=226274 ? oops, sorry, wrong revision. svn log -v -r226277 http://svn.freebsd.org/base/head MFC to stable/9 might be a good idea... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW svn commit: r226322 - stable/9/etc Thanks everyone -- George Kontostanos aisecure.net It still doesn't upgrade the index file properly : hp# portsnap fetch update && portversion -v | grep "<" Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap5.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Thu Oct 6 11:21:13 EEST 2011 to Sat Oct 15 12:06:45 EEST 2011. Fetching 3 metadata patches.. done. Applying metadata patches... done. Building new INDEX files... done. ezm3-1.1_2 < needs updating (port has 1.2_1) hp# cd /usr/ports/ hp# make fetchindex /usr/ports/INDEX-9.bz2100% of 1512 kB 183 kBps hp# portversion -v | grep "<" [Updating the portsdb in /usr/ports ... - 22730 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000... . done] ezm3-1.1_2 < needs updating (port has 1.2_1) ffmpeg-0.7.5,1 < needs updating (port has 0.7.6,1) libltdl-2.4 < needs updating (port has 2.4_1) libtool-2.4 < needs updating (port has 2.4_1) mpfr-3.0.1 < needs updating (port has 3.1.0_1) p5-Authen-NTLM-1.08_1 < needs updating (port has 1.09) p5-Class-Load-0.10 < needs updating (port has 0.11) p5-DateTime-TimeZone-1.36 < needs updating (port has 1.39) p5-Module-Metadata-1.06 < needs updating (port has 1.07) phpMyAdmin-3.4.5< needs updating (port has 3.4.6.r1) x264-0.115.2000 < needs updating (port has 0.116.2076) I think, but I am not an authority on this, that you should do a portsnap extract so the index is in sync with the extracted ports. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mount GPT from Windows 7 in FreeBSD 9
On Sat, 19 Nov 2011 14:51:19 +0100, Nenhum_de_Nos wrote: On Sat, November 19, 2011 07:58, Jeremy Chadwick wrote: On Fri, Nov 18, 2011 at 10:55:10PM -0200, Nenhum_de_Nos wrote: hail, I have two disks, and the one holding Windows appears just as ada1 or ad8, despite fdisk shows all partitions fine. I tried to kldload geom_gpt_something, but it says it was already loaded. I couldn't mount using mount_ntfs, so I would use fuse to have ability to write on it :) is there a way to solve this ? two disks. One just FreeBSD, the other just Windows. Jeremy, thanks and let's to the answers. First: to my knowledge, fdisk does not support GPT, so I'm not sure what you mean when you say "it shows all partitions fine". You should probably use gpart(8) instead, e.g. "gpart show" and/or "gpart list". See the man page for usage. It will work with all types, and tell you what scheme is used (MBR, GPT, etc.). its all here :) macgyver# fdisk ada1 *** Working on device /dev/ada1 *** parameters extracted from in-core disklabel are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=484521 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 2048, size 204800 (100 Meg), flag 80 (active) beg: cyl 0/ head 107/ sector 16; end: cyl 48/ head 134/ sector 14 The data for partition 2 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 206848, size 103165952 (50374 Meg), flag 0 beg: cyl 48/ head 134/ sector 15; end: cyl 1023/ head 223/ sector 19 The data for partition 3 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 103372800, size 385019904 (187998 Meg), flag 0 beg: cyl 1023/ head 239/ sector 63; end: cyl 1023/ head 239/ sector 63 The data for partition 4 is: macgyver# gpart show ada1 => 34 488397101 ada1 GPT (232G) 34 488397101- free - (232G) macgyver# gpart list ada1 Geom name: ada1 modified: false state: OK fwheads: 16 fwsectors: 63 last: 488397134 first: 34 entries: 128 scheme: GPT Consumers: 1. Name: ada1 Mediasize: 250059350016 (232G) Sectorsize: 512 Mode: r0w0e0 macgyver# dmesg | grep ada1 ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: ATA-7 SATA 1.x device ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad8 macgyver# Next item: what do you mean it appears as "ada1 **or** ad8"? ada1 indicates you're using ahci.ko (not ataahci.ko) which supports AHCI via CAM(4), while the latter indicates you're using ata(4) (even if AHCI is in use; that would be ataahci.ko). Why/how would this change unless you are messing with cables or enabling/disabling drivers? As now I'm on FreeBSD in this machine, there is: macgyver# ls /dev/ada1* /dev/ada1 but the FreeBSD disk: macgyver# ls /dev/ada0* /dev/ada0 /dev/ada0s1 /dev/ada0s1a/dev/ada0s1b /dev/ada0s2 /dev/ada0s2a /dev/ada0s3 /dev/ada0s4 /dev/ada0s4a/dev/ada0s4b and I still have old ad4 and ad8: macgyver# ls /dev/ad4* /dev/ad8* /dev/ad4/dev/ad4s1 /dev/ad4s1a /dev/ad4s1b /dev/ad4s2 /dev/ad4s2a /dev/ad4s3 /dev/ad4s4 /dev/ad4s4a /dev/ad4s4b /dev/ad8 and my point here is there even though fdisk shows some windows partitions, I can't even address them as I just see ada1/ad8. no ada1s1 or anything alike. Next item: I think you're referring to the geom_part_gpt.ko module, but you don't need to do that. GEOM and related kernel bits will load it automatically, which is why it told you it's already loaded. You can use "kldstat" to verify. Otherwise it's statically-included in your kernel. I noticed that. I got to put it on loader.conf: for the record, no good and won't be able to boot the box (usb live solved). I thought I needed to load the module to see the gpt. Next item: this sounds like the crux of your issue. As I understand it, NTFS support via kernel on FreeBSD is in an extremely bad state on numerous levels. You can find complaints about lack-of or badly-done UTF-8 filename/path support, lack of full write support, and the more important/major Non-MPSAFE filesystem declaration here: http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS unfortunately I didn't got to this point as I never got to see the partitions :( but I plan to use ntfs from fuse. It looks like atti...@freebsd.org has taken ownership of the NTFS driver in the kernel at this point. You may want to ask him if there are any patches you could try. However, as I understand it
Re: Sporadic 9.0-RC2 boot-time panic
On Mon, 28 Nov 2011 23:37:27 +0100, Mike Andrews wrote: *Sometimes* when booting 9.0-RC2 on *some* of my machines, I'll get one of the following two panics during multiuser startup, usually while running the /usr/local/etc/rc.d scripts. (The instruction pointer is always exactly one of these two, and they look fairly related.) If after two or three reboots it manages to not panic, the system will run perfectly stable. For some probably-unrelated reason, the dump never finishes in either case. First panic (note em0 warning before it): - em0: discard frame w/o packet header Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x805e4fc5 stack pointer = 0x28:0xff80003299e0 frame pointer = 0x28:0xff8000329a00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (irq256: em0:rx 0) trap number = 9 panic: general protection fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x187 trap_fatal() at trap_fatal+0x290 trap() at trap+0x10a calltrap() at calltrap+0x8 --- trap 0x9, rip = 0x805e4fc5, rsp = 0xff80003299e0, rbp = 0xff8000329a00 --- m_freem() at m_freem+0x25 ether_nh_input() at ether_nh_input+0x82 netisr_dispatch_src() at netisr_dispatch_src+0x20b em_rxeof() at em_rxeof+0x1ca em_msix_rx() at em_msix_rx+0x24 intr_event_execute_handlers() at intr_event_execute_handlers+0x104 ithread_loop() at ithread_loop+0xa4 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff8000329d00, rbp = 0 --- Uptime: 49s Dumping 679 out of 12263 MB: - Second panic (no em0 discard warning this time): - Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x8063c0e4 stack pointer = 0x28:0xff8000329a00 frame pointer = 0x28:0xff8000329a40 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (irq256: em0:rx 0) trap number = 9 panic: general protection fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x187 trap_fatal() at trap_fatal+0x290 trap() at trap+0x10a calltrap() at calltrap+0x8 --- trap 0x9, rip = 0x8063c0e4, rsp = 0xff8000329a00, rbp = 0xff8000329a40 --- ether_nh_input() at ether_nh_input+0x94 netisr_dispatch_src() at netisr_dispatch_src+0x20b em_rxeof() at em_rxeof+0x1ca em_msix_rx() at em_msix_rx+0x24 intr_event_execute_handlers() at intr_event_execute_handlers+0x104 ithread_loop() at ithread_loop+0xa4 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff8000329d00, rbp = 0 --- Uptime: 46s Dumping 657 out of 12263 MB:..3% ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Does it help if you disable msix on your em0? Google for 'sysctl em msix'. Or run 'sysctl -a | grep msix'. NB: I know nothing about the details of em of msix, so hopefully somebody with more clue responds also. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Possible: Configure SAS Sun Jbod J4200 ?
On Wed, 30 Nov 2011 15:01:09 +0100, Denny Schierz wrote: hi, we have a Sun Jbod SAS J4200 and actually there is a running daemon under Solaris 10, which is needed, to configure the JBOD over a (badly) Java Sun tool from a other host machine (Windows XP, for example). If I switch from Solaris to FreeBSD, I don't know, if I can view the status and configure from/over FBSD… The Jbod is only connected through the SAS channel, nothing more. :-/ It means, it doest' have any Network/serial access … any suggestions? cu denny___ Can you boot FreeBSD on it and mail a dmesg output to the mailinglist? That gives people a clue about your hardware setup. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: about thumper aka sun fire x4500
On Tue, 17 Jan 2012 18:59:08 +0100, peter h wrote: I have been beating on of these a few days, i have udes freebsd 9.0 and 8.2 Both fails when i engage > 10 disks, the system craches and messages : "Hyper transport sync flood" will get into the BIOS errorlog ( but nothing will come to syslog since reboot is immediate) Using a zfs radz of 25 disks and typing "zpool scrub" will bring the system down in seconds. Anyone using a x4500 that can comfirm that it works ? Or is this box broken ? Does it work if you make 3 raid groups of 8 disks and 1 spare? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Timekeeping in stable/9
On Sat, 21 Jan 2012 10:18:42 +0100, Martin Sugioarto wrote: Am Wed, 18 Jan 2012 07:50:49 +0100 schrieb Martin Sugioarto : I can confirm this on VirtualBox. I've been running WinXP inside VirtualBox and measured network I/O during downloads. It showed me very high download rates (around 800kB/s) while it's physically possible to download 200kB/s through DSL here (Germany sucks with DSL, even in largest cities, btw!). I correlated this behavior with high disk I/O on the host. That means that the timer issues on the virtual host appear when I start a larger cp job on the host. I also immediately thought that this has something to do with timers. Hi everybody, I just want to add some information on this. I tested a few things with VirtualBox yesterday. I switched off ntpd on the host and tested if there are differences, but the clock is working correctly on the host. I tested it a few times, it is stable, as I expect it to be. It seems to be rather a software problem with VirtualBox. I can see that when the host is under heavy load (CPU!) the guest does not get enough runtime to adjust the clock correctly. After a few minutes there has been a difference of 50 seconds between the host and guest clock. And furthermore, I don't quite understand how the real time clock works in VirtualBox but it seems to slide in the different directions causing weird results with progress bars on MS-Windows XP. I just want to explain why I thought that I/O influences this. I have got my hard disk encrypted, so it puts some load on the CPU, too. If you want to test VirtualBox behavior, you can simple dd from /dev/random and look at the weird results in VirtualBox. -- I hope it helps further, Martin Hi, As I understand it. Host: FreeBSD 9 Guest: WinXP Which one has troubles with its clock? The host or the guest or both? How many CPU's did you assign to the guest? Did you install virtualbox guest additions to the guest? Do you run NTP on the guest XP also? If yes, turn it off. VBox guest additions can sync the guest clock with the host. BTW: My experience with VBox is that it is nice for hobby stuff, but not for heavy load server stuff. VMWare does a better job there. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Timekeeping in stable/9
On Sat, 21 Jan 2012 14:11:51 +0100, Martin Sugioarto wrote: Am Sat, 21 Jan 2012 13:20:51 +0100 schrieb "Ronald Klop" : Hi, As I understand it. Host: FreeBSD 9 Guest: WinXP Which one has troubles with its clock? The host or the guest or both? Hi, only inside VirtualBox, I think it's only an application problem and my emails would be probably better addressed to ports@. ONLY the guest is affected when host is loaded. I noticed additionally: You get better results with a desync'ed clock in the guest system, when you start "openssl speed -multi 20" or similar. Within a few seconds the clock gets a 20 seconds difference. How many CPU's did you assign to the guest? Did you install virtualbox guest additions to the guest? Here a few details (guest additions are installed): Memory size: 1600MB Page Fusion: off VRAM size: 256MB HPET:on/off (tried both settings) Chipset: piix3 Firmware:BIOS Number of CPUs: 1 Synthetic Cpu: off CPUID overrides: None [...] ACPI:on IOAPIC: off PAE: on Time offset: 0 ms RTC: local time Hardw. virt.ext: on Hardw. virt.ext exclusive: on Nested Paging: on Large Pages: on VT-x VPID: on [...] 3D Acceleration: off 2D Video Acceleration: on Do you run NTP on the guest XP also? If yes, turn it off. Windows XP default installation (synch'ed to time.windows.com). Switching this off, does not have any influence. I think MS-Windows does not do continuous synchronization, only at system start, I guess. VBox guest additions can sync the guest clock with the host. I'll try to deinstall them. But I somehow like my shared folder. BTW: My experience with VBox is that it is nice for hobby stuff, but not for heavy load server stuff. VMWare does a better job there. Yes. I know. Still VirtualBox ist nice and cheap solution. -- Martin BTW: I used VBox on Linux at work. Same problems. Different problems come and go with different versions of Linux in combination with different versions of VirtualBox. Using VmWare ESXI solved it. If you search a lot on the vmware website you will find a free version. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9-stable from i386 to amd64
On Sat, 11 Feb 2012 10:58:30 +0100, Randy Bush wrote: These statements are false, esp. worrying is that they are interwinned with some facts that get tilted to support false presumption. Kernel do not care about which interpreter is /libexec/ld-elf.so. The path to the interpreter is specified in the binary itself. So if you have 32bit binary that put '/libexec/ld-elf.so.1' into PH_INTERP, and /libexec/ld-elf.so.1 is 32bit, then amd64 kernel properly executes that combination. Kernel has a hack that falls back to try to use /libexec/ld-elf32.so.1 for some 'brands' of ELF images, in particular, for 32bit binaries. This is done to help in situation when 32bit binaries also specified the same path for interpreter. If you have 32bit world installed and booted 64bit kernel, it will boot. It is the same as running 32bit world in the jail. The management functions, like configuring network interfaces, ZFS and many other system setup functionality does not work, indeed. as the system in this case is half the planet away and without console access, it might be helpful to have network interfaces working. so do you have direct suggestion(s) on how to hack the system (while the 32-bit kernel is running) so that i can boot the 64-bit kernel and get the 64-bit world up? Do you have a spare partition? Probably use the swap partition temporarily. Install the 64 bits stuff into it. Boot from it and than install the 64 bits stuff over the (now unused) 32 bits stuff and reboot into that. If something fails you can always go back to a bootable system. NB: disclaimer: I have never done this. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: disk access seems unitask and ant-slow
On Sat, 18 Feb 2012 12:44:12 +0100, H wrote: Hi I have 9-Stable on one partition of my SATAII disk, with kde4, to be sure I compiled yesterday sources world and kernel happens that any secondary task with diskaccess is so very slow that it is inacceptable for example, compiling firefox and then trying to open an image with gimp, I am sitting here for over 5 minutes and the open image dialog still do not show the directory content ..., same with dolphin or any other diskaccess I have enough cpu and ram, I go back to 8.2 and everything runs smooth and fast as usual, same on fedora10 partition my disk is good and found as ada, no fault anywhere system is almost sleeping CPU: 2.6% user, 0.0% nice, 3.6% system, 1.3% interrupt, 92.5% idle I would be glad to get any good hint how to change that thank's Please post the output of dmesg so people have some information about your system. And /etc/sysctl.conf, /boot/loader.conf and the output of 'mount -v' are interesting also. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Sat, 14 Apr 2012 01:13:30 +0200, Matt Thyer wrote: On Apr 7, 2012 2:38 PM, "Matt Thyer" wrote: On 7 April 2012 14:31, Matt Thyer wrote: Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm no longer having that disk evicted from the raidz2 pool with write errors and I thought that the high interrupt rate issue had also been solved but it's back again. This is on 8-STABLE at revision 230921 (before the new driver hit 8-STABLE). So now I need to go back to trying to determine what the cause is. vmstat -i has shown that the issue was on irq 16. Unfortunately there seems to be a lot of things on irq 16: $ dmesg | grep "irq 16" pcib1: irq 16 at device 1.0 on pci0 mps0: port 0xee00-0xeeff mem 0xfbdfc000-0xfbdf,0xfbd8-0xfbdb irq 16 at device 0.0 on pci1 vgapci0: port 0xff00-0xff07 mem 0xfb40-0xfb7f,0xe000-0xefff irq 16 at device 2.0 on pci0 uhci0: port 0xfe00-0xfe1f irq 16 at device 26.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pcib3: irq 16 at device 28.4 on pci0 atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3 Any idea how to isolate which bit of hardware could be triggering the interrupts ? Unfortunately the only device I could remove would be the SuperMicro AOC-USAS2-L8i (so yes I could eliminate that). My biggest problem right now is not knowing how to trigger the issue. At this stage I'm going to upgrade to 9-STABLE and see if it returns. The problem does not occur with 9-STABLE. Who knows what the problem was ? USB maybe ? Do you still have the same hardware on the same interrupts on 9-STABLE? Are there changes in the use of MSI(-X)? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.3 and 9.0 freeze with firefox
On Fri, 30 Mar 2012 04:28:06 +0200, Joseph Olatt wrote: Hi, Starting with 8.3, I've been experiencing FreeBSD freezing up completely after using firefox for a while. Thinking the problem would go away if I upgraded to 9.0, I did that and I am still experiencing the same freezing up. The mouse pointer freezes, the keyboard freezes (caps lock light will not come on; Ctrl-Alt-F[1-10] does not work etc.). The only way to get the system back is by pressing and holding down the power button. The problem seems similar to: kern/163145 There is nothing in /var/log/messages to indicate a problem. Output of pciconf -lv and uname -a are at: http://www.eskimo.com/~joji/wisdom/ Anybody else experiencing similar freeze ups with 8.3 or 9.0 while using firefox? Since Firefox uses all kinds of GPU stuff nowadays. Is it possible it locks up your graphics card? I suggest trying to turn of GPU hardware acceleration in Firefox. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 157k interrupts per second causing 60% CPU load on idle system
On Sun, 15 Apr 2012 15:09:34 +0200, Matt Thyer wrote: On Apr 15, 2012 6:27 PM, "Ronald Klop" wrote: The problem does not occur with 9-STABLE. Who knows what the problem was ? USB maybe ? Do you still have the same hardware on the same interrupts on 9-STABLE? Are there changes in the use of MSI(-X)? I made no hardware or BIOS changes and I'm running a GENERIC kernel in all testing. That does not mean FreeBSD 9 can't put devices on other interrupts than 8 did. 'dmesg | grep irq' like you did before might show a difference with your previous output. I'm just guessing here for a clue on the result you are seeing, but without any data I cannot answer you (and I guess nobody can). Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Any options on crypt+zfs ?
On Mon, 16 Apr 2012 19:32:43 +0200, Nenhum_de_Nos wrote: hail, I have a soekris running an atom and 2GB RAM and ZFS using 7 drives, small capacity though, to test and study if I can make my home server this box and this way. It will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags: NONE KeysAllocated: 38 KeysTotal: 38 Providers: 1. Name: label/zfs1.eli Mediasize: 160041881600 (149G) Sectorsize: 4096 Mode: r1w1e1 Consumers: 1. Name: label/zfs1 Mediasize: 160041885184 (149G) Sectorsize: 512 Mode: r1w1e1 all disks are this way (just 4 disks are on geli zfs). would it be faster, if I had geli over zfs, and not the other way (as is now) ? my performance is too low (I know the hardware is not that much, but I compared it to a friend's arm based AP-Router gadget and my setup is when much equal. I have 1.6 GHz Atom and 2GB ram, he has not half this ... I know can't compare arm and x86 clock for clock ...) I'll try to run geli on single disk, to see how much ZFS is impacting on performance, but, is there any other way around ? All I want is RAID5, and FreeBSD has not developed RAID5 from GEOM (AFAIK) since a long time. ZFS is the way people go in recent years. suggestions are welcome, just want to upgrade my old 8.0 BETA3 using geom mirror/stripe to a newer approach that would be supported by FreeBSD. I have an external enclosure for 4 SATA disks (port multiplier included) using 4 disks, another port multiplier 5x1 using now 3 disks, and: ahci1@pci0:13:0:0: class=0x010601 card=0x10601b21 chip=0x06121b21 rev=0x01 hdr=0x00 vendor = 'ASMedia Technology Inc.' class = mass storage subclass = SATA with two eSATA to the Port Multipliers. First try to look for the bottleneck. What is the performance without GELI? And what performance do you want to have? If you want performance, why do you use encryption on low-end hardware? Ronald. thanks, matheus machine: ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-RELEASE #0: Wed Apr 11 13:04:15 BRT 2012 root@macgyver:/usr/obj/usr/src/sys/net6501-amd64 amd64 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x20661 Family = 6 Model = 26 Stepping = 1 Features=0xbfe9fbff Features2=0x40e3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 2147352576 (2047 MB) avail memory = 2046488576 (1951 MB) MPTable: Event timer "LAPIC" quality 400 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: on motherboard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: BuildingFreeBSDWithClang (was: Re: (no subject))
On Tue, 22 May 2012 13:04:59 +0200, S.N.Grigoriev wrote: Hi list, I tried to build world and kernel with CLang on my 9-stable amd64 system. The following errors occured: mv -f term.h.new term.h cat /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include/curses.tail >> curses.h.new mv -f curses.h.new curses.h cc -o make_keys -O2 -pipe -I. -I/usr/obj/lib32/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -Qunused-arguments -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_keys.c cc -o make_hash -O2 -pipe -I. -I/usr/obj/lib32/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -Qunused-arguments -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -DMAIN_PROGRAM /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/comp_hash.c cc: unrecognized option '-Qunused-arguments' cc: unrecognized option '-Qunused-arguments' cc1: error: unrecognized command line option "-Wno-empty-body" cc1: error: unrecognized command line option "-Wno-empty-body" cc1: error: unrecognized command line option "-Wno-string-plus-int" cc1: error: unrecognized command line option "-Wno-tautological-compare" cc1: error: unrecognized command line option "-Wno-parentheses-equality" cc1: error: unrecognized command line option "-Wno-string-plus-int" cc1: error: unrecognized command line option "-Wno-tautological-compare" cc1: error: unrecognized command line option "-Wno-parentheses-equality" *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error The only statement in my /etc/src.conf is `WITH_CLANG_IS_CC=yes'. Should I use additional configuration options to successfully build the system with CLang? Thanks, Serguey. http://wiki.freebsd.org/BuildingFreeBSDWithClang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: smtpd +spamd
On Mon, 04 Jun 2012 08:12:51 +0200, Tomasz Marszal wrote: Hi all, I wonder if there is someone who managed to install Opensmtpd + Spamd + Pf + Imap + SquirrelMail. I have already installed Opensmtpd as demon sending emails because i dont have domain yet i will buy it in two days and i will try to install it and write about it ( howto ) on my page but earlier i need to know if there is someone who already do that and can give me some support. Is it possible to do such a combination under FreeBSD 8.3 with newest ports collection. OpenSMTPD port is dated 22.05.2012. Best Regards Tomasz Marszal I didn't do this precise combination, but the setup seems quite standard. I advise you to just go ahead and ask more specific questions on a mailinglist when you encounter a concrete problem. One tip: read about open-relay mailservers and avoid that situation on yours. ;-) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem with sub-path (or sub-url) in smbfs.
On Tue, 29 May 2012 23:00:31 +0200, Manuel Trujillo (TooManySecrets) wrote: On Fri, May 25, 2012 at 12:38 PM, Manuel Trujillo (TooManySecrets) wrote: I have also an /etc/nsmb.conf configured. All runs fine... except because I only can mount up to "recursos" (from the line teide/recursos/usuarios/myuser), and NOT the share "myuser" (the last part of the PATH). Anybody could tell me, please, where is the better site/list to make this question? Thank you very much. Maybe freebsd-fs. Do you have error messages? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
On Fri, 01 Jun 2012 20:57:52 +0200, Thomas David Rivers wrote: We used to have FreeBSD exclusively on desktops... Now, we have migrated to other desktops (mac) with FreeBSD running the build and file server... Why? Because - the mac updates itself! No pain, no installation, no keeping-up with mailing lists/announcements, just and its done. Mac OS has a nice X11 server, the Mac UI is good enough, you don't have to install/update anything, the "app store" is perfect for downloading/installing whatever a desktop user might need. It was just too alluring... So, FreeBSD runs our NFS file server, and we log into a larger FreeBSD machine to do builds, etc... but, the desktop has moved. One developer here uses Linux Debian for about the same reason, it's trivial to update (via the network) to new versions, etc... Our web site used to be FreeBSD-based, but it was just too cost-effective to get a virtual Linux box on the backbone and move everything to that. Our requirements aren't too big, so that works beautifully. There _are_ people doing virtual FreeBSD boxes in a similar fashion, but they were quote a lot more for the annual fee.. so, Linux it was... I suppose, in some sense, you could argue that MacOS is FreeBSD... - Dave Rivers - Have you already tried pc-bsd? http://www.pcbsd.org/ FreeBSD with easy install and auto-update. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su problem
On Sat, 09 Jun 2012 09:55:28 +0200, Sami Halabi wrote: Hi, I Just finished upgrade from FBSD-8.1-R fresh system to FBSD-8.3-p2. once done, i created regular accounts, in wheel group. first all was okay, but suddenly i found my self blocked out, because i can't ssh as root, and i can't su either, when i su i get this: %su - Password: and it stuck in that state whitout givving me root shell #. any ideas how to solve this problem? the system is in the servers farm and i need to drive 3 hours each direction, so if there is remote solution i would appreciate it. %more /etc/group # $FreeBSD: src/etc/group,v 1.35.10.2.2.1 2012/03/03 06:15:13 kensmith Exp $ # wheel:*:0:root,sody . . . sody:*:1001: Thanks in advance, It does not solve your problem now, but if it is a couple of hours away arrange some remote serial console access. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su problem
On Sat, 09 Jun 2012 18:42:27 +0200, Eugene Grosbein wrote: 09.06.2012 19:47, Sami Halabi пишет: %su - Password: load: 0.00 cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k Perpaps, your system had no keyboard attached at boot time; or for some other reason it booted with /dev/console being serial console instead of vidconsole. su locks trying to access serial console that is /dev/ttyd0 by default and has Carrier Detect flag enabled. Hence, it waits for CD on the first serial port (miserably and hopelessly). You can check if it's true with "sysctl kern.console" command. You could ask someone to boot the system with keyboard attached - no need to type anything, though. The system should detect it and assingn /dev/ttyv0 as /dev/console instead of /dev/ttyd0. And "su" won't lock. Eugene Grosbein Can you see what su is doing with procstat -kk ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: su problem
On Mon, 11 Jun 2012 15:53:34 +0200, Sami Halabi wrote: Hi, I opened 2 terminals with user sody. in first i hit "su -", and supplied password, it was stcuked. in the other I did: %ps xau | grep su sody 39830 0.0 0.0 9124 1500 0 S+4:51PM 0:00.00 grep su root 39812 0.0 0.0 21732 2088 1 I 4:49PM 0:00.00 su - root 39813 0.0 0.0 21732 2108 1 I+4:49PM 0:00.00 su - %procstat -kk 39812 PIDTID COMM TDNAME KSTACK %procstat -kk 39813 PIDTID COMM TDNAME KSTACK % Mmmm, I'm out of options than. Maybe somebody else has a good idea. Ronald. Sami On Mon, Jun 11, 2012 at 11:14 AM, Ronald Klop wrote: On Sat, 09 Jun 2012 18:42:27 +0200, Eugene Grosbein wrote: 09.06.2012 19:47, Sami Halabi пишет: %su - Password: load: 0.00 cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k Perpaps, your system had no keyboard attached at boot time; or for some other reason it booted with /dev/console being serial console instead of vidconsole. su locks trying to access serial console that is /dev/ttyd0 by default and has Carrier Detect flag enabled. Hence, it waits for CD on the first serial port (miserably and hopelessly). You can check if it's true with "sysctl kern.console" command. You could ask someone to boot the system with keyboard attached - no need to type anything, though. The system should detect it and assingn /dev/ttyv0 as /dev/console instead of /dev/ttyd0. And "su" won't lock. Eugene Grosbein Can you see what su is doing with procstat -kk ? __**_ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable<http://lists.freebsd.org/mailman/listinfo/freebsd-stable> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@**freebsd.org " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: devd problem with 9-stable
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman
wrote:
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the "action" command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are helpful.
If you do does devd match the right devd.conf sections and start the
action?
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: devd problem with 9-stable
On Fri, 15 Jun 2012 08:01:21 +0200, Kevin Oberman
wrote:
On Thu, Jun 14, 2012 at 3:11 AM, Ronald Klop
wrote:
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman
wrote:
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the "action" command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are helpful.
If you do does devd match the right devd.conf sections and start the
action?
With debug i get:
Processing event '!system=USB subsystem=DEVICE type=ATTACH
ugen=ugen1.3 cdev=ugen1.3 vendor=0x0529 product=0x0600 devclass=0xff
devsubclass=0x00 sernum="" release=0x0100 mode=host port=1
parent=ugen1.2'
[long list of "Testing" entries, none of which 'vendor' matched]
Executing 'logger Unknown USB device: vendor 0x0529 product 0x0600 bus
uhub3'
So it looks like devd is not matching the vendor. But my devd.conf
file contains that vendor. I don't know exactly why it is not being
tested against. Nothing in the debug output gives me a clue and I
tried grepping for one of the tested vendor IDs in /etc/devd.conf and
/etc/devd/*.conf. Not found.
I am at a loss.
Just a guess, but "ugen[0-9]+" does not match the dot in ugen1.3. Can you
try "ugen[0-9]+.[0-9]+"?
Or just remove the device-name? Shouldn't the vendor and product be enough
identification?
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: devd problem with 9-stable
On Fri, 15 Jun 2012 08:01:21 +0200, Kevin Oberman
wrote:
On Thu, Jun 14, 2012 at 3:11 AM, Ronald Klop
wrote:
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman
wrote:
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the "action" command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are helpful.
If you do does devd match the right devd.conf sections and start the
action?
With debug i get:
Processing event '!system=USB subsystem=DEVICE type=ATTACH
ugen=ugen1.3 cdev=ugen1.3 vendor=0x0529 product=0x0600 devclass=0xff
devsubclass=0x00 sernum="" release=0x0100 mode=host port=1
parent=ugen1.2'
[long list of "Testing" entries, none of which 'vendor' matched]
Executing 'logger Unknown USB device: vendor 0x0529 product 0x0600 bus
uhub3'
So it looks like devd is not matching the vendor. But my devd.conf
file contains that vendor. I don't know exactly why it is not being
tested against. Nothing in the debug output gives me a clue and I
tried grepping for one of the tested vendor IDs in /etc/devd.conf and
/etc/devd/*.conf. Not found.
I am at a loss.
http://www.freebsd.org/releases/9.0R/errata.html
See point 3 under Open Issues.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: devd problem with 9-stable
On Fri, 15 Jun 2012 15:50:49 +0200, Warren Block
wrote:
On Fri, 15 Jun 2012, Ronald Klop wrote:
On Fri, 15 Jun 2012 08:01:21 +0200, Kevin Oberman
wrote:
On Thu, Jun 14, 2012 at 3:11 AM, Ronald Klop
wrote:
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman
wrote:
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the "action" command, it works fine, but it
fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are
helpful.
If you do does devd match the right devd.conf sections and start the
action?
With debug i get:
Processing event '!system=USB subsystem=DEVICE type=ATTACH
ugen=ugen1.3 cdev=ugen1.3 vendor=0x0529 product=0x0600 devclass=0xff
devsubclass=0x00 sernum="" release=0x0100 mode=host port=1
parent=ugen1.2'
[long list of "Testing" entries, none of which 'vendor' matched]
Executing 'logger Unknown USB device: vendor 0x0529 product 0x0600 bus
uhub3'
So it looks like devd is not matching the vendor. But my devd.conf
file contains that vendor. I don't know exactly why it is not being
tested against. Nothing in the debug output gives me a clue and I
tried grepping for one of the tested vendor IDs in /etc/devd.conf and
/etc/devd/*.conf. Not found.
I am at a loss.
http://www.freebsd.org/releases/9.0R/errata.html
See point 3 under Open Issues.
Even with those changes, devd is not triggering on my scanner attach:
match "subsystem" "DEVICE";
match "type" "ATTACH";
match "cdev" "ugen[0-9]+.[0-9]+";
match "vendor" "0x04b8";
match "product" "0x010a";
action "echo HERE! $cdev > /tmp/zoot";
# devd -d -D -f /etc/devd/wb.conf
Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen0.6
cdev=ugen0.6 vendor=0x04b8 product=0x010a devclass=0xff devsubclass=0xff
sernum="" release=0x0103 mode=host port=4 parent=ugen0.4'
Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen0.6
setting cdev=ugen0.6
setting vendor=0x04b8
setting product=0x010a
setting devclass=0xff
setting devsubclass=0xff
setting sernum=
setting release=0x0103
setting mode=host
setting port=4
setting parent=ugen0.4
Processing notify event
Testing system=USB against ^DEVFS
Testing system=USB against ^DEVFS
Popping table
I tried the same attaching my webcam on pcbsd in vmware.
[root@pcbsd-1684 /etc/devd]# cat /tmp/bla.conf
notify 100 {
match "subsystem" "DEVICE";
match "type" "ATTACH";
match "cdev" "ugen[0-9]+.[0-9]+";
match "vendor" "0x2232";
match "product" "0x1008";
action "echo HERE! $cdev >> /tmp/bla.log";
};
# devd -d -D -f /tmp/bla.conf
...
Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen1.2
cdev=ugen1.2 vendor=0x2232 product=0x1008 devclass=0xef devsubclass=0x02
sernum="" release=0x0019 mode=host port=1 parent=ugen1.1'
Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen1.2
setting cdev=ugen1.2
setting vendor=0x2232
setting product=0x1008
setting devclass=0xef
setting devsubclass=0x02
setting sernum=
setting release=0x0019
setting mode=host
setting port=1
setting parent=ugen1.1
Processing notify event
Testing subsystem=DEVICE against ^DEVICE
Testing type=ATTACH against ^ATTACH
Testing cdev=ugen1.2 against ^ugen[0-9]+.[0-9]+
Testing vendor=0x2232 against ^0x2232
Testing product=0x1008 against ^0x1008
Executing 'echo HERE! ugen1.2 >> /tmp/bla.log'
Popping table
[root@pcbsd-1684 /etc/devd]# cat /tmp/bla.log
HERE! ugen1.2
Do you see a significant difference with your setup?
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: devd problem with 9-stable
On Fri, 15 Jun 2012 18:40:45 +0200, Kevin Oberman
wrote:
On Fri, Jun 15, 2012 at 7:53 AM, Ronald Klop
wrote:
On Fri, 15 Jun 2012 15:50:49 +0200, Warren Block
wrote:
On Fri, 15 Jun 2012, Ronald Klop wrote:
On Fri, 15 Jun 2012 08:01:21 +0200, Kevin Oberman
wrote:
On Thu, Jun 14, 2012 at 3:11 AM, Ronald Klop
wrote:
On Thu, 14 Jun 2012 02:41:58 +0200, Kevin Oberman
wrote:
Since updating my systems to 9-Stable, I am not getting my
smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/local/sbin/openct-control attach usb:529/600 usb
/dev/$dev$
};
detach 50 {
device-name "ugen[0-9]+";
match "vendor" "0x0529";
match "product" "0x0600";
action "/usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p
[a-z0-9]+ $
};
If I manually enter the "action" command, it works fine, but it
fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
Did you run devd with debug messages on? Options -D and -d are
helpful.
If you do does devd match the right devd.conf sections and start the
action?
With debug i get:
Processing event '!system=USB subsystem=DEVICE type=ATTACH
ugen=ugen1.3 cdev=ugen1.3 vendor=0x0529 product=0x0600 devclass=0xff
devsubclass=0x00 sernum="" release=0x0100 mode=host port=1
parent=ugen1.2'
[long list of "Testing" entries, none of which 'vendor' matched]
Executing 'logger Unknown USB device: vendor 0x0529 product 0x0600
bus
uhub3'
So it looks like devd is not matching the vendor. But my devd.conf
file contains that vendor. I don't know exactly why it is not being
tested against. Nothing in the debug output gives me a clue and I
tried grepping for one of the tested vendor IDs in /etc/devd.conf and
/etc/devd/*.conf. Not found.
I am at a loss.
http://www.freebsd.org/releases/9.0R/errata.html
See point 3 under Open Issues.
Even with those changes, devd is not triggering on my scanner attach:
match "subsystem" "DEVICE";
match "type" "ATTACH";
match "cdev" "ugen[0-9]+.[0-9]+";
match "vendor" "0x04b8";
match "product" "0x010a";
action "echo HERE! $cdev > /tmp/zoot";
# devd -d -D -f /etc/devd/wb.conf
Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen0.6
cdev=ugen0.6 vendor=0x04b8 product=0x010a devclass=0xff
devsubclass=0xff
sernum="" release=0x0103 mode=host port=4 parent=ugen0.4'
Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen0.6
setting cdev=ugen0.6
setting vendor=0x04b8
setting product=0x010a
setting devclass=0xff
setting devsubclass=0xff
setting sernum=
setting release=0x0103
setting mode=host
setting port=4
setting parent=ugen0.4
Processing notify event
Testing system=USB against ^DEVFS
Testing system=USB against ^DEVFS
Popping table
I tried the same attaching my webcam on pcbsd in vmware.
[root@pcbsd-1684 /etc/devd]# cat /tmp/bla.conf
notify 100 {
match "subsystem" "DEVICE";
match "type" "ATTACH";
match "cdev" "ugen[0-9]+.[0-9]+";
match "vendor" "0x2232";
match "product" "0x1008";
action "echo HERE! $cdev >> /tmp/bla.log";
};
# devd -d -D -f /tmp/bla.conf
...
Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen1.2
cdev=ugen1.2 vendor=0x2232 product=0x1008 devclass=0xef devsubclass=0x02
sernum="" release=0x0019 mode=host port=1 parent=ugen1.1'
Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen1.2
setting cdev=ugen1.2
setting vendor=0x2232
setting product=0x1008
setting devclass=0xef
setting devsubclass=0x02
setting sernum=
setting release=0x0019
setting mode=host
setting port=1
setting parent=ugen1.1
Processing notify event
Testing subsystem=DEVICE against ^DEVICE
Testing type=ATTACH against ^ATTACH
Testing cdev=ugen1.2 against ^ugen[0-9]+.[0-9]+
Testing vendor=0x2232 against ^0x2232
Testing product=0x1008 against ^0x1008
Executing 'echo HERE! ugen1.2 >> /tmp/bla.log'
Popping table
[root@pcbsd-1684 /etc/devd]# cat /tmp/bla.log
HERE! ugen1.2
Do you see a significant difference with your setup?
Switched to 'notify' with:
notify 50 {
match "system" "USB"
Re: Seeking 6.4 make source for ports
On Wed, 20 Jun 2012 06:57:59 +0200, Michael R. Wayne wrote: Google is littered with messages from people who have 6.3 systems and can no longer upgrade ports. It appears that a recent change requires the version of make from 6.4. While it would be ideal if freebsd.org would build a 6.4 make on a 6.3 system and pseudo-officially support it, a reasonable alternative would be a simple way to download just the files required to build the 6.4 version of make on 6.3. Any possibility to get this tossed on a site someplace? Do you have a problem yourself or did you just found some messages on google? I presume you are running 6.3 yourself. Why don't you upgrade the OS to 6.4 or 7+, but you do upgrade the ports on an unsupported OS? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mountd suddenly stopped working
On Sat, 30 Jun 2012 15:53:53 +0200, Marcin Wisnicki wrote: I have just rebooted an old system after 100 days of uptime and this came up: Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line /tftpboot -ro -mapall Both /etc/exports and /tftpboot are many years old and didn't cause any problems until today. Do you mean these were not edited/changed since the previous reboot? I have tried fsck and rebooting but it didn't help. uname -a FreeBSD ghost.pnet.one.pl 8.2-STABLE FreeBSD 8.2-STABLE #6: Sun Nov 13 05:32:38 CET 2011 Than probably somebody changed something else. Can you provide the content of your exports file? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommendation for Hyervisor to host FreeBSD
On Thu, 05 Jul 2012 13:43:06 +0200, Pete French wrote: So, my work surprise for a Thursday morning is an urgent requirement to see if we can run a set of FreeBSD machines under virtualised servers. I have not done this before personally, but I notice from post here that it doesnt seem uncommon, and I see Xen related commits flowing past, so I am guessing it is doable. So, for running 8 or 9 STABLE can anyone recommend which hypervisor works best, and is 8 or 9 better as the OS to run ? Am doing a bit of research myself, but nothing beats persoanl experience in these matters! cheers, -pete. Hi, It helps if you tell people what you are looking for. - realtime moving of guests between host-servers? - do you really need separate OS'es or would jails serve your purposes? - Are you only going to run FreeBSD on FreeBSD or also Linux or Windows on FreeBSD? - ... etc. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Odd ttyvN TERM settings
On Sun, 08 Jul 2012 16:00:16 +0200, George Mitchell wrote: Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25. On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25 for ttyv1-ttyv8 (even though they all appear to act like xterms). Not surprisingly, this leads to less than desirable results when trying to run vi (or other such programs) on ttyv1 through ttyv8, unless you remember to setenv TERM xterm. Why did we change from cons25 to xterm? How can we get all the ttyvNs to get the correct TERM setting? -- George Mitchell What is in your /etc/ttys? This is the ttys file on 9-STABLE on amd64: http://svnweb.freebsd.org/base/stable/9/etc/etc.amd64/ttys?revision=225736&view=markup&pathrev=238244 Regards, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Resizing GPT partitions
On Tue, 08 Jun 2010 18:58:50 +0200, Stephane Dupille wrote: Hello, I installed a FreeBSD 8.0-RELEASE into a virtual machine (with virtual box), using a GTP partitioning scheme, and zfs. The virtual disk disk is 10 Go. I dumped this disk image to a real machine, which has a 160 Go disk. The system works fine, but I can only use 10 Go of disk space. How can I gain more space ? How can I enlarge the last partition of the disk to use the whole disk ? I tried to create a new partition on the disk, and planned to add it in the zfs pool, but that didn't work : # gpart add -t freebsd-zfs -l disk0f ad0 gpart: autofill: No space left on device That's odd, because it seems that gpart is aware of the new geometry. What's the problem ? Some info : # gpart list Geom name: ad0 fwheads: 16 fwsectors: 63 last: 20971486 ^^ first: 34 ^ entries: 128 scheme: GPT Providers: 1. Name: ad0p1 Mediasize: 65536 (64K) Sectorsize: 512 Mode: r0w0e0 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ad0p2 Mediasize: 4294967296 (4.0G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: swap0 length: 4294967296 offset: 82944 type: freebsd-swap index: 2 end: 8388769 start: 162 3. Name: ad0p3 Mediasize: 6442351104 (6.0G) Sectorsize: 512 Mode: r1w1e2 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: disk0 length: 6442351104 offset: 4295050240 type: freebsd-zfs index: 3 end: 20971486 ^ start: 8388770 Consumers: 1. Name: ad0 Mediasize: 160041885696 (149G) Sectorsize: 512 # fdisk ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 20971487, size 291610321 (142387 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 80/ sector 63 The data for partition 2 is: sysid 0 (),(unused) start 162, size 8388608 (4096 Meg), flag 0 beg: cyl 0/ head 2/ sector 37; end: cyl 522/ head 45/ sector 5 The data for partition 3 is: sysid 0 (),(unused) start 8388770, size 12582717 (6143 Meg), flag 0 beg: cyl 522/ head 45/ sector 6; end: cyl 1023/ head 105/ sector 47 The data for partition 4 is: As far as I see in you 'gpart list' gpart doesn't see the new geometry. See the ^^ lines above. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SIGEPIPE after update to 8.1-RC2
Try rebuilding bash or sh or whatever you are using as shell. I'm not sure though. Ronald. On Sat, 17 Jul 2010 17:24:55 +0200, Alex Kozlov wrote: Hi, stable After updating my buildbox from 26 April 8-STABLE to 8.1-RC2 I constantly getting SIGEPIPE portsnap: Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 27 patches.1020... done. Applying patches... done. Fetching 3 new ports or files... done. sort: write failed: standard output: Broken pipe sort: write error Removing old files and directories... done. sudo make -C /usr/ports/converters/ascii2binary: ===> Patching for ascii2binary-2.13_2 ===> Applying FreeBSD patches for ascii2binary-2.13_2 ===> ascii2binary-2.13_2 depends on shared library: intlgrep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe - found ===> Configuring for ascii2binary-2.13_2 Does anyone know something about this issue? -- Adios ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kernel MCA messages
On Mon, 23 Aug 2010 14:20:35 +0200, John Baldwin wrote: On Monday, August 23, 2010 2:44:38 am Andriy Gapon wrote: on 23/08/2010 05:05 Dan Langille said the following: > On 8/22/2010 9:18 PM, Dan Langille wrote: >> What does this mean? >> >> kernel: MCA: Bank 4, Status 0x940c4001fe080813 >> kernel: MCA: Global Cap 0x0105, Status 0x >> kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 >> kernel: MCA: CPU 0 COR BUSLG Source RD Memory >> kernel: MCA: Address 0x7ff6b0 >> >> FreeBSD 7.3-STABLE #1: Sun Aug 22 23:16:43 > > And another one: > > kernel: MCA: Bank 4, Status 0x9459c0014a080813 > kernel: MCA: Global Cap 0x0105, Status 0x > kernel: MCA: Vendor "AuthenticAMD", ID 0xf5a, APIC ID 0 > kernel: MCA: CPU 0 COR BUSLG Source RD Memory > kernel: MCA: Address 0x7ff670 I believe that you get correctable RAM ECC errors, but not entirely sure. There is mcelog utility that decodes such messages into human-friendly descriptions. The utility is available on Linux-based systems. John Baldwin has a port of it to FreeBSD, but it seems to be WIP and is private so far. Wait and watch John posting decoded text in this thread :-) It is not private, it is in //depot/projects/mcelog/... in p4. It is not a complete port yet though (doesn't support the daemon and client modes for example). Details for these errors: HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 0 4 northbridge ADDR 7ff6b0 Northbridge RAM Chipkill ECC error Chipkill ECC syndrome = fe18 bit32 = err cpu0 bit46 = corrected ecc error bus error 'local node origin, request didn't time out generic read mem transaction memory access, level generic' STATUS 940c4001fe080813 MCGSTATUS 0 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 5 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 0 4 northbridge ADDR 7ff670 Northbridge RAM Chipkill ECC error Chipkill ECC syndrome = 4ab3 bit32 = err cpu0 bit46 = corrected ecc error bus error 'local node origin, request didn't time out generic read mem transaction memory access, level generic' STATUS 9459c0014a080813 MCGSTATUS 0 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 5 As Andriy guessed, I believe both of these are corrected ECC errors. You can likely ignore them as a low rate of corrected ECC errors is not unexpected. Hi, A little off topic, but what is 'a low rate of corrected ECC errors'? At work one machine has them like ones per day, but runs ok. Is ones per day much? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
cname replace in mail address? [off-topic] (Re: Attn Ronald Klop)
offtopic, but why do some mailers replace a CNAME in a mail-address? r...@sheeva2:/var/vmail# host klop.yi.org klop.yi.org CNAME thuis.klop.ws thuis.klop.ws A 212.123.145.58 It is not the first time that I'm bitten by this, but I never understood it. Ronald. On Tue, 24 Aug 2010 22:05:46 +0200, Andriy Gapon wrote: Ronald, your email address bounces, that's inconvenient. Original Message Subject: Returned mail: Service unavailable Date: Tue, 24 Aug 2010 23:03:33 +0300 (EEST) From: Mail Delivery Subsystem To: The original message was received at Tue, 24 Aug 2010 23:03:27 +0300 (EEST) from porto-e.starpoint.kiev.ua [212.40.38.100] - The following addresses had permanent fatal errors - - Transcript of session follows - ... while talking to thuis.klop.ws.: RCPT To: <<< 554 5.7.1 : Relay access denied 554 ... Service unavailable ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cname replace in mail address? [off-topic] (Re: Attn Ronald Klop)
Mandatory? I'm googling, but can't find a document that declares it mandatory and only sendmail seems to do it. I think it is lame to use DNS info to rewrite e-mail addresses, but the person who made it 'mandatory' will have good reasons for it. Does somebody have a pointer to the specs about this? Ronald. On Fri, 27 Aug 2010 10:21:27 +0200, Mark Andrews wrote: In message , "Ronald Klop" writ es: offtopic, but why do some mailers replace a CNAME in a mail-address? Because it used to be manditory to do so. If you don't want it to be done use a MX record. klop.yi.org MX 0 thuis.klop.ws If you need klop.yi.org to have a address record then give it one. klop.yi.org A 212.123.145.58 Mark r...@sheeva2:/var/vmail# host klop.yi.org klop.yi.org CNAME thuis.klop.ws thuis.klop.ws A 212.123.145.58 It is not the first time that I'm bitten by this, but I never understood = =20 it. Ronald. On Tue, 24 Aug 2010 22:05:46 +0200, Andriy Gapon wrote: > > Ronald, > > your email address bounces, that's inconvenient. > > > Original Message > Subject: Returned mail: Service unavailable > Date: Tue, 24 Aug 2010 23:03:33 +0300 (EEST) > From: Mail Delivery Subsystem > To: > > The original message was received at Tue, 24 Aug 2010 23:03:27 +0300 =20 > (EEST) > from porto-e.starpoint.kiev.ua [212.40.38.100] > >- The following addresses had permanent fatal errors - > > >- Transcript of session follows - > ... while talking to thuis.klop.ws.: >>>> RCPT To: > <<< 554 5.7.1 : Relay access denied > 554 ... Service unavailable ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MySQL performance concern
On Sat, 02 Oct 2010 09:06:52 +0200, Rumen Telbizov wrote: Hello everyone, I am experimenting with MySQL running on FreeBSD and comparing with another (older) setup running on a Linux box. My results show that performance on Linux is significantly better than FreeBSD although the hardware is weaker. I'd appreciate your comments and ideas. Here's the setup: 1) FreeBSD 8.1-STABLE amd64 (Tue Sep 14 15:29:22 PDT 2010) running on a SuperMicro machine with 2 x Dual Core Xeon E5502 1.87Ghz ; 4 x SAS 15K in RAID10 setup under ZFS (two mirrored pairs) and 2 x SSD X25-E partitioned for: 8G for ZIL and the rest for L2ARC; 16G ram with 8 of them given to mysql and tons of free. 2) Linux Gentoo with 3 SATA disks in hardware RAID5 with similar cpu/motherboard and same memory size. The sole application that runs is a python script which inserts a batch of lines at a time. Only myisam is used as a format. Here's the problem: On the Linux box it manages to push around *5800*inserts/second while on the FreeBSD box it's only *4000/*second. MySQL version is 5.1.51 During this load the disk subsystem on FreeBSD is pretty much idle (both the SSDs and the SAS disks). CPU utilization contributed to mysqld is only around 30%. So I am clearly heavily under-utilizing the hardware. Linuxthreads support for 64bit architectures is not available so I couldn't try that but aside from that I tried recompiling mysql with all the different Makefile options available without any effect. Changing the recordsize in zfs to 8K doesn't make any difference. Tried percona binary without any luck. Let me know what additional information would be useful and I'll provide it here. Thank you in advance for your comments and suggestions. Cheers, Rumen Telbizov Your app is singlethreaded I presume, so the multi-cores are not relevant in this story. Do you have the same indexes on the tables on both servers? Do they both have the same way to connect with mysql? Unix sockets or localhost? Do they both run mysql 5.1.51, because you mention the Linux one is older? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem with security log
On Tue, 12 Oct 2010 22:50:28 +0200, Marcin wrote: Hi folks, For some time in the file / var / log / security appear illegible entries: kernel: ipfw: 200 Deny UDiPp f1w9:2 .168.10.5:5230503 D22e4n.y0 .U0D.P25 1:15923.5136 o8.u10t. 5va5 3r5e03 224.0.0.251:5353 in via re0 How to get rid of it? Please help... Thanks, Nickson Looks like 2 messages scrambled. I think multiple threads are logging/writing at the same time. Although that might be a bug in itself it can explain what you see. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: VirtualBox OpenSolaris guest [becomes: linux-f10-expat]
On Mon, 18 Oct 2010 14:32:04 +0200, Alex Goncharov
wrote:
,--- You/Harald (Mon, 18 Oct 2010 14:02:27 +0200) *
| What else could I possibly do?
| - portmaster www/opera-linuxplugins # installing linux_base-f10-10_3,
| then stopping as follows:
| ===> Installing for linux-f10-expat-2.0.1
| ===> Generating temporary packing list
| brandelf: error opening file usr/bin/xmlwf: No such file or directory
| *** Error code 1
| Stop in /usr/ports/textproc/linux-f10-expat.
I am not using portmaster; try do it simply through make. I just did
it now:
--
cat /compat/linux/etc/fedora-release
Fedora release 10 (Cambridge)
make -C textproc/linux-f10-expat deinstall clean configure build install
NOCLEANDEPENDS=yes
===> Deinstalling for textproc/linux-f10-expat
===> Deinstalling linux-f10-expat-2.0.1
===> Cleaning for linux-f10-expat-2.0.1
===> Vulnerability check disabled, database not found
===> License check disabled, port has not defined LICENSE
===> Extracting for linux-f10-expat-2.0.1
=> MD5 Checksum OK for rpm/i386/fedora/10/expat-2.0.1-5.i386.rpm.
=> SHA256 Checksum OK for rpm/i386/fedora/10/expat-2.0.1-5.i386.rpm.
===> linux-f10-expat-2.0.1 depends on file: /usr/local/bin/rpm2cpio -
found
===> Patching for linux-f10-expat-2.0.1
===> Configuring for linux-f10-expat-2.0.1
===> Installing for linux-f10-expat-2.0.1
===> linux-f10-expat-2.0.1 depends on file:
/compat/linux/etc/fedora-release - found
===> Generating temporary packing list
===> Checking if textproc/linux-f10-expat already installed
cd /usr/ports/.x/amd64/usr/ports/textproc/linux-f10-expat/work &&
/usr/bin/find * -type d -exec /bin/mkdir -p "/compat/linux/{}" \;
cd /usr/ports/.x/amd64/usr/ports/textproc/linux-f10-expat/work &&
/usr/bin/find * ! -type d | /usr/bin/cpio -pm -R root:wheel /compat/linux
367 blocks
===> Running linux ldconfig
/compat/linux/sbin/ldconfig -r /compat/linux
===> Registering installation for linux-f10-expat-2.0.1
ls -l /compat/linux/usr/bin/xmlwf
-rwxr-xr-x 1 root wheel 20844 Oct 18 08:27
/compat/linux/usr/bin/xmlwf*
file /compat/linux/usr/bin/xmlwf
/compat/linux/usr/bin/xmlwf: ELF 32-bit LSB executable, Intel 80386,
version 1 (GNU/Linux), dynamically linked (uses shared libs), for
GNU/Linux 2.6.9, stripped
--
-- Alex -- alex-goncha...@comcast.net --
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Alex,
What does pkg_info -W /compat/linux/usr/bin/xmlwf say? Maybe
linux-f10-expat misses a dependency which you have installed already.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.1-STABLE: zfs and sendfile: problem still exists
On Sun, 31 Oct 2010 10:02:44 +0100, Alexander Zagrebin wrote: >> I apologize for my haste, it should have been VM_ALLOC_WIRED. > > Ok, applied and tested under some load(~1200 active connections, outgoing > ~80MB/s). Patch work as expected and i has noted no side effects. Just one > question - should grow Active memory counter, if some pages is "hot"(during > multiple sendfile on one file)? Pages used by sendfile are marked as Inactive for faster reclamation on demand. I have a question. When we transfer a file via sendfile, then current code allocates a memory, marked inactive. For example, if the file has size 100 MB, then 100 MB of memory will be allocated. If we have to transfer this file again later, then this memory will used as cache, and no disk io will be required. The memory will be freed if file will be deleted or operating system will need an additional memory. I have correctly understood? If it so, the i continue... Such behaviour is good if we have files with relatively small size. Suppose we have to transfer file with large size (for example, greater than amount of physical memory). While transfering, the inactive memory will grow, pressing the ARC. When size of the ARC will fall to its minimum (vfs.zfs.arc_min), then inactive memory will be reused. So, when transfer is complete, we have: 1. No free memory 2. Size of the ARC has minimal size (it is bad) 3. Inactive memory contains the _tail_ of the file only (it is bad too) Now if we have to transfer this file again, then 1. there is no (or few) file's data in ARC (ARC too small) 2. The inactive memory doesn't contain a head part of the file So the file's data will read from a disk again and again... Also i've noticed that inactive memory frees relatively slowly, so if there is a frequent access to large files, then system will run at very unoptimal conditions. It's imho... Can you comment this? Add more RAM? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: vm.swap_reserved toooooo large?
On Sat, 18 Dec 2010 12:52:10 +0100, George Mamalakis wrote: Oliver, I am sending you this email outside the list, because I think that That didn't work out as you intended. :-) enough emails have been sent regarding my message. Now to your statements: On 18/12/2010 11:47 πμ, Oliver Fromme wrote: George Mamalakis wrote: > Oliver, thanx for your comments. I know it is difficult to choose which > process to kill and how to be "fair" during such a killing procedure. > Nevertheless, I would assume that all non-root processes would have > higher priority to get killed, and that root's processes would get > killed last. The owner of the process is not taken into consideration, because the "run-away" process causing the memory shortage may as well be a root-owned process. In such a situation, if root processes were exempt from killing, the system would deadlock and require a hard reboot. Killing the root-owned process is the lesser of two evils. As I explained in one of my previous emails, I expected that root processes would have *lower priority* than non-root processes; I never implied that root processes shouldn't get killed, it would be irrational to say so. As I already explained, there is a process flag that root- owned processes can set for themselves, preventing the kernel from killing them in low-memory situations. See the description of the MADV_PROTECT flag in the madvise(2) manual page. For example, cron(8) and sshd(8) make use of this, so they will not be killed. This is a better way than simply excluding all root processes. > I understand your comments completely, but I was just so > surprised when I realized how easy it was for me to kill root processes > on my system. Only because you didn't configure resource limits. ;-) When you're the only user on a machine, such as a desktop box, this is usually not a big deal. But in all other cases it's strongly recommended to set resource limits, in particular for shell users and for server processes. Without any resource limits, a normal user can starve the system and take it down. This is an old and well-known problem for all UNIX systems (and most non-UNIX systems, too, I guess). You certainly didn't discover any new problem. If you're concerned, configure resource limits. Period. As I stated in my first message (if I recall correctly), all this happened because I didn't configure my rlimits (it's my laptop). Of course I am aware of resource limits, and I configure them on most of the servers I administer for the last 12 years (I've seen my vmstat showing 500+ processes in blocked-by-io state, and the system wouldn't hang..:)). I never implied to have discovered anything new, and especially something regarding resource limits. All my enthusiasm was caused firstly due to fbsd's memory allocation algorithm (I never knew the system would assume that it could allocate 500+GB of memory, and the replies on this issue where very enlightening for me), and secondly due to fbsd's algorithm on process killing when memory has been starved. Certainly, I was not surprised by the fact that my system was out of memory...exceeding my system's memory limits was my experiment in the first place! Anyway, thanx again for your answer and all your pointers (MADV_PROTECT, etc), and I think there is no need to get angry about my emails. As I initially stated, my questions where rhetorical, and no answers where needed. I trusted that there should be a good reason behind this behavior...Some of you answered on the list and I just replied with my opinion. Nothing more, nothing less. Have a nice day and kind regards, mamalos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks
On Thu, 30 Dec 2010 12:40:00 +0100, Damien Fleuriot wrote: Hello list, I currently have a ZFS zraid1 with 4x 1.5TB drives. The system is a zfs-only FreeBSD 8.1 with zfs version 14. I am concerned that in the event a drive fails, I won't be able to repair the disks in time before another actually fails. I wish to reinstall the OS on a dedicated drive (possibly SSD, doesn't matter, likely UFS) and dedicate the 1.5tb disks to storage only. I have ordered 5x new drives and would like to create a new zraid2 mirrored pool. Then I plan on moving data from pool1 to pool2, removing drives from pool1 and adding them to pool2. My questions are as follows: With a total of 9x 1.5TB drives, should I be using zraid3 instead of zraid2 ? I will not be able to add any more drives so unnecessary parity drives = less storage room. What are the steps for properly removing my drives from the zraid1 pool and inserting them in the zraid2 pool ? Regards, dfl Make sure you have spare drives so you can swap in a new one quickly and have off-line backups in case disaster strikes. Extra backups are always nice. Disks are not the only parts which can break and damage your data. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks
On Sun, 02 Jan 2011 15:31:49 +0100, Damien Fleuriot wrote: On 1/1/11 6:28 PM, Jean-Yves Avenard wrote: On 2 January 2011 02:11, Damien Fleuriot wrote: I remember getting rather average performance on v14 but Jean-Yves reported good performance boosts from upgrading to v15. that was v28 :) saw no major difference between v14 and v15. JY Oopsie :) Seeing I for one will have no backups, I think I won't be using v28 on this box, and stick with v15 instead. Are there any views regarding the "best" implementation for a system ? I currently have a ZFS only system but I'm planning on moving it to UFS, with ZFS used only for mass storage. I understand ZFS root is much trickier, and my main fear is that if I somehow break ZFS (by upgrading to v28 for example) I won't be able to boot anymore, thus no repair process... You can repair by booting from USB of CD in a lot of cases. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: tmpfs runs out of space on 8.2pre-release, zfs related?
On Sun, 02 Jan 2011 09:41:04 +0100, miyamoto moesasji wrote: miyamoto moesasji gmail.com> writes: In setting up tmpfs (so not tmpmfs) on a machine that is using zfs(v15, zfs v4) on 8.2prerelease I run out of space on the tmpfs when copying a file of ~4.6 GB file from the zfs-filesystem to the memory disk. This machine has 8GB of memory backed by swap on the harddisk, so I expected the file to copy to memory without problems. this is in fact worse than I first thought. After leaving the machine running overnight the tmpfs is reduced to a size of 4K, which shows that tmpfs is in fact completely unusable for me. See the output of df: --- h...@pulsarx4:~/ > df -hi /tmp FilesystemSizeUsed Avail Capacity iused ifree %iused Mounted on tmpfs 4.0K4.0K 0B 100% 18 0 100% /tmp --- Relevant zfs-stats info: --- System Memory Statistics: Physical Memory:8161.74M Kernel Memory: 4117.40M DATA: 99.29% 4088.07M TEXT: 0.71% 29.33M ARC Size: Current Size (arcsize): 63.58% 4370.60M Target Size (Adaptive, c): 100.00% 6874.44M Min Size (Hard Limit, c_min): 12.50% 859.31M Max Size (High Water, c_max): ~8:16874.44M --- I'm not sure what triggered this further reduction in size; but the above 4K size is probably important to show how dramatic this goes wrong. Is it possible that some program is filling a file (on your tmpfs) which is deleted? You will not see it with df or ls, but it still takes space on the fs, until the application closes the file. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ssh-keygen between SuSE and FreeBSD
On Thu, 14 Aug 2008 19:25:09 +0200, Gavin Spomer <[EMAIL PROTECTED]> wrote: [snip] I'm not quite sure right now why you're using rsa keys. I'm always using dsa keys (ssh-keygen -t dsa). It comes to my mind, that rsa keys are for ssh version 1, while dsa keys are for ssh version 2. But I could be wrong here ;) No man ssh handy right now, sorry. If that's true, then I believe I will start using the dsa ones! I think I chose rsa because the FreeBSD manual indicated I could use either and I could only find settings for enabling rsa in sshd_config on the remote servers, but I'll look again... This story about rsa and dsa is not true. Rsa wasn't free (patents or something else) until a few years ago. So everybody used dsa. But since quite some time it doesn't matter what you use. I don't know about advantages of one above the other. In daily use they are the same. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh-keygen between SuSE and FreeBSD
On Thu, 14 Aug 2008 19:31:12 +0200, Gavin Spomer <[EMAIL PROTECTED]> wrote: Lyndon Nerenberg <[EMAIL PROTECTED]> 08/14/08 9:47 AM >>> DOn't you have a local IT helpdesk? This is pretty basic stuff that they should have documentation for. Well, I admit I still have more things to learn, even though I've been the admin of "my" own Linux servers for 3 years and FreeBSD for... can't remember, but not quite as long, but I'm not gonna pester my colleagues for something like this, about my own servers! ;) My background is more in programming as I have a CS degree in software design. Still learning in that area too! We are all, always learning. (hopefully) Genuine thanks for the suggestion though. - Gavin Funny, you don't 'pester' your colleagues but do e-mail a couple of thousand people on this mailinglist. Communication is a weird thing. :-) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nVidia driver update today: renders X11 unusable
On Tue, 02 Sep 2008 16:28:20 +0200, O. Hartmann <[EMAIL PROTECTED]> wrote: Andriy Gapon wrote: Question to those having this problem - what kind of nVidia hardware do you have? Is that something that is based on G80 GPU or later (GeForce 8XXX or later)? I see that there is already version 2.1.12 of nv driver (in xorg repository) that is supposed to fix CPUToScreenColorExpandFill function for G80 cards. Well, the problems I have are related to a nv8600GTS based board, this is, as far as I know, a G8X-based graphics board. Nearly 3 months ago some weird behaviour started to be static on the same hardware, Xorg wasn't capable of resetting the terminal is was bound to and presented me funny blinking block graphics on the screen. The Xorg server could oly be revived remotelly by killing the Xorg or within a running session by killing the Xorg for logging off. This problem has gone with today's update, but now my box (nv8600GTS) and the one of a collegue is rendered unusable. My private box runs with a nv6800GT board and there Xorg freezes now very often and renders the box unusable, too. I'm very unpleased about the situation, because it is impossible to do reasonable work. How can I selectively 'downgrade' a port? Mmmm... # whereis portdowngrade portdowngrade: /usr/ports/ports-mgmt/portdowngrade Cheers, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB detach/attach hangs with 7.0-RELEASE and 7.1-PRERELEASE
On Mon, 29 Sep 2008 02:46:15 +0200, Bruce M Simpson <[EMAIL PROTECTED]> wrote: Hi, I've noticed some general instability with plugging in or removing USB devices with FreeBSD 7.x, even when the devices are not actively in use. I had this happen with umass and ucom devices 3 times today. The machine hangs solid, there are no obvious signs of a panic or trap to DDB. I can't provide backtraces unfortunately -- these hangs happen on both my laptop and desktop, and I usually have X running -- if I had more specific information, I'd open a PR. Again, there seems to be no reason why this should happen, the devices are off-the-shelf consumer items known to work with existing drivers, and have been repeatedly used in other OSes without these hangs happening; consider this an "anecdotal report". [For some reason my IBM laptop will often not allow me to break into DDB on a driver related panic, and will just immediately reboot -- I lack free time to track down exactly why this could be. My desktop has a USB keyboard and this appears not to be supported by DDB, I ordered a PS/2 keyboard which hasn't arrived, but that's another story.] thanks BMS On my computer I had to disable USB support in the BIOS because it 'conflicted' with USB support of FreeBSD. FreeBSD still detects USB and all connected devices. Maybe this helps on your computer also. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB detach/attach hangs with 7.0-RELEASE and 7.1-PRERELEASE
In that case I'm out of options. Maybe somebody else on the list can respond. Succes, Ronald. On Fri, 03 Oct 2008 16:51:35 +0200, Henrik Friedrichsen <[EMAIL PROTECTED]> wrote: USB support in the BIOS? What kind of support does the BIOS provide that you can disable? I'm only able to disable the USB device, but that'd turn it off completely :( Henrik. On Mon, Sep 29, 2008 at 10:05:02PM +0200, Ronald Klop wrote: On Mon, 29 Sep 2008 02:46:15 +0200, Bruce M Simpson <[EMAIL PROTECTED]> wrote: >Hi, > >I've noticed some general instability with plugging in or removing USB >devices with FreeBSD 7.x, even when the devices are not actively in use. > >I had this happen with umass and ucom devices 3 times today. The machine >hangs solid, there are no obvious signs of a panic or trap to DDB. I >can't provide backtraces unfortunately -- these hangs happen on both my >laptop and desktop, and I usually have X running -- if I had more >specific information, I'd open a PR. > >Again, there seems to be no reason why this should happen, the devices >are off-the-shelf consumer items known to work with existing drivers, >and have been repeatedly used in other OSes without these hangs >happening; consider this an "anecdotal report". > >[For some reason my IBM laptop will often not allow me to break into DDB >on a driver related panic, and will just immediately reboot -- I lack >free time to track down exactly why this could be. >My desktop has a USB keyboard and this appears not to be supported by >DDB, I ordered a PS/2 keyboard which hasn't arrived, but that's another >story.] > >thanks >BMS On my computer I had to disable USB support in the BIOS because it 'conflicted' with USB support of FreeBSD. FreeBSD still detects USB and all connected devices. Maybe this helps on your computer also. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Block device
On Tue, 04 Nov 2008 17:32:51 +0100, Scott Long <[EMAIL PROTECTED]> wrote: Patrick M. Hausen wrote: h, all, On Tue, Nov 04, 2008 at 03:32:01PM +0100, d_elbracht wrote: Hi list, can someone please explain, why stat -x /dev/da1 show the SCSI-Drive as a character-device ? http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-block.html Wow that's a confusing and misleading article. 1. disk access in the driver layer still happens on a block basis. It's true that to the application layer, the device has character dev semantics, meaning that arbitrary numbers of bytes can be accessed randomly without any restrictions. But deep down inside the kernel, it's still doing block-by-block access. 2. caching still happens at the filesystem level. Doing I/O directly to /dev/daX or adX or whatever will not be cached/buffered, but doing I/O to a file on any of these devices will. 3. Cache coherency between the block and character device representations was indeed an issue, but removing the block/cached representation was really a matter of policy over tools, and it's one reason why FreeBSD gets creamed in the silly-io-benchmarch department. 4. However, in the not-so-silly-io-benchmark department, I think FreeBSD does a whole lot better because you don't have the blind caching of the block device trying to out-guess what the filesystem is trying to do. Scott This explains some things to me as a simple user reading the linked article. I'm not a kernel programmer, but do understand computers and this article made me wonder if I missed something last years about disks and caches. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient starts after NETWORK
On Mon, 07 Dec 2009 10:03:39 +0100, wrote: Wrong order in /etc/rc.d scripts ~]>rcorder /etc/rc.d/* | grep -n -e dhclient -e ntp 66:/etc/rc.d/ntpdate 112:/etc/rc.d/ntpd 139:/etc/rc.d/dhclient Then ifconfig_rl0="DHCP"? ntpdate can`t sync time. It is right to add dhclient in REQUIRE section in /etc/rc.d/NETWORKING ? Does ifconfig_rl0="SYNCDHCP" help? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sheevaplug questions
On Sun, 27 Dec 2009 17:00:25 +0100, Zoran Kolic wrote: Howdy! I ordered sheevaplug box and read as much as I could, regarding controlling this little node from bsd box. Seems that cu works fine on linux, but module should be loaded to enable serial emulation from usb host port to mini usb port on sheevaplug. Does someone use this mini computer and how connects to serial console? Almost all of documetation mentions win and linux. I suppose would be pretty easy to go further with serial line available. Btw, there is freebsd port for this plug already. Would be fine to try it out. Best regards Zoran Hi, I have 2 of them and cu works fine. As root you can do this. The serial-over-usb provides you with 2 serial devices. The second one is the console. The first is the JTAG interface to flash the bios. # cu -l cuaU1 -s 115200 The device number in cuaU1 is depending on how many serial devices you have over usb. When you plug the serial-over-usb in you should see something like these lines in dmesg/messages. Dec 28 18:30:17 sjakie kernel: ugen2.4: at usbus2 Dec 28 18:30:17 sjakie kernel: uftdi0: on usbus2 Dec 28 18:30:17 sjakie kernel: uftdi1: on usbus2 Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Hacked - FreeBSD 7.1-Release
On Tue, 29 Dec 2009 12:45:36 +0100, Edwin Groothuis wrote: On Mon, Dec 28, 2009 at 10:44:41AM -0500, Andresen, Jason R. wrote: The point is, if your machine is on the internet, then bots are going to try password attacks on any open port they can find. It's just the sad fact of life on the current internet. Unfortunately, this activity will also make it much more difficult to determine when you are under attack from an actual person, which was my point earlier. It's one that is not going to be easy to solve either, unless you're willing to rewrite SSH to require every connection attempt to pass a Turing test or something. The turing test is a private/public key with a passphrase. And disable passwords. On all systems which need to be accessible from the public Internet: Run sshd on port 22 and port 8022. Block incoming traffic on port 22 on your firewall. Everybody coming from the outside world needs to know it is running on port 8022. Everybody coming from the inside world has access as normal. Edwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sheevaplug questions
On Tue, 29 Dec 2009 16:51:19 +0100, Zoran Kolic wrote: Howdy! I have 2 of them and cu works fine. As root you can do this. The serial-over-usb provides you with 2 serial devices. The second one is the console. The first is the JTAG interface to flash the bios. # cu -l cuaU1 -s 115200 Perfect! I hardly wait to get the device! When you plug the serial-over-usb in you should see something like these lines in dmesg/messages. Dec 28 18:30:17 sjakie kernel: ugen2.4: at usbus2 Dec 28 18:30:17 sjakie kernel: uftdi0: on usbus2 Dec 28 18:30:17 sjakie kernel: uftdi1: on usbus2 When I turn the plug on, in fact? I suspect Attos tried to connect to wrong device name, or it was on some older freebsd version? Also, there were more than one version of plug, with maybe different hardware parts. Not related to freebsd: forum posts point to error after changing root password on the plug. Someone experienced it? I see no reason to have any problem on default ubuntu 9.04 with simple "passwd". Almost all posters made "apt-get update first". Thank you all for reply. Best regards Zoran Please provide a link to the forum post. Otherwise I can only guess what you mean. There is no error because of changing the password. But there are some thing broken in the default install (missing dir, missing timezone, etc.). Follow the commands in this link and you're ready to go. http://www.plugcomputer.org/plugwiki/index.php/QuickStart Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libusbhid.a
On Thu, 31 Dec 2009 10:59:18 +0100, Jeremy Chadwick wrote: On Thu, Dec 31, 2009 at 10:12:59AM +0100, Oliver Lehmann wrote: I'm trying to build the 7 world from yesterdays CVSup but I'm getting: ===> usr.sbin/bluetooth/bthidcontrol (all) cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/bthidcontrol.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/hid.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c lexer.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c parser.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/sdp.c make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libusbhid.a. Stop I remember that I had the error in June also but then I just disabled building bthidcontrol to work it around. Now I want it fixed ;) User "thompsa" recently (past 24 hours) committed a ton of USB code changes[1] which appears to have broken things on RELENG_8; the periodic tinderbox builds are also failing for all platforms[2]. The builds on tinderbox are failing in a different part of the code (kernel not world), but I've a feeling it's related. [1]: http://www.freshbsd.org/?branch=RELENG_8&project=&committer=thompsa&module=&q= [2]: http://lists.freebsd.org/pipermail/freebsd-stable/2009-December/thread.html (see bottom of page) The original post is mentioning 7 world. Not RELENG_8. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libusbhid.a
On Thu, 31 Dec 2009 10:12:59 +0100, Oliver Lehmann wrote: Hi, I'm trying to build the 7 world from yesterdays CVSup but I'm getting: ===> usr.sbin/bluetooth/bthidcontrol (all) cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/bthidcontrol.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/hid.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c lexer.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c parser.c cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -DBTHIDCONTROL=1 -I/usr/src/usr.sbin/bluetooth/bthidcontrol/../bthidd -Wsystem-headers -Wno-pointer-sign -c /usr/src/usr.sbin/bluetooth/bthidcontrol/sdp.c make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libusbhid.a. Stop I remember that I had the error in June also but then I just disabled building bthidcontrol to work it around. Now I want it fixed ;) Ideas? Some of the regular tips: - Make clean or rm -r /usr/obj - Remove the /usr/src/* and csup/cvsup some fresh src. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Multiple serial consoles via null modem cable
On Fri, 15 Jan 2010 07:34:17 +0100, Marin Atanasov wrote: Thank you a lot for your feedback! Now to the real question again, because I'm a little confused now - can I still get a usb-to-serial port converter having let's say 8 serial ports and then connect each machine to the usb-to-serial hub and manage them remotely from a single location (the host having the usb-to-serial hub)? That way I just specify a serial port number and I get to a specific machine? The model provided by Boris looks nice, and that was my initial idea, but I'm not sure if I could get it working under FreeBSD. Is conserver or conserver-com able to handle this? I know that cu uses COM1 only, but will conserver able to handle serial consoles on different ports, since the usb-to-serial port would appear as multiple serial ports. You can provide cu with the port to connect to on the command line. cu -l cuaU0 -s 115200 cu -l cuaU1 -s 115200 etc. You can not connect several servers on 1 serial port, but you can connect several servers on several serial ports. With serial-over-usb it scales to many serial ports. Ronald. Thank you and regards, Marin On Tue, Jan 12, 2010 at 7:04 PM, Boris Samorodov wrote: On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote: > I'm thinking about the following situation - 1 system acting like a host > with a serial port hub, each port of the hub is connected to a different > machine on sio0, using null modem cables. Along with milti-io serial cards we use multi-usb serial converters, such as SUNIX UTS7009P (7 USB to serial adapter): http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zpool vdev vs. glabel
On Tue, 09 Feb 2010 18:10:21 +0100, Freddie Cash wrote: On Tue, Feb 9, 2010 at 6:26 AM, Jeremy Chadwick wrote: Also, I'm a little confused as to the use of glabel in this case. In what condition do your disk indices (e.g. X of daX) change? Are you yanking multiple disks out of a system at the same time and then shoving them back into different drive bays? Are you switching between storage subsystem drivers (ahci(4) vs. ataahci(4), for example) regularly? I've yet to be convinced glabel is worth bothering with, unless the system adheres to one of the above situations (which are worthy of strangulation anyway ;-) ). Use multiple disk controllers in a server, and watch as kernel updates and/or BIOS updates change the order that the controllers are probed, thus changing the dev node for every disk in the system. Use multiple disk controllers that use CAM, then move from an IDE-based CompactFlash adapter to a SATA-based CompactFlash adapter for the / filesystem, and watch the system renumber all your dev nodes. Use a RAID controller configured for JBOD or "Single Disk" arrays, and replace a drive while the server is running, which assigns the disk "largest da number +1", then renumbers everything when the server reboots. After you run into those kinds of things a few times, you'll start to use glabel(8) for everything. Plus, it just makes things easier to understand. Instead of da0 through da25 which is a mix of SATA, RAID, and USB drives, you have cfdisk0, cfdisk1, disk00 through disk24, and so on. Personally, the greatest thing to ever happen to FreeBSD is the introduction of GEOM, and the addition of the glabel class. :) Yeah. GEOM is very very very nice. It is a very elegant solution to a lot of problems. I always wonder why other OS'es didn't pick it up. Ronald. While ZFS does it's own disk labelling behind the scenes, using glabel just makes things easier. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stable-8 regression: time stands still
Hi Ruben, Some shots in the dark. - Do you run powerd? Try to disable it. - What is your output of 'sysctl kern.timecounter'? Maybe try setting another timecounter. - Maybe you shouldn't name your computer 'ill child' in french. :-) Ronald. On Mon, 01 Mar 2010 22:14:41 +0100, Ruben de Groot wrote: Forgot to mention. The kernel is GENERIC + IPFIREWALL* and IPDIVERT options; nothing else. I also build a RELEASE_8_0 kernel and it shows the same problems, so it's not just a recent -stable issue. On Mon, Mar 01, 2010 at 09:34:50PM +0100, Ruben de Groot typed: Hi, After upgrading my 7.2-PRERELEASE system to 8-stable I encountered some very strange problems, most obvious: - startup would hang on starting devd, only continuing after a ^C - reboot would hang, but reboot -q would work. - nfs clients would report strange locking problems. Now I've found that probably the real problem here is that NO TIME IS PASSING (!!). Successively calling 'date' will allways give me the exact same time to the second. A 'sleep 1' will hang indefinetely. The BIOS is OK. After (and only after) a reboot, time will be updated to the time of reboot, but stay there forever after. Before I go back to 7.2 (tested there are still no problems there with a livecd) maybe someone want to shed some light on this. I've attached dmesg.boot. cheers, Ruben Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-RELEASE-p2 #6: Sun Feb 21 15:45:07 CET 2010 r...@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT module_register: module g_label already exists! Module g_label failed to register: 17 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2700.11-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1958805504 (1868 MB) ACPI APIC Table: <090908 APIC1020> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <090908 RSDT1020> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fff0, 10 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 77f0 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xf000-0xf7ff,0xfe9f-0xfe9f,0xfe80-0xfe8f irq 18 at device 5.0 on pci1 pcib2: at device 5.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3400 re0: MAC rev. 0x miibus0: on re0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:1f:e2:6a:ac:35 re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.10 controller with 4 3Gbps ports, PM supported ata2: on atapci0 ata2: port is not ready (timeout 0ms) tfd = 01d0 ata2: software reset clear timeout ata2: [ITHREAD] ata3: on atapci0 ata3: port is not ready (timeout 0ms) tfd = 01d0 ata3: software reset clear timeout ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 ohci1: mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 ohci1: [ITHREAD] usbus1: on ohci1 ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 ohci2: [ITHREAD] usbus2: on ohci2 ohci3: mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 ohci3: [ITHREAD] usbus3: on ohci3 ohci4: mem 0xfe7fa000-0xfe7fafff irq 18 at device 19.4 on pci0 ohci4: [ITHREAD] usbus4: on ohci4 ehci0: mem 0xfe7ff000-0xfe7ff0ff irq 19 at device 19.5 on pci0 ehci0: [ITHREAD] usbus5: EHCI version 1.0 usbus5: on ehci0 pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] hdac0: mem 0xfe7f4000-0xfe7f7fff irq 16 at device 20.2 on pci0 hdac0: HDA Driver
Re: NFS lockd problem
On Sat, 27 Mar 2010 20:50:17 +0200, Chuck Swiger wrote: On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote: Outset: 1 NFS server (with lockd) 2 NFS client (with lockd) The clients serve several jails with apache, whose data (www) resides on the server If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem. I don't have this experience. I use NFS locking between FreeBSD, Linux, NetApp and SUN stuff. Older versions of FreeBSD had some troubles, but more recent ones work very well. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS lockd problem
On Fri, 26 Mar 2010 12:08:26 +0200, Giulio Ferro wrote: Outset: 1 NFS server (with lockd) 2 NFS client (with lockd) The clients serve several jails with apache, whose data (www) resides on the server From time to time everything seem to freeze. Then, after one minute or so, the system works again as nothing had happened. In these occasions I get this in the logs on the client madchines: Mar 26 10:29:38 virt1 kernel: nfs server 192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding followed shortly after by: Mar 26 10:29:38 virt1 kernel: nfs server 192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again On the server I only get this: Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 I don't think it's a network problem, since all connections are local and high speed (1Gb/s) I must admit that, with the other nfs problem I reported weeks ago, this kind of freebsd system seems less than stable to me, and this is very disappointing... Anyway I'd appreciate any pointer on this issue... I'm no NFS expert, so I don't know if I can help, but regularly people want to know your FreeBSD version(s), your used NFS version, if you are running NFS over TCP or UDP. Does it help to switch between UDP/TCP? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.0 RC3 and linux linprocfs
On Tue, 26 Feb 2008 00:01:53 +0100, Paul Schmehl <[EMAIL PROTECTED]> wrote: --On Monday, February 25, 2008 23:34:59 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote: Paul Schmehl wrote: Is it no longer required to mount linprocfs in 7.0 RC3? I noticed that it wasn't added to /etc/rc.conf, and that linux.ko is loaded. Just wondering if the mount is still required or not? linux.ko doesn't provide linprocfs. There have not been changes to the linuxulator and related code recently in the release cycle. Can you explain in more detail the new behaviour you are seeing? I'm not seeing any new behavior. I might be missing something, but I haven't noticed anything yet. I use Mulberry for mail, and it's working fne. (It requires the linux emulator.) I just moved to a new box and installed 7.0 RC3 on it. Updated and recompiled the kernel and world. I was comparing my old setup to the new when I realized I wasn't mounting linprocfs. If I don't need it, there's no point in mounting it. The only major problem I'm having is usb just doesn't work right at all. The system doesn't sense when I insert a new device, and I had to enable moused to get the mouse working. (But the usb keyboard works fine.?!) When I insert a usb thumb drive into a slot, I don't see the usual console messages, and there's no /dev/da?, so I'm not sure what to do next. Maybe you can help with that? Did you kldload umass before inserting you usb drive? Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bluetooth keyboards and /etc/rc.d/bluetooth
On Sun, 27 Apr 2008 23:52:52 +0200, Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: Hello, Today I set up a bluetooth keyboard on a FreeBSD machine for the first time. The machine is running FreeBSD 7.0-stable: [EMAIL PROTECTED] uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 I used the Handbook chapter about bluetooth[1] (which needs updating as it doesn't mention bthidd at all) and mailing list messages as my guide. Basically, I found out that I needed to set up hcsecd(8) and bthidd(8) in order for this to work. You can read more ramblings about this experience on my "various hardware"[3] page. I wrote a mini how-to about the setup here[2], in case anyone is interested. I haven't worked with netgraph before. Netgraph devices aren't supposeed to create device node (names) in /dev, right? where does /etc/rc.d/bluetooth fit in the picture? Do I need to use that at all? References: 1) http://www.freebsd.org/doc/en/books/handbook/network-bluetooth.html 2) http://geekinfo.net/article.php?story=2008042704364 3) http://tingox.googlepages.com/freebsd_various_hw You can mail to [EMAIL PROTECTED] to. There are some responsive people with the right knowledge overthere. Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic in drm
s2 is ufs/test. Trying to mount root from ufs:/dev/ad0s3a WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() WARNING: attempt to net_add_domain(netgraph) after domainfinalize() ipfw2 initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled netsmb_dev: loaded drm0: on vgapci0 info: [drm] AGP at 0xe800 128MB info: [drm] Initialized i915 1.5.0 20060119 drm0: [ITHREAD] pid 3421 (fstat), uid 0: exited on signal 6 encode_long: negative value -633 in accounting record -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic in drm
On Thu, 26 Jun 2008 18:01:07 +0200, Gavin Atkinson
<[EMAIL PROTECTED]> wrote:
On Thu, 2008-06-26 at 16:09 +0200, Ronald Klop wrote:
Hello,
At my work I see a panic if I do this.
Leaf my computer on screensaver (don't no if that is necessary) and come
back the next morning. My monitor is than black, but the light is green,
so DPMS didn't kick in.
Keys or mouse don't wake up the system. CTRL-ALT-F1 switches to the
console and immediately triggers this panic.
I'm running latest x.org with xf86-video-i810-1.7.4_1. The newer
xf86-video-intel also crashes my system sometimes when I'm working on
it,
so a downgraded.
Any ideas, suggestions or fixes available?
This sounds very familiar to me. I think I was seeing the same panic in
2006...
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-12/msg00344.html
Can you add this to src/sys/dev/drm/i915_irq.c
if (!dev->irqr) {
return DRM_ERR(EINVAL);
}
just above the DRM_WAIT_ON in i915_driver_vblank_wait() (around line
140), and see if that prevents the panic? Note that I believe this to
be a workaround, and not really the correct fix.
(sorry for not supplying patches, I'm not in a position to right now)
Gavin
Thanks, I'll try this next week.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
installdate of a port/package?
Hello, I just upgraded a machine from FreeBSD 6 to 7. Very nice. But my portupgrade -fa failed after a while. How can I know which ports/packages are still from FreeBSD 6? Is there a datee recorded somewhere or the FreeBSD-version of the port/package? The date of the files in /var/db/pkg/* is unreliable, because installing a package gives these files the date of the files in the package. How do I know which ports I still need to update? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic in drm
On Fri, 27 Jun 2008 11:55:45 +0200, Ronald Klop
<[EMAIL PROTECTED]> wrote:
On Thu, 26 Jun 2008 18:01:07 +0200, Gavin Atkinson
<[EMAIL PROTECTED]> wrote:
On Thu, 2008-06-26 at 16:09 +0200, Ronald Klop wrote:
Hello,
At my work I see a panic if I do this.
Leaf my computer on screensaver (don't no if that is necessary) and
come
back the next morning. My monitor is than black, but the light is
green,
so DPMS didn't kick in.
Keys or mouse don't wake up the system. CTRL-ALT-F1 switches to the
console and immediately triggers this panic.
I'm running latest x.org with xf86-video-i810-1.7.4_1. The newer
xf86-video-intel also crashes my system sometimes when I'm working on
it,
so a downgraded.
Any ideas, suggestions or fixes available?
This sounds very familiar to me. I think I was seeing the same panic in
2006...
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-12/msg00344.html
Can you add this to src/sys/dev/drm/i915_irq.c
if (!dev->irqr) {
return DRM_ERR(EINVAL);
}
just above the DRM_WAIT_ON in i915_driver_vblank_wait() (around line
140), and see if that prevents the panic? Note that I believe this to
be a workaround, and not really the correct fix.
(sorry for not supplying patches, I'm not in a position to right now)
Gavin
Thanks, I'll try this next week.
Ronald.
Unfortunately, your change didn't fix it for me. I also added a DRM_ERROR
message in the diff and it is never displayed.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UMASS problem on 7.0 STABLE
On Tue, 08 Jul 2008 20:27:26 +0200, Paul Schmehl <[EMAIL PROTECTED]> wrote: Ever since I upgraded this workstation to 7.0 STABLE, I have been unable to reboot with my USB hard drive attached. During the boot sequence, the device is properly detected and identified, but then I get an error message, a crash dump and a reboot. I enabled /var/log/console.log in the hope that I would catch the error message, but it doesn't appear in the log. I also don't have any kernel dumps, so I can't trace those to see what the problem might be. An additional problem that I have is that, during boot, the system says there is no dump device available. This is despite the fact that swap is twice the real memory size and /etc/defaults/rc.conf defines dumpdev as auto. I even tried defining dumpdev as the swap partition (in /etc/rc.conf), but nothing changed. I have to be doing something wrong, but I'm at a loss to know what it is. I've rebuilt world and kernel nine times now, in the desparate hope that something might have changed in the usb code that would solve this problem. (Every time "#find /usr/src -newer /boot/kernel" returns changes in the usb code, I rebuild kernel and world.) Is there something I can enable that will capture the boot sequence during a failed boot while devices are still being detected? # grep -i umass /var/log/console.log Any helpful hints would be gratefully appreciated. # uname -a FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #8: Mon Jul 7 10:41:03 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # sysctl -a | grep hw.physmem hw.physmem: 3474407424 # dmesg | grep -i umass umass0: 2> on uhub5 da0 at umass-sim0 bus 0 target 0 lun 0 # grep swap /etc/fstab /dev/ad8s1b noneswapsw 0 0 # swapctl -l Device: 1024-blocks Used: /dev/ad8s1b 8388608 0 # grep -i usb /var/run/dmesg.boot uhci0: port 0xff20-0xff3f irq 16 at device 26.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhci1: port 0xff00-0xff1f irq 17 at device 26.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 ehci0: mem 0xfebd9c00-0xfebd9fff irq 22 at device 26.7 on pci0 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 ums0: on uhub3 uhci2: port 0xff80-0xff9f irq 23 at device 29.0 on pci0 usb3: on uhci2 usb3: USB revision 1.0 uhub4: on usb3 uhci3: port 0xff60-0xff7f irq 17 at device 29.1 on pci0 usb4: on uhci3 usb4: USB revision 1.0 uhub5: on usb4 uhci4: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 usb5: on uhci4 usb5: USB revision 1.0 uhub6: on usb5 ehci1: mem 0xff980800-0xff980bff irq 23 at device 29.7 on pci0 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub7: on usb6 It might be something else, but I had usb problems in 6-STABLE until I disabled usb support in the bios. FreeBSD still detects the usb hardware. In my case there was some sort of conflict between the usb detection of the bios and the detection FreeBSD. The symptoms where very weird, because it also depended on the connected usb devices on time of boot. Connecting theme after booting did work. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UMASS problem on 7.0 STABLE
On Thu, 10 Jul 2008 17:31:51 +0200, Paul Schmehl <[EMAIL PROTECTED]> wrote: --On Wednesday, July 09, 2008 11:50:25 +0200 Ronald Klop <[EMAIL PROTECTED]> wrote: On Tue, 08 Jul 2008 20:27:26 +0200, Paul Schmehl <[EMAIL PROTECTED]> wrote: Ever since I upgraded this workstation to 7.0 STABLE, I have been unable to reboot with my USB hard drive attached. During the boot sequence, the device is properly detected and identified, but then I get an error message, a crash dump and a reboot. I enabled /var/log/console.log in the hope that I would catch the error message, but it doesn't appear in the log. I also don't have any kernel dumps, so I can't trace those to see what the problem might be. An additional problem that I have is that, during boot, the system says there is no dump device available. This is despite the fact that swap is twice the real memory size and /etc/defaults/rc.conf defines dumpdev as auto. I even tried defining dumpdev as the swap partition (in /etc/rc.conf), but nothing changed. I have to be doing something wrong, but I'm at a loss to know what it is. I've rebuilt world and kernel nine times now, in the desparate hope that something might have changed in the usb code that would solve this problem. (Every time "#find /usr/src -newer /boot/kernel" returns changes in the usb code, I rebuild kernel and world.) Is there something I can enable that will capture the boot sequence during a failed boot while devices are still being detected? # grep -i umass /var/log/console.log Any helpful hints would be gratefully appreciated. # uname -a FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #8: Mon Jul 7 10:41:03 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # sysctl -a | grep hw.physmem hw.physmem: 3474407424 # dmesg | grep -i umass umass0: on uhub5 da0 at umass-sim0 bus 0 target 0 lun 0 # grep swap /etc/fstab /dev/ad8s1b noneswapsw 0 0 # swapctl -l Device: 1024-blocks Used: /dev/ad8s1b 8388608 0 # grep -i usb /var/run/dmesg.boot uhci0: port 0xff20-0xff3f irq 16 at device 26.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhci1: port 0xff00-0xff1f irq 17 at device 26.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 ehci0: mem 0xfebd9c00-0xfebd9fff irq 22 at device 26.7 on pci0 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 ums0: on uhub3 uhci2: port 0xff80-0xff9f irq 23 at device 29.0 on pci0 usb3: on uhci2 usb3: USB revision 1.0 uhub4: on usb3 uhci3: port 0xff60-0xff7f irq 17 at device 29.1 on pci0 usb4: on uhci3 usb4: USB revision 1.0 uhub5: on usb4 uhci4: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 usb5: on uhci4 usb5: USB revision 1.0 uhub6: on usb5 ehci1: mem 0xff980800-0xff980bff irq 23 at device 29.7 on pci0 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub7: on usb6 It might be something else, but I had usb problems in 6-STABLE until I disabled usb support in the bios. FreeBSD still detects the usb hardware. In my case there was some sort of conflict between the usb detection of the bios and the detection FreeBSD. The symptoms where very weird, because it also depended on the connected usb devices on time of boot. Connecting theme after booting did work. Dell's BIOS has three options for the USB controller; off, on and no umass device support. Off allows the box to boot properly, but I have no keyboard. (Kind of not useful.) The other two manifest the same problem. So this didn't solve the problem for me. Does 'off' still let FreeBSD detect the usb controller? If so, this might point you in the right direction for pinpointing the reason of the problem. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to get more logging from GEOM?
On Fri, 11 Jul 2008 09:59:33 +0200, Jo Rhett <[EMAIL PROTECTED]> wrote: About 10 days ago one of my personal machines started hanging at random. This is the first bit of instability I've ever experienced on this machine (2+ years running) FreeBSD triceratops.netconsonance.com 6.2-RELEASE-p11 FreeBSD 6.2- RELEASE-p11 #0: Wed Feb 13 06:44:57 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 After about 2 weeks of watching it carefully I've learned almost nothing. It's not a disk failure (AFAIK) it's not cpu overheat (now running healthd without complaints) it's not based on any given network traffic... however it does appear to accompany heavy cpu/disk activity. It usually dies when indexing my websites at night (but not always) and it sometimes dies when compiling programs. Just heavy disk isn't enough to do the job, as backups proceed without problems. Heavy cpu by itself isn't enough to do it either. But if I start compiling things and keep going a while, it will eventually hang. My best guess is that geom is having a problem and locking up. There's no log entry before failure to back this idea up, but I think this because during boot I see the following: ad0: 286168MB at ata0-master UDMA100 GEOM_MIRROR: Device gm0 created (id=575427344). GEOM_MIRROR: Device gm0: provider ad0 detected. ad1: 286168MB at ata0-slave UDMA100 GEOM_MIRROR: Device gm0: provider ad1 detected. GEOM_MIRROR: Device gm0: provider ad1 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. GEOM_MIRROR: Device gm0: rebuilding provider ad0. Every time it is rebuilding ad0. Every single boot in the last two weeks. Is this any way to get more logging from geom, to confirm or deny this theory? Is there anything else I should be looking at? FWIW, this never happened before the p11 patch to 6.2. I don't know if that is related or not. Obviously, I can't upgrade to 6.3 if heavy cpu/disk activity kills the system. No, I don't have any other insights. I'm not prone to posting "duh help me please!" posts, so I'm quite a bit frustrated by this one. You can try going into the kernel debugger to see where it is hanging. Debugging via a serial cable is also very easy. I don't know the details, but there is a lot of info in the Freebsd handbook. Put this in google 'freebsd handbook kernel debug'. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
trim src/UPDATING in RELENG_7?
Hi, The file src/UPDATING in RELENG_7 goes back until 2004 (the RELENG_5 branchpoint) and is now almost 1000 lines long. Is it an idea to trim this file a bit? And to update this sentence: 'To upgrade in-place from 5.x-stable to current'? And footnote [5] seems a bit dated also. 'if you last updated from current before 20020224 or from -stable before 20020408.' Or is upgrading from 5.x to 7 also supported? Cheers, Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upcoming ABI Breakage in RELENG_7
On Wed, 30 Jul 2008 11:47:34 +0200, David Southwell <[EMAIL PROTECTED]> wrote: On Tuesday 29 July 2008 08:45:45 Ken Smith wrote: Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules that are not part of the baseline system (those will be patched by the MFC) which deal with advisory locks. As such the impact should not cause many people problems. The work that will be MFCed fixes issues with filesystem advisory locks, and moves the advisory locks list from filesystem-private data structures into the vnode structure. The MFC will be done by Kostantin Belousov some time this coming Friday (August 1st, 2008) if you have concerns and want to watch for it. Thanks. Sometimes information gets posted to this list on the assumption that everyone understand what the writer means. This is one of those occasions!! For those of us who are not as well informed and experienced as others could someone please explain what is meant by an ABI breakage, its implications and how to deal with them. Thanks David Googling for ABI gives me this: http://en.wikipedia.org/wiki/Application_binary_interface That is part of what you want to know. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upcoming ABI Breakage in RELENG_7
On Wed, 30 Jul 2008 13:02:52 +0200, Heiko Wundram <[EMAIL PROTECTED]> wrote: Am Mittwoch, 30. Juli 2008 13:11:31 schrieb David Southwell: i.e. Circumstances and what commands to apply in those circumstances? If you don't know what to do, don't run -STABLE? I think in this case (the ABI breakage) it is more nice to say: "If you don't know what to do, you wil probably not see any problem because of this." The edge case of what can go wrong is so small, that you must be doing quite specialized stuff to see breakage. In that case you would understand what is going on. (IMHO) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x to 6.x or 7.x with 64MB /
On Mon, 04 Aug 2008 18:48:03 +0200, Nick Barnes <[EMAIL PROTECTED]> wrote: I have a machine which I have recently upgraded using cvsup, from 4.x to RELENG_5, as a staging post en route to 7.x. The upgrade went well until installworld ran out of disk on / and I realised it was only 64BMB. My bad; should have checked before upgrading. With help from an on-site colleague the installworld was nursed to completion. But can I get the same machine up to 6.x or 7.x without repartitioning? Advice please. Partitions are as follows. ad0 2439 M ad0s1 2439 M ad0s1a64 M / ad0s1b 128 M swap ad0s1e 1024 M /var ad0s1f 600 M /home ad0s1g 623 M - ad157259 M ad1s1 57259 M ad0s1a 10240 M /usr It occurs to me that if ad0s1a is insufficient then I could use ad0s1g as swap, and repurpose ad0s1b as a new /. Is it straightforward to installworld/mergemaster to somewhere other than / ? That is very well doable. On boot you can interrupt the boot process by pressing space an set another location for the kernel. More information is here. http://www.freebsd.org/doc/en/books/handbook/boot-blocks.html The rest is just about files. After you copy everything in ad0s1b (with a fs in it) you can boot from ad0s1b:/boot/kernel. I think you can do something like make installkernel DESTDIR=/blabla, but I'm not sure. Maybe more easy is booting with a LIVE-cd. Than you can mount everything needed for installworld in /mnt/tmproot, so you get: /mnt/tmproot mounted the _new_ / partition (ad0s1b?) /mnt/tmproot/usr where /usr is mounted (ad0s1a) /mnt/tmproot/var where /var is mounted (ad0s1e) Do a chroot /mnt/tmproot and than run installworld and mergemaster as usual from /usr/src. Don't forget to make a backup. It is on your own risk. ;-) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to handle the pack files now we have switched to git?
Van: Pete French Datum: dinsdag, 5 januari 2021 12:08 Aan: FreeBSD Stable Mailing List Onderwerp: How to handle the pack files now we have switched to git? So, for me the switch to git went very smoothly. I havent moved to etcupdate yet, but will probably do that soon. Hopwever I did hit one issue. What I do is to build on a single machine, and then send that to a number of places using rsync. But what seems to happen wuth git is that it has a big pack file of objects, and the name of the opack file is the SHA1 of whatever is inside it. So if something chnages then the filename chnages - and thus rsync tries to move the entire lot all over again, even if the change is tiny. Does anyone have a solution to this ? Currently I am telling rsync to ignore .git when it sends the source, but am not entirely happy with that. But apart from that, git works fine ;) -pete. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Why are you not happy with ignoring .git? It sounds like a pretty reasonable thing to do for your setup. Otherwise (if you keep the .git dir) there is nothing you can do about this (AFAIK) and you will rsync quite some data now and then. Regards, Ronald. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Poudriere failed to build pkg in 13-stable jail under 12-stable
On Mon, 25 Jan 2021 05:46:43 +0100, Thomas Legg wrote: The build of a 13-stable source and kernel were a success under 12-stable (though with some issues on freeze-ups and hard reboots that I suspect might be related to the bufdaemon issue and my 0x15 gen AMD cpu). Created a 13-stable poudriere jail with the knowledge that there may be issues with builds under a 12-stable r369076 kernel. I didn't expect this failure on packaging pkg. > Compressing man pages (compress-man) ===> Installing ldconfig configuration file === ===> ===> Building package for pkg-1.16.2 cp: /wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg/pkg-1.16.2.txz: Function not implemented *** Error code 1 cp in 13-stable uses the system call copy_file_range which is not in the 12-stable kernel. In general running newer code (13) on older kernel (12) is unsupported. Version 12 is not forwards compatible. Regards, Ronald. Stop. make[1]: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Stop. make: stopped in /usr/ports/ports-mgmt/pkg =>> Cleaning up wrkdir ===> Cleaning for pkg-1.16.2 build of ports-mgmt/pkg | pkg-1.16.2 ended at Mon Jan 25 12:16:12 HKT 2021 build time: 00:02:01 !!! build failure encountered !!! ___ freebsd-curr...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
daily run output misses zpool errors
Hi, Below my daily report. And here my zpool status -x. It would be nice to see this error in my daily info. I am running with daily_show_info="NO", but this looks more severe than info. [root@sjakie /etc]# zpool status -x pool: extern state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub repaired 47K in 2h36m with 0 errors on Sat Sep 15 21:00:32 2012 config: NAMESTATE READ WRITE CKSUM extern ONLINE 0 0 0 da0 ONLINE 0 0 0 errors: 2 data errors, use '-v' for a list Running /etc/periodic/daily/404.status-zfs by hand does give all the output. Regards, Ronald. --- Forwarded message --- From: "Charlie Root" <***@***> To: ***@*** Cc: Subject: ***.***.*** daily run output Date: Tue, 25 Sep 2012 03:34:38 +0200 Removing stale files from /var/preserve: Cleaning out old system announcements: Removing stale files from /var/rwho: Backup passwd and group files: Verifying group file syntax: /etc/group is fine Backing up package db directory: Rotating accounting logs and gathering statistics: Network interface status: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em01500 00:21:70:46:6c:da 138201 0 0 202008 0 00 em01500 192.168.1.0 sjakie.home 97029 - - 205741 - -- em01500 192.168.1.36/ 192.168.1.36 42458 - - 0 - -- usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 lo0 163849842 0 0 9842 0 00 lo0 16384 localhost ::1 0 - - 0 - -- lo0 16384 fe80::1%lo0 fe80::1 0 - - 0 - -- lo0 16384 your-net localhost0 - - 9842 - -- ipfw0 65536 0 0 0 0 0 00 Security check: (output mailed separately) Checking for denied zone transfers (AXFR and IXFR): -- End of daily output -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: daily run output misses zpool errors
On Wed, 03 Oct 2012 22:01:49 +0200, Alexander Leidinger wrote: On Tue, 25 Sep 2012 14:56:49 +0200 "Ronald Klop" wrote: Hi, Below my daily report. And here my zpool status -x. It would be nice to see this error in my daily info. I am running with daily_show_info="NO", but this looks more severe than info. Just to make sure: you verified that you have daily_status_zfs_enable=YES in periodic.conf? In the daily mail you provided I've seen several headings without content, but I haven't seen the "Checking status of zfs pools:" part which is supposed to show up when the zfs stats script is run. Bye, Alexander. Yes. My point is that as long as the pool is healthy the daily e-mail tells me that and when the pool is unhealthy it does not show me any info. I setup a test to reproduce this. I broke a mirror by dd-ing /dev/random over one of the md backing files. $ cat /etc/periodic.conf daily_show_info="NO" weekly_show_info="NO" monthly_show_info="NO" daily_status_zfs_enable="YES" daily_scrub_zfs_enable="YES" daily_status_smart_devices="AUTO" daily_clean_hoststat_enable="NO" daily_status_mail_rejects_enable="NO" daily_status_include_submit_mailq="NO" daily_submit_queuerun="NO" $ zpool status test pool: test state: ONLINE status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-4J scan: scrub repaired 0 in 0h0m with 0 errors on Wed Oct 17 14:26:43 2012 config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0ONLINE 0 0 0 md0 ONLINE 0 0 0 18290078248358455968 UNAVAIL 0 0 0 was /dev/md1 errors: No known data errors The daily mail before I broke the pool: - Removing stale files from /var/preserve: Cleaning out old system announcements: Removing stale files from /var/rwho: Backup passwd and group files: Verifying group file syntax: /etc/group is fine Backing up package db directory: Rotating accounting logs and gathering statistics: Checking status of zfs pools: NAME SIZE ALLOC FREECAP DEDUP HEALTH ALTROOT extern 298G 161G 137G54% 1.00x ONLINE - tank 292G 215G 77.2G73% 1.00x ONLINE - test95.5M 5.32M 90.2M 5% 1.00x ONLINE - all pools are healthy Network interface status: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll Drop em01500 00:21:70:46:6c:da 427203 0 0 321583 0 00 em01500 192.168.1.0 sjakie.home 368631 - - 322492 - -- em01500 192.168.1.36/ 192.168.1.36 64146 - - 0 - -- usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 usbus 00 0 0 0 0 00 lo0 16384 20857 0 0 20857 0 00 lo0 16384 localhost ::1 0 - - 0 - -- lo0 16384 fe80::1%lo0 fe80::1 0 - - 0 - -- lo0 16384 your-net localhost 34 - - 20857 - -- ipfw0 65536 0 0 0 0 0 00 Security check: (output mailed separately) Checking for denied zone transfers (AXFR and IXFR): Scrubbing of zfs pools: skipping scrubbing of pool 'extern': last scrubbing is 20 days ago, threshold is set to 35 days skipping scrubbing of pool 'tank': last scrubbing is 4 days ago, threshold is set to 35 days skipping scrubbing of pool 'test': last scrubbing is 0 days ago, threshold is set to 35 days -- End of daily output -- The daily mail after I broke the pool: - Removing stale files from /var/preserve: Cleaning out old system announcements: R
portsnap not updating
Hello, Probably the wrong mailinglist. But portsnap is not updating since a few days while there are commits on the ports tree. [1] After some searching I found I am not the only one. Apparently there is maintenance being done on the servers. http://www.mail-archive.com/freebsd-ports@freebsd.org/msg45395.html I read a lot of blogs/RSS/etc. Nowhere any signs of maintenance on the servers. What is wrong with announcing these things on for example www.freebsd.org? NB: I know it is voluntary work, thanks for doing it. Regards, Ronald. [1] [root@sjakie ~]# time update_portstree.sh Looking up eu.portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. ===>>> There are no new versions available ===>>> 968 total installed ports Thu Nov 15 13:23:57 CET 2012 [root@sjakie ~]# ls -l /usr/ports/INDEX-* -rw-r--r-- 1 root wheel 26830552 Nov 12 20:38 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26714819 Nov 12 20:38 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26696014 Nov 12 20:38 /usr/ports/INDEX-9 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Node conflicts in SVN [SEC=UNCLASSIFIED]
Svn says it sees conflicts. Best thing is to view what the conflicts are using 'svn status' and 'svn diff'. That might shine some more light on this case. Ronald. On Mon, 19 Nov 2012 23:35:11 +0100, Robinson, Greg wrote: UNCLASSIFIED Hi, Could this be an indication of the recent security incident: http://www.freebsd.org/news/2012-compromise.html ie, non-svn modifications to a svn repository have occurred? Greg. -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Frank Seltzer Sent: Tuesday, 20 November 2012 6:07 AM To: Kevin Oberman Cc: freebsd-stable@freebsd.org Subject: Re: Node conflicts in SVN On Mon, 19 Nov 2012, Kevin Oberman wrote: On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer wrote: I run a nightly ports tree update and I have been getting the following errors the last couple of days. I haven't seen this asked before so is this just me or is anyone else seeing this? Have I fat-fingered something? Updating '/usr/ports': Skipped '/usr/ports/astro' -- Node remains in conflict Skipped '/usr/ports/devel' -- Node remains in conflict Skipped '/usr/ports/sysutils' -- Node remains in conflict Skipped '/usr/ports/audio' -- Node remains in conflict Skipped '/usr/ports/textproc' -- Node remains in conflict Skipped '/usr/ports/x11-fm' -- Node remains in conflict Skipped '/usr/ports/MOVED' -- Node remains in conflict Skipped '/usr/ports/games' -- Node remains in conflict Skipped '/usr/ports/mail' -- Node remains in conflict Skipped '/usr/ports/net' -- Node remains in conflict Skipped '/usr/ports/multimedia' -- Node remains in conflict At revision 307524. Summary of conflicts: Skipped paths: 11 This usually indicates non-SVN updates to these items. If you have not modified them intentionally, just 'rm -r' them and 'snv up /usr/ports' again. I hit this after switch to svn when a cron job did a csup of ports. Oops! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com Nope, no non-SVN updates or manual changes. I am getting this on 3 separate boxes and have disabled csup in cron on them all. Are you sure about 'rm -r'ing them? IIRC, I reran 'svn co' instead of 'svn up' by mistake on 1 box and it pulled the entire collection again. Not sure about this as my memory ain't what it used to be. You know what they say, The mind is the first thing to go! Thanks, Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Node conflicts in SVN
On Wed, 21 Nov 2012 09:44:22 +0100, Frank Seltzer wrote: On Tue, 20 Nov 2012, Sergey V. Dyatko wrote: Can you run `svn status`? What does it show ? -- wbr, tiger 'svn status > stat' creates a 5.5 meg file mostly consisting of lines like: D Mk/bsd.apache.mk D Mk/bsd.autotools.mk D Mk/bsd.cmake.mk D Mk/bsd.commands.mk D Mk/bsd.cran.mk D Mk/bsd.database.mk D Mk/bsd.destdir.mk D Mk/bsd.drupal.mk D Mk/bsd.efl.mk etc. I can forward this file to you if you would like to take a look at it. Following that with 'grep -A1 C\ stat' shows 217 lines similar to these: D C accessibility > local unversioned, incoming add upon update -- D C arabic > local unversioned, incoming add upon update -- D C archivers > local unversioned, incoming add upon update -- D C astro > local unversioned, incoming add upon update -- D C audio > local unversioned, incoming add upon update It's up to 27 now (see below). Again, this is on 3 separate boxes, none running csup, cvsup or anything else but 'svn co'. Updating '.': Skipped 'MOVED' -- Node remains in conflict Skipped 'irc' -- Node remains in conflict Skipped 'net-p2p' -- Node remains in conflict Skipped 'games' -- Node remains in conflict Skipped 'sysutils' -- Node remains in conflict Skipped 'textproc' -- Node remains in conflict Skipped 'net' -- Node remains in conflict Skipped 'japanese' -- Node remains in conflict Skipped 'databases' -- Node remains in conflict Skipped 'graphics' -- Node remains in conflict Skipped 'security' -- Node remains in conflict Skipped 'x11-fm' -- Node remains in conflict Skipped 'dns' -- Node remains in conflict Skipped 'www' -- Node remains in conflict Skipped 'archivers' -- Node remains in conflict Skipped 'astro' -- Node remains in conflict Skipped 'math' -- Node remains in conflict Skipped 'devel' -- Node remains in conflict Skipped 'audio' -- Node remains in conflict Skipped 'Mk' -- Node remains in conflict Skipped 'deskutils' -- Node remains in conflict Skipped 'mail' -- Node remains in conflict Skipped 'net-mgmt' -- Node remains in conflict Skipped 'net-im' -- Node remains in conflict Skipped 'multimedia' -- Node remains in conflict Skipped 'finance' -- Node remains in conflict Skipped 'ftp' -- Node remains in conflict At revision 307611. Summary of conflicts: Skipped paths: 27 Frank http://svnbook.red-bean.com/en/1.2/svn.ref.svn.c.status.html 'D' Item is scheduled for Deletion. Your files are marked deleted at your host. And it complains that it gets an update from the server for a file which is deleted locally. Something f*cked up your ports tree. The solution for you is to remove /usr/ports and do a new checkout. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Increasing the DMESG buffer....
On Wed, 21 Nov 2012 19:41:42 +0100, Torfinn Ingolfsen wrote: On Wed, 21 Nov 2012 18:25:22 +0100 Willem Jan Withagen wrote: Why bother... Because FreeBSD also runs on hardware with minimal memory? yes, but defaults should be for the masses and it is tunable for the rest Because FreeBSD is a stable, sane operating system and we want to keep it that way? yes, but how does an increased buffer bring instability? You can use your argument for every commit. Because it breaks POLA? how? Because it make developers act sloppy? How do you go from increasing a buffer to hold all the data which solves a practical problem to people being sloppy? I'm sorry (I'm not picking on you in particular, but this comment represents a growing trend in attitude), but more and more people today are becoming careless in the way they think (or not think). I do not want FreeBSD to suffer because of that. If you are a FreeBSD developer or user; be vigilant! Don't let the sloppyness silnently slip into or favorite operating system, or the way we handle it! IMHO these arguments are more about general feelings than actual to the point remarks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
