00:40imirkin: Lyude: unfortunately that test is hardcoded for 160x160 =/
00:40imirkin: anyways, wtvr
00:40imirkin: i think a lot of tests are buggy like that
04:00vpelletier: imirkin: if you are around, I just booted my ppc64 on the same 4.11.8 kernel, this time with nouveau.config=NvMSI=0 nouveau.vram_pushbuf=1 (as I was not intending to debug the MSI issue) and I caught this line during boot:
04:01vpelletier: nouveau 0001:06:00.0: bus: MMIO write of 00000000 FAULT at 6813c8
04:02vpelletier: the card is still in the "wrong" slot (PCIe 4x under a bridge under hypertransport bus, and not on the dedicated PCIe 16x (native ?) bus)
04:05imirkin: did it have one of the patches i had you try with endianness?
04:05vpelletier: (but this boot seems to have other issues too, windfarm kernel thread is stuck and cpu0 was soft-locked when I tried to reboot)
04:08vpelletier: I do not think, checking
04:10vpelletier: there is no "+" suffix to the uname, so the working copy was clean AFAIK. and I do not see any local commit I would have done with these patches
04:11vpelletier: OTOH, after a forced shutdown and another boot, I do not see this error anymore :(
04:17vpelletier: another issue I noticed was that the card is not considered as supporting opengl 2.1 and I remember you said this comes from endianness and GL_* color formats
04:18mooch2: mwk: pls bby work on nv3
04:18vpelletier: if I understand correctly, this would be a mesa-level fix (likely nouveau-specific)
04:20mooch2: imirkin, i added the dumb fucking pci device id configuration to my nvidia emulation
04:20mooch2: why oh why did they have to do that
04:40vpelletier: imirkin: ...and I cannot identify where mesa is probing driver for supported extensions (as nouveau does not reference sRGB I guess it instead exposes some lower-level capabilities that mesa uses to decide which GL-level extensions are available). Any hint ?
04:41vpelletier: fwiw I'm looking in src/mesa as of 9ac1432a5714f2c946d005dcdaa90dc5f738a6d8
04:41vpelletier: from git://anongit.freedesktop.org/git/mesa/mesa
04:42imirkin: and nv30_format.c
04:42imirkin: the issue could also be a lack of a byte-swapped srgb format
08:28ccaione: hey guys, any idea on https://bugs.freedesktop.org/show_bug.cgi?id=101782 ?
15:30docmax: boah geht mir das auf den keks
15:30docmax: etwas total simples und es schreibt keiner eine vernünftige anleitung im netz
15:30docmax: /dev/sda als NBD exportieren
15:30docmax: wie geht das?
15:30docmax: oh wrong channel
15:31mupuf: indeed :)
15:32RSpliet: poor biscuits...
16:07karolherbst: docmax: very wrong :p
22:38tobijk: mhh does the atomic modeset thingy really handle the complete modeset enable/disable for nouveau already? :o
22:40imirkin: for nv50+ yea
22:41tobijk: so thats ith then: https://hastebin.com/qizekuhepi.md
22:41tobijk: pretty unspectactular
22:42tobijk: whoops wrong one
22:43tobijk: this one: https://hastebin.com/uzetimemes.md
22:43imirkin: the if might go elsewhere. it's also questionable whether pre-nv50 needs it. i think skeggsb is just removing it.
22:44tobijk: yeah the if goes outside the loop for the final one
22:44tobijk: not sure if it is needed fpr pre nv50, but maybe keep it for now?!
22:45imirkin: ben's taking care of it :)
22:45imirkin: there are some additional vblank-related issues he's trying to address while he's at it
22:51skeggsb: just removing it leads to hitting other WARNs
22:52imirkin: of course it does.
22:52skeggsb: unfortunately.. the interactions of off/on/get/put and a combination of how the hw works + how we use it makes it non-trivial to implement all the rest "properly"
22:52tobijk: so encapsulate the for_each with !drm_drv_uses_atomic_modeset(dev)
22:53tobijk: does the trick for me
22:53skeggsb: tobijk: the warns happen *on* the atomic path
22:53skeggsb: unload the module, for example..
22:53tobijk: with the crtc attached?
22:54skeggsb: i don't think we need it for the non-atomic path either (we shutdown all crtcs, and the dispnv04 code calls off when a crtc is disabled already), but i hvaen't explicitly tested that yet
22:58tobijk: mh i'm no expert in unloading :D (dont get it done)
22:58tobijk: does it happen when you put the system to hibernate?
23:01tobijk: never mind, got the warning