search for: amd64_syscall

...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 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generi...

...e 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+0x6ef sys_select+0x5d amd64_syscall+0x546 Xfast_syscall+0xf7 71195 195544 slapd - mi_swi...

..._APV() at VOP_CREATE_APV+0xea/frame 0xfffffe0238a8f6e0 messages-Sep 26 02:01:27 leader kernel: vn_open_cred() at vn_open_cred+0x300/frame 0xfffffe0238a8f830 messages-Sep 26 02:01:27 leader kernel: kern_openat() at kern_openat+0x261/frame 0xfffffe0238a8f9a0 messages-Sep 26 02:01:27 leader kernel: amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe0238a8fab0 messages-Sep 26 02:01:27 leader kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0238a8fab0 messages-Sep 26 02:01:27 leader kernel: --- syscall (5, FreeBSD ELF64, sys_open), rip = 0x80185baca, rsp = 0x7fffffffd168, rbp = 0x7fffffffd1a0...

...102 #3 0xffffffff80678702 at vm_fault_unwire+0xd2 #4 0xffffffff80680841 at vm_map_delete+0x171 #5 0xffffffff80680abf at vm_map_remove+0x5f #6 0xffffffff80683ee9 at vmspace_exit+0xc9 #7 0xffffffff8041f3ad at exit1+0x72d #8 0xffffffff804203ae at sys_sys_exit+0xe #9 0xffffffff806afd6f at amd64_syscall+0x3bf #10 0xffffffff8069a817 at Xfast_syscall+0xf7 Uptime: 2d0h35m3s Fri Sep 20 17:49:57 2013 +1000 ozsrv04# kgdb kernel.debug /var/crash/vmcore.1 ... panic: vm_page_unwire: page 0xfffffe022f5fc238's wire count is zero cpuid = 2 KDB: stack backtrace: #0 0xffffffff80490268 at k...

...=0) at /usr/src/sys/kern/kern_event.c:1847 #8 0xffffffff808f4a5b in knote_fdclose (td=0xfffffe0009a34490, fd=9924) at /usr/src/sys/kern/kern_event.c:2065 #9 0xffffffff808ea573 in kern_close (td=0xfffffe0009a34490, fd=9924) at /usr/src/sys/kern/kern_descrip.c:1250 #10 0xffffffff80d127da in amd64_syscall (td=0xfffffe0009a34490, traced=0) at subr_syscall.c:135 #11 0xffffffff80cfcf57 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391 #12 0x00000008019e9a9c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Thanks, regards

Hello after upgrading to 9.2-release i can see periodical page faults. advises welcome. examples: 1. Fatal trap 12: page fault while in kernel mode cpuid = 5; apic id = 22 fault virtual address = 0x18 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8051095c stack pointer = 0x28:0xffffff88a9d77800 frame pointer =

Hi, after updating my freebsd amd64 box from 9.1 (r250841) to 9.2-RC (r254276) virtualbox crashes the machine. Seconds after starting VBOX the screen freezes and then reboots (probably a trap, cannot see it, as screen is in graphics mode). The kernel modules of vbox have been recompiled. Going back to 9.1 kernel and matching vbox modules works. In both cases VBOX 4.2.16 is used. cheers, Thomas

...map.c:422 #6 0xffffffff8045d725 in exit1 (td=0xfffffe0005a05470, rv=Variable "rv" is not available. ) at /usr/src/sys/kern/kern_exit.c:315 #7 0xffffffff8045e5ce in sys_sys_exit (td=Variable "td" is not available. ) at /usr/src/sys/kern/kern_exit.c:122 #8 0xffffffff8066737f in amd64_syscall (td=0xfffffe0005a05470, traced=0) at subr_syscall.c:135 #9 0xffffffff80652d97 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #10 0x0000000800d51c1c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Of course I may do something wrong, and I hope so but unfortunat...

...ffffe00039ae8e0, fd=Variable "fd" is not available. ) at file.h:293 #21 0xffffffff8053a4ad in sys_ioctl (td=0xfffffe00039ae8e0, uap=0xffffff80d89acb70) at /usr/src/sys/kern/sys_generic.c:691 ---Type <return> to continue, or q <return> to quit--- #22 0xffffffff806fc902 in amd64_syscall (td=0xfffffe00039ae8e0, traced=0) at subr_syscall.c:135 #23 0xffffffff806e84a7 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #24 0x0000000801d89c5c in ?? () Previous frame inner to this frame (corrupt stack?) Before the panic, a lot of ACPI Error appears in dmesg like t...

