similar to: IO error after s2ram resume; device stays open

(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 >

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]

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

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

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

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

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then crashes when used=2837436K free=4127432K. By crash I mean the gnome screen was blown away, replaced by a black screen with white log lines. That seems to happen every time dom0 uses a large amount of memory. After setting

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

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

Hi Everyone! I've been trying to get my Nvidia 9800m GT working with the latest nouveau drivers with no luck so far. First of all I'd like to mention that this is a weird card as it is an SLI in one piece of hardware (not 2 separated cards). It came with my Dell XPS M1730 laptop. I know SLI is not currently supported and _I don't want_ to use SLI, I just would like to use one of

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

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 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

Hellow all, i need help to fix this bug: ACPI BIOS Bug: Error: A valid RSDP was not found (20120711/tbxfroot-219) Because of this first errors i get this after, and it causes don''t work USB ports and some PCI cards on the system: can''t find IRQ for PCI INT A; please try using pci=biosirq Kernel: 3.6.1-xen self compiled (work perfect without xen multiboot) Xen Version: 4.2

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

Hi list! I recently butchered my filesystem, and I was wondering if anyone knows how to help. Problem: My filesystem is screwed up, and I can''t mount it at all right now. In the logs, the problem begins around 45s. Background: I''m running a 6x4TB RAID5 array using md. I have a few virtual machines using said array, and one of them is a btrfs storage server. I ran into some

Hello, since weeks I was ignoring this warning at my CentOS 5.6/64 bit machine - /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md0 in the hope that the software RAID will slowly repair itself. I also had executed "echo 100000 > /proc/sys/dev/raid/speed_limit_max" on the advice from the mailing list. But now my web server is offline - I had to boot

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