FreeBSD10: lock order reversal with portsnap extract
I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM. One of the first things I do is a 'portsnap fetch extract'. As soon as the extract starts it produces a 'lock order reversal' message with a KDB stack backtrace, but then proceeds successfully to verify the integrity and install the ports tree. Should I worry? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD10: lock order reversal with portsnap extract
El 01/06/2013 15:44, Walter Hurry walterhu...@gmail.com escribió: I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM. One of the first things I do is a 'portsnap fetch extract'. As soon as the extract starts it produces a 'lock order reversal' message with a KDB stack backtrace, but then proceeds successfully to verify the integrity and install the ports tree. Should I worry? LORs should be avoided when possible but are not a bug per se. You should check the pages listed here[1] to see if your lor has already been reported. Cheers. [1] https://wiki.freebsd.org/LOR ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD10: lock order reversal with portsnap extract
Hi, Reference: From: Walter Hurry walterhu...@gmail.com Date: Sat, 1 Jun 2013 13:43:47 + (UTC) Walter Hurry wrote: I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM. One of the first things I do is a 'portsnap fetch extract'. As soon as the extract starts it produces a 'lock order reversal' message with a KDB stack backtrace, but then proceeds successfully to verify the integrity and install the ports tree. Should I worry? Yes, you should worry ;-) Worry you didn't realise: a) questions@ list was created originally for beginners b) the so called 10 is actually current for that you should subscribe @ ask on curr...@freebsd.org Best go review the descriptions of the 50 odd lists we have on @freebsd.org Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD10: lock order reversal with portsnap extract
On Sat, 01 Jun 2013 20:22:29 +0200, Julian H. Stacey wrote: Hi, Reference: From:Walter Hurry walterhu...@gmail.com Date:Sat, 1 Jun 2013 13:43:47 + (UTC) Walter Hurry wrote: I'm installing FreeBSD10 (head; snapshot from 30 May 2013) into a VM. One of the first things I do is a 'portsnap fetch extract'. As soon as the extract starts it produces a 'lock order reversal' message with a KDB stack backtrace, but then proceeds successfully to verify the integrity and install the ports tree. Should I worry? Yes, you should worry ;-) Worry you didn't realise: a) questions@ list was created originally for beginners b) the so called 10 is actually current for that you should subscribe @ ask on curr...@freebsd.org Best go review the descriptions of the 50 odd lists we have on @freebsd.org Oh, OK. Sorry. Will do. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD SCSI LUN reservation (essentially an exclusive lock)
Hello all, Is there any way for a process in user space to try to trigger a SCSI LUN reservation in FreeBSD? This would be a very useful thing to have when using a multi-port storage device which can be simultaneously connected to multiple systems. --jau ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: File permissions - how to lock a directory
On Sat, Sep 29, 2012 at 4:41 PM, Paul Schmehl pschmehl_li...@tx.rr.comwrote: I have a particularly thorny problem I'm trying to solve, but I'll bet FreeBSD has a solution. I'm running a webserver using suphp. It's very picky about permissions. It wants the web server user (www) to be the owner of all directories and files. Meanwhile, the site owners want to be able to update and add files to the site. When they update files everything is fine. When they upload new files, the ownership of the file is user:user instead of www:user, so apache can't display them. Is there a way to lock a directory such that all files created in that directory are owned by the directory owner? If not, I'll have to script something to change perms after uploads. There is the suiddir option, see mount(8) and chmod(2). -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xfce and session lock (xlock)
Hello, I use Xfce 4.8, is there a way to lock the session when the screen goes to sleep? Thanks, regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xfce and session lock (xlock)
On Fri, 2 Dec 2011 01:23:19 +0100, Patrick Lamaiziere wrote: I use Xfce 4.8, is there a way to lock the session when the screen goes to sleep? I think you can install the port xscreensaver which integrates well with Xfce. At least it did the last time I did look at it. :-) The xscreensaver program does show a screensaver or use the monitor's DPMS feature after a specified time without interaction. It will then require a password to unlock the session. Note: I'm using the classic xlock command (with installed port xlockmore) and usually lock the session by pressing (slapping) the Help key (which is the double-width key on the top left on a Sun keyboard, quite handy). I'm not sure if xlock has an option for setting a timeout value... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
lock order reversal @ FreeBSD 9.0B3
Hi all, I'm seeing weird messages at dmesg saying someting about lock order reversal (see below) on my FreeBSD 9.0 beta 3. I think this has something to do with the filesystem, so I'm a little bit worried. Does anybody know if this is a known bug? (If so, how do you know?) Shall I report it? Thanks, Antonio P.S.: Details lock order reversal: 1st 0xc86d88d8 ufs (ufs) @ /usr/src/sys/kern/vfs_syscalls.c:3572 2nd 0xe0778a00 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:260 3rd 0xc86d86b8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2134 KDB: stack backtrace: db_trace_self_wrapper(c0eff6ac,632e7262,3331323a,6f000a34,632e7370,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a42bdb,c0f03028,c6d65370,c6d69338,ef34190c,...) at kdb_backtrace+0x2a _witness_debugger(c0f03028,c86d86b8,c0ef2288,c6d69338,c0f0ad74,...) at _witness_debugger+0x25 witness_checkorder(c86d86b8,9,c0f0ad74,856,0,...) at witness_checkorder+0x839 __lockmgr_args(c86d86b8,80100,c86d86d8,0,0,...) at __lockmgr_args+0x824 ffs_lock(ef341a34,c0a53e1b,c0f0a05e,80100,c86d8660,...) at ffs_lock+0x8a VOP_LOCK1_APV(c10493e0,ef341a34,c794d670,c1059a80,c86d8660,...) at VOP_LOCK1_APV+0xb5 _vn_lock(c86d8660,80100,c0f0ad74,856,4,...) at _vn_lock+0x5e vget(c86d8660,80100,c794d5c0,50,0,...) at vget+0xb9 vfs_hash_get(c7447ca8,7af825,8,c794d5c0,ef341b78,...) at vfs_hash_get+0xe6 ffs_vgetf(c7447ca8,7af825,8,ef341b78,1,...) at ffs_vgetf+0x49 softdep_sync_buf(c86d8880,e07789a0,1,106,0,...) at softdep_sync_buf+0xac9 ffs_syncvnode(c86d8880,1,c794d5c0,c86a03b8,c86d892c,...) at ffs_syncvnode+0x24c ffs_fsync(ef341c48,ef341cec,0,ef341c48,ef341c6c,...) at ffs_fsync+0x27 VOP_FSYNC_APV(c10493e0,ef341c48,c0f0c048,df9,0,...) at VOP_FSYNC_APV+0xa5 sys_fsync(c794d5c0,ef341cec,c0f493b6,c0eebb0e,286,...) at sys_fsync+0x1df syscall(ef341d28) at syscall+0x284 Xint0x80_syscall() at Xint0x80_syscall+0x21 --- syscall (95, FreeBSD ELF32, sys_fsync), eip = 0x2859a1c7, esp = 0xbfbfe1bc, ebp = 0xbfbfe1d8 --- pid 2085 (perl5.12.4), uid 0: exited on signal 6 (core dumped) pid 2083 (perl5.12.4), uid 0: exited on signal 6 (core dumped) lock order reversal: 1st 0xe07a0e24 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2658 2nd 0xc86b5200 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper(c0eff6ac,7366752f,7366752f,7269645f,68736168,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a42bdb,c0f0300f,c6d65370,c6d69408,f15327e8,...) at kdb_backtrace+0x2a _witness_debugger(c0f0300f,c86b5200,c0f31d92,c6d69408,c0f31a17,...) at _witness_debugger+0x25 witness_checkorder(c86b5200,9,c0f31a17,11c,0,...) at witness_checkorder+0x839 _sx_xlock(c86b5200,0,c0f31a17,11c,c8893828,...) at _sx_xlock+0x85 ufsdirhash_acquire(e07a0dc4,c8893828,f1532918,e5263e74,f15328b8,...) at ufsdirhash_acquire+0x35 ufsdirhash_add(c8893828,f1532918,3e74,f15328a4,f15328a8,...) at ufsdirhash_add+0x13 ufs_direnter(c889caa0,c89a5660,f1532918,f1532bc0,0,...) at ufs_direnter+0x739 ufs_makeinode(f1532bc0,0,f1532b04,f1532a60,c0d5fc85,...) at ufs_makeinode+0x59d ufs_create(f1532b04,f1532b1c,0,0,f1532b80,...) at ufs_create+0x30 VOP_CREATE_APV(c10493e0,f1532b04,f1532bc0,f1532a9c,0,...) at VOP_CREATE_APV+0xa5 vn_open_cred(f1532b80,f1532c48,1a4,0,c74ce280,...) at vn_open_cred+0x215 vn_open(f1532b80,f1532c48,1a4,c86a3508,2835a000,...) at vn_open+0x3b kern_openat(c7ac6b80,ff9c,289ffa60,0,a03,...) at kern_openat+0x1ec kern_open(c7ac6b80,289ffa60,0,a02,1b4,...) at kern_open+0x35 sys_open(c7ac6b80,f1532cec,c,f1532d80,282,...) at sys_open+0x30 syscall(f1532d28) at syscall+0x284 Xint0x80_syscall() at Xint0x80_syscall+0x21 --- syscall (5, FreeBSD ELF32, sys_open), eip = 0x282b1343, esp = 0xbf9f100c, ebp = 0xbf9f1038 --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: lock order reversal @ FreeBSD 9.0B3
That looks like LOR #261, known not be a problem. [ http://ipv4.sources.zabbadoz.net/freebsd/lor.html ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ATI libreoffice lock up Xorg
I just noticed this, but I'm pretty sure it's a result of the last ATI driver update, FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011 xf86-video-ati-6.14.2 + libreoffice-3.3.3_2 + xorg-7.5.1 = hard lockup, keyboard LEDs work for a bit, can't change to a console, kill X. ssh'ing in, running top shows Xorg at 100% CPU time. Nothing gets printed to the Xorg.0.log xf86-video-vesa-2.3.0_1 + libreoffice-3.3.3_2 + xorg-7.5.1 = works fine. vgapci0@pci0:6:3:0: class=0x03 card=0x51571002 chip=0x4c571002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'Mobility Radeon 7500 (M7 [LW])' class = display subclass = VGA vgapci0: VGA-compatible display port 0xb800-0xb8ff mem 0xd000-0xdfff,0xff52-0xff52 irq 19 at device 3.0 on pci6 drm0: ATI Radeon LW RV200 Mobility 7500 M7 on vgapci0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ATI libreoffice lock up Xorg
On Mon, 15 Aug 2011, Jimmie James wrote: I just noticed this, but I'm pretty sure it's a result of the last ATI driver update, FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011 xf86-video-ati-6.14.2 + libreoffice-3.3.3_2 + xorg-7.5.1 = hard lockup, keyboard LEDs work for a bit, can't change to a console, kill X. ssh'ing in, running top shows Xorg at 100% CPU time. Nothing gets printed to the Xorg.0.log xf86-video-vesa-2.3.0_1 + libreoffice-3.3.3_2 + xorg-7.5.1 = works fine. vgapci0@pci0:6:3:0: class=0x03 card=0x51571002 chip=0x4c571002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'Mobility Radeon 7500 (M7 [LW])' class = display subclass = VGA vgapci0: VGA-compatible display port 0xb800-0xb8ff mem 0xd000-0xdfff,0xff52-0xff52 irq 19 at device 3.0 on pci6 drm0: ATI Radeon LW RV200 Mobility 7500 M7 on vgapci0 We've been talking about ATI lockups on the forums: http://forums.freebsd.org/showthread.php?t=25540 It's mystifying to me, since I haven't seen the lockups at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ATI libreoffice lock up Xorg
On 08/15/11 21:06, Warren Block wrote: On Mon, 15 Aug 2011, Jimmie James wrote: I just noticed this, but I'm pretty sure it's a result of the last ATI driver update, FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45 EDT 2011 xf86-video-ati-6.14.2 + libreoffice-3.3.3_2 + xorg-7.5.1 = hard lockup, keyboard LEDs work for a bit, can't change to a console, kill X. ssh'ing in, running top shows Xorg at 100% CPU time. Nothing gets printed to the Xorg.0.log xf86-video-vesa-2.3.0_1 + libreoffice-3.3.3_2 + xorg-7.5.1 = works fine. vgapci0@pci0:6:3:0: class=0x03 card=0x51571002 chip=0x4c571002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'Mobility Radeon 7500 (M7 [LW])' class = display subclass = VGA vgapci0: VGA-compatible display port 0xb800-0xb8ff mem 0xd000-0xdfff,0xff52-0xff52 irq 19 at device 3.0 on pci6 drm0: ATI Radeon LW RV200 Mobility 7500 M7 on vgapci0 We've been talking about ATI lockups on the forums: http://forums.freebsd.org/showthread.php?t=25540 It's mystifying to me, since I haven't seen the lockups at all. Thanks for the heads up, replied to the thread there, and will here too. Switching to XAA fixes this lock up for me. However, changing a window size, opening a new app causing flickering of said window. Changing desktops is laggy, and windows from desktop 1 appear for about 5-10 seconds on desktop 2. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible
I tried searching the archives, but didn't get hits. Goggle hits revealed little info. Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible -- System Name: doris.StevenFriedrich.org Window Manager(s): kde4-4.6.2 X Window System: xorg-7.5.1X.Org X Server 1.7.7 OS version: FreeBSD 8.2-RELEASE i386 (5.9 MB kernel) Platform:HP pavilion zd8000 (zd8215us) CPU: 2.40GHz Intel Pentium 4 with 511 MB memory FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: CMedia CMI8738 (play/rec) default ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible
On Apr 18, 2011, at 12:18 PM, Steven Friedrich wrote: I tried searching the archives, but didn't get hits. Goggle hits revealed little info. Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible Does this thread help: http://forums.freebsd.org/showthread.php?p=130978 Also, posting the output of sysctl -a | grep kern.ipc.shm might be helpful. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: lock contention problem?
It might be a hardware resource starvation problem. It is possible to nice umass by simply adding a line like: .interval = 2,/* 2 milliseconds */ Thanks, but it didn't help. Also tried setting it to 1, 4, and 20. http://svn.freebsd.org/changeset/base/217350 Is this supposed to work for 8.0? Is there more to it than a couple line change in a .h file? /usr/src/sys/dev/usb/controller/usb_controller.c: In function 'usb_attach_sub': /usr/src/sys/dev/usb/controller/usb_controller.c:434: warning: implicit declaration of function 'PI_SWI' /usr/src/sys/dev/usb/controller/usb_controller.c:434: warning: nested extern declaration of 'PI_SWI' I'm feeding fwcontrol -u 1 -S /dev/stdin from a pipe. The write() to the pipe took over a second. Perhaps connected to the lock contention of over a second? The EAGAIN comes from the writev() roughly 20 lines from the end of /usr/src/usr.sbin/fwcontrol/fwdv.c. CPU is 98% idle. Data rate is only 3.4 MiB/second. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
lock contention problem?
I suspect that I have a problem with lock/mutex contention. Reading from a USB disk appears to lock out the firewire driver for too long, causing data transfer (writing to firewire bus) to fail with EAGAIN. Once it fails it does not recover. kernel: fwohci1: IT DMA underrun (0x40308011) (stat OHCI_CNTL_CYCMATCH_S) last message repeated 63 times This is from the end of the fwohci_itxbuf_enable() function in dev/firewire/fwohci.c I added LOCK_PROFILING to the kernel and gathered some data. The data is quite verbose, so I sorted by max and am including the first 40 lines. This is a true real-time task, so I am concerned with the worst case rather than the average. First, data from approx 20 seconds without a problem: debug.lock.prof.enable: 0 debug.lock.prof.reset: 0 debug.lock.prof.stats: max wait_max total wait_total countavg wait_avg cnt_hold cnt_lock name 16990 0 2216486 01837 1206 0 0 0 /usr/src/sys/kern/vfs_vnops.c:533 (lockmgr:ufs) 5852 0 11669 0 18648 0 0 0 /usr/src/sys/kern/vfs_subr.c:1693 (lockmgr:syncer) 1659 05522 0 34162 0 0 0 /usr/src/sys/kern/vfs_mount.c:2231 (sleep mutex:struct mount mtx) 1540 0 30353 0 15283 1 0 0 0 /usr/src/sys/kern/sys_pipe.c:574 (sleep mutex:pipe mutex) 1415 0 1885651 0 53865 35 0 0 0 /usr/src/sys/vm/vm_map.c:3526 (sx:user map) 1385 0 252414 0 53865 4 0 0 0 /usr/src/sys/vm/vm_fault.c:937 (sleep mutex:vm object) 1361 0 84475 0 53865 1 0 0 0 /usr/src/sys/vm/vm_fault.c:938 (sleep mutex:vm page queue mutex) 1044 02079 0 2 1039 0 0 0 /usr/src/sys/kern/vfs_mount.c:2194 (sleep mutex:struct mount mtx) 934 0 65031 0 146445 0 0 0 /usr/src/sys/vm/vm_pager.c:311 (lockmgr:bufwait) 864 0 194008 0 53865 3 0 0 0 /usr/src/sys/amd64/amd64/pmap.c:2958 (sleep mutex:pmap) 864 0 192948 0 53865 3 0 0 0 /usr/src/sys/amd64/amd64/pmap.c:2957 (sleep mutex:vm page queue mutex) 862 0 24690 0 30823 0 0 0 /usr/src/sys/kern/kern_mutex.c:147 (sleep mutex:nfe0) 857 0 84478 0 53863 1 0 0 0 /usr/src/sys/amd64/amd64/trap.c:740 (sleep mutex:process lock) 697 0 154340 03292 46 0 0 0 /usr/src/sys/kern/vfs_bio.c:2559 (lockmgr:bufwait) 557 0 896107 0 13438 66 0 0 0 /usr/src/sys/kern/vfs_bio.c:1835 (lockmgr:bufwait) 519 01615 0 11146 0 0 0 /usr/src/sys/ufs/ffs/ffs_vfsops.c:1321 (sleep mutex:struct mount mtx) 481 0 24417 0 13438 1 0 0 0 /usr/src/sys/kern/vfs_subr.c:1595 (sleep mutex:bufobj interlock) 367 0 65371 09178 7 0 0 0 /usr/src/sys/kern/sys_pipe.c:643 (sleep mutex:pipe mutex) 351 02324 0 52 44 0 0 0 /usr/src/sys/kern/vfs_subr.c:2083 (lockmgr:ufs) 333 0 325772 0 53865 6 0 0 0 /usr/src/sys/vm/vm_fault.c:297 (sleep mutex:vm object) 329 0 171709 0 108608 1 0 0 0 /usr/src/sys/amd64/amd64/pmap.c:3989 (sleep mutex:pmap) 329 02090 0 534 3 0 0 0 /usr/src/sys/kern/vfs_subr.c:337 (sleep mutex:struct mount mtx) 327 0 99170 0 58917 1 0 0 0 /usr/src/sys/vm/vm_page.c:1052 (sleep mutex:vm page queue free mutex) 305 0 514 0 4128 0 0 0 /usr/src/sys/vm/vm_object.c:541 (sleep mutex:vm object) 304 0 304 0 1304 0 0 0 /usr/src/sys/vm/uma_core.c:1565 (sleep mutex:UMA lock) 297 0 359 0 13 27 0 0 0 /usr/src/sys/kern/vfs_bio.c:3611 (sleep mutex:vm object) 296 0 23341 0 983 23 0 0 0 /usr/src/sys/kern/tty_ttydisc.c:467 (sleep mutex:ttymtx) 291 0 448 0 6 74 0 0 0 /usr/src/sys/vm/vm_object.c:1719 (sleep mutex:vm object) 284 0 12090 0 997 12 0 0 0 /usr/src/sys/kern/sys_generic.c:1446 (sleep mutex:select mtxpool) 281 08752 0 955 9 0 0 0 /usr/src/sys/kern/sys_generic.c
Re: lock contention problem?
On Thursday 13 January 2011 21:28:15 dieter...@engineer.com wrote: I suspect that I have a problem with lock/mutex contention. Reading from a USB disk appears to lock out the firewire driver for too long, causing data transfer (writing to firewire bus) to fail with EAGAIN. Once it fails it does not recover. kernel: fwohci1: IT DMA underrun (0x40308011) (stat OHCI_CNTL_CYCMATCH_S) last message repeated 63 times This is from the end of the fwohci_itxbuf_enable() function in dev/firewire/fwohci.c I added LOCK_PROFILING to the kernel and gathered some data. The data is quite verbose, so I sorted by max and am including the first 40 lines. This is a true real-time task, so I am concerned with the worst case rather than the average. Hi, It might be a hardware resource starvation problem. It is possible to nice umass by simply adding a line like: .interval = 2,/* 2 milliseconds */ Inside the following structure in /sys/dev/usb/storage/umass.c : umass_bbb_config[] In states: UMASS_T_BBB_DATA_WRITE UMASS_T_BBB_DATA_READ Another idea: http://svn.freebsd.org/changeset/base/217350 --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
On Fri, 11 Dec 2009 23:58:05 -0800 Yuri wrote: I guess that's a side effect of /compat/linux not being owned by root. Yes, you've found the root of the problem. Chown it to root:wheel and all should be fine. -- WBR, bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Boris Samorodov wrote: ...and remove /compat/linux/home if it exists. You should make sure that installer doesn't create /compat/linux/home. Because I never created it myself, must have been installer. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
On Fri, 11 Dec 2009 11:34:51 -0800 Yuri wrote: Boris Samorodov wrote: ...and remove /compat/linux/home if it exists. You should make sure that installer doesn't create /compat/linux/home. Because I never created it myself, must have been installer. Please show me how can I repeat that case. Or at least show # ls -l /compat/linux -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Boris Samorodov wrote: Please show me how can I repeat that case. Or at least show # ls -l /compat/linux The problem is actually a bug (?) in googleearth, that it leaves the lock file when it finishes ungracefully, and after it is restarted it complains about this file without understanding that the previous process is dead. But it talks about /home/ files, and it's confusing since it really talks about /compat/linux/home/... files. Now I found who creates /compat/linux/home. It's skype. After I delete /compat/linux/home and relaunch skype it recreates it. So maybe to prevent such things link /compat/linux/home - /home should be created by installer? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
On Fri, 11 Dec 2009 15:17:19 -0800 Yuri wrote: Now I found who creates /compat/linux/home. It's skype. After I delete /compat/linux/home and relaunch skype it recreates it. That's possible only if you are root. That's the most essential info. Please, annouce it everytime you have any error at the very beginning of an e-mail with capital letters. Never work as root. Never-never work as root under X. -- WBR, bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Boris Samorodov wrote: That's possible only if you are root. That's the most essential info. Please, annouce it everytime you have any error at the very beginning of an e-mail with capital letters. Never work as root. Never-never work as root under X. I don't work as root. /compat/linux diectory is owned by my user, not root, not sure why. This is a very, very old system. Upgraded many times. That's how /compat/linux/home could get created. I can't understand why skype would create it instead of using /home. I guess that's a side effect of /compat/linux not being owned by root. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
googleearth complains about file instance-running-lock
Hi, I am getting this fatal error: Unable to create symlink for lock '/home/yuri/.googleearth/instance-running-lock'. File exists. google-earth-5.1.3509.4636 8.0-STABLE Thanks, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
On Thu, Dec 10, 2009 at 8:39 PM, Yuri y...@rawbw.com wrote: Hi, I am getting this fatal error: Unable to create symlink for lock '/home/yuri/.googleearth/instance-running-lock'. File exists. Remove the file? Or rename it? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Glen Barber wrote: Remove the file? Or rename it? I wouldn't ask this question if it was that easy. There is even no such directory: /home/yuri/.googleearth Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
On Thu, Dec 10, 2009 at 8:46 PM, Yuri y...@rawbw.com wrote: Glen Barber wrote: Remove the file? Or rename it? I wouldn't ask this question if it was that easy. There is even no such directory: /home/yuri/.googleearth Could you provide possibly important information such as this in future questions? Have you tried creating the directory? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Glen Barber wrote: Have you tried creating the directory? Creating it doesn't help. But I solved the problem: when it talks about /home/yuri/~.googleearth it actually means /compat/linux/home/yuri/.googleearth/ Deleting file there fixes the problem. I guess it's a good idea to have a link /compat/linux/home -/home Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: googleearth complains about file instance-running-lock
Yuri wrote: Glen Barber wrote: Remove the file? Or rename it? I wouldn't ask this question if it was that easy. There is even no such directory: /home/yuri/.googleearth Check /compat/linux/home/yuri/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: googleearth complains about file instance-running-lock
On Fri, 11 Dec 2009 06:44:26 + Matthew Seaman wrote: Yuri wrote: Glen Barber wrote: Remove the file? Or rename it? I wouldn't ask this question if it was that easy. There is even no such directory: /home/yuri/.googleearth Check /compat/linux/home/yuri/ ...and remove /compat/linux/home if it exists. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0-RC3 USB lock up on mounting two partitions from one USB drive
When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-sta...@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
It looks like a system issue since it also happens to the SATA drive. The USB drive seems having more difficulty. I will back up rest partitions, Then redo the slice and partition to see if problem goes away. If so, then 8.0-R has a backward compatibility issue on the partition table or format to older FreeBSD release. -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Wednesday, November 18, 2009 3:14 AM To: freebsd-...@freebsd.org Cc: Guojun Jin; freebsd-sta...@freebsd.org; questi...@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-sta...@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-sta...@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Lock order reversals on RELENG_8
Hi, Are these lock order reversals reported any reason for preoccupation and/or should I report elsewhere? The kernel I just built does not boot at all, so I don´t know whether these are a closed issue already. I´m off for a couple of days and will retry then. Thanks regards, Peter. --- Note: Kernels are GENERIC w/o i386/i486 options, Plus from no 4 onwards with VIMAGE and w/o SCTP option, All fs encrypted with geli except /. --- Aug 16 13:51:56 netserv kernel: FreeBSD 8.0-BETA2 #3: Sun Aug 16 10:28:08 UTC 2009 Aug 16 13:51:56 netserv kernel: r...@netserv.ka.cornelius:/usr/Obj-RELENG_8/usr/Src-RELENG_8/sys/NETSERV Aug 16 13:51:56 netserv kernel: WARNING: WITNESS option enabled, expect reduced performance. Aug 16 13:51:56 netserv kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Aug 16 13:51:56 netserv kernel: CPU: Intel Pentium III (1004.52-MHz 686-class CPU) Aug 16 13:51:56 netserv kernel: Origin = GenuineIntel Id = 0x686 Stepping = 6 Aug 16 13:51:56 netserv kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR,SSE Aug 16 13:51:56 netserv kernel: real memory = 1610612736 (1536 MB) Aug 16 13:51:56 netserv kernel: avail memory = 1559375872 (1487 MB) Aug 16 13:51:56 netserv kernel: ACPI APIC Table: ASUS CUV4X-D Aug 16 13:51:56 netserv kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Aug 16 13:51:56 netserv kernel: FreeBSD/SMP: 2 package(s) x 1 core(s) Aug 16 13:51:56 netserv kernel: cpu0 (BSP): APIC ID: 3 Aug 16 13:51:56 netserv kernel: cpu1 (AP): APIC ID: 0 (...) Aug 16 13:58:56 netserv kernel: lock order reversal: Aug 16 13:58:56 netserv kernel: 1st 0xd8d413f0 bufwait (bufwait) @ /usr/Src-RELENG_8/sys/kern/vfs_bio.c:2559 Aug 16 13:58:56 netserv kernel: 2nd 0xc5782000 dirhash (dirhash) @ /usr/Src-RELENG_8/sys/ufs/ufs/ufs_dirhash.c:285 Aug 16 13:58:56 netserv kernel: KDB: stack backtrace: Aug 16 13:58:56 netserv kernel: db_trace_self_wrapper(c0c73804,e782c75c,c08c0d25,c08b1a0b,c0c7675b,...) at db_trace_self_wrapper+0x26 Aug 16 13:58:56 netserv kernel: kdb_backtrace(c08b1a0b,c0c7675b,c4d2be90,c4d2f228,e782c7b8,...) at kdb_backtrace+0x29 Aug 16 13:58:56 netserv kernel: _witness_debugger(c0c7675b,c5782000,c0c97efa,c4d2f228,c0c97b8a,...) at _witness_debugger+0x25 Aug 16 13:58:56 netserv kernel: witness_checkorder(c5782000,9,c0c97b8a,11d,0,...) at witness_checkorder+0x839 Aug 16 13:58:56 netserv kernel: _sx_xlock(c5782000,0,c0c97b8a,11d,c58d9ae0,...) at _sx_xlock+0x85 Aug 16 13:58:56 netserv kernel: ufsdirhash_acquire(d8d41390,da0ab800,200,da0ab818,e782c888,...) at ufsdirhash_acquire+0x35 Aug 16 13:58:56 netserv kernel: ufsdirhash_add(c58d9ae0,e782c8d0,818,e782c874,e782c878,...) at ufsdirhash_add+0x13 Aug 16 13:58:56 netserv kernel: ufs_direnter(c596953c,c596696c,e782c8d0,e782cbd0,0,...) at ufs_direnter+0x729 Aug 16 13:58:56 netserv kernel: ufs_makeinode(e782cbd0,0,e782cabc,e782ca18,c0bbc895,...) at Aug 16 13:58:56 netserv kernel: ufs_makeinode+0x508 Aug 16 13:58:56 netserv kernel: ufs_create(e782cabc,e782cad4,0,0,e782cba4,...) at ufs_create+0x30 Aug 16 13:58:56 netserv kernel: VOP_CREATE_APV(c0d77740,e782cabc,e782cbd0,e782ca54,0,...) at VOP_CREATE_APV+0xa5 Aug 16 13:58:56 netserv kernel: vn_open_cred(e782cba4,e782cc5c,1a4,0,c51d2b00,...) at vn_open_cred+0x215 Aug 16 13:58:56 netserv kernel: vn_open(e782cba4,e782cc5c,1a4,c51fadc8,c0c98f76,...) at vn_open+0x3b Aug 16 13:58:56 netserv kernel: kern_openat(c5232000,ff9c,28412180,0,a02,...) at kern_openat+0x11f Aug 16 13:58:56 netserv kernel: kern_open(c5232000,28412180,0,a01,1a4,...) at kern_open+0x35 Aug 16 13:58:56 netserv kernel: open(c5232000,e782ccf8,c,c0c77024,c0d55f6c,...) at open+0x30 Aug 16 13:58:56 netserv kernel: syscall(e782cd38) at syscall+0x2a3 Aug 16 13:58:56 netserv kernel: Xint0x80_syscall() at Xint0x80_syscall+0x20 Aug 16 13:58:56 netserv kernel: --- syscall (5, FreeBSD ELF32, open), eip = 0x28335923, esp = 0xbfbfe7bc, ebp = 0xbfbfe7e8 --- (...) Aug 16 14:16:04 netserv kernel: lock order reversal: Aug 16 14:16:04 netserv kernel: 1st 0xc6df37ac ufs (ufs) @ /usr/Src-RELENG_8/sys/kern/vfs_lookup.c:497 Aug 16 14:16:04 netserv kernel: 2nd 0xd8debf40 bufwait (bufwait) @ /usr/Src-RELENG_8/sys/ufs/ffs/ffs_softdep.c:6177 Aug 16 14:16:04 netserv kernel: 3rd 0xc6e3f164 ufs (ufs) @ /usr/Src-RELENG_8/sys/kern/vfs_subr.c:2083 Aug 16 14:16:04 netserv kernel: KDB: stack backtrace: Aug 16 14:16:04 netserv kernel: db_trace_self_wrapper(c0c73804,e78b33cc,c08c0d25,c08b1a0b,c0c76774,...) at db_trace_self_wrapper+0x26 Aug 16 14:16:04 netserv kernel: kdb_backtrace(c08b1a0b,c0c76774,c4d2be90,c4d2f1c0,e78b3428,...) at kdb_backtrace+0x29 Aug 16 14:16:04 netserv kernel: _witness_debugger(c0c76774,c6e3f164,c0c690c7,c4d2f1c0,c0c7db33,...) at _witness_debugger+0x25 Aug 16 14:16:04 netserv kernel: witness_checkorder(c6e3f164,9,c0c7db33,823,0,...) at witness_checkorder+0x839 Aug 16 14:16:04 netserv kernel: __lockmgr_args
Re: Lock order reversals on RELENG_8
On Thu, Aug 20, 2009 at 2:08 PM, Peter Corneliusp...@gmx.net wrote: Hi, Are these lock order reversals reported any reason for preoccupation and/or should I report elsewhere? The kernel I just built does not boot at all, so I don´t know whether these are a closed issue already. I´m off for a couple of days and will retry then. Maybe the link reported here[1] could be useful. Cheers. [1]http://lists.freebsd.org/pipermail/freebsd-questions/2009-July/202308.html Thanks regards, Peter. --- Note: Kernels are GENERIC w/o i386/i486 options, Plus from no 4 onwards with VIMAGE and w/o SCTP option, All fs encrypted with geli except /. --- Aug 16 13:51:56 netserv kernel: FreeBSD 8.0-BETA2 #3: Sun Aug 16 10:28:08 UTC 2009 Aug 16 13:51:56 netserv kernel: r...@netserv.ka.cornelius:/usr/Obj-RELENG_8/usr/Src-RELENG_8/sys/NETSERV Aug 16 13:51:56 netserv kernel: WARNING: WITNESS option enabled, expect reduced performance. Aug 16 13:51:56 netserv kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Aug 16 13:51:56 netserv kernel: CPU: Intel Pentium III (1004.52-MHz 686-class CPU) Aug 16 13:51:56 netserv kernel: Origin = GenuineIntel Id = 0x686 Stepping = 6 Aug 16 13:51:56 netserv kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR,SSE Aug 16 13:51:56 netserv kernel: real memory = 1610612736 (1536 MB) Aug 16 13:51:56 netserv kernel: avail memory = 1559375872 (1487 MB) Aug 16 13:51:56 netserv kernel: ACPI APIC Table: ASUS CUV4X-D Aug 16 13:51:56 netserv kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Aug 16 13:51:56 netserv kernel: FreeBSD/SMP: 2 package(s) x 1 core(s) Aug 16 13:51:56 netserv kernel: cpu0 (BSP): APIC ID: 3 Aug 16 13:51:56 netserv kernel: cpu1 (AP): APIC ID: 0 (...) Aug 16 13:58:56 netserv kernel: lock order reversal: Aug 16 13:58:56 netserv kernel: 1st 0xd8d413f0 bufwait (bufwait) @ /usr/Src-RELENG_8/sys/kern/vfs_bio.c:2559 Aug 16 13:58:56 netserv kernel: 2nd 0xc5782000 dirhash (dirhash) @ /usr/Src-RELENG_8/sys/ufs/ufs/ufs_dirhash.c:285 Aug 16 13:58:56 netserv kernel: KDB: stack backtrace: Aug 16 13:58:56 netserv kernel: db_trace_self_wrapper(c0c73804,e782c75c,c08c0d25,c08b1a0b,c0c7675b,...) at db_trace_self_wrapper+0x26 Aug 16 13:58:56 netserv kernel: kdb_backtrace(c08b1a0b,c0c7675b,c4d2be90,c4d2f228,e782c7b8,...) at kdb_backtrace+0x29 Aug 16 13:58:56 netserv kernel: _witness_debugger(c0c7675b,c5782000,c0c97efa,c4d2f228,c0c97b8a,...) at _witness_debugger+0x25 Aug 16 13:58:56 netserv kernel: witness_checkorder(c5782000,9,c0c97b8a,11d,0,...) at witness_checkorder+0x839 Aug 16 13:58:56 netserv kernel: _sx_xlock(c5782000,0,c0c97b8a,11d,c58d9ae0,...) at _sx_xlock+0x85 Aug 16 13:58:56 netserv kernel: ufsdirhash_acquire(d8d41390,da0ab800,200,da0ab818,e782c888,...) at ufsdirhash_acquire+0x35 Aug 16 13:58:56 netserv kernel: ufsdirhash_add(c58d9ae0,e782c8d0,818,e782c874,e782c878,...) at ufsdirhash_add+0x13 Aug 16 13:58:56 netserv kernel: ufs_direnter(c596953c,c596696c,e782c8d0,e782cbd0,0,...) at ufs_direnter+0x729 Aug 16 13:58:56 netserv kernel: ufs_makeinode(e782cbd0,0,e782cabc,e782ca18,c0bbc895,...) at Aug 16 13:58:56 netserv kernel: ufs_makeinode+0x508 Aug 16 13:58:56 netserv kernel: ufs_create(e782cabc,e782cad4,0,0,e782cba4,...) at ufs_create+0x30 Aug 16 13:58:56 netserv kernel: VOP_CREATE_APV(c0d77740,e782cabc,e782cbd0,e782ca54,0,...) at VOP_CREATE_APV+0xa5 Aug 16 13:58:56 netserv kernel: vn_open_cred(e782cba4,e782cc5c,1a4,0,c51d2b00,...) at vn_open_cred+0x215 Aug 16 13:58:56 netserv kernel: vn_open(e782cba4,e782cc5c,1a4,c51fadc8,c0c98f76,...) at vn_open+0x3b Aug 16 13:58:56 netserv kernel: kern_openat(c5232000,ff9c,28412180,0,a02,...) at kern_openat+0x11f Aug 16 13:58:56 netserv kernel: kern_open(c5232000,28412180,0,a01,1a4,...) at kern_open+0x35 Aug 16 13:58:56 netserv kernel: open(c5232000,e782ccf8,c,c0c77024,c0d55f6c,...) at open+0x30 Aug 16 13:58:56 netserv kernel: syscall(e782cd38) at syscall+0x2a3 Aug 16 13:58:56 netserv kernel: Xint0x80_syscall() at Xint0x80_syscall+0x20 Aug 16 13:58:56 netserv kernel: --- syscall (5, FreeBSD ELF32, open), eip = 0x28335923, esp = 0xbfbfe7bc, ebp = 0xbfbfe7e8 --- (...) Aug 16 14:16:04 netserv kernel: lock order reversal: Aug 16 14:16:04 netserv kernel: 1st 0xc6df37ac ufs (ufs) @ /usr/Src-RELENG_8/sys/kern/vfs_lookup.c:497 Aug 16 14:16:04 netserv kernel: 2nd 0xd8debf40 bufwait (bufwait) @ /usr/Src-RELENG_8/sys/ufs/ffs/ffs_softdep.c:6177 Aug 16 14:16:04 netserv kernel: 3rd 0xc6e3f164 ufs (ufs) @ /usr/Src-RELENG_8/sys/kern/vfs_subr.c:2083 Aug 16 14:16:04 netserv kernel: KDB: stack backtrace: Aug 16 14:16:04 netserv kernel: db_trace_self_wrapper(c0c73804,e78b33cc,c08c0d25,c08b1a0b,c0c76774,...) at db_trace_self_wrapper+0x26 Aug 16 14:16:04 netserv kernel: kdb_backtrace(c08b1a0b,c0c76774,c4d2be90,c4d2f1c0,e78b3428,...) at kdb_backtrace
Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)
On Mon, Jul 27, 2009 at 07:37:26PM -0800, Mel Flynn wrote: On Monday 27 July 2009 18:35:17 Marc G. Fournier wrote: --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote: On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, I get this error: # /usr/local/etc/periodic/monthly/300.statistics /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0 : 34) == 0) failed That error from bind, [:1: unexpected operator Is not handled gracefully in the bsdstats script. Is there something I can do to improve the script to handle it better? Well, if OP can provide sh -x /usr/local/etc/periodic/monthly/300.statistics output, it's easier to see which variable is empty as a result of a resolver error. Then fix the test expression and either exit or use a retry_x_times mechanism. # script zzz sh -x /usr/local/etc/periodic/monthly/300.statistics -nodelay Script started on Tue Jul 28 11:14:53 2009 + [ -r /etc/defaults/periodic.conf ] + . /etc/defaults/periodic.conf + periodic_conf_files='/etc/periodic.conf /etc/periodic.conf.local' + local_periodic=/usr/local/etc/periodic + daily_output=root + daily_show_success=YES + daily_show_info=YES + daily_show_badconfig=NO + daily_clean_disks_enable=NO + daily_clean_disks_files='[#,]* .#* a.out *.core *.CKP .emacs_[0-9]*' + daily_clean_disks_days=3 + daily_clean_disks_verbose=YES + daily_clean_tmps_enable=NO + daily_clean_tmps_dirs=/tmp + daily_clean_tmps_days=3 + daily_clean_tmps_ignore='.X*-lock .X11-unix .ICE-unix .font-unix .XIM-unix' + daily_clean_tmps_ignore='.X*-lock .X11-unix .ICE-unix .font-unix .XIM-unix quota.user quota.group' + daily_clean_tmps_verbose=YES + daily_clean_preserve_enable=YES + daily_clean_preserve_days=7 + daily_clean_preserve_verbose=YES + daily_clean_msgs_enable=YES + daily_clean_msgs_days='' + daily_clean_rwho_enable=YES + daily_clean_rwho_days=7 + daily_clean_rwho_verbose=YES + daily_clean_hoststat_enable=YES + daily_backup_passwd_enable=YES + daily_backup_aliases_enable=YES + daily_calendar_enable=NO + daily_accounting_enable=YES + daily_accounting_compress=NO + daily_accounting_flags=-q + daily_accounting_save=3 + daily_news_expire_enable=YES + daily_status_disks_enable=YES + daily_status_disks_df_flags='-l -h' + daily_status_zfs_enable=NO + daily_status_ata_raid_enable=NO + daily_status_gmirror_enable=NO + daily_status_graid3_enable=NO + daily_status_gstripe_enable=NO + daily_status_gconcat_enable=NO + daily_status_network_enable=YES + daily_status_network_usedns=YES + daily_status_rwho_enable=YES + daily_status_mailq_enable=YES + daily_status_mailq_shorten=NO + daily_status_include_submit_mailq=YES + daily_status_security_enable=YES + daily_status_mail_rejects_enable=YES + daily_status_mail_rejects_logs=3 + daily_status_mail_rejects_shorten=NO + daily_status_named_enable=YES + daily_status_named_usedns=YES + daily_status_ntpd_enable=NO + daily_queuerun_enable=YES + daily_submit_queuerun=YES + daily_local=/etc/daily.local + daily_status_security_inline=NO + daily_status_security_output=root + daily_status_security_noamd=NO + daily_status_security_logdir=/var/log + daily_status_security_diff_flags='-b -u' + daily_status_security_chksetuid_enable=YES + daily_status_security_chkmounts_enable=YES + daily_status_security_chkuid0_enable=YES + daily_status_security_passwdless_enable=YES + daily_status_security_logincheck_enable=YES + daily_status_security_ipfwdenied_enable=YES + daily_status_security_ipfdenied_enable=YES + daily_status_security_pfdenied_enable=YES + daily_status_security_ipfwlimit_enable=YES + daily_status_security_ipf6denied_enable=YES + daily_status_security_kernelmsg_enable=YES + daily_status_security_loginfail_enable=YES + daily_status_security_tcpwrap_enable=YES + weekly_output=root + weekly_show_success=YES + weekly_show_info=YES + weekly_show_badconfig=NO + weekly_locate_enable=YES + weekly_whatis_enable=YES + weekly_catman_enable=NO + weekly_noid_enable=NO + weekly_noid_dirs=/ + weekly_status_pkg_enable=NO + pkg_version=pkg_version + pkg_version_index=/usr/ports/INDEX-8 + weekly_local=/etc/weekly.local + monthly_output=root + monthly_show_success=YES + monthly_show_info=YES + monthly_show_badconfig=NO + monthly_accounting_enable=YES + monthly_local=/etc/monthly.local + [ -z '' ] + source_periodic_confs_defined=yes + source_periodic_confs + local i sourced_files + sourced_files=:/etc/periodic.conf: + [ -r /etc/periodic.conf ] + . /etc/periodic.conf + monthly_statistics_enable=YES + monthly_statistics_report_devices=YES + monthly_statistics_report_ports=YES + sourced_files=:/etc/periodic.conf::/etc/periodic.conf.local: + [ -r /etc/periodic.conf.local ] + periodic_conf=/etc/periodic.conf + umask + oldmask=0022 + umask 066 + version=5.4 + checkin_server=rpt.bsdstats.org
bsdstats - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)
On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, I get this error: # /usr/local/etc/periodic/monthly/300.statistics /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0 : 34) == 0) failed [:1: unexpected operator # I recall some mutex errors reported by perl-10 tests. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)
On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote: On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, I get this error: # /usr/local/etc/periodic/monthly/300.statistics /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0 : 34) == 0) failed That error from bind, [:1: unexpected operator Is not handled gracefully in the bsdstats script. The annoyance is that ISC Bind finds it not useful to print errno, which is what you'd need to figure out why this lock can't be destroyed. It is however a programming error in bind, or a rare case of stack corruption by the kernel. If you see this error a lot or can reliably reproduce it, I'd file a PR. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote: On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, I get this error: # /usr/local/etc/periodic/monthly/300.statistics /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0 : 34) == 0) failed That error from bind, [:1: unexpected operator Is not handled gracefully in the bsdstats script. Is there something I can do to improve the script to handle it better? - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpuY+UACgkQ4QvfyHIvDvOquwCdGpyNjkbx2e/jt9TB48RX6JrD mJEAoL+l0a5UI3xCX/2/F+MJB5hPgIR/ =uH7U -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)
On Monday 27 July 2009 18:35:17 Marc G. Fournier wrote: --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote: On ia64 8.0-beta1 SMP, running bsdstats-5.4_2, I get this error: # /usr/local/etc/periodic/monthly/300.statistics /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0 : 34) == 0) failed That error from bind, [:1: unexpected operator Is not handled gracefully in the bsdstats script. Is there something I can do to improve the script to handle it better? Well, if OP can provide sh -x /usr/local/etc/periodic/monthly/300.statistics output, it's easier to see which variable is empty as a result of a resolver error. Then fix the test expression and either exit or use a retry_x_times mechanism. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Wednesday 15 July 2009 04:53:19 Jonathan McKeown wrote: On Wednesday 15 July 2009 12:45:02 Matthew Seaman wrote: I used to be a NeXTie, and the Screensaver.app there had a really nifty little feature. I'm surprised it's not been copied into other screensaver applications since, as it's pretty simple. They just had a facility where moving the mouse cursor to one corner of the screen and leaving it still for a few seconds would cause the screen saver / screen lock to come on straight away. KDE 3.5 provides this feature - it's under Advanced Options on the screensaver configuration. And 4.x too. Visually timed at ~3 seconds. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
Chad Perrin wrote: Does /usr/ports/x11/xscreensaver.app do this? It almost certainly requires the GNUStep framework as a dependency, but you may find a number of old friends (applications you liked) are available for that framework, in varying states of faithfulness to what you remember. If you like the old interface as a whole, you might try using WindowMaker with the GNUStep framework. I already do use WindowMaker -- it's actually a nice fairly light-weight X11 window manager in it's own right, even if you don't use it with all the GnuStep desktop apps. I'll check out xscreensaver.app shortly -- thanks for the tip. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Automatic screen lock when leaving desk
On Wednesday 15 July 2009 01:20:19 Frederique Rijsdijk wrote: I guess I'll look into the bluetooth thing. That looks quite doable. If you can spare the time, I'd appreciate write-up of how you got it working on FreeBSD as it's the first bluetooth application that seems worthwhile to me. I also remembered a gadget on thinkgeek [1], but unfortunately the software part requires windows. [1] http://www.thinkgeek.com/computing/accessories/76ed/ -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
Hi all, Frederique Rijsdijk wrote: I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? Thanks all for the replies. To answer some questions: - I prefer automatic. I already have a key on my kb mapped to 'xlockmore -mode blank', but in some rare cases I still forget to do it, or I'm in an application that overrides the mapping and the key will not work. I'm using a DasKeyboard, that doesn't have any 'unused' keys like media stuff. I guess I'll look into the bluetooth thing. That looks quite doable. Thanks! -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
Chad Perrin wrote: On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote: Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? Why does it have to be automatic? Something like xlockmore or slock can be tied to a keyboard shortcut, such as Ctrl+Alt+L. If for some reason you require automatic locking, though, you could perhaps set up some kind of Bluetooth connection detection if you have a Bluetooth enabled cellphone in your pocket (or something else that would work as a Bluetooth token) and if your computer has the right hardware. I imagine writing a daemon in Perl or Ruby that checks for loss of a Bluetooth connection would be easier than getting Bluetooth working in the first place might be, depending on the state of Bluetooth support in FreeBSD. I'm not really well-versed in the ephemera of what is used to determine inactivity on a computer, but if it's reasonably easy (or if there's a Perl module for it), that seems like the obvious way to handle it -- though of course that may present problems, such as false positives on detecting inactivity when watching a movie on the computer or something like that. I used to be a NeXTie, and the Screensaver.app there had a really nifty little feature. I'm surprised it's not been copied into other screensaver applications since, as it's pretty simple. They just had a facility where moving the mouse cursor to one corner of the screen and leaving it still for a few seconds would cause the screen saver / screen lock to come on straight away. Conversely you could designate another corner of the screen as don't turn on screensaver even after an extended period of idleness. Being a NeXT app this was all configurable by dragging little '+' or '-' icons around a scaled down image of the screen, or off it entirely if you didn't want that facility. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Automatic screen lock when leaving desk
On Wed, 15 Jul 2009 11:45:02 +0100, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: I used to be a NeXTie, and the Screensaver.app there had a really nifty little feature. I'm surprised it's not been copied into other screensaver applications since, as it's pretty simple. They just had a facility where moving the mouse cursor to one corner of the screen and leaving it still for a few seconds would cause the screen saver / screen lock to come on straight away. Conversely you could designate another corner of the screen as don't turn on screensaver even after an extended period of idleness. Being a NeXT app this was all configurable by dragging little '+' or '-' icons around a scaled down image of the screen, or off it entirely if you didn't want that facility. This feature has been implemented in the (original) Norton Commander (Version 4 or 5, I think), but just as a screensaver, no real lock. Remember, it was DOS. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Wednesday 15 July 2009 12:45:02 Matthew Seaman wrote: I used to be a NeXTie, and the Screensaver.app there had a really nifty little feature. I'm surprised it's not been copied into other screensaver applications since, as it's pretty simple. They just had a facility where moving the mouse cursor to one corner of the screen and leaving it still for a few seconds would cause the screen saver / screen lock to come on straight away. Conversely you could designate another corner of the screen as don't turn on screensaver even after an extended period of idleness. Being a NeXT app this was all configurable by dragging little '+' or '-' icons around a scaled down image of the screen, or off it entirely if you didn't want that facility. KDE 3.5 provides this feature - it's under Advanced Options on the screensaver configuration. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Wed, Jul 15, 2009 at 11:45:02AM +0100, Matthew Seaman wrote: I used to be a NeXTie, and the Screensaver.app there had a really nifty little feature. I'm surprised it's not been copied into other screensaver applications since, as it's pretty simple. They just had a facility where moving the mouse cursor to one corner of the screen and leaving it still for a few seconds would cause the screen saver / screen lock to come on straight away. Conversely you could designate another corner of the screen as don't turn on screensaver even after an extended period of idleness. Being a NeXT app this was all configurable by dragging little '+' or '-' icons around a scaled down image of the screen, or off it entirely if you didn't want that facility. Does /usr/ports/x11/xscreensaver.app do this? It almost certainly requires the GNUStep framework as a dependency, but you may find a number of old friends (applications you liked) are available for that framework, in varying states of faithfulness to what you remember. If you like the old interface as a whole, you might try using WindowMaker with the GNUStep framework. I actually used WindowMaker/GNUStep for a while, and liked it, but eventually decided I liked Sawfish slightly more, then that I liked AHWM a *lot* more. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Quoth Alan Kay: I invented the term 'Object-Oriented', and I can tell you I did not have C++ in mind. pgpc0w4wExAkF.pgp Description: PGP signature
Automatic screen lock when leaving desk
Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? It could be infrared based (heat signature), video based (webcam w/ motion detection) or even mechanical (switch in seat? meh..). And how would FreeBSD interface with such device? Most likely via USB, since my lt doesn't have any serial ports. Any ideas? Experience? -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
In response to Frederique Rijsdijk frederi...@isafeelin.org: I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? It could be infrared based (heat signature), video based (webcam w/ motion detection) or even mechanical (switch in seat? meh..). And how would FreeBSD interface with such device? Most likely via USB, since my lt doesn't have any serial ports. Any ideas? Experience? Unless your requirements are really as strict as you state, you're probably better off just installing xscreensaver and configuring it to lock the screen after a reasonable amount of inactivity. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
Hi, On Tue, Jul 14, 2009 at 11:32 AM, Frederique Rijsdijkfrederi...@isafeelin.org wrote: Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? It could be infrared based (heat signature), video based (webcam w/ motion detection) or even mechanical (switch in seat? meh..). And how would FreeBSD interface with such device? Most likely via USB, since my lt doesn't have any serial ports. Any ideas? Experience? There was an application about a year or so, Gnome based, that I saw in the Ubuntu repository. I just checked the ports tree, but unfortunately I don't see it. (I searched based on key, not name, because I forget the exact name.) It would connect to bluetooth on a cellular phone / smartphone, and if the bluetooth signal was lost (ie, you walked away) xscreensaver would kick in. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote: Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? Why does it have to be automatic? Something like xlockmore or slock can be tied to a keyboard shortcut, such as Ctrl+Alt+L. If for some reason you require automatic locking, though, you could perhaps set up some kind of Bluetooth connection detection if you have a Bluetooth enabled cellphone in your pocket (or something else that would work as a Bluetooth token) and if your computer has the right hardware. I imagine writing a daemon in Perl or Ruby that checks for loss of a Bluetooth connection would be easier than getting Bluetooth working in the first place might be, depending on the state of Bluetooth support in FreeBSD. I'm not really well-versed in the ephemera of what is used to determine inactivity on a computer, but if it's reasonably easy (or if there's a Perl module for it), that seems like the obvious way to handle it -- though of course that may present problems, such as false positives on detecting inactivity when watching a movie on the computer or something like that. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Quoth Paul Graham: SUVs are gross because they're the solution to a gross problem. (How to make minivans look more masculine.) pgps08FekitOV.pgp Description: PGP signature
Re: Re: Automatic screen lock when leaving desk
On 14 Jul 2009 21:43, Chad Perrin per...@apotheon.com wrote: On Tue, Jul 14, 2009 at 05:32:01PM +0200, Frederique Rijsdijk wrote: Hi, I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? Why does it have to be automatic? Something like xlockmore or slock can be tied to a keyboard shortcut, such as ++. If for some reason you require automatic locking, though, you could perhaps set up some kind of Bluetooth connection detection if you have a Bluetooth enabled cellphone in your pocket (or something else that would work as a Bluetooth token) and if your computer has the right hardware. I imagine writing a daemon in Perl or Ruby that checks for loss of a Bluetooth connection would be easier than getting Bluetooth working in the first place might be, depending on the state of Bluetooth support in FreeBSD. I'm not really well-versed in the ephemera of what is used to determine inactivity on a computer, but if it's reasonably easy (or if there's a Perl module for it), that seems like the obvious way to handle it -- though of course that may present problems, such as false positives on detecting inactivity when watching a movie on the computer or something like that. Although it would ravish your cellphone's battery Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Tuesday 14 July 2009 07:52:43 Bill Moran wrote: In response to Frederique Rijsdijk frederi...@isafeelin.org: I'm looking for a way to automaticaly lock my X session when I leave my desk. Probably just using 'xlockmore -mode blank' or such. But how to detect? It could be infrared based (heat signature), video based (webcam w/ motion detection) or even mechanical (switch in seat? meh..). And how would FreeBSD interface with such device? Most likely via USB, since my lt doesn't have any serial ports. Any ideas? Experience? Unless your requirements are really as strict as you state, you're probably better off just installing xscreensaver and configuring it to lock the screen after a reasonable amount of inactivity. And use xev to figure out the keycode of an unused key on your keyboard you can easily access (like multimedia keys). Then you can activate it when leaving your spot or when that creepy guy from accounting tries to look over your shoulder. You would probably need some window/session manager that supports global key shortcuts. I like the bluetooth idea too, with the caveat that the range might not be sufficient. There's an article about it here: http://johnny.chadda.se/2007/08/09/lock-and-unlock-your-gnome-screensaver-using-your-bluetooth-phone/ I don't use bluetooth at all, so can't help you with the FreeBSD specifics. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Tue, 14 Jul 2009 14:03:04 -0800, Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: And use xev to figure out the keycode of an unused key on your keyboard you can easily access (like multimedia keys). Then you can activate it when leaving your spot or when that creepy guy from accounting tries to look over your shoulder. You would probably need some window/session manager that supports global key shortcuts. Just as an example, I do use this with WindowMaker. My Sun Type 6 keyboard has a nice double-width button Help in the upper left - excellent for hitting it when leaving the workstation. It is connected with the xlock command. I like the bluetooth idea too, with the caveat that the range might not be sufficient. To make it more complicated, what about wearing some specific USB device on your clothes, attached to a chain, and when you leave the computer, it will pop out of the USB socket and therefore cause xlock to be called? :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
To make it more complicated, what about wearing some specific USB device on your clothes, attached to a chain, and when you leave the computer, it will pop out of the USB socket and therefore cause xlock to be called? :-) Haha... Polytropon's witty responses are enough reason in themselves to monitor this mailing list :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Wed, Jul 15, 2009 at 12:35:24AM +0200, Polytropon wrote: To make it more complicated, what about wearing some specific USB device on your clothes, attached to a chain, and when you leave the computer, it will pop out of the USB socket and therefore cause xlock to be called? :-) Does FreeBSD still have the kernel panic when mounted USB storage devices are detached without unmounting problem? If so, you could just mount a USB storage device, and unplug it when you leave the keyboard. Then your computer would be safe from snooping, because it would kernel panic every time you walk away! -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Quoth Larry Wall: You can never entirely stop being what you once were. That's why it's important to be the right person today, and not put it off till tomorrow. pgpTOQ9RgOEGA.pgp Description: PGP signature
Re: Automatic screen lock when leaving desk
On Tue, 14 Jul 2009 18:33:50 -0600, Chad Perrin per...@apotheon.com wrote: On Wed, Jul 15, 2009 at 12:35:24AM +0200, Polytropon wrote: To make it more complicated, what about wearing some specific USB device on your clothes, attached to a chain, and when you leave the computer, it will pop out of the USB socket and therefore cause xlock to be called? :-) Does FreeBSD still have the kernel panic when mounted USB storage devices are detached without unmounting problem? Hmmm... How do other operating systems react if you suddenly remove a direct storage media that is just read from or written to? Do other operating systems go like, Oh wow, the hard disk just disappeared, so then I will write the data on another hard disk... :-) As far as I know, there are some tools like DBUS and HAL that make using USB sticks more easy in terms of automount if plugged in, autoumount when removed, but I have to be honest: I don't use any automount feature (due to security reasons), so in my opinion it's always safe to first umount, then remove. If so, you could just mount a USB storage device, and unplug it when you leave the keyboard. Then your computer would be safe from snooping, because it would kernel panic every time you walk away! I first thought about that, too, but in my opinion it's not needed to mount whatever you plug in as USB device, maybe a defective MP3 player made from crap, a memory stick or who knows what. The lock / unlock action could be assigned to the simple presence of the device. And: Yes, I know, that's a very stupid idea. :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic screen lock when leaving desk
On Tuesday 14 July 2009 17:36:24 Polytropon wrote: so in my opinion it's always safe to first umount, then remove. Kids (or aging muscles) force you to revise your view. Not to mention low quality USB camera cables. AFAIK the panic is resolved in 8.x though. Not sure about the 7.x series. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Determining file on which process is trying to acquire lock / fbsd 7.1
Hello!
I have a web server running nginx + php-fpm FreeBSD 7.1-RELEASE. When
traffic increases, the load doesn't go up noticeably, but I start getting
massive timeouts because the php-cgi processes stop responding. In top, I
see a whole bunch of these php-cgi processes in lockf state, so I assume
they're blocking while trying to acquire a lock on some file.
I tried using truss to see where this is occurring and get a lot of the
following:
# truss -p 77214
...
poll({10/POLLIN|POLLERR|POLLHUP},1,1000) = 1 (0x1)
recvfrom(10,STORED\r\n,8192,0x80,NULL,0x0) = 8 (0x8)
close(10)= 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
fcntl(4,F_SETLKW,0x7fffc580) = 0 (0x0)
...
That last line is repeated about 20 times, then the process seems to get the
lock and go about its business, and then repeat. There always seems to be a
pause in the truss output to my terminal after the
poll({10/POLLIN|POLLERR|POLLHUP},1,1000) line as well.
Is there a way to determine which file the process is trying to set a lock
on? Or any other way to troubleshoot the cause of this problem?
I tried running lsof -p 77214, which showed a long list of files used by
the process, but I didn't see anything about it trying to get a lock on a
file. Googling suggests that pfiles on Solaris might help with this -- is
there an analogous utility on FreeBSD?
Thanks a lot in advance for any advice you might have!
Antonio
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Determining file on which process is trying to acquire lock / fbsd 7.1
Antonio L. wrote: I tried running lsof -p 77214, which showed a long list of files used by the process, but I didn't see anything about it trying to get a lock on a file. Googling suggests that pfiles on Solaris might help with this -- is there an analogous utility on FreeBSD? # procstat -f $pid Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Num Lock key in X, PF keys, involves xmodmap, xev
Dear list, since I moved to a new keyboard, I have some trouble. Everything except the Num Lock functionality works fine. Let me explain: The keyboard is a BOSCOM PS/2 keyboard (with 122 keys, intended for 5250 operations on a PC) that contains a keyboard controller, so the keyboard can simply be attached to the PC. THis is how the keyboard looks like: http://www.ioconnections.com/images/products/bos_5250keyboard_black.jpg It's a very nice one, so I want to use it instead of my Sun USB keyboard because it has more and better keys. Think about the IBM model M. Same mechanics. The keyboard can operate in two different modes, which are selected by a jumper inside the keyboard (where the LEDs are located). In jumper mode, keys operate like their caption (the key cap) indicates it. For example, the keys on the left generate SysRq, Print, Escape and so on. Some of them generate composed characters, this means when I press a key, the keyboard sends a key combination, such as Alt+F3 for the key or Shift+F1 for F13. Quite useless. In no jumper mode, each key sends a unique keycode. Some keys do not do what their key cap says, but that's no problem because the caps can be re-arranged. And I've got enough space keycaps with very nice captions from other keyboards, so it's no problem to make my own layout be represented correctly by the key caps. This is the mode I need. Using the xev program, I could easily find out which keys generate which keycode, so I made a .xmodmaprc and assigned names to the different keys according to what I intended them to use. For example, F13 .. F24 now are described as F13 .. F24, so they can be assigned several actions by the means of the window manager, i. e. WindowMaker - easy game, e. g. starting programs or issuing a window arrangement command (front, background, roll up, hide, lock screen and so on). On the numerical keypad, I have a comma as well as a dot - in Germany, the comma is the decimal delimiter, so it's not possible to type IPs on the numeric keypad only. But now, I can do things like 192.168.1.1,192.168.1.2 all within the numerical keypad. Now my problem: I can't get the Num Lock to work. First of all, I checked which keycode would be generated when I press the key I want to have as Num Lock - it's the one placed where it should be on the standard 102 keys model, numerical keypad, upper left. This is the xev output when the key is pressed: KeyPress event, serial 27, synthetic NO, window 0x181, root 0x73, subw 0x0, time 1285024705, (76,91), root:(355,651), state 0x0, keycode 9 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False The keycode 9 (former Escape, I think) has been assigned to the key symbol Num_Lock by this entry in .xmodmaprc (file attached, I hope): ! Num keycode 9 = Num_Loc The comment, preceeded by !, states what is on the key cap, to make finding them easier. The problem is: Pressing this key doesn't change the Num state. So I checked man xmodmap and found out that there are modes that can be changed by certain keys. % xmodmap xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lockCaps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1Alt_L (0x40), Meta_L (0x9c) mod2Num_Lock (0x4d) mod3 mod4Super_L (0x7f), Hyper_L (0x80) mod5Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c) This output states that Num_Lock toggles mod2 - is this the Num mode? I checked it through this command: % xmodmap -e add mod2 = Num_Lock Ha! Pressing this key toggles Num now. Fine. No, not fine. Problem: The keys on the left as well as the 2nd row of function keys does not work anymore. If I switch off Num, they work again. Huh? I didn't have that on the Sun keyboard, there using the keys on the left (which I assigned F13 .. F27) always worked, no matter if Num was on or off. However, xev tells me that the correct symbols are emitted when I press the key, but the actions that have been assigned don't work anymore. So, for example, F13 doesn't launch Opera anymore. KeyPress event, serial 27, synthetic NO, window 0x181, root 0x73, subw 0x0, time 1285459063, (175,3), root:(362,537), state 0x10, keycode 181 (keysym 0xffca, F13), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False But when I turn Num off and press F13, it works again. And as I said, I didn't have such kind of behaviour with the Sun model. Basically, I'm doing the same. What am I doing wrong here? What am I missing? Ideas, anyone? =^_^= PS. Follow-up question: What
Re: Num Lock key in X, PF keys, involves xmodmap, xev
Additional information, just recognized: When Num Lock is on (as described in my first message), some window manager functions don't work anymore: When doubleclicking on a title bar, the window does not roll up. When pressing Alt and dragging a window with the left mouse button, the window does not move. If Num Lock is switched off, it works as intended. With Num Lock on, other things still work, such as pressing Ctrl and Shift and double- clicking on the title bar maximizes the window (Ctrl alone maximizes vertically, and Shift horizontally). Pressing Alt and clicking left on the title bar sets the window into the background. (For most of these functionalities, I'd like to use the 2x5 keys on the left as I did it with the Sun keyboard.) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Num Lock key in X, PF keys, involves xmodmap, xev
On 7/5/09, Polytropon free...@edvax.de wrote: Additional information, just recognized: When Num Lock is on (as described in my first message), some window manager functions don't work anymore: When doubleclicking on a title bar, the window does not roll up. When pressing Alt and dragging a window with the left mouse button, the window does not move. If Num Lock is switched off, it works as intended. With Num Lock on, other things still work, such as pressing Ctrl and Shift and double- clicking on the title bar maximizes the window (Ctrl alone maximizes vertically, and Shift horizontally). Pressing Alt and clicking left on the title bar sets the window into the background. (For most of these functionalities, I'd like to use the 2x5 keys on the left as I did it with the Sun keyboard.) Functionality you are seeking is trivial in fvwm2 case. There is IgnoreModifiers [L][2][5] command. In syscons(4) case available functionality is somehow limited ... -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stale lock files
Hi, What are stale lock files? I've been having them for a few weeks now, they need to go away! r...@curly /root# portupgrade -a ** Stale lock file was found. Removed. ** Stale lock file was found. Removed. [...] r...@curly /root# portversion -c ** Stale lock file was found. Removed. # # p5-BerkeleyDB # needs updating (port has 0.39) # pkgs=$pkgs p5-BerkeleyDB-0.38 # # portaudit # needs updating (port has 0.5.13) # pkgs=$pkgs portaudit-0.5.12 # # ruby # needs updating (port has 1.8.7.160_3,1) # pkgs=$pkgs ruby-1.8.7.160_1,1 if [ X$pkgs != X ]; then portupgrade $@ $pkgs fi Thanks, Charles -- Pretty women make us BUY beer. Ugly women make us DRINK beer. - Al Bundy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stale lock files
On Sat, 27 Jun 2009 10:00:24 -0500, Charles Howse cho...@charter.net wrote: What are stale lock files? I've been having them for a few weeks now, they need to go away! Lock files are used by several programs to indicate file-wise that they are running. The lock file is created when the program starts, and usually deleted when it ends. If it is interrupted (due to an error or ^C), the lock file isn't removed. Most programs remove stale lock files by theirselves when they are started again (e. g. fetchmail). It's possible that there are programs that refuse to start, because the lock file (falsely) indicates that the program is already running. The location of the lock file seems to depend on the respective program. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stale lock files
Charles Howse writes: What are stale lock files? I've been having them for a few weeks now, they need to go away! r...@curly /root# portupgrade -a ** Stale lock file was found. Removed. ** Stale lock file was found. Removed. [...] r...@curly /root# portversion -c ** Stale lock file was found. Removed. These are related to a (harmless) twitch in a recent version of ruby. Updating to the latest version fixed it for me. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stale lock files
On Jun 27, 2009, at 10:42 AM, Robert Huff wrote: Charles Howse writes: What are stale lock files? I've been having them for a few weeks now, they need to go away! r...@curly /root# portupgrade -a ** Stale lock file was found. Removed. ** Stale lock file was found. Removed. [...] r...@curly /root# portversion -c ** Stale lock file was found. Removed. These are related to a (harmless) twitch in a recent version of ruby. Updating to the latest version fixed it for me. Thanks Robert and Polytropon, Running 'portversion -c' after 'portupgrade -a' no longer shows any stale lock files. Just wondering...is there any utility to find and remove these things? Maybe a reboot? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stale lock files
Charles Howse writes: ** Stale lock file was found. Removed. These are related to a (harmless) twitch in a recent version of ruby. Updating to the latest version fixed it for me. Running 'portversion -c' after 'portupgrade -a' no longer shows any stale lock files. Just wondering...is there any utility to find and remove these things? Maybe a reboot? A successful run _after_ the aforementioned ruby upgrade should remove all the laggards. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GJournal: Out of cache force switch - With lock up
2009/5/13 David N david...@gmail.com: Hi, I'm running geom journal in debug and I'm seeing some GEOM_JOURNAL[1]: No cache, waking up the switcher. GEOM_JOURNAL[1]: Out of cache, force switch (used=.. limit=.. ) But on the journal i left 2GB, how come its running out of cache? or is that the journal cache that it flushes to disk? I've also managed to lock up the system, and just trying to pin point the problem. This is a 7.1R just upgraded to 7.2 with GPT + gmirror + gjournal with GENERIC kernel. All SSH no data. Local console is locked as well, but the num lock light turns on/off. I had gstat running, and all disk activity went to zero before it locked. I'm just cp -av from one gmirror to the new gmirror with journal. I've done it twice so far, with about 1 hour of copying and it'll lock up. Regards David N It happened again GEOM_JOURNAL[1]: Out of cache, force switch (used=175878656 limit=167772160). GEOM_JOURNAL[1]: Msync time of /usr: 0.156931s GEOM_JOURNAL[1]: Sync time of /usr: 0.006427s GEOM_JOURNAL[1]: Cache flush time: 0.267372s GEOM_JOURNAL[1]: BIO_FLUSH time of mirror/gm0p6: 0.267709s GEOM_JOURNAL[1]: Data has been copied. GEOM_JOURNAL[1]: Data has been copied. GEOM_JOURNAL[1]: Suspend time of /usr: 31.412925s GEOM_JOURNAL[1]: Starting copy of journal. GEOM_JOURNAL[1]: Cache flush time: 0.290278s GEOM_JOURNAL[1]: Cache flush time: 0.000101s GEOM_JOURNAL[1]: Switch time of mirror/gm0p6: 0.296598s GEOM_JOURNAL[1]: Msync time of /var: 0.31s GEOM_JOURNAL[1]: Sync time of /var: 0.48s GEOM_JOURNAL[1]: Cache flush time: 0.395199s GEOM_JOURNAL[1]: BIO_FLUSH time of mirror/gm0p5: 0.395694s GEOM_JOURNAL[1]: Suspend time of /var: 0.000226s GEOM_JOURNAL[1]: Starting copy of journal. GEOM_JOURNAL[1]: Cache flush time: 0.708414s GEOM_JOURNAL[1]: Cache flush time: 0.912773s GEOM_JOURNAL[1]: Switch time of mirror/gm0p5: 3.372491s GEOM_JOURNAL[1]: Entire switch time: 35.917632s managed to copy this before it locked up, the used is greater than the limit... Is there anything in sysctl i can tune to make it switch quicker? The last debug message is Data has been copied. Regards David N ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
GJournal: Out of cache force switch - With lock up
Hi, I'm running geom journal in debug and I'm seeing some GEOM_JOURNAL[1]: No cache, waking up the switcher. GEOM_JOURNAL[1]: Out of cache, force switch (used=.. limit=.. ) But on the journal i left 2GB, how come its running out of cache? or is that the journal cache that it flushes to disk? I've also managed to lock up the system, and just trying to pin point the problem. This is a 7.1R just upgraded to 7.2 with GPT + gmirror + gjournal with GENERIC kernel. All SSH no data. Local console is locked as well, but the num lock light turns on/off. I had gstat running, and all disk activity went to zero before it locked. I'm just cp -av from one gmirror to the new gmirror with journal. I've done it twice so far, with about 1 hour of copying and it'll lock up. Regards David N ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
hi... have a look here: http://docs.hp.com/en/5991-7517/ch01s04.html I think the cleanest solution would be to create a match block for your user, and apply the forcecommand within that block... -- Olli On Fr, 2009-03-13 at 21:50 -0400, Steve Bertrand wrote: Jonathan Chen wrote: On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote: [..] If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Change the contents of ~/.login to: exec vtysh This overlays the shell with vtysh. When it exits, the session will be closed. Thank you. This appears to be what I want. I was trying it with the previous setup, but I had to put the user in the wheel group. I haven't yet figured where permissions were going astray. Your procedure will allow me to put the user in the wheel group for now, knowing that logout will occur as soon as the program terminates. This way, I can safely know it works, and make myself a note for Monday to fix the permissions issues ;) Regards, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
And I think the cleanest solution would be to link .login to vtysh , make sure that your system logs out when it finishes this command or you can't use this technique. Steve Bertrand wrote (earlier today): I think the cleanest solution would be to create a match block for your user, and apply the forcecommand within that block... -- Olli On Fr, 2009-03-13 at 21:50 -0400, Steve Bertrand wrote: Jonathan Chen wrote: On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote: [..] If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Change the contents of ~/.login to: exec vtysh This overlays the shell with vtysh. When it exits, the session will be closed. Thank you. This appears to be what I want. I was trying it with the previous setup, but I had to put the user in the wheel group. I haven't yet figured where permissions were going astray. Your procedure will allow me to put the user in the wheel group for now, knowing that logout will occur as soon as the program terminates. This way, I can safely know it works, and make myself a note for Monday to fix the permissions issues ;) Regards, Steve Looking for insurance? Compare and save today. Click here. http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTInoLb38jeH2ZxV89B2QnR6ZNekJuaR3qGCHLhnMekVw3DI3haDtu/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Execute and lock a user into a program upon login
Hi everyone, Although the application of my question focuses on network operation, I believe that the objective fits this list. Mostly irrelevant, I have been working on securing my network perimeter. I have a FreeBSD box that acts as a host-based BGP peer to all edge connected routers. I use this host-based Quagga FBSD router to distribute routes that are to be blackholed by the edge devices. What I want is to set up an environment so that when a specific user logs in to the box via SSH, a command is run, and they immediately get dropped into the environment that the command produces. When they exit this 'command', the login session is dropped. Essentially, I want to 'lock' a user into a program upon SSH login, and drop them from the SSH session when the program terminates. In essence: - user 'router' connects via SSH - user is dropped into the application 'vtysh' - user performs operations - user exits from program - shell drops (ie. user does not have to exit the csh shell to drop the SSH connection) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
Steve Bertrand wrote: Hi everyone, Although the application of my question focuses on network operation, I believe that the objective fits this list. Mostly irrelevant, I have been working on securing my network perimeter. I have a FreeBSD box that acts as a host-based BGP peer to all edge connected routers. I use this host-based Quagga FBSD router to distribute routes that are to be blackholed by the edge devices. What I want is to set up an environment so that when a specific user logs in to the box via SSH, a command is run, and they immediately get dropped into the environment that the command produces. When they exit this 'command', the login session is dropped. Essentially, I want to 'lock' a user into a program upon SSH login, and drop them from the SSH session when the program terminates. In essence: - user 'router' connects via SSH - user is dropped into the application 'vtysh' - user performs operations - user exits from program - shell drops (ie. user does not have to exit the csh shell to drop the SSH connection) I probably should have explicitly stated that I'd like help as to how I would go about doing what I want to do, instead of simply stating my goals ;) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
On Fri, 13 Mar 2009 21:12:07 -0400, Steve Bertrand st...@ibctech.ca wrote: Steve Bertrand wrote: Hi everyone, Although the application of my question focuses on network operation, I believe that the objective fits this list. Mostly irrelevant, I have been working on securing my network perimeter. I have a FreeBSD box that acts as a host-based BGP peer to all edge connected routers. I use this host-based Quagga FBSD router to distribute routes that are to be blackholed by the edge devices. What I want is to set up an environment so that when a specific user logs in to the box via SSH, a command is run, and they immediately get dropped into the environment that the command produces. When they exit this 'command', the login session is dropped. Essentially, I want to 'lock' a user into a program upon SSH login, and drop them from the SSH session when the program terminates. In essence: - user 'router' connects via SSH - user is dropped into the application 'vtysh' - user performs operations - user exits from program - shell drops (ie. user does not have to exit the csh shell to drop the SSH connection) I probably should have explicitly stated that I'd like help as to how I would go about doing what I want to do, instead of simply stating my goals ;) If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Idea: When the application vtysh is terminated, the next command in the .login file will be executed, which is the logout command that will cause the login shell to exit. This will close the SSH connection as well. (I haven't checked this, sorry.) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
Polytropon wrote: On Fri, 13 Mar 2009 21:12:07 -0400, Steve Bertrand st...@ibctech.ca wrote: Steve Bertrand wrote: Hi everyone, Although the application of my question focuses on network operation, I believe that the objective fits this list. Mostly irrelevant, I have been working on securing my network perimeter. I have a FreeBSD box that acts as a host-based BGP peer to all edge connected routers. I use this host-based Quagga FBSD router to distribute routes that are to be blackholed by the edge devices. What I want is to set up an environment so that when a specific user logs in to the box via SSH, a command is run, and they immediately get dropped into the environment that the command produces. When they exit this 'command', the login session is dropped. Essentially, I want to 'lock' a user into a program upon SSH login, and drop them from the SSH session when the program terminates. In essence: - user 'router' connects via SSH - user is dropped into the application 'vtysh' - user performs operations - user exits from program - shell drops (ie. user does not have to exit the csh shell to drop the SSH connection) I probably should have explicitly stated that I'd like help as to how I would go about doing what I want to do, instead of simply stating my goals ;) If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Idea: When the application vtysh is terminated, the next command in the .login file will be executed, which is the logout command that will cause the login shell to exit. This will close the SSH connection as well. (I haven't checked this, sorry.) Thanks! No problem for lack of testing. To be honest, an extra 'exit' command via the shell is acceptable in this case, given that it will be only internal network ops working this anyway. I pretty much just wanted to provide a Cisco-like environment for adding a route upon login (as opposed to having to manually running the vtysh command). Manually logging out of a secure shell session is ok. I'll test the log out portion. If it works, that'd be most handy. Nonetheless, you've helped me out greatly. Cheers! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote: [..] If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Change the contents of ~/.login to: exec vtysh This overlays the shell with vtysh. When it exits, the session will be closed. -- Jonathan Chen j...@chen.org.nz We laugh in the face of danger, we drop icecubes down the vest of fear - Edmond Blackadder III ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Execute and lock a user into a program upon login
Jonathan Chen wrote: On Sat, Mar 14, 2009 at 02:18:27AM +0100, Polytropon wrote: [..] If the user's shell is csh (FreeBSD's standard dialog shell), you could achieve the goal: ~/.login vtysh logout Only problem: I don't know how the shell will act when the user terminates the vtysh application (^C)... Change the contents of ~/.login to: exec vtysh This overlays the shell with vtysh. When it exits, the session will be closed. Thank you. This appears to be what I want. I was trying it with the previous setup, but I had to put the user in the wheel group. I haven't yet figured where permissions were going astray. Your procedure will allow me to put the user in the wheel group for now, knowing that logout will occur as soon as the program terminates. This way, I can safely know it works, and make myself a note for Monday to fix the permissions issues ;) Regards, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 3ware array access lock up on 7.1-RC
Mel пишет: On Friday 26 December 2008 08:12:49 Artem Kuchin wrote: I am not even sure that it is related to freebsd, but maybe someone could point out the problem. We wanted to upgrade our hosting server from FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5 to FreeBSD 7.1 (RC for now), 9550SXU-4LP, raid 10 We have tested the new installation on ASUS P5K WS motherboard with PCI-X slot while the server kept running. The server has Supermicro X5DPE-G2 (pretty old one, 2004). So, when everything was ready, i just took out the old controller and disks and installed the new controller and the array disks. The system booted up, but when i started very intense file operations the file system just froze. The weird thing is that any open program which does not use filesystem kept running fine. For example, i could type and edit in open ee editor, but copying progress bar in midnight commander just stood still. If i tried to save file or open file or do anything disk related from ee in another console the program froze too, apparently waiting for disk system to reply forever (i tried waiting for 20 minutes). I could even connect to ssh port, but it does not auth because sshd needs to read something from the disk. I put everything back into Asus P5K WS and tested it. Everything worked fine again. Any idea what might going on here? OS bugs aside, a dead disk that keeps getting IO request explains all symptoms. Dead can also mean, faulty cable, buggy connector. I would expect the hardware raid controller to pick up on it though and remove it from the array. No, not the case here. As i said, the same controller with the same disks work perfectly on ASUS motherboard. -- Artem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 3ware array access lock up on 7.1-RC
On Friday 26 December 2008 08:12:49 Artem Kuchin wrote: I am not even sure that it is related to freebsd, but maybe someone could point out the problem. We wanted to upgrade our hosting server from FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5 to FreeBSD 7.1 (RC for now), 9550SXU-4LP, raid 10 We have tested the new installation on ASUS P5K WS motherboard with PCI-X slot while the server kept running. The server has Supermicro X5DPE-G2 (pretty old one, 2004). So, when everything was ready, i just took out the old controller and disks and installed the new controller and the array disks. The system booted up, but when i started very intense file operations the file system just froze. The weird thing is that any open program which does not use filesystem kept running fine. For example, i could type and edit in open ee editor, but copying progress bar in midnight commander just stood still. If i tried to save file or open file or do anything disk related from ee in another console the program froze too, apparently waiting for disk system to reply forever (i tried waiting for 20 minutes). I could even connect to ssh port, but it does not auth because sshd needs to read something from the disk. I put everything back into Asus P5K WS and tested it. Everything worked fine again. Any idea what might going on here? OS bugs aside, a dead disk that keeps getting IO request explains all symptoms. Dead can also mean, faulty cable, buggy connector. I would expect the hardware raid controller to pick up on it though and remove it from the array. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
3ware array access lock up on 7.1-RC
I am not even sure that it is related to freebsd, but maybe someone could point out the problem. We wanted to upgrade our hosting server from FreeBSD 6.2, 3ware 8506-4LP SATA RAID, raid 5 to FreeBSD 7.1 (RC for now), 9550SXU-4LP, raid 10 We have tested the new installation on ASUS P5K WS motherboard with PCI-X slot while the server kept running. The server has Supermicro X5DPE-G2 (pretty old one, 2004). So, when everything was ready, i just took out the old controller and disks and installed the new controller and the array disks. The system booted up, but when i started very intense file operations the file system just froze. The weird thing is that any open program which does not use filesystem kept running fine. For example, i could type and edit in open ee editor, but copying progress bar in midnight commander just stood still. If i tried to save file or open file or do anything disk related from ee in another console the program froze too, apparently waiting for disk system to reply forever (i tried waiting for 20 minutes). I could even connect to ssh port, but it does not auth because sshd needs to read something from the disk. I put everything back into Asus P5K WS and tested it. Everything worked fine again. Any idea what might going on here? -- Artem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Could not lock the file /var/tmp/gconf-test-locking-file-blah
Hello, I've installed FreeBSD 7.0-RELEASE #0 on an Acer Aspire 5100 laptop, and Gnome errors out when I try to start it. The kernel was compiled with no ehci support in order to get the laptop to not freeze on shutdown after syncing the disks, but there are no other major changes. I've installed gnome and all other packages from packages-7-stable/Lastest on the website, and it gives me the error from the subject line, 'Could not lock the file /var/tmp/gconf-test-locking-file-blah'. It says that it's an NFS locking error, but I'm not using NFS. Do you think that the packages from 7-stable are simply not compatible with 7.0-RELEASE (kde works fine), or is something else going on? My dmesg follows: Copyright (c) 1992-2008 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 7.0-RELEASE #0: Sat Nov 15 00:34:06 PST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOEHCI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-50 (1596.01-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x40f82 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x1fLAHF,CMP,SVM,ExtAPIC,CR8 Cores per package: 2 usable memory = 924700672 (881 MB) avail memory = 890621952 (849 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Nov 15 2008 00:33:42) acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, 1000 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_ec0: Embedded Controller: GPE 0x10 port 0x62,0x66 on acpi0 cpu0: ACPI CPU on acpi0 powernow0: PowerNow! K8 on cpu0 cpu1: ACPI CPU on acpi0 powernow1: PowerNow! K8 on cpu1 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x9000-0x90ff mem 0xc800-0xcfff,0xc010-0xc010 irq 17 at device 5.0 on pci1 pcib2: ACPI PCI-PCI bridge at device 4.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 5.0 on pci0 pci4: ACPI PCI bus on pcib3 ohci0: ATI SB400 USB Controller mem 0xc0004000-0xc0004fff irq 19 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: ATI SB400 USB Controller on ohci0 usb0: USB revision 1.0 uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 4 ports with 4 removable, self powered ohci1: ATI SB400 USB Controller mem 0xc0005000-0xc0005fff irq 19 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: ATI SB400 USB Controller on ohci1 usb1: USB revision 1.0 uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 4 ports with 4 removable, self powered pci0: serial bus, USB at device 19.2 (no driver attached) pci0: serial bus, SMBus at device 20.0 (no driver attached) atapci0: ATI IXP400 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8410-0x841f irq 16 at device 20.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pcm0: ATI SB450 High Definition Audio Controller mem 0xc000-0xc0003fff irq 16 at device 20.2 on pci0 pcm0: [ITHREAD] isab0: PCI-ISA bridge at device 20.3 on pci0 isa0: ISA bus on isab0 pcib4: ACPI PCI-PCI bridge at device 20.4 on pci0 pci6: ACPI PCI bus on pcib4 rl0: RealTek 8139 10/100BaseTX port 0xa000-0xa0ff mem 0xc021-0xc02100ff irq 21 at device 1.0 on pci6 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:16:d4:14:c8:0f rl0: [ITHREAD] ath0: Atheros 5212 mem 0xc020-0xc020 irq 22 at device 2.0 on pci6 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:16:ce:7f:d8:05 ath0: mac 7.8 phy 4.5 radio 5.6 cbb0: PCI-CardBus Bridge mem 0xc0211000-0xc0211fff irq 20 at device 4.0 on pci6 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb0: [ITHREAD] pci6: memory, flash at device 4.1 (no driver
Where are Lock Order Reversals
Aloha, Loading a FreeBSD 8 Current I get Lock Order Reversals. There used to be a site for looking into them. What do we do now? ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-STABLE lock order reversal
Kris Kennaway wrote: Per olof Ljungmark wrote: 7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Yes or try posting to net@ first. It looks like maybe the new multiple routing table support is implicated. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I tried to load the newest version of FreeBSD 7-STABLE and had the same error. I went back and used an older release and it didnt have this error. Does this happen on 8-CURRENT (I had problems with this on the 200707 CURRENT as well.) -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-STABLE lock order reversal
Al Plant wrote: Kris Kennaway wrote: Per olof Ljungmark wrote: 7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Yes or try posting to net@ first. It looks like maybe the new multiple routing table support is implicated. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha, I tried to load the newest version of FreeBSD 7-STABLE and had the same error. I went back and used an older release and it didnt have this error. Does this happen on 8-CURRENT (I had problems with this on the 200707 CURRENT as well.) Corrects Typo: Does this happen on 8-CURRENT (I had problems with this on the 200807 CURRENT as well.) -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-STABLE lock order reversal
Al Plant wrote: Kris Kennaway wrote: Per olof Ljungmark wrote: 7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Aloha, I tried to load the newest version of FreeBSD 7-STABLE and had the same error. I went back and used an older release and it didnt have this error. Does this happen on 8-CURRENT (I had problems with this on the 200707 CURRENT as well.) Out of curiosity, what do you use as router? In my case the problem occurs with an OpenBSD box that runs IPSec. --per ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-STABLE lock order reversal
Per olof Ljungmark wrote: Al Plant wrote: Kris Kennaway wrote: Per olof Ljungmark wrote: 7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Aloha, I tried to load the newest version of FreeBSD 7-STABLE and had the same error. I went back and used an older release and it didnt have this error. Does this happen on 8-CURRENT (I had problems with this on the 200707 CURRENT as well.) Out of curiosity, what do you use as router? In my case the problem occurs with an OpenBSD box that runs IPSec. --per ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Aloha Per, The one box was on an ATM circuit and the other behind a Freesco router / fire wall. Errors showed on reboot after installing from CDROM's of FreeBSD 7 and 8 -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
7-STABLE lock order reversal
7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Aug 19 22:12:47 kreutzman kernel: uhid0: Logitech G9 Laser Mouse, class 0/0, rev 2.00/50.00, addr 4 on uhub5 Aug 19 22:12:47 kreutzman kernel: lock order reversal: Aug 19 22:12:47 kreutzman kernel: 1st 0xc7077a14 rtentry (rtentry) @ /usr/src/sys/net/route.c:328 Aug 19 22:12:47 kreutzman kernel: 2nd 0xc6eee07c radix node head (radix node head) @ /usr/src/sys/net/route.c:879 Aug 19 22:12:47 kreutzman kernel: KDB: stack backtrace: Aug 19 22:12:47 kreutzman kernel: db_trace_self_wrapper(c0af8084,e71f5a4c,c07a777e,c0afa653,c6eee07c,...) at db_trace_self_wrapper+0x26 Aug 19 22:12:47 kreutzman kernel: kdb_backtrace(c0afa653,c6eee07c,c0afa6b4,c0afa6b4,c0b031c2,...) at kdb_backtrace+0x29 Aug 19 22:12:47 kreutzman kernel: witness_checkorder(c6eee07c,9,c0b031c2,36f,c6c5f2b8,...) at witness_checkorder+0x6de Aug 19 22:12:47 kreutzman kernel: _mtx_lock_flags(c6eee07c,0,c0b031c2,36f,c0af3ca5,...) at _mtx_lock_flags+0xbc Aug 19 22:12:47 kreutzman kernel: rtrequest1_fib(1,e71f5ae8,e71f5b18,0,ce,...) at rtrequest1_fib+0x82 Aug 19 22:12:47 kreutzman kernel: rtredirect_fib(e71f5bb8,e71f5ba8,0,16,e71f5b98,...) at rtredirect_fib+0x13d Aug 19 22:12:47 kreutzman kernel: in_rtredirect(e71f5bb8,e71f5ba8,0,6,e71f5b98,...) at in_rtredirect+0x34 Aug 19 22:12:47 kreutzman kernel: icmp_input(c7081d00,14,80246,c0bf53c0,e71f5c08,...) at icmp_input+0x526 Aug 19 22:12:47 kreutzman kernel: ip_input(c7081d00,14e,800,c6c89400,800,...) at ip_input+0x650 Aug 19 22:12:47 kreutzman kernel: netisr_dispatch(2,c7081d00,10,3,0,...) at netisr_dispatch+0x73 Aug 19 22:12:47 kreutzman kernel: ether_demux(c6c89400,c7081d00,3,0,3,...) at ether_demux+0x1f1 Aug 19 22:12:47 kreutzman kernel: ether_input(c6c89400,c7081d00,c0ac0c3e,c57,c6c89400,...) at ether_input+0x3d9 Aug 19 22:12:47 kreutzman kernel: bge_intr(c6c9,0,c0af18b8,442,c6b334e8,...) at bge_intr+0x7ca Aug 19 22:12:47 kreutzman kernel: ithread_loop(c6c946d0,e71f5d38,c0af1622,305,c6c97ad0,...) at ithread_loop+0x1c5 Aug 19 22:12:47 kreutzman kernel: fork_exit(c074ce40,c6c946d0,e71f5d38) at fork_exit+0xb8 Aug 19 22:12:47 kreutzman kernel: fork_trampoline() at fork_trampoline+0x8 Aug 19 22:12:47 kreutzman kernel: --- trap 0, eip = 0, esp = 0xe71f5d70, ebp = 0 --- Aug 19 22:12:47 kreutzman kernel: Expensive timeout(9) function: 0xc068b7f0(0xc0c82f00) 0.004460343 s Aug 19 22:12:47 kreutzman savecore: no dumps found ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-STABLE lock order reversal
Per olof Ljungmark wrote: 7.0-STABLE #0: Tue Aug 19 20:39:48 CEST 2008 After system update from June 12 sources to Aug 12 I have seen frequent lockups during network operations. Compiled debugging kernel and got the below during boot. Should I open a PR? Suggestions welcome. Thanks. Yes or try posting to net@ first. It looks like maybe the new multiple routing table support is implicated. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic: spin lock held too long when booting
On Tuesday 15 July 2008, Kris Kennaway wrote:
Mike Clarke wrote:
I'm getting frequent panics due to spin lock held too long when
booting my recently built 6.3 system with an Athlon 4850e dual core
processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and
nForce 430 chipsets).
[snip]
You should add options WITNESS also and this will probably generate
additional debugging and/or a panic before the error occurs.
I rebuilt the kernel yesterday and the system obligingly panicked for me
this morning. This time things went as far as letting me type in the
first 2 characters of my password on the KDM login screen then froze.
After a few minutes of inactivity I powered off and savecore even found
and saved the core dump when I rebooted.
There didn't appear to be any extra clues in dmesg or /var/log/messages.
I've no experience of interpreting dumps other than obtaining a
bactrace so any suggestions on what to do next would be very welcome.
Here's the backtrace:
curlew:/root# uname -a
FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #4: Tue Jul 15 17:40:18
BST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURLEW i386
curlew:/root# cd /usr/obj/usr/src/sys/CURLEW
curlew:/usr/obj/usr/src/sys/CURLEW# kgdb
kernel.debug /usr/crash/vmcore.2
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as i386-marcel-freebsd...
Unread portion of the kernel message buffer:
spin lock sio held by 0xc6a65780 for 5 seconds
exclusive spin mutex sio r = 0 (0xc07d4980) locked
@ /usr/src/sys/dev/sio/sio.c:1390
panic: spin lock held too long
cpuid = 1
Uptime: 45s
Dumping 1983 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 1983MB (507632 pages) 1967 1951 1935 1919 1903 1887 1871 1855
1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631
1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407
1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183
1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943
927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655
639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367
351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79
63 47 31 15
Reading symbols from /boot/kernel/linux.ko...done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/snd_ich.ko...done.
Loaded symbols for /boot/kernel/snd_ich.ko
Reading symbols from /boot/kernel/sound.ko...done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/atapicam.ko...done.
Loaded symbols for /boot/kernel/atapicam.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/cpufreq.ko...done.
Loaded symbols for /boot/kernel/cpufreq.ko
Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc052eaad in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:410
#2 0xc052ee03 in panic (fmt=0xc07170dc spin lock held too long)
at /usr/src/sys/kern/kern_shutdown.c:566
#3 0xc0525110 in _mtx_lock_spin (m=0xc07d4980, tid=3332789760, opts=0,
file=0xc072e277 /usr/src/sys/dev/sio/sio.c, line=1390)
at /usr/src/sys/kern/kern_mutex.c:634
#4 0xc0524df0 in _mtx_lock_spin_flags (m=0xc07d4980, opts=0,
file=0xc072e277 /usr/src/sys/dev/sio/sio.c, line=1390)
at /usr/src/sys/kern/kern_mutex.c:398
#5 0xc06b9b2a in siointr (arg=0x0) at /usr/src/sys/dev/sio/sio.c:1390
#6 0xc06d5a1c in intr_execute_handlers (isrc=0xc6a584a4,
iframe=0xe55c2c6c)
at /usr/src/sys/i386/i386/intr_machdep.c:271
#7 0xc06d87ca in lapic_handle_intr (frame=
{if_vec = 59, if_fs = 8, if_es = 40, if_ds = 40, if_edi
= -961263592, if_esi = -961263616, if_ebp = -446944080, if_ebx = 0,
if_edx = 0, if_ecx = 1000, if_eax = 1000, if_eip = -1055641643, if_cs =
32, if_eflags = 530, if_esp = -446944036, if_ss = -1055671695})
at /usr/src/sys/i386/i386/local_apic.c:637
#8 0xc06d18e3 in Xapic_isr1 () at apic_vector.s:110
#9 0xc1142fd5 in acpi_cpu_c1 () from /boot/kernel/acpi.ko
#10 0xc113ba71 in acpi_cpu_idle () from /boot/kernel/acpi.ko
#11 0xc06da5d8 in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1174
#12 0xc0514d85 in idle_proc (dummy=0x0)
at /usr/src/sys/kern/kern_idle.c:115
#13 0xc0514aa8 in fork_exit (callout=0xc0514d10 idle_proc, arg=0x3e8,
frame=0x3e8)
at /usr/src/sys/kern/kern_fork.c:788
#14 0xc06d158c in fork_trampoline ()
at /usr/src/sys/i386/i386/exception.s:208
(kgdb) quit
--
Mike Clarke
Panic: spin lock held too long when booting
I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21 BST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURLEW i386 I'd welcome any advice on how to understand and fix this. The panics usually happen immediately after the Mounting local filesystem message, but sometimes just before the end of the boot process. The system goes through the motions of producing a crash dump with a visible count down on the screen followed with... Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs ... then it just hangs until I do a hard reset. The odd thing is that when I reboot there doesn't appear to be any crash dump - I see the following messages: Checking for core dump on /dev/ad4s1b... savecore: no dumps found Is the lack of a dump due to some config error of mine, or an effect of the spin lock problem? Here's the head of my kernel file ... include GENERIC nocpu I486_CPU nocpu I586_CPU ident CURLEW nooptions COMPAT_FREEBSD4 # Compatible with FreeBSD4 nooptions COMPAT_FREEBSD5 # Compatible with FreeBSD5 options DDB options KDB options KDB_UNATTENDED ... the rest of the file is just nodevice lines for various devices I don't have. And from /etc/rc.conf ... dumpdir=/usr/crash dumpdev=/dev/ad4s1b Messages on the console while booting imply debugging is enabled... KDB: debugger backends: ddb KDB: current backend: ddb ... kernel dumps on /dev/ad4s1b ... But I'm still a bit dubious as to whether I've really managed to create a debugging kernel. I was under the impression that there should be some *.symbols files in the /boot/kernel directory but there aren't any (or is this just a rev. 7 thing?) and the kernel directory is only 24 MB. I also noticed when building the kernel there were lines like ... objcopy --strip-debug kernel.debug kernel ... though I do still have /usr/obj/usr/src/sys/CURLEW/kernel.debug. should I be doing something with this? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic: spin lock held too long when booting
Mike Clarke wrote: I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21 BST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURLEW i386 I'd welcome any advice on how to understand and fix this. The panics usually happen immediately after the Mounting local filesystem message, but sometimes just before the end of the boot process. The system goes through the motions of producing a crash dump with a visible count down on the screen followed with... Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs ... then it just hangs until I do a hard reset. The odd thing is that when I reboot there doesn't appear to be any crash dump - I see the following messages: Checking for core dump on /dev/ad4s1b... savecore: no dumps found Is the lack of a dump due to some config error of mine, or an effect of the spin lock problem? Here's the head of my kernel file ... include GENERIC nocpu I486_CPU nocpu I586_CPU ident CURLEW nooptions COMPAT_FREEBSD4 # Compatible with FreeBSD4 nooptions COMPAT_FREEBSD5 # Compatible with FreeBSD5 options DDB options KDB options KDB_UNATTENDED You should add options WITNESS also and this will probably generate additional debugging and/or a panic before the error occurs. But I'm still a bit dubious as to whether I've really managed to create a debugging kernel. I was under the impression that there should be some *.symbols files in the /boot/kernel directory but there aren't any (or is this just a rev. 7 thing?) and the kernel directory is only 24 MB. I also noticed when building the kernel there were lines like ... objcopy --strip-debug kernel.debug kernel ... though I do still have /usr/obj/usr/src/sys/CURLEW/kernel.debug. should I be doing something with this? You can just use it post-mortem with kgdb. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic: spin lock held too long when booting
On Tuesday 15 July 2008, Kris Kennaway wrote: Mike Clarke wrote: I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). [snip] You should add options WITNESS also and this will probably generate additional debugging and/or a panic before the error occurs. OK, done that. The first reboot came up OK, sods law being what it is the next few boots will be clean and I'll have to wait a while for results from the next panic but in the meantime here's the messages generated by WITNESS for the clean boot: curlew:/home/mike% grep WITNESS /var/run/dmesg.boot WARNING: WITNESS option enabled, expect reduced performance. WITNESS: spin lock scrlock not in order list WITNESS: spin lock intrcnt not in order list WITNESS: spin lock ctl.rm_mtx not in order list WITNESS: spin lock dev.rm_mtx not in order list ... do they give any clues? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic: spin lock held too long when booting
Mike Clarke wrote: On Tuesday 15 July 2008, Kris Kennaway wrote: Mike Clarke wrote: I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). [snip] You should add options WITNESS also and this will probably generate additional debugging and/or a panic before the error occurs. OK, done that. The first reboot came up OK, sods law being what it is the next few boots will be clean and I'll have to wait a while for results from the next panic but in the meantime here's the messages generated by WITNESS for the clean boot: curlew:/home/mike% grep WITNESS /var/run/dmesg.boot WARNING: WITNESS option enabled, expect reduced performance. WITNESS: spin lock scrlock not in order list WITNESS: spin lock intrcnt not in order list WITNESS: spin lock ctl.rm_mtx not in order list WITNESS: spin lock dev.rm_mtx not in order list ... do they give any clues? Not really, they are basically just advisory in this context (and fixed in later releases AFAIK). Unfortunately WITNESS can drastically change timing of events which can mask this kind of problem. If you can afford it, keep trying with it enabled for a while. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Lock order reversal submissions?
Does anybody happen to know where I can submit lock order reversal outputs (like the one below)? I don't want to spam freebsd-current and http://sources.zabbadoz.net/freebsd/lor.html seems to have not been updated in over a year now. Thanks - Tobias This is from 8.0-CURRENT: May 22 10:57:08 santafe kernel: lock order reversal: May 22 10:57:08 santafe kernel: 1st 0xc6768df4 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2044 May 22 10:57:08 santafe kernel: 2nd 0xc681cc94 devfsmount (devfsmount) @ /usr/src/sys/fs/devfs/devfs_vnops.c:293 May 22 10:57:08 santafe kernel: KDB: stack backtrace: May 22 10:57:08 santafe kernel: db_trace_self_wrapper(c0b28775,c63f9bb4,c07b908e,c0b2afd0,c681cc94,...) at db_trace_self_wrapper+0x26 May 22 10:57:08 santafe kernel: kdb_backtrace(c0b2afd0,c681cc94,c0b1be5e,c0b1be5e,c0b1be78,...) at kdb_backtrace+0x29 May 22 10:57:08 santafe kernel: witness_checkorder(c681cc94,9,c0b1be78,125,123,...) at witness_checkorder+0x6de May 22 10:57:08 santafe kernel: _sx_xlock(c681cc94,0,c0b1be78,125,c681cc94,...) at _sx_xlock+0x7d May 22 10:57:08 santafe kernel: devfs_allocv(c6858000,c686b000,c63f9c20,c6490d20,c6490dc4,...) at devfs_allocv+0x142 May 22 10:57:08 santafe kernel: devfs_root(c686b000,8,c0c9f334,c6490d20,4,...) at devfs_root+0x51 May 22 10:57:08 santafe kernel: set_rootvnode(c0c9f320,0,c0b30d78,5f6,c07f6a20,...) at set_rootvnode+0x2d May 22 10:57:08 santafe kernel: vfs_mountroot(c0c4c0d0,4,c0b20362,264,c63f9cc4,...) at vfs_mountroot+0x34c May 22 10:57:08 santafe kernel: start_init(0,c63f9d38,c0b21cf9,30d,c648ed0c,...) at start_init+0x65 May 22 10:57:08 santafe kernel: fork_exit(c0744e00,0,c63f9d38) at fork_exit+0xb8 May 22 10:57:08 santafe kernel: fork_trampoline() at fork_trampoline+0x8 May 22 10:57:08 santafe kernel: --- trap 0, eip = 0, esp = 0xc63f9d70, ebp = 0 --- May 22 10:57:08 santafe kernel: Trying to mount root from ufs:/dev/ad4s1a May 22 10:57:08 santafe kernel: lock order reversal: (sleepable after non-sleepable) May 22 10:57:08 santafe kernel: 1st 0xc68792c0 bufobj interlock (bufobj interlock) @ /usr/src/sys/kern/vfs_bio.c:2442 May 22 10:57:08 santafe kernel: 2nd 0xda4e5c80 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2456 May 22 10:57:08 santafe kernel: KDB: stack backtrace: May 22 10:57:08 santafe kernel: db_trace_self_wrapper(c0b28775,c63f9790,c07b908e,c0b2afd0,da4e5c80,...) at db_trace_self_wrapper+0x26 May 22 10:57:08 santafe kernel: kdb_backtrace(c0b2afd0,da4e5c80,c0b2fd41,c0b2fd41,c0b2f2f0,...) at kdb_backtrace+0x29 May 22 10:57:08 santafe kernel: witness_checkorder(da4e5c80,9,c0b2f2f0,998,c0b24355,...) at witness_checkorder+0x6de May 22 10:57:08 santafe kernel: __lockmgr_args(da4e5c80,81900,c68792c0,c0b2fc9d,50,...) at __lockmgr_args+0x777 May 22 10:57:08 santafe kernel: getblk(c6879218,0,0,800,0,...) at getblk+0x153 May 22 10:57:08 santafe kernel: breadn(c6879218,0,0,800,0,...) at breadn+0x44 May 22 10:57:08 santafe kernel: bread(c6879218,0,0,800,0,...) at bread+0x4c May 22 10:57:08 santafe kernel: ffs_blkatoff(c6879218,0,0,0,c63f99a8,...) at ffs_blkatoff+0xd1 May 22 10:57:08 santafe kernel: ufs_lookup(c63f99ec,c6879218,c63f9b50,c6879218,c63f9a0c,...) at ufs_lookup+0x2e6 May 22 10:57:08 santafe kernel: VOP_CACHEDLOOKUP_APV(c0c025c0,c63f99ec,c63f9b50,c63f9b3c,c645e300,...) at VOP_CACHEDLOOKUP_APV+0xa5 May 22 10:57:08 santafe kernel: vfs_cache_lookup(c63f9a6c,c63f9a6c,50c,8,c6879218,...) at vfs_cache_lookup+0xd0 May 22 10:57:08 santafe kernel: VOP_LOOKUP_APV(c0c025c0,c63f9a6c,c0b30b26,1b0,c63f9b3c,...) at VOP_LOOKUP_APV+0xa5 May 22 10:57:08 santafe kernel: lookup(c63f9b24,c0b30b26,d8,c0,c645e42c,...) at lookup+0x57e May 22 10:57:08 santafe kernel: namei(c63f9b24,c63f9b28,c07b886c,c076fe5c,c0c9ebd0,...) at namei+0x44b May 22 10:57:08 santafe kernel: kern_unlinkat(c6490d20,ff9c,c0b311b5,1,c63f9c5c,...) at kern_unlinkat+0x46 May 22 10:57:08 santafe kernel: kern_unlink(c6490d20,c0b311b5,1,631,0,...) at kern_unlink+0x27 May 22 10:57:08 santafe kernel: vfs_mountroot_try(c0b3136f,c0b1f07b,c0b17ad8,1,c07f6a20,...) at vfs_mountroot_try+0x472 May 22 10:57:08 santafe kernel: vfs_mountroot(c0c4c0d0,4,c0b20362,264,c63f9cc4,...) at vfs_mountroot+0x40e May 22 10:57:08 santafe kernel: start_init(0,c63f9d38,c0b21cf9,30d,c648ed0c,...) at start_init+0x65 May 22 10:57:08 santafe kernel: fork_exit(c0744e00,0,c63f9d38) at fork_exit+0xb8 May 22 10:57:08 santafe kernel: fork_trampoline() at fork_trampoline+0x8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lock order reversal submissions?
On Fri, May 23, 2008 at 05:26:29AM -0700, Tobias Hoellrich wrote: Does anybody happen to know where I can submit lock order reversal outputs (like the one below)? I don't want to spam freebsd-current and http://sources.zabbadoz.net/freebsd/lor.html seems to have not been updated in over a year now. Thanks - Tobias This is from 8.0-CURRENT: Most have been reported 2^N times and are harmless. If any have not, then report them to the mailing list. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SOLVED: minimalist config, (was Lock down the all-staff email list? sendmail, alias, majordomo?)
What is the best way to have a list that only certain users are able to send to? That sounds like you're getting into a full blown mailing0list package. I set up the minimalist port for a small list last year. Small very easy to config. I think it has the restriction you want. -R The majordomo and mailman were a bit more than what I was looking for. The minimalist port does look like it does exactly what I'm looking for, but I'm having an issue getting it configured. My minimalist port seems to have been installed in '/usr/local/share/minimalist' and the config file appears to be in '/usr/local/etc/minimalist.conf'. All files are under the '/usr/local/share' folder except the minimalist.conf in '/usr/local/etc' I have set the directory directive to '/usr/local/share/minimalist' in the '/usr/local/etc/minimalist.conf' and created my list directories under there, but I am not able to see it when I send 'info' message to '[EMAIL PROTECTED]'. reply from server for email with 'info' as subject: These are the mailing lists available at email.domain.com: -- Sincerely, the Minimalist under /usr/local/share/minimalist: My list.lst file has: farmThe Farm mailing list. southMailing list for Southern area. I have the farm and south directories with a very short list file: list: [EMAIL PROTECTED] [EMAIL PROTECTED] my /usr/local/etc/minimalist.conf (only non-commented lines) minimalist.conf directory = /usr/local/share/minimalist password = 12345 admin = [EMAIL PROTECTED] auth = mailfrom [EMAIL PROTECTED]:@/usr/local/etc/mml.trusted Any ideas where I might be going wrong? The mechanism seems to be working, as I can send messages to 'minimalist' and get info, but its not seeing my lists. Thanks the problem was: the auth = mailfrom line was in the global config, and that needed to be in the directory for the list. I commented the auth line out of the 'global config' /usr/local/etc/minimalist.conf and added it to the file 'config' under the 'farm' directory. yay it works now. thanks rob for pointing me at minimalist. _ Make every e-mail and IM count. Join the i’m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ MakeCount___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
