search for: 0x000

I''m not seeing the problem that Fan Zhao is reporting, instead I get this one. Not sure if ti''s the same one or a different problem... This happens with my simple-guest [i.e. not using hvmloader, as I described before]. This worked fine yesterday. (XEN) event_channel.c:178:d0 EVTCHNOP failure: domain 0, error -22, line 178 (XEN) bad shared page: 0 (XEN) domain_crash_sync called

...+79,7 @@ nvkm_gddr3_calc(struct nvkm_ram *ram) WR = ram->next->bios.timing_10_WR; DLL = !ram->next->bios.ramcfg_DLLoff; ODT = ram->next->bios.timing_10_ODT; + RON = ram->next->bios.ramcfg_RON; break; case 0x20: CWL = (ram->next->bios.timing[1] & 0x00000f80) >> 7; @@ -89,6 +90,7 @@ nvkm_gddr3_calc(struct nvkm_ram *ram) ODT = (ram->mr[1] & 0x004) >> 2 | (ram->mr[1] & 0x040) >> 5 | (ram->mr[1] & 0x200) >> 7; + RON = !(ram->mr[1] & 0x300) >> 8; break; default:...

...[<ffff82c48013ceed>] cpufreq_enable_turbo+0x1d/0x29 (XEN) [<ffff82c48014c427>] do_pm_op+0x884/0x8e7 (XEN) [<ffff82c480124fd8>] do_sysctl+0x6d8/0x9f0 (XEN) [<ffff82c48021511e>] compat_hypercall+0xae/0x107 (XEN) (XEN) Pagetable walk from 0000000000000051: (XEN) L4[0x000] = 0000000116dbc027 000000000001bd22 (XEN) L3[0x000] = 0000000119ba8027 000000000001eb36 (XEN) L2[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: 000...

...EXEC_VIRTUALIZE_X2APIC_MODE; _vmx_secondary_exec_control = adjust_vmx_controls( @@ -659,17 +660,47 @@ void vmx_disable_intercept_for_msr(struct vcpu *v, u32 msr, int type) if ( msr <= 0x1fff ) { if (type & MSR_TYPE_R) - __clear_bit(msr, msr_bitmap + 0x000/BYTES_PER_LONG); /* read-low */ + clear_bit(msr, msr_bitmap + 0x000/BYTES_PER_LONG); /* read-low */ if (type & MSR_TYPE_W) - __clear_bit(msr, msr_bitmap + 0x800/BYTES_PER_LONG); /* write-low */ + clear_bit(msr, msr_bitmap + 0x800/BYTES_PER_LONG); /* wri...

...m a pull a few weeks ago) If you need the symbols, there from the same Xen I linked to in my post from a few days ago... (XEN) mm.c:3498:d4 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 4 on VCPU 0 (ec=0003) (XEN) Pagetable walk from 00000000c08187f0: (XEN) L4[0x000] = 00000004dfa38027 000000000000063c (XEN) L3[0x003] = 00000004e0071027 0000000000000003 (XEN) L2[0x004] = 00000004df8cd067 00000000000007a7 (XEN) L1[0x018] = 00000004df85c061 0000000000000818 (XEN) domain_crash_sync called from entry.S (XEN) Domain 4 (vcpu#0) crashed on cpu#2: (XEN) ----[ Xen-3...

...000000000 0000000000000002 ffff8300bffa5000 (XEN) 00000037a6cb1580 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff82d080181c79>] set_cpu_sibling_map+0x39/0x340 (XEN) [<ffff82d08018213c>] start_secondary+0x1bc/0x260 (XEN) (XEN) Pagetable walk from 0000000000000020: (XEN) L4[0x000] = 000000083d21c063 ffffffffffffffff (XEN) L3[0x000] = 000000083d21b063 ffffffffffffffff (XEN) L2[0x000] = 000000083d21a063 ffffffffffffffff (XEN) L1[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 2: (XEN) FATAL PAGE FAULT (XEN)...

...000000000 0000000000000002 ffff8300bfd0b000 (XEN)??? 00000037bd295580 0000000000000000 (XEN) Xen call trace: (XEN)??? [<ffff82d080181ba9>] set_cpu_sibling_map+0x39/0x340 (XEN)??? [<ffff82d08018206c>] start_secondary+0x1bc/0x260 (XEN) (XEN) Pagetable walk from 0000000000000020: (XEN)? L4[0x000] = 000000083d5c1063 ffffffffffffffff (XEN)? L3[0x000] = 000000083d5c0063 ffffffffffffffff (XEN)? L2[0x000] = 000000083d5bf063 ffffffffffffffff (XEN)? L1[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 2: (XEN) FATAL PAGE FAULT (XEN)...

Hello, Attached a small patch that correctly identifies the DLLoff bit for >=GF100. Marked RFC because I haven't seen any GDDR5 samples that *enable* the DLL. I'd like to verify whether the DLL should be reset when enabled. Could increase likelihood of succesfull reclock. Ben: could you do some experiments with this bit to see if GDDR5 needs some DLL reset logic? Thanks, and happy

...00 0000000000000002 ffff8300bffa5000 (XEN)??? 00000037a6cb1580 0000000000000000 (XEN) Xen call trace: (XEN)??? [<ffff82d080181c79>] set_cpu_sibling_map+0x39/0x340 (XEN)??? [<ffff82d08018213c>] start_secondary+0x1bc/0x260 (XEN) (XEN) Pagetable walk from 0000000000000020: (XEN)? L4[0x000] = 000000083d21c063 ffffffffffffffff (XEN)? L3[0x000] = 000000083d21b063 ffffffffffffffff (XEN)? L2[0x000] = 000000083d21a063 ffffffffffffffff (XEN)? L1[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 2: (XEN) FATAL PAGE FAUL...

...fcn <- structure(function() {}, foo="foo", class=c("foo")) > str(fcn) function () - attr(*, "srcref")=Class 'srcref' atomic [1:8] 1 18 1 30 18 30 1 1 .. ..- attr(*, "srcfile")=Classes 'srcfilecopy', 'srcfile' <environment: 0x000 000000c00d128> - attr(*, "foo")= chr "foo" - attr(*, "class")= chr "foo" > formals(fcn) <- list(a=1) > str(fcn) function (a = 1) > attributes(fcn) NULL TROUBLESHOOTING: >From the definition of formals()<-, it's quite clear why th...

...ct nouveau_drm *drm) +{ + struct nv10_fence_priv *priv = drm->fence; + + nouveau_bo_wr32(priv->bo, 0, priv->sequence); +} + int nv10_fence_create(struct nouveau_drm *drm) { @@ -197,6 +204,8 @@ nv10_fence_create(struct nouveau_drm *drm) if (ret == 0) { nouveau_bo_wr32(priv->bo, 0x000, 0x00000000); priv->base.sync = nv17_fence_sync; + + priv->base.resume = nv17_fence_resume; } } diff --git a/drivers/gpu/drm/nouveau/nv50_fence.c b/drivers/gpu/drm/nouveau/nv50_fence.c index c20f272..4cc0ce6 100644 --- a/drivers/gpu/drm/nouveau/nv50_fence.c +++ b/drivers/gpu/drm/...

...1. cd /var/log 2. grep -ri "Check Spelling & Mumble" * 3. (or) grep -ri "Check Spelling & Mumble" *gz Actual results: Fails with: *** glibc detected *** free(): invalid next size (normal): *** Aborted. Sometimes: *** glibc detected *** realloc(): invalid next size: 0x000.... *** Aborted. Expected results: No failure. Additional info: Grepping 7GB of compressed logs on one server, grepping 4GB logs on other server. x86_64 Server had 35M or 3G+cache ram free; i686 server had 374M ram free, 960M+cache.

...>] cpufreq_enable_turbo+0x1d/0x29 (XEN) [<ffff82c48014c427>] do_pm_op+0x884/0x8e7 (XEN) [<ffff82c480124fd8>] do_sysctl+0x6d8/0x9f0 (XEN) [<ffff82c48021511e>] compat_hypercall+0xae/0x107 (XEN) (XEN) Pagetable walk from 0000000000000051: (XEN) L4[0x000] = 0000000116dbc027 000000000001bd22 (XEN) L3[0x000] = 0000000119ba8027 000000000001eb36 (XEN) L2[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (X...

Hi Jan, Attached patch dumps io page fault flags. The flags show the reason of the fault and tell us if this is an unmapped interrupt fault or a DMA fault. Thanks, Wei signed-off-by: Wei Wang <wei.wang2@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

...> +#define VIRTIO_MDEV_DEVICE_API_STRING "virtio-mdev" > > > + > > > +/* > > > + * Control registers > > > + */ > > > + > > > +/* Magic value ("virt" string) - Read Only */ > > > +#define VIRTIO_MDEV_MAGIC_VALUE 0x000 > > > + > > > +/* Virtio device version - Read Only */ > > > +#define VIRTIO_MDEV_VERSION 0x004 > > > + > > > +/* Virtio device ID - Read Only */ > > > +#define VIRTIO_MDEV_DEVICE_ID 0x008 > > > + > > > +/* Virtio vendor ID -...

...> +#define VIRTIO_MDEV_DEVICE_API_STRING "virtio-mdev" > > > + > > > +/* > > > + * Control registers > > > + */ > > > + > > > +/* Magic value ("virt" string) - Read Only */ > > > +#define VIRTIO_MDEV_MAGIC_VALUE 0x000 > > > + > > > +/* Virtio device version - Read Only */ > > > +#define VIRTIO_MDEV_VERSION 0x004 > > > + > > > +/* Virtio device ID - Read Only */ > > > +#define VIRTIO_MDEV_DEVICE_ID 0x008 > > > + > > > +/* Virtio vendor ID -...

...transform the output to look more like the GDB output that the CHECK-lines are looking for. > > // CHECK: ${{[0-9]+}} = > // CHECK: Data ={{.*}} 0x0{{(0*)}} > // CHECK: Kind = 2142 > > In WinDbg this is going to be more like: > > Local var @ 0x6ffa50 Type SVal > +0x000 Data : (null) > +0x004 Kind : 0x85e > > So we're also going to need different check lines. > At this point, the only similarities in the PDB / DWARF tests is going to be the source code, as I don't see an easy way to automatically translate command l...

...escue.txt done echo "# @@ -59,12 +59,12 @@ echo "# # Run nbdkit. -start_nbdkit -P data-file.pid -U $sock \ +start_nbdkit -P ddrescue.pid -U $sock \ --filter=ddrescue data \ ddrescue-mapfile="ddrescue-test1.map"\ size=1M \ data=" - @0x000 <data-ddrescue.txt + @0x000 <ddrescue.txt " nbdsh --connect "nbd+unix://?socket=$sock" \ -- 2.25.0

...he output to look more like the GDB > output that the CHECK-lines are looking for. > > > // CHECK: ${{[0-9]+}} = > // CHECK: Data ={{.*}} 0x0{{(0*)}} > // CHECK: Kind = 2142 > > In WinDbg this is going to be more like: > > Local var @ 0x6ffa50 Type SVal > > +0x000 Data : (null) +0x004 Kind : 0x85e > > > > Alternatively, this is still similar enough that we could relax the check > to look like > CHECK: Data{{.*[:=].*(0x0|.null.)}} > CHECK: Kind{{.*[:=].*(2142|0x85e)}} > without much loss. > > -- adr...

Hi, We are trying to use OCFS2 as VM storage. After running into problems with qemu's disk_mirror feature we now think there could be a problem with the FIEMAP ioctl in OCFS2. As far as I understand the situation looks like this: Qemu inquiries the FS if the given section of the image is already allocated via the FIEMAP ioctl [1] It especially checks if fm_mapped_extents is greater 0.