search for: handler

.... 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, and is there a way to stop it? *Handler Int 12 stats RW *Handler Opaque/struct 13 accept_sourceroute RW *Handler Int 14 fastforwarding RW *Handler Int 15 keepfaith RW *Handler Int 16 gifttl RW *Handler Int 100 subnets_are_local RW *Handler Int 101 fw RW Node 100 enable RW *Handler Int...

...''t find Rails. These are box stock standard installs. Here''s what we''re seeing when we trace the process: stat64("/www/mysite/docroot/rails/../config/../vendor/rails/actionpack/lib/action_view/helpers/../../action_controller/vendor/html-scanner/soap/ encodingstyle/handler.so", 0xbffe2b10) = -1 ENOENT (No such file or directory) stat64("/www/mysite/docroot/rails/../config/../vendor/rails/actionpack/lib/action_view/vendor/soap/encodingstyle/handler.rb", 0xbffe2b10) = -1 ENOENT (No such file or directory) stat64("/www/mysite/docroot/rails/../config/...

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 answered SIP/6149236651-eafb Urgent handler -- Hungup 'Zap/1-1' Urgent handler Urge...

...ut 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) Urgent handler == numeris1: Incoming call '046720XXXX' -> '9100' Urgent handler -- numeris1: info element PI 84 83 Urgent handler -- numeris1: info element CALLED PARTY NUMBER Urgent handler -- numeris1: info element CHANNEL IDENTIFICATION 89 Urgent handler -- numeris1: info e...

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 deadlock, it is a competing solution to Maarten Lankhorst's 'drm/nouveau: fix vblank deadlock'. This series fixes the vblank event deadlock by converting the event handle...

...ple with this working. Does it have to do with the NAT? If is simply a configuration file thing, could someone please mail me a file that works? Here is a section of the log file. I just need a little toe hold. Thanks in advance. Regards, 'Carl <p>[23/Apr/2003:20:01:57] [19:Connection Handler] DEBUG: Building request out of [GET /stream2 HTTP/1.1] [23/Apr/2003:20:01:57] [19:Connection Handler] DEBUG: Building clean request from [/stream2] [23/Apr/2003:20:01:57] [19:Connection Handler] DEBUG: Building request out of [Host: 192.168.1.10] [23/Apr/2003:20:01:57] [19:Connection Handler] DEBU...

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 sb->s_xattr are used to raise IO...

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 on...

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 int2f: unknown/not implemented parameters: int2f: AX ed00, BX 0c03, CX 4445, DX 5351, SI 0cfe, DI 571e, DS 199b, ES 199b err:int:DOSVM_Int2fHandler int...

...arn+all". A timing issue I guess... After validating the serial number, the dictionaries raised a segfault at all my trials, but the registration worked since it does not bring the registration window anymore. After some investigation, the segfault is due to a stack overflow in an exception handler. I can't know for sure, but this look like a recursive loop to me. At the end of this mail, I attach the last function called, and then the first recursive call. This goes until segfault, adding one pair of these line at a time... 0009:trace:seh:call_stack_handlers handler at 0x7bc2f440 return...

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...

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 other applications (https://wiki.asterisk.org/ wiki/display/AST/Pre-Dial+Handlers)....

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 the arguments ... provide handlers, and that these are matched to the condition. It a...

...d.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 quite the same thing that they mean elsewhere. (Maybe that’s an argument for using a different construct.) There’s also a good chance that I’m being inconsistent in how I chose to represent catch clauses versus cleanup clauses. In the case you refer to, if an exception thro...

...OS 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: 19.179 No irq handler for vector (irq -1) do_IRQ: 3.220 No irq handler for vector (irq -1) do_IRQ: 18.213 No irq handler for vector (irq -1) do_IRQ: 18.79 No irq handler for vector (irq -1) do_IRQ: 3.144 No irq handler for...

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 temporary" event handlers (such as u...

...al 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 client 28 from [209.245.202.133] on mountpoint [/lofi]. 8 clients connected [26/Aug/2001:16:05:04] [1:Calendar Thread] directory_touch_xa([yp.icecast.org:80]) completed...server id = 69 [26/Aug/2001:16:05:04] [1:Calendar Thread] directory_touch_xa([yp.mp3.de:80]) completed...server id = 6...

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). > > > I want to have my custom hangup-handler be run only once and when > > &g...

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...

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...