search for: 0x2000

...nfigured to accept all inbound invites. Calls from A1 to B, all work fine, and in a sip debug session I can see A1 is offering codecs: [May 6 16:43:19] WARNING[25404]: channel.c:720 ast_best_codec: Don't know any of 0x4000 formats Audio is at <IP HIDDEN> port 14958 Adding codec 0x2000 (amr) to SDP Adding codec 0x4 (ulaw) to SDP Adding codec 0x8 (alaw) to SDP Adding non-codec 0x1 (telephone-event) to SDP But when A2 makes the same call to B, it only offers amr: [May 6 16:38:44] WARNING[20408]: channel.c:720 ast_best_codec: Don't know any of 0x4000 formats Audio i...

...MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=6093 CAS=896, CE Err=0x10000 > (Correctable Patrol Data ECC)) > May??3 11:27:21 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=1 RDWR=Read RAS=1330 CAS=4, CE Err=0x2000 > (Correctable Non-Mirrored Demand Data ECC)) > May??3 11:27:22 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=2673 CAS=4, CE Err=0x2000 > (Correctable Non-Mirrored Demand Data ECC)) > May??3 11:27:23 s-virt kernel: EDAC MC0: C...

...ot; elf_xen_addr_calc_check: addresses: virt_base = 0x0 elf_paddr_offset = 0x0 virt_offset = 0x0 virt_kstart = 0x0 virt_kend = 0x1dfa4 virt_entry = 0x0 xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0x0 -> 0x1dfa4 xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each xc_dom_mem_init: 0x2000 pages xc_dom_boot_mem_init: called x86_compat: guest xen-3.0-x86_32p, address size 32 here is the log when xend is intact.... xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... OK elf_parse_binary: phdr: paddr=0x0 memsz=0x1e1a4 elf...

Hi Tim, thanks for the swift response! @debug is defined in the same module, which makes this all the more confusing. The target information from the working example are: target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64" target triple = "armv6kz--linux-gnueabihf" from the ghc produced module: target datalayout =

...ex, skb->tc_verd (okay, that was reaching). If I ping with different QoS bits which I''m assigning to different htb flows, I see (these are my debugging messages in the driver): ~$ ping -Q 0x10 172.29.50.230 kernel: outpkt: priority:06 tclassid:0x0 tc_classid:0x0 tc_index:0x0 tc_verd:0x2000 nfmark:00 ~$ ping -Q 0x08 172.29.50.230 kernel: outpkt: priority:02 tclassid:0x0 tc_classid:0x0 tc_index:0x0 tc_verd:0x2000 nfmark:00 Nada. ''pri'' does change, but it seems to get set by the QoS value directly (?), no change if I map them to different flows anyhow. Now if I us...

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

Hi Sean, The hook to add symbols into the Reader is through Writer->addFiles function. I think still the linker script should be parsed by Writer. Also the linker script functionality is only needed by ELF and not anything else. It should be contained only within ELF. Thanks Shankar Easwaran On 1/6/2013 2:05 PM, Sean Silva wrote: > On Wed, Jan 2, 2013 at 12:04 PM, Shankar Easwaran

...After rebooting, my message log is flooded every second or so with this error messages: Oct 6 14:52:20 xenserver1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": NON-FATAL recoverable (Branch=0 DRAM-Bank=0 Buffer ID = 0 RDWR=Read RAS=0 CAS=0 NON-FATAL recovera ble Err=0x2000 (FB-DIMM Configuration Write error on first attempt)) and Oct 6 15:17:23 xenserver1 kernel: EDAC MC0: CE row 0, channel 0, label "": Corrected error (Branch=0 DRAM-Bank=0 RDWR=Read RAS=0 CAS=0, CE Err=0x10000 (Correctable Non-Mirrored Demand Data E CC)) The machine is a new Tyan S5397...

...console with chain.c32: chain.c32 cmldr=/cmldr - Gert Hulselmans $ diff -u chain.c.textmode chain.c.cmldr --- chain.c.textmode 2009-12-28 21:32:17.658783777 +0100 +++ chain.c.cmldr 2009-12-28 22:23:15.118787984 +0100 @@ -48,6 +48,10 @@ * ntldr=<loader>: * equivalent to -seg 0x2000 -file <loader>, used with WinNT's loaders * + * cmldr=<loader>: + * used with Recovery Console of Windows NT/2K/XP. + * same as ntldr=<loader> & "cmdcons\0" written to memory address 0000:7C03 + * * freedos=<loader>: * equivalent to -seg 0x...

...0.314337] pci 0000:04:00.4: Enabling fixed DMA alias to 00.0 [ 0.314438] pci 0000:04:00.4: supports D1 D2 [ 0.314439] pci 0000:04:00.4: PME# supported from D0 D1 D2 D3hot D3cold [ 0.314620] pci 0000:00:1c.2: PCI bridge to [bus 04-05] [ 0.314624] pci 0000:00:1c.2: bridge window [io 0x2000-0x3fff] [ 0.314628] pci 0000:00:1c.2: bridge window [mem 0xe3100000-0xe59fffff] [ 0.314700] pci_bus 0000:05: extended config space not accessible [ 0.314718] pci_bus 0000:05: busn_res: [bus 05] end can not be updated to 08 [ 0.314724] pci 0000:00:1c.2: bridge has subordinate 05 but ma...

https://bugzilla.netfilter.org/show_bug.cgi?id=1347 Bug ID: 1347 Summary: ebtables-nft: regression in -o option Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: iptables over nftable Assignee:

On Wed, Jan 2, 2013 at 12:04 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > You might want to look at the ELFLayout changes to see what functionality is > missing from that. > > The ELFLayoutOptions has a hook into reading the Linker script which needs > to be implemented. So, looking into it a bit, I think that ELFLayoutOptions is not the right place to parse the

...ecked the conditions and found none of them was violated. The results are as follows CR0 : 0x80000031 IA32_VMX_CR0_FIXED0: 0x80000021 IA32_VMX_CR0_FIXED1: 0xFFFFFFFF CR4 : 0x2250 IA32_VMX_CR4_FIXED0: 0x2000 IA32_VMX_CR4_FIXED1: 0x27FF IA32_VMX_BASIC_MSR is 001A 0400 0000 0007 The revision ID 0x07 is assigned to the corresponding field in vmxon region in the step 4.d IA32_FEATURE_CONTROL is 0x05 My PC has a 32 bit, VT-support multi-core CPU. I use only the BSP and haven''t de...

.../bios/init.c @@ -546,9 +546,9 @@ init_tmds_reg(struct nvbios_init *init, u8 tmds) * CR58 for CR57 = 0 to index a table of offsets to the basic * 0x6808b0 address, and then flip the offset by 8. */ - const int pramdac_offset[13] = { + static const int pramdac_offset[13] = { 0, 0, 0x8, 0, 0x2000, 0, 0, 0, 0x2008, 0, 0, 0, 0x2000 }; - const u32 pramdac_table[4] = { + static const u32 pramdac_table[4] = { 0x6808b0, 0x6808b8, 0x6828b0, 0x6828b8 }; if (tmds >= 0x80) { -- 2.20.1

.../bios/init.c @@ -546,9 +546,9 @@ init_tmds_reg(struct nvbios_init *init, u8 tmds) * CR58 for CR57 = 0 to index a table of offsets to the basic * 0x6808b0 address, and then flip the offset by 8. */ - const int pramdac_offset[13] = { + static const int pramdac_offset[13] = { 0, 0, 0x8, 0, 0x2000, 0, 0, 0, 0x2008, 0, 0, 0, 0x2000 }; - const u32 pramdac_table[4] = { + static const u32 pramdac_table[4] = { 0x6808b0, 0x6808b8, 0x6828b0, 0x6828b8 }; if (tmds >= 0x80) { -- 2.27.0

...20 2015) [sssd[be[default]]] [dp_get_options] > (0x0400): Option ldap_access_filter has no value > (Tue May 12 13:16:20 2015) [sssd[be[default]]] [dp_get_options] > (0x0400): Option ldap_access_order has value host > (Tue May 12 13:16:20 2015) [sssd[be[default]]] [be_process_init] > (0x2000): ACCESS backend target successfully loaded from provider [ldap]. <snip> I really don't know this level, but from the above, my first reaction is to see if there has to be an ldab_access_filter that then leads to the ldap_access_order in the chain. mark

...x1330 */ - __u8 pad16[0x1340-0x1338]; /* 0x1338 */ + __u8 pad17[0x1340-0x1338]; /* 0x1338 */ __u32 access_regs_save_area[16]; /* 0x1340 */ __u64 cregs_save_area[16]; /* 0x1380 */ /* align to the top of the prefix area */ - __u8 pad17[0x2000-0x1400]; /* 0x1400 */ + __u8 pad18[0x2000-0x1400]; /* 0x1400 */ #endif /* !__s390x__ */ } __attribute__((packed)); /* End structure*/

...NING MULTICAST MTU:1500 Metric:1 RX packets:1166 errors:0 dropped:0 overruns:0 frame:0 TX packets:268 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:104255 (101.8 Kb) TX bytes:19936 (19.4 Kb) Interrupt:5 Base address:0x2000 I wounder about RX bytes and TX bytes, what does it mean, how does it collect its data How often does it zero the counters, every boot, hour or somethings else?. Is the information reliable Thanks Tronn -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:/...

...no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 -drive file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw -d...

...an, NV34TCL_TX_ENABLE_ENABLE); - OUT_RING (chan, (((uint32_t)exaGetPixmapPitch(pPix)) << NV34TCL_TX_SWIZZLE_RECT_PITCH_SHIFT ) | - fmt->card_swz); + pitch = exaGetPixmapPitch(pPix); + OUT_RING (chan, (pitch << NV34TCL_TX_SWIZZLE_RECT_PITCH_SHIFT) | + fmt->card_swz); + + /* 0x2000 = engine lock */ + if (pPict->filter == PictFilterBilinear) { + OUT_RING (chan, NV34TCL_TX_FILTER_MINIFY_LINEAR | + NV34TCL_TX_FILTER_MAGNIFY_LINEAR | 0x2000); + } else { + OUT_RING (chan, NV34TCL_TX_FILTER_MINIFY_NEAREST | + NV34TCL_TX_FILTER_MAGNIFY_NEAREST | 0x2000); + } - OUT_R...