search for: handleres

After I recently installed 4.8-stable and configured it as my gateway, I started getting messages like the following during startup. This fills dmesg completely, so I can't go back and view the startup messages for diagnostic purposes. I haven't found any references to this in archive and google searches, and I don't know what's causing it. Has this happened to anyone else,

I''m trying to help the sys admins of my server figure out what is up with our Rails installation (debian sarge - completely up to date). Hitting a simple page yields 31,000 failed stat64''s and takes anywhere from 8 - 44 seconds. They #! for ruby is correct everywhere, but it''s like it can''t find Rails. These are box stock standard installs. Here''s

Group When I dial a phone number that should go out to the telco my local phone rings. Does anyone have any hits ? Thanks Asterisk Ready. *CLI> -- Called g1/6144196143 Urgent handler Urgent handler -- Starting simple switch on 'Zap/2-1' Urgent handler Urgent handler -- Called 6149236651 Urgent handler -- SIP/6149236651-1d93 is ringing Urgent handler -- Zap/1-1

Hello, I'm trying to use the version 0.6 of chan_capi-cm for outgoing calls it works perfectly but for incoming calls it doesn't work. I tried to set an extension to dial my from-pstn context and it works. So I think there's a problem with my capi.conf or something... Here's a debug when calling -- CONNECT_IND (PLCI=0x101,DID=9100,CID=46720XXXX,CIP=0x4,CONTROLLER=0x1)

This series was originally motivated by a deadlock, introduced in commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b 'drm/nouveau/disp: port vblank handling to event interface', due to inverted lock order between nouveau_drm_vblank_enable() and nouveau_drm_vblank_handler() (the complete lockdep report is included in the patch 4/5 changelog). Because this series fixes the vblank event

I have been successfully streaming mp3's with icecast for about a year now with 1.3.12, but I have never needed to add a second stream until now. I know this is hashed out over and over in the list of please forgive me if I post yet another plea for help. And I am sorry I am not using icecast2. but I don't need to. I have tried everything that I can think of but cannot get the second

Hey everyone, after we finished the introduction of the new posix acl api last cycle we still left the generic POSIX ACL xattr handler around for two reasons. First, because a few filesystems relied on the ->list() method of the generic POSIX ACL xattr handlers in their ->listxattr() inode operation. Second, during inode initalization in inode_init_always() the registered xattr handlers in

Allow handlers to declare their capabilities and allow clients to obtain that information. So far we have these use cases: * If the handler is able to switch DDC separately, clients need to probe EDID with drm_get_edid_switcheroo(). We should allow them to detect a capable handler to ensure this function only gets called when needed. * Likewise if the handler is unable to switch AUX

I install Wine on Ubuntu 9.04, i have errors when run MS foxpro : namhv at ubuntu:/media/disk/ktgd$ wine foxprox.exe fixme:gdi:get_default_fonts unhandled charset 0x000000a3 - use ANSI_CHARSET for default stock objects err:int:DOSVM_Int15Handler int15: unknown/not implemented parameters: int15: AX 2403, BX e6f5, CX 0c6c, DX 00fc, SI 0cfe, DI 571e, DS 199b, ES f000 err:int:DOSVM_Int2fHandler

Hi all, I'm trying to run the Larousse Multilingue Dictionnary pack. I've tried to run it under wine 0.9.17 (from codeweaver), 0.9.25 (from debian testing) 0.9.28 (from debian unstable) and 0.9.29 (from source). My wine setting is functional since I can use an older Larousse dictionnary (Bibliorom), no problem at all for any of the versions above. I downloaded a (legal) version of the

Prepare for transition to RCU-based event handler list; since RCU list traversal may have stale pointers, local storage may go out of scope before handler completes. Introduce nouveau_event_handler_create/_destroy which provides suitable semantics for multiple, temporary event handlers. Signed-off-by: Peter Hurley <peter at hurleysoftware.com> --- drivers/gpu/drm/nouveau/core/core/event.c

Hello Asterisk Users, Hope you all doing fine! I am working with a quite complex dialplan, and I've come to some situations where it makes some nasty use of pre-bridge handlers. The pre-bridge handlers wiki (https://wiki.asterisk.org/ wiki/display/AST/Pre-Bridge+Handlers) doesn't have the big warning the pre-dial one has indicating it must return and must not put the caller/callee in

I'm confused by the page documenting tryCatch and friends. I think it describes 3 separate mechanisms: tryCatch (in which control returns to the invoking tryCatch), withCallHandlers (in which control goes up to the calling handler/s but then continues from the point at which signalCondition() was invoked), and withRestarts (I can't tell where control ends up). For tryCatch the docs say

Hi Reid, Thanks for the input. You wrote: > The @_Z4testv.unwind.1 helper just calls ~Inner(), but not ~Outer. That’s actually intentional. The thing to keep in mind is that all of the landing pads are going to be effectively removed by the time the final object image is generated. They are just there to facilitate the table generation, and in the __CxxFrameHandler3 case they don’t mean

I setup a CentOS 6 server to use with KVM/QEMU, and I am getting the following error a good bit, granted it doesn't seem to be causing any trouble. I figured I would post and see if anyone has any ideas on the issue, or if I can just dismiss it. If I look at my logging/dmesg, I see: do_IRQ: 19.217 No irq handler for vector (irq -1) do_IRQ: 3.178 No irq handler for vector (irq -1) do_IRQ:

Complete migration of nouveau_event_get/_put from add/remove semantics to enable/disable semantics. Introduce nouveau_event_handler_install/_remove interface to add/remove non-local-scope event handlers (ie., those stored in parent containers). This change in semantics makes explicit the handler lifetime, and distinguishes "one-of" event handlers (such as gpio) from "many

We just built a new server to run Icecast 1.3.11 and Ices 0.22. It's a Dual PIII running RH7.1. We put it online last night and Icecast ran fine for 20 hours. Then it started throwing some errors.. That's when Ices died. Ices reported a libshout error. Part of the Icecast log is included. What can I do about this? Hunter [26/Aug/2001:16:05:01] [32:Connection Handler] Accepted

2013/3/26 Richard Mudgett <rmudgett at digium.com> > > On 03/25/2013 05:17 PM, Olivier wrote: > > > Hello, > > > > > > I'm giving hangup-handlers a try on a new Asterisk 11.2.1 setup. > > > My plan is to use this handler to update my CDRs with values such > > > as > > > Asterish and Tech cause (see function HANGUP_CAUSE). >

This patch lets interrupt handler functions have their natural type (ie. exactly match the data pointer type); for transition it allows the old irq_handler_t type as well. To do this it uses a gcc extension, cast-to-union, which allows a type to be cast to any type within the union. When used in a wrapper macro, it's a simple way of allowing one of several types. (Some drivers now need to

This patch lets interrupt handler functions have their natural type (ie. exactly match the data pointer type); for transition it allows the old irq_handler_t type as well. To do this it uses a gcc extension, cast-to-union, which allows a type to be cast to any type within the union. When used in a wrapper macro, it's a simple way of allowing one of several types. (Some drivers now need to