search for: f0000000

...veau: DRM:00000000:0000917d: init running... Feb 28 23:07:11 laptop kernel: [ 13.753072] nouveau: DRM:00000000:0000917d: init children... Feb 28 23:07:11 laptop kernel: [ 13.753073] nouveau: DRM:00000000:0000917d: init completed in 25us Feb 28 23:07:11 laptop kernel: [ 13.753098] nouveau: DRM:f0000000:0000003d: init running... Feb 28 23:07:11 laptop kernel: [ 13.753099] nouveau: DRM:f0000000:0000003d: init children... Feb 28 23:07:11 laptop kernel: [ 13.753100] nouveau: DRM:f0000000:0000003d: init completed in 1us Feb 28 23:07:11 laptop kernel: [ 13.753111] nouveau: DRM:f0000001:0000003d:...

...000:0000917d: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753072] nouveau: DRM:00000000:0000917d: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753073] nouveau: DRM:00000000:0000917d: init completed in 25us > Feb 28 23:07:11 laptop kernel: [ 13.753098] nouveau: DRM:f0000000:0000003d: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753099] nouveau: DRM:f0000000:0000003d: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753100] nouveau: DRM:f0000000:0000003d: init completed in 1us > Feb 28 23:07:11 laptop kernel: [ 13.753111] nouveau: DRM:f000...

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

...=0x0. gpe_en_write: addr=0x1f6e, val=0x0. gpe_en_write: addr=0x1f6f, val=0x0. gpe_en_write: addr=0x1f6c, val=0x8. gpe_en_write: addr=0x1f6d, val=0x0. gpe_en_write: addr=0x1f6e, val=0x0. gpe_en_write: addr=0x1f6f, val=0x0. reset requested in cpu_handle_ioreq. Issued domain 15 reboot track_dirty_vram(f0000000, 12c) failed (-1, 3) track_dirty_vram(f0000000, 12c) failed (-1, 3) Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...+nouveau: DRM:00000000:00000002: fini completed in 64us nouveau: DRM:00000000:00000002: destroy children... nouveau: DRM:00000000:00000002: destroy running... -nouveau: DRM:00000000:00000002: destroy completed in 69us... +nouveau: DRM:00000000:00000002: destroy completed in 68us... nouveau: DRM:f0000000:0000003d: init running... nouveau: DRM:f0000000:0000003d: init children... -nouveau: DRM:f0000000:0000003d: init completed in 64us +nouveau: DRM:f0000000:0000003d: init completed in 66us nouveau: DRM:f0000001:0000003d: init running... nouveau: DRM:f0000001:0000003d: init children... -nouveau: DR...

Occasionally I see the message '' track_dirty_vram(f0000000, 26) failed (-1, 3)'' in the qemu-dm logs as the DomU reboots. Is it a concern at all? Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...ws 2008) was started ,and you can still connect to the consolev via VNC but just get a static image.there is no network access to the VM.User domain is a web server on windows 2008.The last time it occurred I noticed in the /var/log/xen/qemu-xxxxxxxxx.log of the following message : track_dirty_vram(f0000000, 26) failed (-1, 3) can u help me resolve this issue.thank you! hiam Brs Telephone：18922958921 13480228533 E-mail：lizx@g-cloud.com.cn _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

Hi there, I am gettings tons of messages in dmesg output such as: [...] [ 2419.238990] [drm:drm_mode_addfb2 [drm]] [FB:65] [ 2419.243388] 00a0 2 base507c_ntfy_set [ 2419.243391] 00000060 [ 2419.243391] f0000000 [ 2419.243393] 0084 1 base827c_image_set [ 2419.243394] 00000010 [ 2419.243395] 00c0 1 base827c_image_set [ 2419.243395] fb00007a [ 2419.243396] 0110 2 base827c_image_set [ 2419.243397] 00000000 [ 2419.243398] 00000000 [ 2419.243399] 0800 5 base827c_image_set [ 2419.243399] 0007ce00 [ 2419.243400]...