...owing 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=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) USB UHCI Controller' class = serial bus subclass = USB u...

...= 0 KDB: stack backtrace: #0 0xffffffff80920bb6 at kdb_backtrace+0x66 #1 0xffffffff808eabce at panic+0x1ce #2 0xffffffff80bd8640 at trap_fatal+0x290 #3 0xffffffff80bd897d at trap_pfault+0x1ed #4 0xffffffff80bd8f9e at trap+0x3ce #5 0xffffffff80bc355f at calltrap+0x8 #6 0xffffffff80bd7ee6 at amd64_syscall+0x546 #7 0xffffffff80bc3847 at Xfast_syscall+0xf7 Uptime: 21h22m6s Dumping 847 out of 4043 MB:..2%..12%..21%..31%..42%..51%..61%..72%..82%..91% Same result can be obtained on FreeBSD 9.1 Any patches, advices ? Thank you, Luke

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

...3c39 at devfs_destroy_cdevpriv+0x69 #7 0xffffffff80513e47 at devfs_close_f+0x57 #8 0xffffffff805b4b23 at _fdrop+0x23 #9 0xffffffff805b65ec at closef+0x4c #10 0xffffffff805b76cc at fdfree+0x23c #11 0xffffffff805c4945 at exit1+0x305 #12 0xffffffff805c5d0e at sys_sys_exit+0xe #13 0xffffffff808a6b56 at amd64_syscall+0x5d6 #14 0xffffffff80891327 at Xfast_syscall+0xf7 Full backtrace from kgdb: #0 doadump (textdump=<value optimized out>) at pcpu.h:234 No locals. #1 0xffffffff805f9aa4 in kern_reboot (howto=260) at /usr/home/julian/src/freebsd/sys/kern/kern_shutdown.c:449 _ep = (struct eventhandler_entry...

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, I'm experiencing a kernel panic that appears to be caused by zfs. No errors are making it into /var/log/messages, but here is the error message that appears on my screen after panic (transcribed): panic solaris assert BSWAP_32(sa_hdr_phys->sa_magic) == SA_MAGIC, file: /src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c, line 1262 I can reproduce this by

...fffffff803fec69 in boot (howto=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:428 #7 0xffffffff803fef86 in reboot (td=<value optimized out>, uap=0xffffff8000238bb0) at /usr/src/sys/kern/kern_shutdown.c:191 #8 0xffffffff805db1b4 in amd64_syscall (td=0xffffff000235e8e0, traced=0) at subr_syscall.c:114 #9 0xffffffff805c282c in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 (kgdb) f 5 #5 0xffffffff80493202 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:3321 3321...

...12fd6fe3b0 0 0 0 /liu/etc/samba/private/msg.sock/99775 Process kernel stacks for the process: > 17:01/procstat-kk-a.log:99775 102090 winbindd - pmap_remove_ptes+0x101 pmap_remove+0x35b vm_map_delete+0x14e kern_munmap+0x8d amd64_syscall+0xa38 fast_syscall_common+0x101 Ps auxwww output: > 17:01/ps-auxwww.log:root 99775 100.0 1.8 4888744 4702144 - R 07:00 67:53.99 winbindd: domain child [AD] (winbindd) (At 17:02 I “kill -9” killed it) Setup: FreeBSD 11.2-RELEASE-p5 Samba 4.9.3 / 4.7.6 (with a local patch to...

...h_add() at ufsdirhash_add+0x3b/frame 0xfffffe012fb8c5d0 ufs_direnter() at ufs_direnter+0x688/frame 0xfffffe012fb8c690 ufs_vinit() at ufs_vinit+0x33f3/frame 0xfffffe012fb8c890 VOP_MKDIR_APV() at VOP_MKDIR_APV+0xf0/frame 0xfffffe012fb8c8c0 kern_mkdirat() at kern_mkdirat+0x1ff/frame 0xfffffe012fb8cae0 amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe012fb8cbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012fb8cbf0 --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x80092faaa, rsp = 0x7fffffffd788, rbp = 0x7fffffffdc70 --- Clearing /tmp (X related). Updating motd:. Configuring syscons: keymap blan...