similar to: nouveau_fan_update: possible circular locking dependency detected

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

This may not be the proper place to raise this question but I've had little luck elsewhere. After trying again, unsuccessfully this time, to install the proprietary NVIDIA driver, I've decided to focus my efforts on the open source Nouveau driver. I've seen video drivers blamed for varying degrees of "freeze on resume" but I'm not certain that's what I'm up

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

Hey, Are there any known issues with the Intel''s integrated HD graphics 4000? I just bought a new laptop and have tried everything I can think of to get Xen to load. After choosing Xen in GRUB, it just boots to a black screen. There is no error message , no dmesg output, nothing. I have no idea what is causing this problem. I''ve gotten Xen to install with no problems on another

Hi all, I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video card. I want to install FreeBSD 9-Release on it via PXE, but after booting the system, it seems that video card driver doesn't work properly. Have a look at this picture: http://img703.imageshack.us/img703/5648/20120714393.jpg I've tried the # vidcontrol 80x25 but unfortunately it doesn't help. Do

Hello, I''m getting many "Error getting mfn" on a xen4.1.3 with dom0 3.4.11 x86_32. I thought it could be related to xen/mmu: Release just the MFN list, not MFN list and part of pagetables. http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=785f62314984ea3af9dd830b020289ba2509ae69 (XEN) Freed 212kB init memory. (XEN) mm.c:908:d0 Error getting mfn 2009b (pfn

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

[ 0.000000] microcode: CPU0 microcode updated early to revision 0x1b, date = 2014-05-29 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc3+ (airlied at crackbookpro) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #44 SMP Sat Dec 5 16:05:39 AEST 2015 [

https://bugs.freedesktop.org/show_bug.cgi?id=76818 Priority: medium Bug ID: 76818 Assignee: nouveau at lists.freedesktop.org Summary: Xorg EQ overflowing lock up QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: max.snow at 4mation.com.au

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Hi, I am having problems with the nouveau driver from Debian. Can I get help here? Cheers

I was using my computer normally when suddenly my btrfs volume became read-only. This is on Chris'' for-linus branch (latest commit cb77fcd88) Here''s the relevant excerpt from dmesg [ 50.877500] r8169 0000:01:00.0: eth1: link up [ 50.880296] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 60.959215] eth1: no IPv6 routers present [ 1904.463247] atkbd serio0: Unknown key

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

For some reason it seems to fail somewhere in either nouveau_display_create or nouveau_display_init. Kernel 3.16 is nearly 2 years old though, and countless changes and fixes have gone into the nouveau kernel driver since then. Does this still happen with a recent kernel? You can try a livecd from https://nouveau.pmoreau.org/ which has all the very latest nouveau-related software. On Wed, Jul 6,

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

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001