similar to: 3.12rc1-pre Nouveau? oops

On Sun, Sep 8, 2013 at 12:53 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > 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) Looks like you have Optimus (intel + nvidia), and the backtrace has runtime pm in it, which is something new

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

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

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

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

My kernel crashed for some other reason, and now I can''t mount my btrfs filesystem. I don''t care about the data, it''s backed up. I''ll compile a 3.5 kernel, but is there any info you''d like off that filesystem to see why btrfs is crashing on mount? Marc [ 313.152857] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/disk1 [ 313.171318]

(copying xen-devel, full logs are at bugs.debian.org/748052, this is Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was with though, Wheezy's 3.2 or Jessie's 3.13) On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote: > Here are some results with (now) the latest BIOS version 41. (was >

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

Howdy! I've been doing a lot of troubleshooting, and haven't arrived at a solution yet. Kernel log attached. VBIOS also attached. Ubuntu 19.10 $ uname -a Linux joyful 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l|grep nouveau ii libdrm-nouveau2:amd64 2.4.99-1ubuntu1 amd64

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

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

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

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

Hi all, I'm getting frequent system crashes (every few hours or so) and it seems that the nouveau driver is causing the issue (dmesg output below). I see it with both v5.2.8 and the v4.19 LTS kernel. Sometimes the system completely freezes and sometimes seemingly just the nouveau driver goes down. The screen freezes and colours stream across it. Often after I reboot the BIOS logo is mangled

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

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

2017-07-29 20:17 GMT+08:00 lampahome <pahome.chen@mirlab.org>: > > > 2017-07-29 18:00 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: >> >> > I download the newset package and extract in my >> > path(/share/CACHEDEV1_DATA/appliance/) and set env >> > It doesn't work. >> > and I run the libugestfs-test-tool: >> >>

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