search for: notify

...4000000 ( 64 MB) [ 0.000000] .init : 0xc03c1000 - 0xc0402000 ( 260 kB)Guest base is at 0xb3cde000 device 0: console mapped initrd /boot/initrd.img-2.6.23-rc9 size=14139392 @ 0x3284000 Linear mapping of 16384 pages in 16 pte pages at 0x3273000 Guest: 0xb3cde000 - 0xb7ce4000 (0x4006000) Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on...

...4000000 ( 64 MB) [ 0.000000] .init : 0xc03c1000 - 0xc0402000 ( 260 kB)Guest base is at 0xb3cde000 device 0: console mapped initrd /boot/initrd.img-2.6.23-rc9 size=14139392 @ 0x3284000 Linear mapping of 16384 pages in 16 pte pages at 0x3273000 Guest: 0xb3cde000 - 0xb7ce4000 (0x4006000) Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on address 0x3bdf23 Notify on...

...d that on occasion the page-all will cause asterisk to crash (safe_asterisk then restarts it again). The particular customer has about 20 phones, and also has 5 Linksys 932 to monitor the state of these extensions. I'm not sure whether it is the page-all that causes the crash, or the subsequent NOTIFY storm to all of the 932s that are monitoring those extensions (since the page-all causes them all to go to In-Use and then Idle). Here's a log snippet of right before the crash (previous crashes look very similar). Also, this is a production box, so there's no way at this time I can recomp...

Greetings all, Anyone have a clue on this behavior (see below) on this behavior with FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.02, addr 2> on usbus1 Dec 10 21:40:12

here: diff --git a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c index 53f5db0003d..efd9cf2b004 100644 --- a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c +++ b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c @@ -365,7 +365,7 @@ nouveau_vp3_fill_picparm_h264_vp(struct nouveau_vp3_decoder *dec, refs[j] = (struct

...erver. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to come from 172.16/16 subnet. To do this, I use allow-notify in the slave config file: zone: name: "black" zonefile: "/var/nsd/zones/black.zone" allow-notify: 172.16.0.0/24 NOKEY Then I receive error message from nsd-checkconf: /etc/nsd-dns-sl...

Nice! it seems to works. Later this evening when I'll be back to my home I'll try to unplug the power chord from my ups. Apr 3 14:08:11 archivio notifier: nut not running? (check > /var/db/nut/upsd.pid). > Apr 3 14:08:11 archivio notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Apr 3 14:08:11 archivio notifier: nut_upslog not running? (check >

Hi, When I added this association... class User < ActiveRecord::Base has_one :notify end ...and tried then to update column in User table it will call queries for notify table automatic? Output --------------------------------------------------------------- User Columns (0.041488) SHOW FIELDS FROM `users` User Load (0.001544) SELECT * FROM `users` WHERE (`users`.`nickname`...

...host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. When an online channel device disappears on System z the kernel's CIO layer informs the driver (virtio_ccw) about the lost device. It's just the block device drivers that care to provide a notify callback. Here are some more error details: For a particular block device virtio's request function virtblk_request() is called by the block layer to queue requests to be handled by the host. In case of a lost device requests can still be queued, but an appropriate subsequent host kick usuall...

...host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. When an online channel device disappears on System z the kernel's CIO layer informs the driver (virtio_ccw) about the lost device. It's just the block device drivers that care to provide a notify callback. Here are some more error details: For a particular block device virtio's request function virtblk_request() is called by the block layer to queue requests to be handled by the host. In case of a lost device requests can still be queued, but an appropriate subsequent host kick usuall...

...x); + else if (!mutex_trylock(&svmm->mutex)) return false; + mmu_interval_set_seq(mni, cur_seq); - mutex_unlock(&sn->svmm->mutex); + nouveau_svmm_invalidate(svmm, range->start, range->end); + + /* Stop tracking the range if it is an unmap. */ + if (range->event == MMU_NOTIFY_UNMAP) + nouveau_svmm_do_unmap(mni, range); + + mutex_unlock(&svmm->mutex); return true; } +static void nouveau_svmm_interval_release(struct mmu_interval_notifier *mni) +{ + struct svmm_interval *smi = + container_of(mni, struct svmm_interval, notifier); + + kfree(smi); +} + static c...

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 #1 0x080641f2 in imap_client_notify_ns (notify_n...

...;vmm->vmm.object.client->super = true; + ret = nvif_object_ioctl(&svmm->vmm->vmm.object, data, size, NULL); + svmm->vmm->vmm.object.client->super = false; + mutex_unlock(&svmm->mutex); + + return ret; } static int @@ -559,7 +584,6 @@ nouveau_svm_fault(struct nvif_notify *notify) } i; u64 phys[16]; } args; - struct hmm_range range; struct vm_area_struct *vma; u64 inst, start, limit; int fi, fn, pi, fill; @@ -615,6 +639,7 @@ nouveau_svm_fault(struct nvif_notify *notify) args.i.p.version = 0; for (fi = 0; fn = fi + 1, fi < buffer->fault_nr;...

nothing appens. The output is exactly the same as below (attached screen with freenas config) [image: Immagine in linea 2] 2014-04-03 13:16 GMT+02:00 Charles Lepple <clepple at gmail.com>: > please reply to the list. thanks! > > See below. > > On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > > thanks for your reply.* I'm running the latest version of

...host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. When an online channel device disappears on System z the kernel's CIO layer informs the driver (virtio_ccw) about the lost device. It's just the block device drivers that care to provide a notify callback. Here are some more error details: For a particular block device virtio's request function virtblk_request() is called by the block layer to queue requests to be handled by the host. In case of a lost device requests can still be queued, but an appropriate subsequent host kick usuall...

...host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. When an online channel device disappears on System z the kernel's CIO layer informs the driver (virtio_ccw) about the lost device. It's just the block device drivers that care to provide a notify callback. Here are some more error details: For a particular block device virtio's request function virtblk_request() is called by the block layer to queue requests to be handled by the host. In case of a lost device requests can still be queued, but an appropriate subsequent host kick usuall...

Hi, I have a query regarding running a manual update of nsd via: # nsdc update My NSD server is accepting notifications from two servers. From my nsd.conf: # master 1 allow-notify: X.X.X.X NOKEY request-xfr: AXFR X.X.X.X NOKEY # master 2 allow-notify: Y.Y.Y.Y NOKEY request-xfr: AXFR Y.Y.Y.Y NOKEY Are both servers sequentially queried each time the update is run? Or is it a random one of the two servers that answers and the second one...

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting

Hello, I'm using dovecot 1.1.1 and dovecot-sieve-1.1.5 . I'm very interested in the notify plugin, I've tried many code which have generated some errors (coding errors that have been arrived in the .dovecot.sieve.err) but these errors are fixed. But Notify is still not working, I've the following in mail.log :deliver(webmaster at xxx.net): SIEVE ERROR: Unknown [unimplemented] not...

please reply to the list. thanks! See below. On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > thanks for your reply. I'm running the latest version of FreeNAS based on 9.2 with NUT 2.7.1 > > [root at archivio ~]# uname -a > FreeBSD archivio.dannyb78.home 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu