search for: notifies

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi, We've implemented a 'page-all' function for some of our customers, and we've noticed 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

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

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. 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

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 >

...------------------------------- User Columns (0.041488) SHOW FIELDS FROM `users` User Load (0.001544) SELECT * FROM `users` WHERE (`users`.`nickname` = ''jamal'') LIMIT 1 SQL (0.000373) BEGIN SQL (0.001843) SHOW TABLES User::Notify Load (0.001113) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.001009) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.000996) SELECT * FROM `user_notifies` WHERE (user_notifies.user_id = 1) LIMIT 1 User::Notify Load (0.000862) SELECT * FROM...

Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z there exists no handshake mechanism between host and guest when a device

Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z there exists no handshake mechanism between host and guest when a device

Update nouveau to only use the mmu interval notifiers. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- drivers/gpu/drm/nouveau/nouveau_svm.c | 313 +++++++++++++++++--------- 1 file changed, 201 insertions(+), 112 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_svm.c b/drivers/gpu/drm/nouveau/nouveau_svm.c index df9bf1fd1bc0..0343e48d41d7 100644 ---

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,

From: Jason Gunthorpe <jgg at mellanox.com> Remove the hmm_mirror object and use the mmu_range_notifier API instead for the range, and use the normal mmu_notifier API for the general invalidation callback. While here re-organize the pagefault path so the locking pattern is clear. nouveau is the only driver that uses a temporary range object and instead forwards nearly every invalidation

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

Hi, here is an updated patch-set with changes as suggested by Michael Tsirkin. When an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z

Hi, here is an updated patch-set with changes as suggested by Michael Tsirkin. When an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. On System z

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

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]

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