From: Mark v Wolher <trilight@ns666.com>
To: Mark v Wolher <trilight@ns666.com>
Cc: Jiri Slaby <xslaby@fi.muni.cz>,
Sami Farin <7atbggg02@sneakemail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
arjan@infradead.org, jesper.juhl@gmail.com,
s0348365@sms.ed.ac.uk, rlrevell@joe-job.com
Subject: Re: system keeps freezing once every 24 hours / random apps crashing
Date: Sun, 01 Jan 2006 18:47:56 +0100 [thread overview]
Message-ID: <43B815CC.3070300@ns666.com> (raw)
In-Reply-To: <43B7EB99.8010604@ns666.com>
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 ?
next prev parent reply other threads:[~2006-01-01 17:48 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:05 system keeps freezing once every 24 hours / random apps crashing Trilight
2005-12-30 14:11 ` Ochal Christophe
2005-12-30 14:27 ` Jesper Juhl
2005-12-30 15:52 ` Mark v Wolher
2005-12-30 16:37 ` Mark v Wolher
2005-12-30 16:47 ` Folkert van Heusden
2005-12-30 17:14 ` Mark v Wolher
2005-12-30 18:30 ` Folkert van Heusden
2005-12-30 19:22 ` Mark v Wolher
2005-12-30 20:24 ` Folkert van Heusden
2005-12-30 20:58 ` Mark v Wolher
2005-12-30 21:15 ` Mark v Wolher
2005-12-30 21:30 ` Mark v Wolher
2005-12-30 21:35 ` Lee Revell
2005-12-30 21:47 ` Mark v Wolher
2005-12-30 21:51 ` Lee Revell
2005-12-30 21:57 ` Mark v Wolher
2005-12-30 22:00 ` Lee Revell
2005-12-30 22:05 ` Mark v Wolher
2005-12-30 22:11 ` Lee Revell
2005-12-30 22:16 ` Mark v Wolher
2005-12-30 23:11 ` Alistair John Strachan
2005-12-30 23:42 ` Mark v Wolher
2005-12-30 23:56 ` Alistair John Strachan
2005-12-31 0:20 ` Mark v Wolher
2005-12-31 0:27 ` Alistair John Strachan
2005-12-31 0:42 ` Mark v Wolher
2005-12-31 0:51 ` Alistair John Strachan
2005-12-31 0:54 ` Mark v Wolher
2005-12-31 10:31 ` Mark v Wolher
2005-12-31 11:08 ` Jesper Juhl
2005-12-31 11:40 ` Mark v Wolher
2005-12-31 11:49 ` Jesper Juhl
2005-12-31 12:46 ` Mark v Wolher
2005-12-31 15:18 ` Mark v Wolher
2005-12-31 15:22 ` Arjan van de Ven
2005-12-31 15:34 ` Mark v Wolher
2005-12-31 15:51 ` Mark v Wolher
2005-12-31 16:34 ` Sami Farin
2005-12-31 16:48 ` Mark v Wolher
2005-12-31 17:02 ` Sami Farin
2005-12-31 17:26 ` Mark v Wolher
2005-12-31 22:01 ` Sami Farin
2006-01-01 2:26 ` Mark v Wolher
2006-01-01 13:06 ` Mark v Wolher
2006-01-01 14:47 ` Mark v Wolher
2006-01-01 17:47 ` Mark v Wolher [this message]
2006-01-01 18:38 ` Jiri Slaby
2006-01-01 18:49 ` Mark v Wolher
2006-01-01 19:01 ` Mauro Carvalho Chehab
2006-01-01 19:12 ` Jiri Slaby
2006-01-01 19:37 ` Mark v Wolher
2006-01-01 23:20 ` Re; system keeps freezing once every 24 hours / random apps crashing Peter Missel
2006-01-02 22:29 ` Alan Cox
2006-01-03 0:19 ` Mauro Carvalho Chehab
2006-01-01 18:49 ` Folkert van Heusden
2006-01-01 18:54 ` Mark v Wolher
2006-01-01 20:49 ` Folkert van Heusden
2006-01-01 21:38 ` Mark v Wolher
2006-01-01 21:41 ` Lee Revell
2006-01-01 22:01 ` Mark v Wolher
2006-01-25 12:46 ` Jiri Slaby
2006-01-01 15:14 ` Sami Farin
2005-12-31 11:23 ` Jesper Juhl
2005-12-31 11:31 ` Jesper Juhl
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=43B815CC.3070300@ns666.com \
--to=trilight@ns666.com \
--cc=7atbggg02@sneakemail.com \
--cc=arjan@infradead.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=s0348365@sms.ed.ac.uk \
--cc=xslaby@fi.muni.cz \
/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;
as well as URLs for NNTP newsgroup(s).