search for: 21587

Displaying 7 results from an estimated 7 matches for "21587".

Did you mean: 2158
2008 Feb 04
0
PRI ISSUE
....0.154' of Request 102: Match Found Feb 3 18:29:48 DEBUG[21583] chan_sip.c: Stopping retransmission on '7bee3df516afaa3225c2a8614ac32a0a at 192.168.0.154' of Request 102: Match Found ######On internet someone saied it's normal infomation, is it right? LOG2: Feb 3 18:29:08 NOTICE[21587] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 Feb 3 18:29:08 NOTICE[21587] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 Feb 3 18:29:08 NOTICE[21587] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 Feb 3 18:29:...
2006 Mar 23
1
can befor_filter expect other controller''s action?
i put befor_filter :setup_user,:except=>:login in ApplicationController.rb but i want to put action login to other controller how can i do it? does rails has this support? befor_filter :setup_user,:except=>{{controller=>''user'',action=>''login''},...} -- Posted via http://www.ruby-forum.com/.
2003 Mar 16
0
2.4.20: ext3/raid5 - allocating block in system zone/multiple 1 requests for sector]
...9;m starting to see errors of the form: kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in system zone - block = 140509185 and kernel: EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in directory #70254593: rec_len %% 4 != 0 - offset=28, inode=23880564, rec_len=21587, name_len=76 and kernel: raid5: multiple 1 requests for sector 281018464 This is on an x86 which has been running fine on the smaller raid for years (albeit Reiser); the array is built from 5 200GB Western Digi IDEs on a mix of promise and HPT controllers (there are no IDE errors visible). This...
2003 Mar 18
2
Re: 2.4.20: ext3/raid5 - allocating block in system zone/multiple 1 requests for sector
...> kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in > system zone - block = 140509185 > > and > > kernel: EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in > directory #70254593: rec_len %% 4 != 0 - offset=28, inode=23880564, > rec_len=21587, name_len=76 > > and > > kernel: raid5: multiple 1 requests for sector 281018464 I had exactly these symptoms about a year ago in 2.4.18. I found and fixed the problem and have just checked and the fix is definately in 2.4.20. So if you really are running 2.4.20 then it looks like a...
2005 Oct 09
2
compiling asterisk on SuSE Linux 9.3 fails: illegal instruction
...ect(0x40205000, 4096, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0x402ff6c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0x40018000, 99332) = 0 set_tid_address(0x402ff708) = 21587 rt_sigaction(SIGRTMIN, {0x4003a760, [], SA_SIGINFO}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x4003a3a0, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 _sysctl({{CTL_KERN, KERN...
2020 Aug 31
3
[PATCH v10 0/2] s390: virtio: let arch validate VIRTIO features
Hi all, The goal of the series is to give a chance to the architecture to validate VIRTIO device features. The tests are back to virtio_finalize_features. No more argument for the architecture callback which only reports if the architecture needs guest memory access restrictions for VIRTIO. I renamed the callback to arch_has_restricted_virtio_memory_access, and the config option to
2015 Jan 25
2
Bug#776237: xen-hypervisor-4.4-amd64: kernel panic on dom0 boot
...3.059079] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 [ 3.059079] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 [ 3.059079] tlb_flushall_shift: 6 [ 3.059398] Freeing SMP alternatives memory: 20K (ffffffff81a19000 - ffffffff81a1e000) [ 3.060320] ftrace: allocating 21587 entries in 85 pages [ 3.066149] Performance Events: Fam15h core perfctr, (XEN) traps.c:2514:d0 Domain attempted WRMSR 00000000c0010201 from 0x0000000000000000 to 0x000000000000ffff. Broken PMU hardware detected, using software events only. [ 3.066340] Failed to access perfctr msr (MSR c001020...