Re: OOPS in 2.4.25-rc1 -- video1394

[Roland Mas <roland.mas@free.fr>]

Ben Collins, 2004-02-09 12:57:31 -0500 :

[...]

> Looks to me like it is failing in alloc_dma_iso_ctx(), and then calling
> free_dma_iso_ctx() where it encounters some bad data. I can't see off
> hand where this might happen. Was there any message prior to this, like
> maybe a video1394 error message?

There were messages before that, yes.  Here come bits of my kern.log.
,----
| Feb  9 12:11:11 mirexpress kernel: mask: 8000000000000000 usage: 0000000000000000
| Feb  9 12:11:11 mirexpress kernel: video1394_0: Iso transmit DMA: 8 buffers of size 163840 allocated for a frame size 163840, each with 320 prgs
| Feb  9 12:11:11 mirexpress kernel: video1394_0: Iso context 0 talk on channel 63
| Feb  9 12:11:21 mirexpress kernel: video1394_0: Iso context 0 stop talking on channel 63
| Feb  9 12:12:51 mirexpress kernel: mask: 8000000000000000 usage: 0000000000000000
| Feb  9 12:12:51 mirexpress kernel: dma_region_alloc: vmalloc_32() failed
| Feb  9 12:12:51 mirexpress kernel: video1394_0: Failed to allocate dma buffer
| Feb  9 12:12:51 mirexpress kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004Feb  9 12:12:51 mirexpress kernel:  printing eip:
| Feb  9 12:12:51 mirexpress kernel: fcd81136
| Feb  9 12:12:51 mirexpress kernel: *pde = 00000000
| Feb  9 12:12:51 mirexpress kernel: Oops: 0002
| Feb  9 12:12:51 mirexpress kernel: CPU:    0
| Feb  9 12:12:51 mirexpress kernel: EIP:    0010:[<fcd81136>]    Not tainted
| Feb  9 12:12:51 mirexpress kernel: EFLAGS: 00210246
| [snip]
`----
The entries until 12:11:21 are when I used dvconnect (which worked).
So there are indeed three lines before the actual oops, including two
that look like error messages.

  If there's anything else I can povide, just say so, I just can't
think of anything.

  Thanks,

Roland.
-- 
Roland Mas

A man walks into a bar.
Bang.