search for: 0x3000

...the ADSL is otherwise unused. The FTP server gots 8Kbps and the rest of the traffic 24kpbs. Finally, the filters: tc filter add dev eth0 prio 1 protocol ip parent 1:0\ u32 match ip dst 192.168.0.0/24 flowid 1:10 tc filter add dev eth0 prio 2 protocol ip parent 1:0\ u32 match ip sport 0x3000 0x3000 flowid 1:111 tc filter add dev eth0 prio 2 protocol ip parent 1:0\ u32 match ip sport 0x4000 0x4000 flowid 1:111 tc filter add dev eth0 prio 2 protocol ip parent 1:0\ u32 match ip sport 0x20 0xff flowid 1:111 I''m serving passive FTP only in ports from 0x3000 to 0x4fff...

...vlan patch at layer3. > All nics into the box are 3Com except 1 one them which is based on realtek > chipset. > The status are.... > > [root@fw-inet1 proc]# mii-diag eth0 > Basic registers of MII PHY #24: 3000 782d 0040 6176 05e1 0021 0000 0000. > Basic mode control register 0x3000: Auto-negotiation enabled. > You have link beat, and everything is working OK. > Your link partner is generating 10baseT link beat (no autonegotiation). > [root@fw-inet1 proc]# mii-diag eth1 > Basic registers of MII PHY #24: 3000 782d 0040 6176 05e1 45e1 0003 0000. > Basic mo...

An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110628/64de4f5c/attachment.html>

...@@ clock-frequency = <600000000>; st,syscfg = <&syscfg_core 0x224>; }; + + /* fdma audio */ + fdma0: dma-controller at 8e20000 { + compatible = "st,stih407-fdma-mpe31-11", "st,slim-rproc"; + reg = <0x8e20000 0x8000>, + <0x8e30000 0x3000>, + <0x8e37000 0x1000>, + <0x8e38000 0x8000>; + reg-names = "slimcore", "dmem", "peripherals", "imem"; + clocks = <&clk_s_c0_flexgen CLK_FDMA>, + <&clk_s_c0_flexgen CLK_EXT2F_A9>, + <&clk_s...

...ted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 # file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 trusted.glusterfs.dht=0x000000010000000000000000ffffffff trusted.glusterfs.quota.dirty=0x3000 trusted.glusterfs.quota.f065a5e7-ac06-445f-add0-83acf8ce4155.contri.1=0x000000000000060000000000000000060000000000000001 trusted.glusterfs.quota.size.1=0x000000000000060000000000000000060000000000000001 NODE 2: File: ?/data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/di...

...4900-b889-0fe7fce46a13=0x00000001 > > # file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ > trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 > trusted.glusterfs.dht=0x000000010000000000000000ffffffff > trusted.glusterfs.quota.dirty=0x3000 > trusted.glusterfs.quota.f065a5e7-ac06-445f-add0-83acf8ce4155.contri.1=0x000000000000060000000000000000060000000000000001 > trusted.glusterfs.quota.size.1=0x000000000000060000000000000000060000000000000001 > > > NODE 2: > > File: ?/data/myvolume-private/brick/dir1/dir2/dir3...

...y unresponsive). lspci reports: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) while Xorg.0.log reads: (--) PCI:*(0:2:0) Intel Corporation unknown chipset (0x0102) rev 9, Mem @ 0xe0c00000/22, 0xd0000000/28, I/O @ 0x3000/6 I've been searching for an rpm for adding the right driver with no success. Could anybody try to help me out, please? Thank you. Robi

Hi all :)) This matches what I want: tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\ match ip sport 0x3000 0xf000 flowid 1:22 and traffic goes to 1:22, but this one doesn''t match: tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\ match tcp src 0x3000 0xf000 flowid 1:22 I don''t understand why the first one matches and the second one doesn''t :? bec...

...;t give useful information (seems like "nexthdr" doesn''t work right, but I don''t know why...). I really want to know what am I doing wrong... This filter matches what I want: tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\ match ip sport 0x3000 0xf000 flowid 1:22 and traffic goes to 1:22, but this one doesn''t match: tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\ match tcp src 0x3000 0xf000 flowid 1:22 I don''t understand why the first one matches and the second one doesn''t...

...===================================================================================================== > > > > trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 > > > > trusted.glusterfs.dht=0x000000010000000000000000ffffffff > > > > trusted.glusterfs.quota.dirty=0x3000 > > > > trusted.glusterfs.quota.f065a5e7-ac06-445f-add0-83acf8ce4155.contri.1=0x000000000000060000000000000000060000000000000001 > > > > trusted.glusterfs.quota.size.1=0x000000000000060000000000000000060000000000000001 > > > > NODE 2: > > > > File...

