Mark v Wolher wrote:
> Mark v Wolher wrote:
>
>>Mark v Wolher wrote:
>>
>>
>>>Jiri Slaby wrote:
>>>
>>>
>>>
>>>>>Hi Sami,
>>>>>
>>>>>That caused also a crash, i kept pressing the v key and within 15
>>>>>seconds it crashed, then i saw the crash-info appear in the log and when
>>>>>i clicked on mozilla then it crashed too but without crahs info and
>>>>>system froze totally.
>>>>>
>>>>>Below the crash info:
>>>>>
>>>>>Dec 31 17:38:32 localhost kernel: Unable to handle kernel paging request
>>>>>at virtual address c8111000
>>>>>Dec 31 17:38:32 localhost kernel: printing eip:
>>>>>Dec 31 17:38:32 localhost kernel: c036037a
>>>>>Dec 31 17:38:32 localhost kernel: *pgd = 21063
>>>>>Dec 31 17:38:32 localhost kernel: *pmd = 21063
>>>>>Dec 31 17:38:32 localhost kernel: *pte = 8111000
>>>>>Dec 31 17:38:32 localhost kernel: Oops: 0002 [#4]
>>>>
>>>>[snip]
>>>>Could you try the attached patch?
>>>>
>>>>--
>>>>diff --git a/drivers/media/video/bttv-risc.c b/drivers/media/video/bttv-risc.c
>>>>--- a/drivers/media/video/bttv-risc.c
>>>>+++ b/drivers/media/video/bttv-risc.c
>>>>@@ -53,7 +53,7 @@ bttv_risc_packed(struct bttv *btv, struc
>>>> /* estimate risc mem: worst case is one write per page border +
>>>> one write per scan line + sync + jump (all 2 dwords) */
>>>> instructions = (bpl * lines) / PAGE_SIZE + lines;
>>>>- instructions += 2;
>>>>+ instructions += 4;
>>>> if ((rc = btcx_riscmem_alloc(btv->c.pci,risc,instructions*8)) < 0)
>>>> return rc;
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>Hi Jiri,
>>>
>>>Tried it but it seems to crash indeed faster, and this time it didn't
>>>leave traces in the log.
>>>
>>>Appreciate your help eitherway !
>>>-
>>
>>
>>
>>Hiya all,
>>
>>First of all happy new year ! :-)
>>
>>
>>I might have discovered something interesting which might be responsible
>>for all those lockups/freezes/crashes !
>>
>>Right now, i'm putting a huge load on the system, disk i/o, swapping
>>high, virusscan, number crushing with ssh-keygen moduli etc ...
>>
>>5 hours passed with this load and no single crash/freeze/lockup happened
>>! Normally with all this load sooner or later something would have
>>happened.
>>
>>What did i do ?
>>
>>I disabled bttv support in the kernel, so no tv for me at this moment.
>>I'm planning to let this run for at least another 5 hours with heavy
>>load and see if still nothing happens...
>>
>>Keeping you informed.
>>
>>Mark
>>
>>
>>
>>
>
>
> 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 ?
-
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]