similar to: irq 45: nobody cared (try booting with the "irqpoll" option)

On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Ben, > commit Hey Thomas, Are you able to double-check that bisect? I'm not at all sure how that particular commit could trigger the issue you're seeing. Some of the others, certainly. It might be worth trying a couple of times before marking something as "good", in case

Hello Ben, commit (mini) [~/work/linux-2.6] git bisect bad 8777c5c11764d8336d8270f96778158c34c92108 is the first bad commit commit 8777c5c11764d8336d8270f96778158c34c92108 Author: Ben Skeggs <bskeggs at redhat.com> Date: Fri Jun 6 18:09:55 2014 +1000 drm/nouveau/dp: probe dpcd to determine connectedness Signed-off-by: Ben Skeggs <bskeggs at redhat.com> introduces a

Hello everyone, the current git HEAD of Linus Torvalds tree breaks Nouveau on my Mac Mini Model 2010. I get variation of the following kernel panic when booting. (gateway) [~] nc -u -l -p 6666 [ 3.796018] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.796100] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.796304] ata1.00: ATA-7: INTEL SSDSA2M160G2GC, 2CV102HA, max

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

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

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

dmesg output: --------------------------------------------------------------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-38-generic (buildd at allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #52~14.04.1-Ubuntu

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]

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

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

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 [

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

Hello, The idea was to use the modesetting DDX instead of Nouveau’s one for Maxwell+ as EXA was [broken][1]. But you can give a try at Ilia’s [patches][2], which fix the Nouveau DDX for GM10x and GM20x (I don’t think it has been tested on a GM108 yet). Best regards, Pierre Moreau [1]: https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3e2e0faa2ee1cce9c1bb5c7ad80d0592460f3edc

hi, give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with 4.9, so 4.10 is required. Greetings. On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" <smo at translucent.dk> wrote: >Hi again, > >It works :-) > >Reclocking, however, is another kettle of fish. > >Trying #echo 0f > /sys/kernel/debug/dri/0/pstate

also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.

you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all

Hallo, while trying to use nouveau drivers with GFX 5500 I've got nothing but hang-ups of my machine. The hangup occurs after I'm trying to start Xwindow (not directly, when machine is booting up). After it occured, keyboard isn't available anymore, and I can't switch machine off gracefully with ATX power button. The test has been done with recommended "4-line