similar to: BTRFS crash on mount with 3.4.4

https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

dmesg output after a resume from a suspend. the device in question was /dev/sdb mounted on /home. after a device failure to resume properly, the link is then reset by the kernel but comes back as /dev/sde. /dev/sdb disappeared entirely, and is now referred to as sde. attempted to remount rw of sde, seemed to succeed, mount/mtab said that it was rw now but i couldn''t write to the volume

Dear CentOS users, I run a small Facebook game at a CentOS 6.3 machine with PostgreSQL 8.4.3 + few PHP scripts + 1 Perl daemon and even though the server worked ok, I've suggested my users to double up the RAM to 32 GB and they have collected money for that. Now my problem is that I don't know, which knob to turn and how to really use the additional memory. Below is my top output at the

Does anybody please have any experience with the following CentOS 6 warnings in logwatch? WARNING: Kernel Errors Present ACPI Error (psargs-0359): [ ...: 1 Time(s) pci 0000:00:01.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.5: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.6: PCIe errors

Hello. Minimal testcase for my problem: No X running, just a TTY. Use of the nouveau kernel module as of today (or any older) with an up to date vanilla kernel. Hardware: DELL Vostro 3500 with Geforce 310M. To suspend to ram I use this script, as suggested in Documentation/power/s2ram.txt: #!/bin/sh sync echo 1 > /sys/power/pm_trace echo mem > /sys/power/state When I try to suspend to

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important The Xen hypervisor very unreliably boots on my 4GB Lenovo Thinkpad T400 2765D2G. Right after installation it booted the DomO kernel from linux-image-2.6.26-1-xen-amd64 without any problems, but every subsequent restart failed completely. Once I had a XEN "early fatal page fault" error message, on every other of

Hi there, with the latest snapshot of linus tree, i see a stack trace and my system does not start X! Maybe someone finds this useful! (3.11 is working like a charm) BUG: unable to handle kernel NULL pointer dereference at (null) IP: [< (null)>] (null) PGD 24eaa0067 PUD 24e7ac067 PMD 0 Oops: 0010 [#1] PREEMPT SMP Modules linked in: bnep snd_hda_codec_hdmi

Hi, I have an Optimus-enabled laptop with a GTX 1060m. I never got it to fully work with Nouveau even after Pascal support was added. I need to run the kernel with nouveau.runpm=0 to get it to work. Unfortunately without proper power mangement support, my laptop will run out of battery after about 1h30, so I'd love to get Optimus working. What I can see is that when the extra GPU is not in

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal Hello, I was running Xen for a few years and after a PSU failure I never got the system working stable again. I suspected damage to the board so I replaced everything in the system piece by piece but Xen enabled kernel always crashes even with only Dom0 running when moderate amount of IO happens on the box. kvm seems

Hei, 839ca903f12e (drm/nouveau/kms/nv50: transition to atomic interfaces internally, 2016-11-04) seems to introduce a regression on my machine. Attached dmesg output. Has anyone else seen this on a MacBookPro? Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu -------------- next part -------------- [ 0.000000] microcode: microcode updated early to revision 0x16, date = 2016-04-01 [

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-6 Severity: normal Dear Maintainer, I'm trying to boot into xen/dom0 but so far all attempts have resulted in a crash followed by an automatic reboot. My hardware is Motherboard: Asus Sabertooth 990FX R2.0 CPU: AMD FX-8350 GPU: Sapphire Radeon R9 285 A trace of the kernel panic follows (full log captured over serial should

Hello again, I would be very glad if you could help me: I have a blank screen on my Debian jessie system and on the current Debian live cd. When i use the nomodeset param I can get a console but startx fails. (obviously since then nouveau wont work) The card is a 660Ti with UEFI VBIOS. Error in Xorg: "[drm] KMS not enabled [drm] Couldn't open device.... and so on" I quote the

Hi. While testing subvolumes in btrfs on 2.6.32.9, I hit a kernel BUG: [ 492.164012] kernel BUG at fs/btrfs/inode.c:4365! The commands to reproduce this bug are as follows: # mount -t btrfs /dev/sda5 /scratch # btrfsctl -S subvol /scratch # date > /scratch/date # ln /scratch/date /scratch/subvol/ ln segfaults, and the bug above is found in dmesg. Subsequent accesses to the subvolume

Thanks for the quick help! Indeed a kernel update resolved the issue, there one problem left though: I get an error: Xorg.0.log: Couldn't load sub module "fb". I can't find out what package this module is part of. Maybe you know? I already purged and reinstalled xserver-xorg and xserver-xorg-core with no effect. Cheers Am 06.07.2016 um 23:06 schrieb Ilia Mirkin: > For

Hm, well you can see the messages about failure to set plls, which is why you don't see anything. The only odd thing I see is that you're using vesa, which can definitely mess things up. Try not using that. Also try booting with nouveau.debug=debug drm.debug=0xe which might provide more relevant info. On Jun 12, 2015 8:34 AM, "Andre Campos Rodovalho" <andre.rodovalho at

Hi, I took this issue to the Fedora forum initially, but no-one there has been able to offer any guidance, so I have decided to come to the nouveau community directly. I was running a KDE desktop under Fedora 21 successfully, including the ability to use a direct text login on an older card (GXT 560 Ti) with an entirely stock Fedora, fully updated. I simply replaced the old card with an

Ok, nevermind the problem was ofcourse some idiot, who specified a wrong path for said fb module. (obviously me) Startx works now, my gnome crashes with “Oh no! Something has gone wrong.”, but I guess this has nothing to do with nouveau so you can take this case as solved! Installing the new kernel solved all issues, but I really don’t know, why Debian ships such an old kernel… Von: Ilia

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: grave Hello, I am trying to install the XEN Hypervisor on a Debian Jessie Server. When I am booting without the Hypervisor, everything works fine, but when I am Booting WITH the XEN-Hypervisor, then System crashes / reboots after the "Scrubbing Free RAM" Message without any Error-message, just a blank screen.