drm/nv50: initialize ramht_refs list for faked 0 channel
Subsystems (4)
PATCH 1/1 drm/nv50: initialize ramht_refs list for faked 0 channel
We need it for PFIFO_INTR_CACHE_ERROR interrupt handling, because nouveau_fifo_swmthd looks for matching gpuobj in ramht_refs list.
It fixes kernel panic in nouveau_gpuobj_ref_find.
--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
drivers/gpu/drm/nouveau/nv50_instmem.c +2 -0
@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan; +INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);
Signature · 1 line
1.7.1.1
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 16 lines · Marcin Slusarz
We need it for
PFIFO_INTR_CACHE_ERRORinterrupt handling, becausenouveau_fifo_swmthdlooks for matching gpuobj inramht_refslist.
It fixes kernel panic innouveau_gpuobj_ref_find.Signed-off-by Marcin Slusarz <[email protected]>--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)drivers/gpu/drm/nouveau/nv50_instmem.c +0
-0
drivers/gpu/drm/nouveau/nv50_instmem.c nv50_instmem_init(struct drm_device *dev) · line 146
Quoted 8 lines
drivers/gpu/drm/nouveau/nv50_instmem.c +2
-0@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan; +INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);
ping
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 19 lines · Marcin Slusarz
Quoted 18 lines · Marcin Slusarz
We need it for
PFIFO_INTR_CACHE_ERRORinterrupt handling, becausenouveau_fifo_swmthdlooks for matching gpuobj inramht_refslist.
It fixes kernel panic innouveau_gpuobj_ref_find.Signed-off-by Marcin Slusarz <[email protected]>--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)drivers/gpu/drm/nouveau/nv50_instmem.c +0
-0@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan;
Quoted 8 lines
drivers/gpu/drm/nouveau/nv50_instmem.c nv50_instmem_init(struct drm_device *dev) · line 146
Quoted 6 lines
drivers/gpu/drm/nouveau/nv50_instmem.c +2
-0+INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);ping
Pong! Thank you for the patch.
I meant to reply to this earlier but it slipped my mind. I have a number of pending cleanups to all this stuff that should make this patch unnecessary.
Ben.
Quoted 5 lines
_______________________________________________
Nouveau mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/nouveau
Quoted 28 lines · Ben Skeggs
Quoted 19 lines · Marcin Slusarz
Quoted 18 lines · Marcin Slusarz
We need it for
PFIFO_INTR_CACHE_ERRORinterrupt handling, becausenouveau_fifo_swmthdlooks for matching gpuobj inramht_refslist.
It fixes kernel panic innouveau_gpuobj_ref_find.Signed-off-by Marcin Slusarz <[email protected]>--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)drivers/gpu/drm/nouveau/nv50_instmem.c +0
-0@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan;Quoted 8 lines
drivers/gpu/drm/nouveau/nv50_instmem.c nv50_instmem_init(struct drm_device *dev) · line 146
Quoted 6 lines
drivers/gpu/drm/nouveau/nv50_instmem.c +2
-0+INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);ping
Quoted 5 lines
Pong! Thank you for the patch.
I meant to reply to this earlier but it slipped my mind. I have a number of pending cleanups to all this stuff that should make this patch unnecessary.
Oh, come on. It's a simple one-line bugfix for easily triggerable kernel panic. Patch like this should not wait a week for any response - it should be applied ASAP and go to Linus possibly with -stable tag.
Marcin
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 31 lines · Marcin Slusarz
Quoted 30 lines · Ben Skeggs
Quoted 19 lines · Marcin Slusarz
Quoted 18 lines · Marcin Slusarz
We need it for
PFIFO_INTR_CACHE_ERRORinterrupt handling, becausenouveau_fifo_swmthdlooks for matching gpuobj inramht_refslist.
It fixes kernel panic innouveau_gpuobj_ref_find.Signed-off-by Marcin Slusarz <[email protected]>--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)drivers/gpu/drm/nouveau/nv50_instmem.c +0
-0@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan;Quoted 8 lines
drivers/gpu/drm/nouveau/nv50_instmem.c nv50_instmem_init(struct drm_device *dev) · line 146
Quoted 6 lines
drivers/gpu/drm/nouveau/nv50_instmem.c +2
-0+INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);ping
Pong! Thank you for the patch.
Quoted 7 lines
Quoted 3 lines
I meant to reply to this earlier but it slipped my mind. I have a number of pending cleanups to all this stuff that should make this patch unnecessary.
Oh, come on. It's a simple one-line bugfix for easily triggerable kernel panic. Patch like this should not wait a week for any response - it should be applied ASAP and go to Linus possibly with -stable tag.
Oh please, it's hardly easily triggerable. I've *never* seen it personally, and triggering errors on those channels isn't something that generally happens. If you feel that strongly about it I'll send it to Dave to go to Linus.
Ben.
Quoted 3 lines
Marcin
Quoted 36 lines · Ben Skeggs
Quoted 35 lines · Marcin Slusarz
Quoted 33 lines · Ben Skeggs
Quoted 19 lines · Marcin Slusarz
Quoted 18 lines · Marcin Slusarz
We need it for
PFIFO_INTR_CACHE_ERRORinterrupt handling, becausenouveau_fifo_swmthdlooks for matching gpuobj inramht_refslist.
It fixes kernel panic innouveau_gpuobj_ref_find.Signed-off-by Marcin Slusarz <[email protected]>--- drivers/gpu/drm/nouveau/nv50_instmem.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)drivers/gpu/drm/nouveau/nv50_instmem.c +0
-0@@ -139,6 +139,8 @@ nv50_instmem_init(struct drm_device *dev) chan->file_priv = (struct drm_file *)-2 ; dev_priv->fifos[0 ] = dev_priv->fifos[127 ] = chan;Quoted 8 lines
drivers/gpu/drm/nouveau/nv50_instmem.c nv50_instmem_init(struct drm_device *dev) · line 146
Quoted 6 lines
drivers/gpu/drm/nouveau/nv50_instmem.c +2
-0+INIT_LIST_HEAD (&chan->ramht_refs); +/* Channel's PRAMIN object + heap */ ret =nouveau_gpuobj_new_fake (dev,0 , c_offset, c_size,0 ,NULL , &chan->ramin);ping
Pong! Thank you for the patch.
I meant to reply to this earlier but it slipped my mind. I have a number of pending cleanups to all this stuff that should make this patch unnecessary.
Quoted 6 lines
Quoted 3 lines
Oh, come on. It's a simple one-line bugfix for easily triggerable kernel panic. Patch like this should not wait a week for any response - it should be applied ASAP and go to Linus possibly with -stable tag.
Oh please, it's hardly easily triggerable. I've *never* seen it personally, and triggering errors on those channels isn't something that generally happens.
Are you sure you have *never* seen it? Do you have netconsole enabled all the time? I'm asking because once you hit this bug, machine is dead and you won't find anything in the logs.
I'm attaching the testcase. Yes, it's that simple.
--
#include <stdio.h>
#include <libdrm/nouveau_drmif.h>
#include <nouveau/nouveau_channel.h>
int main()
{
struct nouveau_device *dev = NULL;
struct nouveau_channel *chan = NULL;
if (nouveau_device_open(&dev, "")) {
perror("nouveau_device_open");
return 1;
}
if (nouveau_channel_alloc(dev, 0, 0, &chan)) {
perror("nouveau_channel_alloc");
return 2;
}
return 0;
}Hi,
I just tried that patch, but unfortunately nether with nor without it kdb seems not to work.
It could be id10t error from my side, but I did test the kdb in the past with few KMS patches, and it seemed to work.
Now I can't even get its prompt on the console.
This is what I do:
echo kbd | sudo tee /sys/module/kgdboc/parameters/kgdboc (also tried booting with kgdboc=kbd)
Both seems to start kdb, because
maxim@maxim-laptop:~$ cat /sys/module/kgdboc/parameters/kgdboc kbd
maxim@maxim-laptop:~$ dmesg | grep kgdb [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.36-rc3+ root=UUID=52341b68-74f3-4c96-aaf8-7586a06c4b4e ro splash video=nouveau nmi_watchdog=lapic kgdboc=kbd [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.36-rc3+ root=UUID=52341b68-74f3-4c96-aaf8-7586a06c4b4e ro splash video=nouveau nmi_watchdog=lapic kgdboc=kbd [ 2.671914] kgdb: Registered I/O driver kgdboc.
Now when I first switch to console and then press Alt+SysRQ+G, I just get SYSRQ: DEBUG, and system hangs. It could be printk level, but that should be ok, no?
maxim@maxim-laptop:~$ cat /proc/sys/kernel/printk 7 4 1 7
Also if I remember correct inputting 'g' then ENTER should resume the system, but it doesn't.
So I think kdb doesn't work at all here
Best regards,
Maxim Levitsky
Sorry, wrong thread!