From: Gerd Knorr <kraxel@bytesex.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Duncan Sands <baldrick@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Fw: Oops at bttv_risc_packed (2.6.8-rc1)
Date: Tue, 17 Aug 2004 16:22:55 +0200 [thread overview]
Message-ID: <20040817142255.GA18704@bytesex> (raw)
In-Reply-To: <20040804212106.04f19bad.akpm@osdl.org>
> DEBUG_PAGEALLOC
Hmm, amd64 hasn't this one?
> [pg0+543078197/1069322240] bttv_buffer_risc+0x4b5/0x5b0 [bttv]
Looks like the buffer for the risc instructions overflows. No idea why
through, the size calculation looks ok. Can you please apply the debug
patch below, load bttv with "bttv_debug=1" insmod option and try again?
What app triggers this btw, and which capture parameters (size, format)?
Gerd
Index: bttv-risc.c
===================================================================
RCS file: /home/cvsroot/video4linux/bttv-risc.c,v
retrieving revision 1.3
diff -u -p -r1.3 bttv-risc.c
--- bttv-risc.c 6 Jul 2004 07:52:17 -0000 1.3
+++ bttv-risc.c 17 Aug 2004 14:17:14 -0000
@@ -55,6 +55,8 @@ bttv_risc_packed(struct bttv *btv, struc
instructions += 2;
if ((rc = btcx_riscmem_alloc(btv->c.pci,risc,instructions*8)) < 0)
return rc;
+ dprintk("bttv%d: risc packed: bpl %d lines %d instr %d size %d ptr %p\n",
+ btv->c.nr, bpl, lines, instructions, risc->size, risc->cpu);
/* sync instruction */
rp = risc->cpu;
@@ -99,8 +101,10 @@ bttv_risc_packed(struct bttv *btv, struc
offset += todo;
}
offset += padding;
+ dprintk("bttv%d: risc packed: line %d ptr %p\n",
+ btv->c.nr, line, rp);
}
- dprintk("bttv%d: risc planar: %d sglist elems\n", btv->c.nr, (int)(sg-sglist));
+ dprintk("bttv%d: risc packed: %d sglist elems\n", btv->c.nr, (int)(sg-sglist));
/* save pointer to jmp instruction address */
risc->jmp = rp;
next parent reply other threads:[~2004-08-17 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040804212106.04f19bad.akpm@osdl.org>
2004-08-17 14:22 ` Gerd Knorr [this message]
2004-09-08 7:37 ` Fw: Oops at bttv_risc_packed (2.6.8-rc1) Duncan Sands
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040817142255.GA18704@bytesex \
--to=kraxel@bytesex.org \
--cc=akpm@osdl.org \
--cc=baldrick@free.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox