search for: 0x11

...x5 }, { 0x2, 0x3, 0x4, 0x6 }, { 0x3, 0x4, 0x5, 0x7 }, { 0x4, 0x5, 0x6, 0x8 }, { 0x5, 0x6, 0x7, 0x9 }, { 0x6, 0x7, 0x8, 0xa }, { 0x7, 0x8, 0x9, 0xb }, { 0x8, 0x9, 0xa, 0xc }, { 0x9, 0xa, 0xb, 0xd }, { 0xa, 0xb, 0xc, 0xe }, { 0xb, 0xc, 0xd, 0xf }, { 0xc, 0xd, 0xe, 0x10 }, { 0xd, 0xe, 0xf, 0x11 }, { 0xe, 0xf, 0x10, 0x12 }, { 0xf, 0x10, 0x11, 0x13 }, { 0x10, 0x11, 0x12, 0x14 }, { 0x11, 0x12, 0x13, 0x15 }, { 0x12, 0x13, 0x14, 0x16 }, { 0x13, 0x14, 0x15, 0x17 }, { 0x14, 0x15, 0x16, 0x18 }, { 0x15, 0x16, 0x17, 0x19 }, { 0x16, 0x17, 0x18, 0x1a }, { 0x17, 0x18, 0x19, 0x1b }, { 0x18,...

...x5 }, { 0x2, 0x3, 0x4, 0x6 }, { 0x3, 0x4, 0x5, 0x7 }, { 0x4, 0x5, 0x6, 0x8 }, { 0x5, 0x6, 0x7, 0x9 }, { 0x6, 0x7, 0x8, 0xa }, { 0x7, 0x8, 0x9, 0xb }, { 0x8, 0x9, 0xa, 0xc }, { 0x9, 0xa, 0xb, 0xd }, { 0xa, 0xb, 0xc, 0xe }, { 0xb, 0xc, 0xd, 0xf }, { 0xc, 0xd, 0xe, 0x10 }, { 0xd, 0xe, 0xf, 0x11 }, { 0xe, 0xf, 0x10, 0x12 }, { 0xf, 0x10, 0x11, 0x13 }, { 0x10, 0x11, 0x12, 0x14 }, { 0x11, 0x12, 0x13, 0x15 }, { 0x12, 0x13, 0x14, 0x16 }, { 0x13, 0x14, 0x15, 0x17 }, { 0x14, 0x15, 0x16, 0x18 }, { 0x15, 0x16, 0x17, 0x19 }, { 0x16, 0x17, 0x18, 0x1a }, { 0x17, 0x18, 0x19, 0x1b }, { 0x18,...

...entry; +}; + +static struct IO_APIC_route_entry __ioapic_read_entry(int apic, int pin, int raw) +{ + unsigned int (*read)(unsigned int, unsigned int) + = raw ? __io_apic_read : io_apic_read; + union entry_union eu; + eu.w1 = (*read)(apic, 0x10 + 2 * pin); + eu.w2 = (*read)(apic, 0x11 + 2 * pin); + return eu.entry; +} + +static struct IO_APIC_route_entry ioapic_read_entry(int apic, int pin, int raw) +{ + struct IO_APIC_route_entry entry; + unsigned long flags; + + spin_lock_irqsave(&ioapic_lock, flags); + entry = __ioapic_read_entry(apic, pin, raw); + spin_...

...entry; +}; + +static struct IO_APIC_route_entry __ioapic_read_entry(int apic, int pin, int raw) +{ + unsigned int (*read)(unsigned int, unsigned int) + = raw ? __io_apic_read : io_apic_read; + union entry_union eu; + eu.w1 = (*read)(apic, 0x10 + 2 * pin); + eu.w2 = (*read)(apic, 0x11 + 2 * pin); + return eu.entry; +} + +static struct IO_APIC_route_entry ioapic_read_entry(int apic, int pin, int raw) +{ + struct IO_APIC_route_entry entry; + unsigned long flags; + + spin_lock_irqsave(&ioapic_lock, flags); + entry = __ioapic_read_entry(apic, pin, raw); + spin_...

...w-r----- 1 admin admin 1041830 May 25 21:34 .imap.index.data -rw-r----- 1 admin admin 2576 May 25 21:34 .imap.index.log -rw-r----- 1 admin admin 263396 May 25 21:34 .imap.index.tree bash-2.05a$ strace /usr/libexec/dovecot/imap ... getdents64(0x9, 0x8098730, 0x1000, 0x11) = 4064 getdents64(0x9, 0x8098730, 0x1000, 0x11) = 1392 getdents64(0x9, 0x8098730, 0x1000, 0x11) = 4056 getdents64(0x9, 0x8098730, 0x1000, 0x11) = 1408 getdents64(0x9, 0x8098730, 0x1000, 0x11) = 1672 getdents64(0x9, 0x8098730, 0x1000, 0x11) = 0 close(9) = 0 read(8, &q...

...truct nvkm_bios *b, struct nvbios_vpstate_header *h) > h->ecount = nvbios_rd08(b, h->offset + 0x5); > > h->base_id = nvbios_rd08(b, h->offset + 0x0f); > - h->boost_id = nvbios_rd08(b, h->offset + 0x10); > - h->tdp_id = nvbios_rd08(b, h->offset + 0x11); > + if (h->hlen > 0x10) > + h->boost_id = nvbios_rd08(b, h->offset + 0x10); > + else > + h->boost_id = 0xff; > + if (h->hlen > 0x11) > + h->tdp_id = nvbios_rd08(b, h->offset + 0x11); > + else > + h->tdp_id = 0xff; > return 0;...

...h the first descriptor again > >After writing down this explanation, I think the names aren't >great. > >Let me try an alternative explanation. > >--------------- >A two-bit field, DRIVER_OWNER, signals the buffer ownership. >It has 4 possible values: >values 0x1, 0x11 are written by driver >values 0x0, 0x10 are written by device The 0x prefix might add to the confusion here. It is really just two bits, no? >each time driver writes out a descriptor, it must make sure >that the high bit in OWNER changes. > >each time device writes out a descriptor...

...h the first descriptor again > >After writing down this explanation, I think the names aren't >great. > >Let me try an alternative explanation. > >--------------- >A two-bit field, DRIVER_OWNER, signals the buffer ownership. >It has 4 possible values: >values 0x1, 0x11 are written by driver >values 0x0, 0x10 are written by device The 0x prefix might add to the confusion here. It is really just two bits, no? >each time driver writes out a descriptor, it must make sure >that the high bit in OWNER changes. > >each time device writes out a descriptor...

On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote: > 2) the changelog _completely_ fails to explain the sync 0x11 and sync > 0x12 semantics nor does it provide a publicly accessible link to > documentation that does. Ralf pointed me at: https://imgtec.com/mips/architectures/mips64/ > 3) it really should have explained what you did with > smp_llsc_mb/smp_mb__before_llsc() in _detail_. And reading...

On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote: > 2) the changelog _completely_ fails to explain the sync 0x11 and sync > 0x12 semantics nor does it provide a publicly accessible link to > documentation that does. Ralf pointed me at: https://imgtec.com/mips/architectures/mips64/ > 3) it really should have explained what you did with > smp_llsc_mb/smp_mb__before_llsc() in _detail_. And reading...

...partially by using the correct 3d class. However there were a lot of checks left over comparing against the chipset. Reported-and-tested-by: John F. Godfrey <jfgodfrey at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I guess I didn't have to change the >= 0x11 checks, but seemed nicer for consistency. src/mesa/drivers/dri/nouveau/nv10_context.c | 8 ++++---- src/mesa/drivers/dri/nouveau/nv10_state_fb.c | 4 ++-- src/mesa/drivers/dri/nouveau/nv10_state_raster.c | 3 ++- 3 files changed, 8 insertions(+), 7 deletions(-) diff --git a/src/mesa/dri...

...] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:22 <server> kernel: [<ffffffff80032c68>] kthread+0xfe/0x132 Nov 1 14:34:22 <server> kernel: [<ffffffff8005dfc1>] child_rip+0xa/0x11 Nov 1 14:34:22 <server> kernel: [<ffffffff800a3d4a>] keventd_create_kthread+0x0/0xc4 Nov 1 14:34:23 <server> kernel: [<ffffffff80032b6a>] kthread+0x0/0x132 Nov 1 14:34:23 <server> kernel: [<ffffffff8005dfb7>] child_rip+0x0/0x11

...0x80 [<ffffffff812c6d84>] register_con_driver+0x34/0x140 [<ffffffff812c84e9>] take_over_console+0x29/0x60 [<ffffffff8126e76b>] fbcon_takeover+0x5b/0xb0 [<ffffffff81272bb5>] fbcon_event_notify+0x715/0x820 [<ffffffff810693a5>] notifier_call_chain+0x55/0x110 [<ffffffff810697d7>] __blocking_notifier_call_chain+0x67/0xc0 [<ffffffff81069841>] blocking_notifier_call_chain+0x11/0x20 [<ffffffff81262a16>] fb_notifier_call_chain+0x16/0x20 [<ffffffff81264c1d>] register_framebuffer+0x1bd/0x2f0 [<ffffffff81ac2bd4&gt...

...f>] ? getname_flags+0x4f/0x1a0 [26399.968481]? [<ffffffffaf45b6ab>] filename_lookup+0x2b/0xc0 [26399.968487]? [<ffffffffaf45d5f7>] user_path_at_empty+0x67/0xc0 [26399.968492]? [<ffffffffaf450695>] ? cp_new_stat+0x165/0x1a0 [26399.968497]? [<ffffffffaf45d661>] user_path_at+0x11/0x20 [26399.968501]? [<ffffffffaf450343>] vfs_fstatat+0x63/0xc0 [26399.968505]? [<ffffffffaf4506fe>] SYSC_newstat+0x2e/0x60 [26399.968530]? [<ffffffffaf33e3f6>] ? __audit_syscall_exit+0x1e6/0x280 [26399.968534]? [<ffffffffaf450bbe>] SyS_newstat+0xe/0x10 [26399.968544]? [<...

...xc4 kernel: [<ffffffff8021b93a>] md_thread+0xf8/0x10e kernel: [<ffffffff800a0947>] keventd_create_kthread+0x0/0xc4 kernel: [<ffffffff8021b842>] md_thread+0x0/0x10e kernel: [<ffffffff8003296e>] kthread+0xfe/0x132 kernel: [<ffffffff8005dfb1>] child_rip+0xa/0x11 kernel: [<ffffffff800a0947>] keventd_create_kthread+0x0/0xc4 kernel: [<ffffffff80032870>] kthread+0x0/0x132 kernel: [<ffffffff8005dfa7>] child_rip+0x0/0x11 kernel: The /var/log/mcelog is empty. # df -h Filesystem Size Used Avail Use% Mounted on /dev/md1...

If I'm using the SR-IOV Pool assignment method (from http://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition ), how would I check how many virtual functions are already in use? Is there a method other then looping through all the active guests and determining if they're using the SR-IOV interface?

...when I enter them in /etc/iproute/rt_dsfield. to demonstrate this, I added prohibit rules for different marked packets and tried if the packets are dropped when I try to "ping -Q tosvalue <somehost>": #: ip route add prohibit default tos 0xb8 #: ip route add prohibit default tos 0x11 #: ip route add prohibit default tos 0x10 #: ip route add prohibit default tos 0x02 #: ip route <some rules snipped> prohibit default tos high prohibit default tos test prohibit default tos lowdelay prohibit default tos mincost default via 192.168.10.1 dev eth0 #: cat /etc/iproute2/...

Get it now. Please correct me if I missing something. Flags status hints, - DESC_DRIVER only: driver owns the descriptor w/o available info ready for device to use - DESC_DRIVER | DESC_WRAP: driver has prepared an available descriptor, device hasn't used it yet - None: device has used the descriptor, and write descriptor out - DESC_WRAP only: shall not happen, device make sure to clear

Get it now. Please correct me if I missing something. Flags status hints, - DESC_DRIVER only: driver owns the descriptor w/o available info ready for device to use - DESC_DRIVER | DESC_WRAP: driver has prepared an available descriptor, device hasn't used it yet - None: device has used the descriptor, and write descriptor out - DESC_WRAP only: shall not happen, device make sure to clear

Hi, Hey people, i have a TE210P with a ISDN PRI in M?xico. It is working just fine with Asterisk, I just have a minor glinch. When I dial a number that doesn't exists the Zap channel is imediatly hungup, instead of putting my trougth the providers message: "Sorry, the number that you dialed does not exists, etc". I have a call center and the people there really need to be able to