...s and the workstation are Debian Squeeze installed from bootstrap with almost identical installs. I have searched for similar situations on Google and the forums, but have come up empty handed. Only thing I can see from /var/log/xen/qemu-dm-rasfs.log is the last line says track_dirty_vram(f0000000, 26) failed (-1,3). Any help would be apprecitated on how to resolve this. Thank you -- Shane D. Johnson IT Administrator Rasmussen Equipment Workstation Server 1 Server 2 CPU Phenom 9950 Opteron 6174 Phenom 1100t MB Gigabyte ga-ma790x-ds4 Asus M4A78LT-M Asus KGPE-D16 Mem 8G...

...Device 1100 Physical Slot: 2 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Region 0: Memory at f0000000 (32-bit, prefetchable) [size=32M] Region 1: Memory at f2000000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at f2010000 [disabled] [size=64K] How can I increase the resolution? Are any guest modifications necessary? -- Christian

...rporation physical id: 0 bus info: pci at 0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller cap_list configuration: latency=0 resources: memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f7000000-f707ffff Thanks, Marius Gripsgard -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20160510/4aa51032/attachment.html>

...try? THanks, jerry 01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01) (prog-if 00 [VGA]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7142 Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 201 Memory at f0000000 (32-bit, prefetchable) [size=64M] Memory at f4000000 (32-bit, non-prefetchable) [size=16M] Capabilities: [60] Power Management version 2 Capabilities: [70] AGP version 3.0

...RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. xs_read(/local/domain/0/device-model/35/xen_extended_power_mgmt): read error I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 It says something with xen_extended_power_mgmt Who can help me ? Cheers, Maik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...mething in your VBIOS is different, or if the logic has regressed. (It would have been working in 4.4 or so.) You can find the VBIOS in of, it's called "NVDA,BMP", should be accessible in procfs or sysfs somewhere, but not 100% sure where. (From an old guide, /proc/device-tree/pci at f0000000/NVDA,Parent at 10/NVDA,BMP seems to be it, possibly with some local adjustments.) Thanks, -ilia

...#39;dhcp'' vif = [ ''mac=00:16:3E:FF:00:8D'' ] pci = [ ''04:04.0'' ] extra = ''2 console=hvc0'' Parts from dmesg on domU that could be interesting; [ 0.000000] Allocating PCI resources starting at 20000000 (gap: 10000000:f0000000) [ 0.038071] PCI: Fatal: No config space access function found [ 0.040252] PCI: System does not support PCI [ 0.040258] PCI: System does not support PCI [ 0.271698] XENBUS: Device with no driver: device/pci/0 _______________________________________________ Xen-users mailing list Xen-u...

...Interrupt: pin A routed to IRQ 16 Region 0: Memory at f0810000 (32-bit, non-prefetchable) [disabled] [size=256] Region 1: I/O ports at e000 [disabled] [size=256] Region 2: Memory at e0000000 (32-bit, non-prefetchable) [disabled] [size=256M] Region 3: Memory at f0000000 (32-bit, non-prefetchable) [disabled] [size=8M] Expansion ROM at f0800000 [disabled] [size=64K] Capabilities: [40] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable-...

...[drm]] [CRTC:40:head-0] [ 2368.141717] [drm:drm_mode_setcrtc [drm]] [CONNECTOR:44:DVI-I-1] [ 2368.141735] 0900 1 nv50_head_base [ 2368.141736] 00000001 [ 2368.141737] 08a0 1 nv50_head_dither [ 2368.141737] 00000003 [ 2368.141752] 00a0 2 nv50_base_ntfy_set [ 2368.141752] 00000120 [ 2368.141753] f0000000 [ 2368.141754] 0084 1 nv50_base_image_set [ 2368.141754] 00000010 [ 2368.141755] 00c0 1 nv50_base_image_set [ 2368.141755] fb000000 [ 2368.141756] 0800 5 nv50_base_image_set [ 2368.141756] 00009400 [ 2368.141757] 00000000 [ 2368.141757] 04b00780 [ 2368.141757] 00100800 [ 2368.141758] 00001e0...

...lt;MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at d000 [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)...