...======================================================================= > > > > > > trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 > > > > > > trusted.glusterfs.dht=0x000000010000000000000000ffffffff > > > > > > trusted.glusterfs.quota.dirty=0x3000 > > > > > > trusted.glusterfs.quota.f065a5e7-ac06-445f-add0-83acf8ce4155.contri.1=0x000000000000060000000000000000060000000000000001 > > > > > > trusted.glusterfs.quota.size.1=0x000000000000060000000000000000060000000000000001 > > > > > > NOD...

On 05/15/2018 12:38 PM, mabi wrote: > Dear all, > > I have upgraded my replica 3 GlusterFS cluster (and clients) last Friday from 3.12.7 to 3.12.9 in order to fix this bug but unfortunately I notice that I still have exactly the same problem as initially posted in this thread. > > It looks like this bug is not resolved as I just got right now 3 unsynched files on my arbiter node

...============================================================== >>>> >>>> trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 >>>> >>>> trusted.glusterfs.dht=0x000000010000000000000000ffffffff >>>> >>>> trusted.glusterfs.quota.dirty=0x3000 >>>> >>>> trusted.glusterfs.quota.f065a5e7-ac06-445f-add0-83acf8ce4155.contri.1=0x000000000000060000000000000000060000000000000001 >>>> >>>> trusted.glusterfs.quota.size.1=0x000000000000060000000000000000060000000000000001 >>>> >>&gt...

...at hasn't been a problem. The only snag is I can't figure out how to define the start of the .data section in a sane way. Let's say we want our flash (.text) section to start at address 0x20000 with a max size of 0x8000 bytes and a data section start at 0x20005000 with a max length of 0x3000 bytes. We'd usually accomplish this with a combination of MEMORY and SECTION entries in the linker script tied together by region aliases, the "AT" directive and the ">" operator: MEMORY { flash (rx) : ORIGIN = 0x20000, LENGTH = 0x8000 ram (rwx) : ORIGIN = 0x...

Dear all, I have upgraded my replica 3 GlusterFS cluster (and clients) last Friday from 3.12.7 to 3.12.9 in order to fix this bug but unfortunately I notice that I still have exactly the same problem as initially posted in this thread. It looks like this bug is not resolved as I just got right now 3 unsynched files on my arbiter node like I used to do before upgrading. This problem started

...cker (becker@scyld.com) http://www.scyld.com/diag/index.html MII PHY #24 transceiver registers: 3000 780d 0040 6176 05e1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 1000 0300 0000 0000 0000 03ed 0300 0000 0036 000c 0f00 ff40 0026 0000 0000 000b. Basic mode control register 0x3000: Auto-negotiation enabled. You have link beat, and everything is working OK. This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation not complete. Your link partner does not do autonegotiation, and this transceiver type does...

Whilst always using the DMA API is OK on ARM systems in most cases, there can be a problem if a hypervisor fails to tell its guest that a virtio device is cache-coherent. In that case, the guest will end up making non-cacheable mappings for DMA buffers (i.e. the vring), which, if the host is using a cacheable view of the same buffer on the other end, is not a recipe for success. It turns out that

Whilst always using the DMA API is OK on ARM systems in most cases, there can be a problem if a hypervisor fails to tell its guest that a virtio device is cache-coherent. In that case, the guest will end up making non-cacheable mappings for DMA buffers (i.e. the vring), which, if the host is using a cacheable view of the same buffer on the other end, is not a recipe for success. It turns out that

Hello list, I'm experimenting with a little GlusterFS cluster on debian wheezy: === snip === muzzy:~# cat /etc/debian_version wheezy/sid muzzy:~# dpkg -l | grep gluster ii glusterfs-client 3.2.6-1 clustered file-system (client package) ii glusterfs-common 3.2.6-1 GlusterFS common libraries and translator modules ii glusterfs-server 3.2.6-1 clustered file-system (server package) === snip

...gt; The only snag is I can't figure out how to define the start of the .data >> section in a sane way. Let's say we want our flash (.text) section to >> start at address 0x20000 with a max size of 0x8000 bytes and a data section >> start at 0x20005000 with a max length of 0x3000 bytes. We'd usually >> accomplish this with a combination of MEMORY and SECTION entries in the >> linker script tied together by region aliases, the "AT" directive and the >> ">" operator: >> >> MEMORY >> >> { >> >>...