search for: mi_switch

...r somthing wrong to use it? Also, I don't know how to detect an error of writing to local device from hastd. Does anyone know about it? Thanks, Daisuke Aoyama -- the procstat shows like this: [root at nas4free-nodeb /tmp]# procstat -ka|grep hast 11668 100069 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep kern_wait sys_wait4 amd64_syscall Xfast_syscall 17981 100406 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17981 100559 hastd -...

...penldap slapd daemon. The slapd runs for some days and then hangs, consuming high amounts of CPU. In this state slapd can only be restarted by SIGKILL. # procstat -kk 71195 PID TID COMM TDNAME KSTACK 71195 149271 slapd - mi_switch+0x186 sleepq_catch_signals+0x2cc sleepq_wait_sig+0x16 _sleep+0x29d do_wait+0x678 __umtx_op_wait+0x68 amd64_syscall+0x546 Xfast_syscall+0xf7 71195 194998 slapd - mi_switch+0x186 sleepq_catch_signals+0x2cc sleepq_wait_sig+0x16 _cv_wait_sig+0x12e seltdwait+0x110 kern_select+...

...420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc sleepq_wait() at sleepq_wait+0x4d _sleep() at _sleep+0x3f6 ipmi_submit_driver_request() at ipmi_submit_driver_request+0x97 ipmi_set_watchdog() at ipmi_set_watchdog+0xb1 ipmi_wd_event() at ipmi_wd_event+0x8f kern_do_pat() at kern_do_pat+0x10...

Not sure what all to do, but doing a 'gdb -k kernel.debug /dev/mem', a backtrack on one of the processes shows ... server has been up 12 days now, and running a June 8th kernel ... #0 0x20f4f0 in ?? () (kgdb) proc 67258 (kgdb) bt #0 mi_switch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a3d2200, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479 #2 0x80141507 in acquire (lkp=0x8a3d2200, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 #3 0x8014179c in loc...

...psleep c0372fc0 vmdaemon 2 dc35cc60 defc5000 0 0 0 000204 3 psleep c0351e58 pagedaemon 1 dc35ce00 dc361000 0 0 1 004284 3 wait dc35ce00 init 0 c037b4a0 c040d000 0 0 0 000204 3 sched c037b4a0 swapper The hung tasks look like this: db> t 446 mi_switch(c34ab600,1000040,0,0,ffffffff) at mi_switch+0x1c8 tsleep(c34ab600,8,c031a54a,0,c34ab600) at tsleep+0x1d1 acquire(c34ab600,1000040,600,c34ab600,20002) at acquire+0xbc lockmgr(c34ab600,1030002,defc4e6c,e75e1220,defc4e00) at lockmgr+0x2cc vop_stdlock(e766bd28,e766bd38,c01fa02c,e766bd28,defc4e00) at vo...

...umass0: at uhub3, port 1, addr 2 (disconnected) At this point that particular USB port is effectively useless. Plugging anything into the ports shows no device showing up. Running usbconfig hangs with: PID TID COMM TDNAME KSTACK 48562 101874 usbconfig - mi_switch+0x186 sleepq_wait+0x42 _sx_xlock_hard+0x426 usbd_enum_lock+0xac usb_ref_device+0x21c usb_open+0xc7 devfs_open+0x197 vn_open_cred+0x2ff kern_openat+0x20a amd64_syscall+0x540 Xfast_syscall+0xf7 Controller is: uhci0@pci0:0:26:0: class=0x0c0300 card=0x02091028 chip=0x28348086 rev=0x02 hdr=0x...

neptune# ps -M vmcore.1 -N kernel.debug -axl | grep inode | wc -l 961 and I have a vmcore to work on here !! :) (kgdb) proc 99643 (kgdb) bt #0 mi_switch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a4ef600, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479 #2 0x80141507 in acquire (lkp=0x8a4ef600, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 #3 0x8014179c in loc...

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down

Hello! My attempt to build openoffice.org-3 seems to be hanging. Pressing Ctrl-T produces: load: 0.11 cmd: tcsh 79759 [sleeping without queue] 0.00u 0.00s 0% 0k (tcsh is used by OOo's build-script). What is this "sleeping without queue" state, and why is process in it for so long? This is an 4-CPU amd64 system with 4Gb of RAM. Only 16% of the swap is currently in use and

...t /usr/src/sys/kern/sched_ule.c:1932 1932 cpuid = PCPU_GET(cpuid); (kgdb) bt #0 sched_switch (td=0xffffff000235e8e0, newtd=<value optimized out>, flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1932 #1 0xffffffff80407836 in mi_switch (flags=260, newtd=0x0) at /usr/src/sys/kern/kern_synch.c:466 #2 0xffffffff8043e0e2 in sleepq_wait (wchan=0xffffff007f7e559c, pri=80) at /usr/src/sys/kern/subr_sleepqueue.c:613 #3 0xffffffff80407fc6 in _sleep (ident=0xffffff007f7e559c, lock=0xffffff007f7e...

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine

...= (struct thread *) 0x6 #14 0xc06ffb0c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 No locals. (kgdb) (kgdb) thread apply all bt Thread 175 (Thread 100290): #0 sched_switch (td=0xc7172000, newtd=0xc6bea780, flags=1) at /usr/src/sys/kern/sched_4bsd.c:959 #1 0xc0555eef in mi_switch (flags=1, newtd=0x0) at /usr/src/sys/kern/kern_synch.c:420 #2 0xc0573ff9 in sleepq_switch (wchan=0x0) at /usr/src/sys/kern/subr_sleepqueue.c:464 #3 0xc05741a1 in sleepq_wait_sig (wchan=0xc6d20010) at /usr/src/sys/kern/subr_sleepqueue.c:560 #4 0xc055592e in msleep (ident=0xc6d20010, mtx=0x0, p...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-12:08.linux Security Advisory The FreeBSD Project Topic: Linux compatibility layer input validation error Category: core Module: kernel

I've been playing around with snapshots lately but I've got a problem on one of my servers running 7-STABLE amd64: FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 I run the mksnap_ffs command to take the snapshot and some time later the system completely freezes up: paladin# cd /u2/.snap/ paladin#

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

...30 syscall(ed2ddd38) at syscall+0x2d3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (5, FreeBSD ELF32, open), eip = 0x281a161b, esp = 0xbfbfe8cc, ebp = 0xbfbfe8f8 --- db> trace 55 Tracing pid 55 tid 100054 td 0xc6fea460 sched_switch(c6fea460,0,1,17c,29bc06da,...) at sched_switch+0x49b mi_switch(1,0,c0b3ec35,1cb,c6fea460,...) at mi_switch+0x223 sleepq_switch(c6fea460,0,c0b3ec35,243,68,...) at sleepq_switch+0x182 sleepq_wait(c0c5666c,0,c0b3ba36,d8,0,...) at sleepq_wait+0x60 _sleep(c0c5666c,c0ca8988,68,c0b47461,0,...) at _sleep+0x369 sched_sync(0,eaff0d38,c0b37584,31c,c6febae0,...) at sched_...

Hello, Since FreeBSD 9.1 I have strange problems with the distribution. Some servers are rebooting without any kernel panic, instanly. First i thought it's a problem with my KVM system, but one of my FreeBSD under a Dell R210 have the same problem. The servers concerned are now: - Monitoring server - LDAP test server - Some other servers, randomly (not in production). First i thought it's

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained