[Nouveau] [Bug 93887] [NV96] Amilo Xi 3650: G96M [GeForce 9600M GT]: HDMI monitor stays black after s2ram
https://bugs.freedesktop.org/show_bug.cgi?id=93887 --- Comment #47 from Elmar Stellnberger --- Created attachment 125809 --> https://bugs.freedesktop.org/attachment.cgi?id=125809&action=edit vbios+nvapeek-0x101000-Celsius-H270.tar.bz2 Hmm, while the pramin-method produces a smaller output the prom-method reports an invalid signature (see for the *.msg in the .tar.bz2). Anyway both VROMs are different from the corrupted image that should have been fetched on my H265 (both having used the latest envytools-git 1:0.r4326.6e27990-1 from Arch-AUR). Having applied nvapeek 0x101000 0x2 in UHD-Xinerama mode with 2 screens (as usual). Just let me know if you should need something else; I will provide it as soon as possible. -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] [PATCH] drm/nouveau: add Maxwell to backlight initialization
@Ben: ping I would guess that the same can be done for Pascal as well. Cheers, Pierre On 02:41 PM - May 21 2016, Faris Alsalama wrote: > Signed-off-by: Faris Alsalama > --- > drivers/gpu/drm/nouveau/nouveau_backlight.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c > b/drivers/gpu/drm/nouveau/nouveau_backlight.c > index 89eb460..dd1cc9b 100644 > --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c > +++ b/drivers/gpu/drm/nouveau/nouveau_backlight.c > @@ -232,6 +232,7 @@ nouveau_backlight_init(struct drm_device *dev) > case NV_DEVICE_INFO_V0_TESLA: > case NV_DEVICE_INFO_V0_FERMI: > case NV_DEVICE_INFO_V0_KEPLER: > + case NV_DEVICE_INFO_V0_MAXWELL: > return nv50_backlight_init(connector); > default: > break; > -- > 2.1.4 > > ___ > Nouveau mailing list > Nouveau@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau signature.asc Description: PGP signature ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] v4.8-rc2 crashes while probing nvidia graphics card on arm64
I made a hash of LKML email in the previous mail. Re-sending with the address corrected. Apologies for the duplicate. Punit Agrawal writes: > Hi, > > While trying out v4.8-rc2 on Juno r2 (arm64), I ran into the following > crash when probing the nvidia graphics card attached to the PCIe > slot. So I tried rc1 and got the same crash. The card probes without any > errors on v4.7. > > Anybody familiear with the recent changes knows what might have led to > the below crashlog? > > Thanks, > Punit > > ->8- > > [2.996678] [drm] Initialized drm 1.1.0 20060810 > [3.001495] nouveau :06:00.0: enabling device ( -> 0003) > [3.007574] nouveau :06:00.0: NVIDIA GT218 (0a8c00b1) > [3.145407] nouveau :06:00.0: bios: version 70.18.9f.00.09 > [3.202137] nouveau :06:00.0: fb: 512 MiB DDR3 > [3.260766] [TTM] Zone kernel: Available graphics memory: 4070004 kiB > [3.267243] [TTM] Zone dma32: Available graphics memory: 2097152 kiB > [3.273715] [TTM] Initializing pool allocator > [3.278048] [TTM] Initializing DMA pool allocator > [3.282738] nouveau :06:00.0: DRM: VRAM: 512 MiB > [3.287663] nouveau :06:00.0: DRM: GART: 1048576 MiB > [3.292935] nouveau :06:00.0: DRM: TMDS table version 2.0 > [3.298634] nouveau :06:00.0: DRM: DCB version 4.0 > [3.303731] nouveau :06:00.0: DRM: DCB outp 00: 02000360 > [3.310118] nouveau :06:00.0: DRM: DCB outp 01: 02000362 00020010 > [3.316505] nouveau :06:00.0: DRM: DCB outp 02: 028003a6 0f220010 > [3.322891] nouveau :06:00.0: DRM: DCB outp 03: 01011380 > [3.329277] nouveau :06:00.0: DRM: DCB outp 04: 08011382 00020010 > [3.335663] nouveau :06:00.0: DRM: DCB outp 05: 088113c6 0f220010 > [3.342049] nouveau :06:00.0: DRM: DCB conn 00: 00101064 > [3.347661] nouveau :06:00.0: DRM: DCB conn 01: 00202165 > [3.359132] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [3.365698] [drm] Driver supports precise vblank timestamp query. > [3.412273] nouveau :06:00.0: DRM: MM: using COPY for buffer copies > [3.445319] nouveau :06:00.0: DRM: allocated 1024x768 fb: 0x7, bo > 8009764ba400 > [3.570962] Unable to handle kernel paging request at virtual address > 091e11d4 > [3.570964] pgd = 09051000 > [3.570971] [091e11d4] *pgd=0009e003, > *pud=0009d003, *pmd=00099003, *pte=00e80009f5cc4703 > [3.570975] Internal error: Oops: 9661 [#1] PREEMPT SMP > [3.570978] Modules linked in: > [3.570982] CPU: 2 PID: 1 Comm: swapper/0 Not tainted > 4.8.0-rc2-1-g5077753 #1 > [3.570984] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno > Development Platform, BIOS EDK II Aug 5 2016 > [3.570986] task: 800976ca8000 task.stack: 800976cb > [3.570999] PC is at __memcpy+0x7c/0x180 > [3.571003] LR is at OUT_RINGp+0x34/0x70 > [3.571006] pc : [] lr : [] pstate: > 8145 > [3.571007] sp : 800976cb3350 > [3.571011] x29: 800976cb3350 x28: 000e > [3.571014] x27: 8009760f2000 x26: 0001 > [3.571018] x25: 07ff x24: 40006860 > [3.571021] x23: 0005 x22: 8009760f2010 > [3.571024] x21: 0004 x20: 0004 > [3.571026] x19: 800976f67000 x18: > [3.571029] x17: 0008 x16: 800976000c00 > [3.571032] x15: 0018 x14: 03030326 > [3.571035] x13: 8009766b1000 x12: 0540 > [3.571038] x11: 02b68908 x10: 0870 > [3.571042] x9 : 0005 x8 : > [3.571045] x7 : x6 : 091e11d4 > [3.571048] x5 : x4 : > [3.571051] x3 : 0010 x2 : 0010 > [3.571053] x1 : 8009760f2010 x0 : 091e11d4 > [3.571054] > [3.571057] Process swapper/0 (pid: 1, stack limit = 0x800976cb0020) > [3.571059] Stack: (0x800976cb3350 to 0x800976cb4000) > [3.571062] 3340: 800976cb3370 > 0866fcb4 > [3.571065] 3360: 800976f67000 800976cb33c0 > 0866e2cc > [3.571068] 3380: 8009761c1800 800975cee400 8009766b0058 > 8009766b > [3.571071] 33a0: 0010 0010 8009761c1800 > 80097619ac00 > [3.571074] 33c0: 800976cb33f0 084aa794 800975cee400 > 800976cb34d8 > [3.571076] 33e0: 0001 800975cee450 800976cb3450 > 084aa1c4 > [3.571079] 3400: 80097619ac00 800976cb34d8 800975cee200 > 8009761c1800 > [3.571082] 3420: 0720 08a6ad08 > 0002 > [3.571084] 3440: 08679bf8 800976cb3540
[Nouveau] v4.8-rc2 crashes while probing nvidia graphics card on arm64
Hi, While trying out v4.8-rc2 on Juno r2 (arm64), I ran into the following crash when probing the nvidia graphics card attached to the PCIe slot. So I tried rc1 and got the same crash. The card probes without any errors on v4.7. Anybody familiear with the recent changes knows what might have led to the below crashlog? Thanks, Punit ->8- [2.996678] [drm] Initialized drm 1.1.0 20060810 [3.001495] nouveau :06:00.0: enabling device ( -> 0003) [3.007574] nouveau :06:00.0: NVIDIA GT218 (0a8c00b1) [3.145407] nouveau :06:00.0: bios: version 70.18.9f.00.09 [3.202137] nouveau :06:00.0: fb: 512 MiB DDR3 [3.260766] [TTM] Zone kernel: Available graphics memory: 4070004 kiB [3.267243] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [3.273715] [TTM] Initializing pool allocator [3.278048] [TTM] Initializing DMA pool allocator [3.282738] nouveau :06:00.0: DRM: VRAM: 512 MiB [3.287663] nouveau :06:00.0: DRM: GART: 1048576 MiB [3.292935] nouveau :06:00.0: DRM: TMDS table version 2.0 [3.298634] nouveau :06:00.0: DRM: DCB version 4.0 [3.303731] nouveau :06:00.0: DRM: DCB outp 00: 02000360 [3.310118] nouveau :06:00.0: DRM: DCB outp 01: 02000362 00020010 [3.316505] nouveau :06:00.0: DRM: DCB outp 02: 028003a6 0f220010 [3.322891] nouveau :06:00.0: DRM: DCB outp 03: 01011380 [3.329277] nouveau :06:00.0: DRM: DCB outp 04: 08011382 00020010 [3.335663] nouveau :06:00.0: DRM: DCB outp 05: 088113c6 0f220010 [3.342049] nouveau :06:00.0: DRM: DCB conn 00: 00101064 [3.347661] nouveau :06:00.0: DRM: DCB conn 01: 00202165 [3.359132] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.365698] [drm] Driver supports precise vblank timestamp query. [3.412273] nouveau :06:00.0: DRM: MM: using COPY for buffer copies [3.445319] nouveau :06:00.0: DRM: allocated 1024x768 fb: 0x7, bo 8009764ba400 [3.570962] Unable to handle kernel paging request at virtual address 091e11d4 [3.570964] pgd = 09051000 [3.570971] [091e11d4] *pgd=0009e003, *pud=0009d003, *pmd=00099003, *pte=00e80009f5cc4703 [3.570975] Internal error: Oops: 9661 [#1] PREEMPT SMP [3.570978] Modules linked in: [3.570982] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.8.0-rc2-1-g5077753 #1 [3.570984] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Aug 5 2016 [3.570986] task: 800976ca8000 task.stack: 800976cb [3.570999] PC is at __memcpy+0x7c/0x180 [3.571003] LR is at OUT_RINGp+0x34/0x70 [3.571006] pc : [] lr : [] pstate: 8145 [3.571007] sp : 800976cb3350 [3.571011] x29: 800976cb3350 x28: 000e [3.571014] x27: 8009760f2000 x26: 0001 [3.571018] x25: 07ff x24: 40006860 [3.571021] x23: 0005 x22: 8009760f2010 [3.571024] x21: 0004 x20: 0004 [3.571026] x19: 800976f67000 x18: [3.571029] x17: 0008 x16: 800976000c00 [3.571032] x15: 0018 x14: 03030326 [3.571035] x13: 8009766b1000 x12: 0540 [3.571038] x11: 02b68908 x10: 0870 [3.571042] x9 : 0005 x8 : [3.571045] x7 : x6 : 091e11d4 [3.571048] x5 : x4 : [3.571051] x3 : 0010 x2 : 0010 [3.571053] x1 : 8009760f2010 x0 : 091e11d4 [3.571054] [3.571057] Process swapper/0 (pid: 1, stack limit = 0x800976cb0020) [3.571059] Stack: (0x800976cb3350 to 0x800976cb4000) [3.571062] 3340: 800976cb3370 0866fcb4 [3.571065] 3360: 800976f67000 800976cb33c0 0866e2cc [3.571068] 3380: 8009761c1800 800975cee400 8009766b0058 8009766b [3.571071] 33a0: 0010 0010 8009761c1800 80097619ac00 [3.571074] 33c0: 800976cb33f0 084aa794 800975cee400 800976cb34d8 [3.571076] 33e0: 0001 800975cee450 800976cb3450 084aa1c4 [3.571079] 3400: 80097619ac00 800976cb34d8 800975cee200 8009761c1800 [3.571082] 3420: 0720 08a6ad08 0002 [3.571084] 3440: 08679bf8 800976cb3540 084a64d8 [3.571087] 3460: 800976c14000 8009761c1800 084a9cd0 0002 [3.571089] 3480: 0720 800976c141e0 800976c14200 [3.571092] 34a0: 0007 0100 08b1c308 0866b770 [3.571095] 34c0: 8009
Re: [Nouveau] XDC2016
2016-08-15 11:09 GMT+02:00 Martin Peres : > On 15/08/16 11:53, Pierre Moreau wrote: >> >> Hello everyone, >> >> Same place as FOSDEM? XDC is in Helsinki and FOSDEM was in Brussels… >> (IIRC, >> FOSDEM is always located in Brussels.) I would prefer picking an hotel in >> Helsinki rather than traveling every day between Helsinki and Brussels. >> :-p Or >> was that what you meant by "more or less"? :-D >> >> I’ve taken days off starting from Tuesday, so I could even arrive on >> Monday >> evening if there are other persons coming that early. :-) And I am >> planning to >> stay until Sunday (could be Sunday evening, I haven’t booked the hotel nor >> the >> transport yet); apart from a short trip back to Sweden between Friday and >> Saturday. >> >> Cheers, >> Pierre > > > Well, if all of you (Roy, Pierre, Karol and Samuel) want, you can definitely > come to my place. Roy and Samuel were interested already and I assume Ben > will stay with the other red hatters. I have enough space for everyone > though. > > It is a slightly longer commute and a bit less flexible because of the > limited > number of keys though... but we would be together without needing to spend > money on anything else but food, drinks, transports and saunas. > > Martin >> >> >> >> On 09:35 PM - Aug 13 2016, karol herbst wrote: >>> >>> Hi everybody, >>> >>> I saw that some more appeared on the list of Attendees, so it might be >>> a good time to ask how we want to organize the stay and if we plan to >>> book at the same place like we did on fosdem (well more or less). >>> >>> Also how does everybody plans to stay? I was thinking about Tuesday to >>> Sunday, but if everybody comes at Monday already, I might change my >>> plans ;) > > > Great Karol! You are welcomed to stay at MuPuF Inn sounds like a plan :) ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] XDC2016
On 15/08/16 11:53, Pierre Moreau wrote: Hello everyone, Same place as FOSDEM? XDC is in Helsinki and FOSDEM was in Brussels… (IIRC, FOSDEM is always located in Brussels.) I would prefer picking an hotel in Helsinki rather than traveling every day between Helsinki and Brussels. :-p Or was that what you meant by "more or less"? :-D I’ve taken days off starting from Tuesday, so I could even arrive on Monday evening if there are other persons coming that early. :-) And I am planning to stay until Sunday (could be Sunday evening, I haven’t booked the hotel nor the transport yet); apart from a short trip back to Sweden between Friday and Saturday. Cheers, Pierre Well, if all of you (Roy, Pierre, Karol and Samuel) want, you can definitely come to my place. Roy and Samuel were interested already and I assume Ben will stay with the other red hatters. I have enough space for everyone though. It is a slightly longer commute and a bit less flexible because of the limited number of keys though... but we would be together without needing to spend money on anything else but food, drinks, transports and saunas. Martin On 09:35 PM - Aug 13 2016, karol herbst wrote: Hi everybody, I saw that some more appeared on the list of Attendees, so it might be a good time to ask how we want to organize the stay and if we plan to book at the same place like we did on fosdem (well more or less). Also how does everybody plans to stay? I was thinking about Tuesday to Sunday, but if everybody comes at Monday already, I might change my plans ;) Great Karol! You are welcomed to stay at MuPuF Inn ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] XDC2016
Well, you see, I thought it would be a good idea that _we_ stay at the _same_ place ;) Well I plan to leave rather early, because I am smart and didn't take off from work on Monday, so there is that. I could ask to add another day though, depends on what we plan. 2016-08-15 10:53 GMT+02:00 Pierre Moreau : > Hello everyone, > > Same place as FOSDEM? XDC is in Helsinki and FOSDEM was in Brussels… (IIRC, > FOSDEM is always located in Brussels.) I would prefer picking an hotel in > Helsinki rather than traveling every day between Helsinki and Brussels. :-p Or > was that what you meant by "more or less"? :-D > > I’ve taken days off starting from Tuesday, so I could even arrive on Monday > evening if there are other persons coming that early. :-) And I am planning to > stay until Sunday (could be Sunday evening, I haven’t booked the hotel nor the > transport yet); apart from a short trip back to Sweden between Friday and > Saturday. > > Cheers, > Pierre > > > On 09:35 PM - Aug 13 2016, karol herbst wrote: >> Hi everybody, >> >> I saw that some more appeared on the list of Attendees, so it might be >> a good time to ask how we want to organize the stay and if we plan to >> book at the same place like we did on fosdem (well more or less). >> >> Also how does everybody plans to stay? I was thinking about Tuesday to >> Sunday, but if everybody comes at Monday already, I might change my >> plans ;) >> >> PS: if discussing that in public isn't the best idea, we can switch to >> off-list mails later, but I wanted to catch everybody here ;) >> ___ >> Nouveau mailing list >> Nouveau@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/nouveau ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] XDC2016
Hello everyone, Same place as FOSDEM? XDC is in Helsinki and FOSDEM was in Brussels… (IIRC, FOSDEM is always located in Brussels.) I would prefer picking an hotel in Helsinki rather than traveling every day between Helsinki and Brussels. :-p Or was that what you meant by "more or less"? :-D I’ve taken days off starting from Tuesday, so I could even arrive on Monday evening if there are other persons coming that early. :-) And I am planning to stay until Sunday (could be Sunday evening, I haven’t booked the hotel nor the transport yet); apart from a short trip back to Sweden between Friday and Saturday. Cheers, Pierre On 09:35 PM - Aug 13 2016, karol herbst wrote: > Hi everybody, > > I saw that some more appeared on the list of Attendees, so it might be > a good time to ask how we want to organize the stay and if we plan to > book at the same place like we did on fosdem (well more or less). > > Also how does everybody plans to stay? I was thinking about Tuesday to > Sunday, but if everybody comes at Monday already, I might change my > plans ;) > > PS: if discussing that in public isn't the best idea, we can switch to > off-list mails later, but I wanted to catch everybody here ;) > ___ > Nouveau mailing list > Nouveau@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau signature.asc Description: PGP signature ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH] drm/nouveau/tegra: Modify error handling
iommu_domain_alloc returns NULL on error so replace an incorrect IS_ERR check with a NULL check. The Coccinelle semantic patch used to find this issue is as follows: @@ expression e; statement S; @@ *e = iommu_domain_alloc(...); if (IS_ERR(e)) S Signed-off-by: Amitoj Kaur Chawla --- drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c b/drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c index 939682f..ffd8def 100644 --- a/drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/tegra.c @@ -102,7 +102,7 @@ nvkm_device_tegra_probe_iommu(struct nvkm_device_tegra *tdev) if (iommu_present(&platform_bus_type)) { tdev->iommu.domain = iommu_domain_alloc(&platform_bus_type); - if (IS_ERR(tdev->iommu.domain)) + if (!tdev->iommu.domain) goto error; /* -- 1.9.1 ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau