search for: 0xf0000000

...on a 32-bit guest if you are assigning it more than + * ~3G of RAM + */ DWordMemory( ResourceConsumer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, - 0xF0000000, + 0xC0000000, 0xF4FFFFFF, 0x00000000, - 0x05000000) + 0x35000000) }) Return (PRT0) } diff -r 62fc84adc8ed -r dba8f029e222 tools/firm...

Hello! I'm getting this backtrace every time I boot: resource map sanity check conflict: 0xf0000000 0xf1ffffff 0xf1000000 0xf112bfff BOOTFB ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at /home/proskin/src/linux/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x372/0x380() Info: mapping multiple BARs. Your kernel is fine. Modules linked in: CPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.12...

...mplefb is enabled. It's sysfb_simplefb that causes it, a completely > different driver. > > If GRUB keeps the graphic mode, I have this entry in /proc/iomem: > > f1000000-f112bfff : BOOTFB > > It is reserved by sysfb_simplefb. Nouveau tries to map an area at > 0xf0000000-0xf1ffffff, so it includes the existing resource without > being equivalent to it. > > Nouveau correctly calls remove_conflicting_framebuffers() before trying > to map that resource. However, sysfb_simplefb is not a real > framebuffer, so it doesn't free its resources. > &g...

...onflict happens regardless of whether simplefb is enabled. It's sysfb_simplefb that causes it, a completely different driver. If GRUB keeps the graphic mode, I have this entry in /proc/iomem: f1000000-f112bfff : BOOTFB It is reserved by sysfb_simplefb. Nouveau tries to map an area at 0xf0000000-0xf1ffffff, so it includes the existing resource without being equivalent to it. Nouveau correctly calls remove_conflicting_framebuffers() before trying to map that resource. However, sysfb_simplefb is not a real framebuffer, so it doesn't free its resources. iomem_map_sanity_check() doesn...

Hi Pavel On Fri, Oct 4, 2013 at 12:10 AM, Pavel Roskin <proski at gnu.org> wrote: > Hi David, > > On Thu, 3 Oct 2013 00:19:56 +0200 > David Herrmann <dh.herrmann at gmail.com> wrote: > >> >> And your PCI-BAR adjustment doesn't change >> >> anything either, sorry. >> > >> > I simply tried another approach to pacify the

http://bugs.freedesktop.org/show_bug.cgi?id=11918 Summary: drmMap of framebuffer failed Product: Mesa Version: CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pmandin at

...ld be nice, but I assume nvidiafb fails because it > cannot map its BAR regions? The logs are adjusted and so it the kernel config file. $ grep nvidiafb * dm-busy-adjust:nvidiafb_setup START dm-busy-adjust:nvidiafb_probe START dm-busy-adjust:nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] dm-busy-adjust:nvidiafb: cannot request PCI regions dm-busy-noadjust:nvidiafb_setup START dm-busy-noadjust:nvidiafb_probe START dm-busy-noadjust:nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] dm-busy-noadjust:nvidiafb: cannot request PC...

Saludos a la lista, I installed CentOS under Vmware, when start statrx, this service goes down with the this error: (WW) VMWARE (0): Failed to set up write-combining range (0xf0000000, 0x1000000). Somebody knows where may I find a driver or files needed to solve it? Atentamente, Miguel. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070218/cc6d3134/attachment.html>

...erEdge 2650 but I get: FASTCMD> open afa0 Executing: open "afa0" Command Error: <The driver could not execute the requested IOCTL SENDFIB, 22=Invalid argument.> I have "options AAC_COMPAT_LINUX" in the kernel config and dmesg shows: aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 16 at device 8.1 on pci4 aac0: i960RX 100MHz, 118MB cache memory, optional battery present aac0: Kernel 2.7-1, Build 3170, S/N 6841d3 aac0: Supported Options=75c<WCACHE,DATA64,HOSTTIME,WINDOW4GB,SOFTERR,NORECOND,SGMAP64> [ .. ] aacd0: <RAID 1 (Mirror)> on aac0 aacd0:...

...clude "wndw.h" +#include "handles.h" #include <linux/dma-mapping.h> #include <linux/hdmi.h> @@ -153,7 +154,8 @@ nv50_dmac_create(struct nvif_device *device, struct nvif_object *disp, if (!syncbuf) return 0; - ret = nvif_object_init(&dmac->base.user, 0xf0000000, NV_DMA_IN_MEMORY, + ret = nvif_object_init(&dmac->base.user, NV50_DISP_HANDLE_SYNCBUF, + NV_DMA_IN_MEMORY, &(struct nv_dma_v0) { .target = NV_DMA_V0_TARGET_VRAM, .access = NV_DMA_V0_ACCESS_RDWR, @@ -164,7 +166,8 @@ nv50_dmac_create(struct nvif_device *dev...

...clude "wndw.h" +#include "handles.h" #include <linux/dma-mapping.h> #include <linux/hdmi.h> @@ -154,7 +155,8 @@ nv50_dmac_create(struct nvif_device *device, struct nvif_object *disp, if (!syncbuf) return 0; - ret = nvif_object_init(&dmac->base.user, 0xf0000000, NV_DMA_IN_MEMORY, + ret = nvif_object_init(&dmac->base.user, NV50_DISP_HANDLE_SYNCBUF, + NV_DMA_IN_MEMORY, &(struct nv_dma_v0) { .target = NV_DMA_V0_TARGET_VRAM, .access = NV_DMA_V0_ACCESS_RDWR, @@ -165,7 +167,8 @@ nv50_dmac_create(struct nvif_device *dev...

...clude "wndw.h" +#include "handles.h" #include <linux/dma-mapping.h> #include <linux/hdmi.h> @@ -154,7 +155,8 @@ nv50_dmac_create(struct nvif_device *device, struct nvif_object *disp, if (!syncbuf) return 0; - ret = nvif_object_init(&dmac->base.user, 0xf0000000, NV_DMA_IN_MEMORY, + ret = nvif_object_init(&dmac->base.user, NV50_DISP_HANDLE_SYNCBUF, + NV_DMA_IN_MEMORY, &(struct nv_dma_v0) { .target = NV_DMA_V0_TARGET_VRAM, .access = NV_DMA_V0_ACCESS_RDWR, @@ -165,7 +167,8 @@ nv50_dmac_create(struct nvif_device *dev...

https://bugzilla.netfilter.org/show_bug.cgi?id=1739 Bug ID: 1739 Summary: meta mark 0x80000000 display error Product: nftables Version: 1.0.x Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: k at

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/shader/Makefile | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/src/shader/Makefile b/src/shader/Makefile index 46658e9..2d789be 100644 --- a/src/shader/Makefile +++ b/src/shader/Makefile @@ -24,20 +24,21 @@ NVF0_SHADERS = xfrm2nvf0.vpc \ videonvf0.fpc SHADERS = $(NVC0_SHADERS)

...EAU(0): [drm] DRM interface version 1.3 (II) NOUVEAU(0): [drm] created "nouveau" driver at busid "pci:0000:01:00.0" (II) NOUVEAU(0): [drm] added 8192 byte SAREA at 0xf8abb000 (II) NOUVEAU(0): [drm] mapped SAREA 0xf8abb000 to 0xb7f9e000 (II) NOUVEAU(0): [drm] framebuffer handle = 0xf0000000 (II) NOUVEAU(0): [drm] added 1 reserved context for kernel (II) NOUVEAU(0): [drm] installed DRM signal handler drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevi...

Completely fresh,virgin install of b115 SXCE ,zero modifications done. If select XVM from boot menu,it comes all the way till "Starting Desktop login on Display:0..." and reboots. Regular Solaris(not XVM) boots fine. Intel XEON CPU,8G RAM Intel S3210SHLX motherboard(http://www.intel.com/Products/Server/Motherboards/Entry-S3200SH/Entry-S3200SH-overview.htm) Please help and thanks a lot

The XenPVHVM extensions have not been tested much on very old hypervisors. At least Xen 3.4 gets some testing with the pvops kernel. Require at least Xen 3.4 for the PVonHVM extensions. If an older hypervisor is detected the extensions will be disabled and the guest will only see emulated hardware. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- arch/x86/xen/enlighten.c | 27

...xef538000 uncached-minus @ 0xef538000-0xef539000 uncached-minus @ 0xef538000-0xef539000 uncached-minus @ 0xef538000-0xef539000 uncached-minus @ 0xef539000-0xef53a000 uncached-minus @ 0xef539000-0xef53a000 uncached-minus @ 0xef539000-0xef53a000 uncached-minus @ 0xef53a000-0xef53b000 uncached-minus @ 0xf0000000-0xf8000000 uncached-minus @ 0xf00e0000-0xf00e1000 uncached-minus @ 0xf0100000-0xf0101000 uncached-minus @ 0xf0101000-0xf0102000 uncached-minus @ 0xfdac0000-0xfdad0000 uncached-minus @ 0xfdae0000-0xfdaf0000 uncached-minus @ 0xfdaf0000-0xfdb00000 uncached-minus @ 0xfdc43000-0xfdc44000 uncached-minus...

...fffffff] node 0 link 0: mmio [fc000000, fdfeffff] node 0 link 0: mmio [e0000000, efffffff] ==> none node 0 link 0: mmio [a0000, bffff] node 0 link 0: mmio [fdff0000, ffffffff] TOM2: 0000000120000000 aka 4608M bus: [00, 07] on node 0 link 0 bus: 00 index 0 [io 0x0000-0xffff] bus: 00 index 1 [mem 0xf0000000-0xffffffff] bus: 00 index 2 [mem 0x000a0000-0x000bffff] bus: 00 index 3 [mem 0x120000000-0xfcffffffff] ACPI: bus type pci registered PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) PCI: not using MMCONFIG PCI: Using configuration type 1 for base access PCI...

...anged things around to ensure that the first color output ends > up in r0..r3 in the nouveau shader too. The shader generated by > nouveau is: > > HDR[00] = 0x00021462 > HDR[04] = 0x00000000 > HDR[08] = 0x00000000 > HDR[0c] = 0x00000000 > HDR[10] = 0x00000000 > HDR[14] = 0xf0000000 > HDR[18] = 0x00000000 > HDR[1c] = 0x00000000 > HDR[20] = 0x00000000 > HDR[24] = 0x00000000 > HDR[28] = 0x00000000 > HDR[2c] = 0x00000000 > HDR[30] = 0x00000000 > HDR[34] = 0x00000000 > HDR[38] = 0x00000000 > HDR[3c] = 0x00000000 > HDR[40] = 0x00000000 > HDR[44]...