Mark v Wolher wrote:
>> Still no crashes or irregular things happened ! Will let it go for a few
>> more hours. This test is being done with the binary nvidia module loaded
>> and bttv disabled. The next test will be nv for X instead of the binary
>> module with bttv enabled, if crashes and such start to occur then it's
>> very likely that the problem sits in the bttv code.
>
>
>Okay, here are the test results:
>
>
>- heavy load + nvidia (binary module) + bttv with grabdisplay = crash
>- heavy load + nv (not tainted kernel) + bttv with grabdisplay = crash
>
>- heavy load + nvidia (binary module) + bttv with overlay = OK
>- heavy load + nv (not tainted kernel) + bttv with overlay = OK
>
>Adding vmware on top of it will cause the system sooner to freeze/crash
>(using grabdisplay)
>
>So what you think guys ?
Hi,
we still think that there is a problem in bttv_risc_packed in computing
estimated size. My patch was bad, I see it now, but still don't understand, how
it is computed and how it should be:
instructions = (bpl * lines) / PAGE_SIZE + lines;
instructions += 2;
and here it crashes (the first line, the (*rp)) -- actually after while loop.
*(rp++)=cpu_to_le32(BT848_RISC_WRITE|BT848_RISC_EOL|todo);
*(rp++)=cpu_to_le32(sg_dma_address(sg));
So, Mauro (or somebody from list), have you any idea, what could be wrong?
thanks,
--
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ [email protected] _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
