[Nouveau] [Bug 58776] New: DRM NOUVEAU: cannot boot with kernel =3.7
https://bugs.freedesktop.org/show_bug.cgi?id=58776
Priority: medium
Bug ID: 58776
Assignee: nouveau@lists.freedesktop.org
Summary: DRM NOUVEAU: cannot boot with kernel =3.7
QA Contact: xorg-t...@lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: baldu...@units.it
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 72129
-- https://bugs.freedesktop.org/attachment.cgi?id=72129action=edit
lspci output
hello everybody,
following advice from dri-devel list I am opening a bug report here.
Starting with kernel-3.7 I am not able to boot any more in KMS: as
soon as the screen resolution changes in the very early stage of the
boot, the machine freezes and the only option I'm left with is to
press a physical reset button.
I am on an athlon64 dual core machine and using DRM/NOUVEAU with a
NVIDIA GeForce 6200 LE GPU
Here are some facts:
= while kernel-3.7.x gives the problems mentioned above,
kernel-3.6.{8-10} boots just fine (and X11 works nicely)
= if it can be of any use: if I reboot from a running 3.6.x kernel
into a 3.7.x, the obtained freezed console screen shows the (somewhat
misplaced) lines which were printed during the shutdown phase of
the reboot process (this is similar to what reported in Description
of bug#46557)
= kernel-3.7.x boots just fine on another box (another athlon64 dual core with
a GeForce 6150SE nForce 430 (rev a2) GPU); kernel is 32bit there,
if it can matter
I am attaching lspci output, kernel config and dmesg output w/
NOUVEAU_DEBUG_DEFAULT=6
I will be happy to send in any other information which might be useful
thank you very much in advance
ciao
gabriele
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 23223] Regression: Nvidia Geforce 7300 (NV4B) fails to suspend
https://bugs.freedesktop.org/show_bug.cgi?id=23223 --- Comment #7 from Ronald ronald...@gmail.com --- Just tried v3.8rc1 + nouveau HEAD and a patch from: https://bugs.freedesktop.org/show_bug.cgi?id=50121#c31 . It suspends now, altough it takes a while. I hear stuff power down twice, I don't think that's correct... Recent rework made things worse, the screen resumed with a black screen. Latest HEAD with mentioned patch makes stuff regress like pre kernel v3.5 rework: The screen comes up, slightly garbled. It won't respond, and eventually the entire screen locks-up. Any pointers on what to do next?? -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 23223] [NV4B] nVidia Geforce 7300 (NV4B) fails to resume
https://bugs.freedesktop.org/show_bug.cgi?id=23223 Ronald ronald...@gmail.com changed: What|Removed |Added Hardware|Other |x86-64 (AMD64) OS|All |Linux (All) Summary|Regression: Nvidia Geforce |[NV4B] nVidia Geforce 7300 |7300 (NV4B) fails to|(NV4B) fails to resume |suspend | Version|7.2 (2007.02) |git Keywords||regression -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 23223] [NV4B] nVidia Geforce 7300 (NV4B) fails to resume
https://bugs.freedesktop.org/show_bug.cgi?id=23223 Ronald ronald...@gmail.com changed: What|Removed |Added Attachment #28444|0 |1 is obsolete|| Attachment #28445|0 |1 is obsolete|| Attachment #28446|0 |1 is obsolete|| Attachment #28447|0 |1 is obsolete|| --- Comment #8 from Ronald ronald...@gmail.com --- Created attachment 72137 -- https://bugs.freedesktop.org/attachment.cgi?id=72137action=edit Dmesg v3.8rc1+Nouveau_HEAD+patch from #50121#c31 (boot) -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 23223] [NV4B] nVidia Geforce 7300 fails to properly resume
https://bugs.freedesktop.org/show_bug.cgi?id=23223 Ronald ronald...@gmail.com changed: What|Removed |Added Summary|[NV4B] nVidia Geforce 7300 |[NV4B] nVidia Geforce 7300 |(NV4B) fails to resume |fails to properly resume -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 50121] [Regression] Since kernel v3.5 several cards fail to resume, introduced by: 'convert to exec engine, and improve channel sync'
https://bugs.freedesktop.org/show_bug.cgi?id=50121 --- Comment #41 from Ronald ronald...@gmail.com --- I'm waiting on filing a bug for the NV4E. It seems that nouveau works properly, I don't see any delays or errors at all in dmesg. It is whining about the b43 firmware, but even if I unload the driver the resume still takes 1m and 30 seconds. But it works. I'm not sure this is a nouveau bug, hence I'm not filing it. I will dig deeper when I have time. -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 56461] NV11 black screen kernel hang on loading nouveaufb
https://bugs.freedesktop.org/show_bug.cgi?id=56461 --- Comment #34 from Ondrej Zary li...@rainbow-software.org --- I have the same problem on DELL Latitude C810 laptop. 3.2 is the latest working kernel, 3.3-rc1 does not work (LCD fades to white, then backlight turns off and machine hangs). d2edab4acffb35a6e24259886d34efd37e6e is the latest working version (with dea7e0ac45fd28f90bbc38ff226d36a9f788efbf added to fix AGP crash) 2a44e4997c5fee8e1da1589ff57e0bd1c53f03ce is the first bad commit. It oopses in nv_load_state_ext (dev-vblank_enabled is NULL). With line 1024 in nouveau_hw.c commented out, the oops is gone and the fadehang problem appears. -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 50121] [Regression] Since kernel v3.5 several cards fail to resume, introduced by: 'convert to exec engine, and improve channel sync'
https://bugs.freedesktop.org/show_bug.cgi?id=50121 --- Comment #42 from Raphaël Droz gibbo...@gmail.com --- perfect! the last patch did the trick (tested with vanilla 3.7). I hibernated several times, even with a running instance of glxgears. No problem anymore. On my side the startup time is not especially long. thanks -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 55258] nouveau failure on resume (reloc wait_idle failed)
https://bugs.freedesktop.org/show_bug.cgi?id=55258 --- Comment #2 from Raphaël Droz gibbo...@gmail.com --- In my case, the issue is solved by the patch from bug #50121 -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 46557] nouveau: NV4E acceleration corruption when DMA above 31-bit (2 Gig barrier)
https://bugs.freedesktop.org/show_bug.cgi?id=46557 --- Comment #28 from Raphaël Droz gibbo...@gmail.com --- I should add that I've no problem with 3GB. Problem arises when I add 1 more GB. -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 55258] nouveau failure on resume (reloc wait_idle failed)
https://bugs.freedesktop.org/show_bug.cgi?id=55258 Marcin Slusarz marcin.slus...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Marcin Slusarz marcin.slus...@gmail.com --- *** This bug has been marked as a duplicate of bug 50121 *** -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 50121] [Regression] Since kernel v3.5 several cards fail to resume, introduced by: 'convert to exec engine, and improve channel sync'
https://bugs.freedesktop.org/show_bug.cgi?id=50121 Marcin Slusarz marcin.slus...@gmail.com changed: What|Removed |Added CC||mr.dash.f...@googlemail.com --- Comment #43 from Marcin Slusarz marcin.slus...@gmail.com --- *** Bug 55258 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH] drm/nv17-50: restore fence buffer on resume
Since commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 drm/nouveau/fence:
convert to exec engine, and improve channel sync nouveau fence sync
implementation for nv17-50 and nvc0+ started to rely on state of fence buffer
left by previous sync operation. But as pinned bo's (where fence state is
stored) are not saved+restored across suspend/resume, we need to do it
manually.
nvc0+ was fixed by commit d6ba6d215a538a58f0f0026f0961b0b9125e8042
drm/nvc0/fence: restore pre-suspend fence buffer context on resume.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=50121
Signed-off-by: Marcin Slusarz marcin.slus...@gmail.com
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/nouveau/nouveau_fence.h | 1 +
drivers/gpu/drm/nouveau/nv10_fence.c| 9 +
drivers/gpu/drm/nouveau/nv50_fence.c| 2 ++
3 files changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.h
b/drivers/gpu/drm/nouveau/nouveau_fence.h
index bedafd1..cdb83ac 100644
--- a/drivers/gpu/drm/nouveau/nouveau_fence.h
+++ b/drivers/gpu/drm/nouveau/nouveau_fence.h
@@ -60,6 +60,7 @@ u32 nv10_fence_read(struct nouveau_channel *);
void nv10_fence_context_del(struct nouveau_channel *);
void nv10_fence_destroy(struct nouveau_drm *);
int nv10_fence_create(struct nouveau_drm *);
+void nv17_fence_resume(struct nouveau_drm *drm);
int nv50_fence_create(struct nouveau_drm *);
int nv84_fence_create(struct nouveau_drm *);
diff --git a/drivers/gpu/drm/nouveau/nv10_fence.c
b/drivers/gpu/drm/nouveau/nv10_fence.c
index 7ae7f97..0619c02 100644
--- a/drivers/gpu/drm/nouveau/nv10_fence.c
+++ b/drivers/gpu/drm/nouveau/nv10_fence.c
@@ -162,6 +162,13 @@ nv10_fence_destroy(struct nouveau_drm *drm)
kfree(priv);
}
+void nv17_fence_resume(struct nouveau_drm *drm)
+{
+ struct nv10_fence_priv *priv = drm-fence;
+
+ nouveau_bo_wr32(priv-bo, 0, priv-sequence);
+}
+
int
nv10_fence_create(struct nouveau_drm *drm)
{
@@ -197,6 +204,8 @@ nv10_fence_create(struct nouveau_drm *drm)
if (ret == 0) {
nouveau_bo_wr32(priv-bo, 0x000, 0x);
priv-base.sync = nv17_fence_sync;
+
+ priv-base.resume = nv17_fence_resume;
}
}
diff --git a/drivers/gpu/drm/nouveau/nv50_fence.c
b/drivers/gpu/drm/nouveau/nv50_fence.c
index c20f272..4cc0ce6 100644
--- a/drivers/gpu/drm/nouveau/nv50_fence.c
+++ b/drivers/gpu/drm/nouveau/nv50_fence.c
@@ -122,6 +122,8 @@ nv50_fence_create(struct nouveau_drm *drm)
if (ret == 0) {
nouveau_bo_wr32(priv-bo, 0x000, 0x);
priv-base.sync = nv17_fence_sync;
+
+ priv-base.resume = nv17_fence_resume;
}
if (ret)
--
1.8.0.2
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH] drm/nouveau: share fence structures between nv10+ and nv50 implementations
We already rely on them having the same fields and layout.
Signed-off-by: Marcin Slusarz marcin.slus...@gmail.com
---
drivers/gpu/drm/nouveau/nv10_fence.c | 13 +
drivers/gpu/drm/nouveau/nv10_fence.h | 19 +++
drivers/gpu/drm/nouveau/nv50_fence.c | 19 ---
3 files changed, 24 insertions(+), 27 deletions(-)
create mode 100644 drivers/gpu/drm/nouveau/nv10_fence.h
diff --git a/drivers/gpu/drm/nouveau/nv10_fence.c
b/drivers/gpu/drm/nouveau/nv10_fence.c
index 0619c02..2ad4cd5 100644
--- a/drivers/gpu/drm/nouveau/nv10_fence.c
+++ b/drivers/gpu/drm/nouveau/nv10_fence.c
@@ -27,18 +27,7 @@
#include nouveau_drm.h
#include nouveau_dma.h
-#include nouveau_fence.h
-
-struct nv10_fence_chan {
- struct nouveau_fence_chan base;
-};
-
-struct nv10_fence_priv {
- struct nouveau_fence_priv base;
- struct nouveau_bo *bo;
- spinlock_t lock;
- u32 sequence;
-};
+#include nv10_fence.h
int
nv10_fence_emit(struct nouveau_fence *fence)
diff --git a/drivers/gpu/drm/nouveau/nv10_fence.h
b/drivers/gpu/drm/nouveau/nv10_fence.h
new file mode 100644
index 000..e5d9204
--- /dev/null
+++ b/drivers/gpu/drm/nouveau/nv10_fence.h
@@ -0,0 +1,19 @@
+#ifndef __NV10_FENCE_H_
+#define __NV10_FENCE_H_
+
+#include core/os.h
+#include nouveau_fence.h
+#include nouveau_bo.h
+
+struct nv10_fence_chan {
+ struct nouveau_fence_chan base;
+};
+
+struct nv10_fence_priv {
+ struct nouveau_fence_priv base;
+ struct nouveau_bo *bo;
+ spinlock_t lock;
+ u32 sequence;
+};
+
+#endif
diff --git a/drivers/gpu/drm/nouveau/nv50_fence.c
b/drivers/gpu/drm/nouveau/nv50_fence.c
index 4cc0ce6..4bef67c 100644
--- a/drivers/gpu/drm/nouveau/nv50_fence.c
+++ b/drivers/gpu/drm/nouveau/nv50_fence.c
@@ -27,27 +27,16 @@
#include nouveau_drm.h
#include nouveau_dma.h
-#include nouveau_fence.h
+#include nv10_fence.h
#include nv50_display.h
-struct nv50_fence_chan {
- struct nouveau_fence_chan base;
-};
-
-struct nv50_fence_priv {
- struct nouveau_fence_priv base;
- struct nouveau_bo *bo;
- spinlock_t lock;
- u32 sequence;
-};
-
static int
nv50_fence_context_new(struct nouveau_channel *chan)
{
struct drm_device *dev = chan-drm-dev;
- struct nv50_fence_priv *priv = chan-drm-fence;
- struct nv50_fence_chan *fctx;
+ struct nv10_fence_priv *priv = chan-drm-fence;
+ struct nv10_fence_chan *fctx;
struct ttm_mem_reg *mem = priv-bo-bo.mem;
struct nouveau_object *object;
int ret, i;
@@ -91,7 +80,7 @@ nv50_fence_context_new(struct nouveau_channel *chan)
int
nv50_fence_create(struct nouveau_drm *drm)
{
- struct nv50_fence_priv *priv;
+ struct nv10_fence_priv *priv;
int ret = 0;
priv = drm-fence = kzalloc(sizeof(*priv), GFP_KERNEL);
--
1.8.0.2
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 58784] New: Nouveau on NVCE, reclocking: memory type not supported?
https://bugs.freedesktop.org/show_bug.cgi?id=58784 Priority: medium Bug ID: 58784 Assignee: nouveau@lists.freedesktop.org Summary: Nouveau on NVCE, reclocking: memory type not supported? QA Contact: xorg-t...@lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: miga-anyand...@hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Driver/nouveau Product: xorg Created attachment 72144 -- https://bugs.freedesktop.org/attachment.cgi?id=72144action=edit lspci_output, nvce_strap_peek, nvce_timing_peek, nvce_bios.rom, and nvce_vbios_parsed I understand reclocking on Nouveau is very experimental still, but I figured I might as well send in this bug report anyway. On my NVCE (GTX 560 from EVGA), the standard (boot) clock speeds are 50 MHz core, 100 MHz shader, and 135 MHz memory. Naturally because of this, OpenGL performance is terrible (possibly worse than older Intel chips like the 4500HD), about 15-20 FPS in Red Eclipse and about 5 FPS in Xonotic. I am able to reclock the card, however, upon doing so, it comes up with this error in dmesg: [11245.600378] nouveau E[ DRM] cannot reclock unsupported memtype So, I'm able to get the GPU core and shader to run at their highest speeds (850 MHz and 1701 MHz respectively), but the memory speed stays at 135 MHz (when it should be at 2052 MHz). Even though I can change the clock speeds, after a while, the card will crash, forcing me to have to reboot. I'm also uploading things such as my lspci_output, nvce_strap_peek, nvce_timing_peek, nvce_bios.rom, and nvce_vbios_parsed, so it'll hopefully help you guys out on getting things working. -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 56461] NV11 black screen kernel hang on loading nouveaufb
https://bugs.freedesktop.org/show_bug.cgi?id=56461 --- Comment #35 from Ondrej Zary li...@rainbow-software.org --- 70790f4f (+dpms-fix) works for me too and cb75d97e (+dpms-fix) does not. Does not work even with any combination of nouveau.agpmode=0 and nouveau.config=DEVINIT=NvForcePost=1 -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
