From: Mark v Wolher <trilight@ns666.com>
To: Sami Farin <7atbggg02@sneakemail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: system keeps freezing once every 24 hours / random apps crashing
Date: Sat, 31 Dec 2005 17:48:41 +0100 [thread overview]
Message-ID: <43B6B669.6020500@ns666.com> (raw)
In-Reply-To: <20051231163414.GE3214@m.safari.iki.fi>
Sami Farin wrote:
> On Sat, Dec 31, 2005 at 04:18:38PM +0100, Mark v Wolher wrote:
> ...
>
>>Here is new data, this time it had to do with bttv:
>>
>>Dec 31 16:11:35 localhost kernel: Unable to handle kernel paging request at
>>virtual address d162e000
>>Dec 31 16:11:35 localhost kernel: printing eip:
>>Dec 31 16:11:35 localhost kernel: c036037a
>>Dec 31 16:11:35 localhost kernel: *pgd = 46063
>>Dec 31 16:11:35 localhost kernel: *pmd = 46063
>>Dec 31 16:11:35 localhost kernel: *pte = 1162e000
>>Dec 31 16:11:35 localhost kernel: Oops: 0002 [#1]
>>Dec 31 16:11:35 localhost kernel: SMP DEBUG_PAGEALLOC
>>Dec 31 16:11:35 localhost kernel: Modules linked in: nv
>>Dec 31 16:11:35 localhost kernel: CPU: 2
>>Dec 31 16:11:35 localhost kernel: EIP: 0060:[bttv_risc_packed+394/432]
>
>
> Can you try how many seconds it takes to get Oops/crash when you start
> pressing 'v' in xawtv (video capture on/off).
> For me, not very many.
>
> This happens with every 2.6 kernel. And my hardware is OK.
>
>
>>Not tainted VLI
>>Dec 31 16:11:35 localhost kernel: EFLAGS: 00210202 (2.6.14.5)
>>Dec 31 16:11:35 localhost kernel: eax: 14000008 ebx: d5ce9800 ecx:
>>d162e000 edx: 00000008
>>Dec 31 16:11:35 localhost kernel: esi: 00000008 edi: 000000ff ebp:
>>cd06dde8 esp: cd06ddd0
>>Dec 31 16:11:35 localhost kernel: ds: 007b es: 007b ss: 0068
>>Dec 31 16:11:35 localhost kernel: Process xawtv (pid: 31110,
>>threadinfo=cd06c000 task=ca871aa0)
>>Dec 31 16:11:35 localhost kernel: Stack: df80bbf8 c3b25fbc 00000fd0 00000c00
>>000d8000 c3b25ef8 cd06de40 c0361b0b
>>Dec 31 16:11:35 localhost kernel: c06ccba0 c3b25fbc d5ce8000 00000c00
>>00000c00 00000c00 00000120 000001b1
>>Dec 31 16:11:35 localhost kernel: 00000008 c3b25f1c c06cd168 00000000
>>cd06de40 c037022a df80bbf8 c3b25f1c
>>Dec 31 16:11:35 localhost kernel: Call Trace:
>>Dec 31 16:11:35 localhost kernel: [show_stack+127/160]
>>Dec 31 16:11:35 localhost kernel: [show_registers+347/448]
>>Dec 31 16:11:35 localhost kernel: [die+256/384]
>>Dec 31 16:11:35 localhost kernel: [do_page_fault+1084/2083]
>>Dec 31 16:11:35 localhost kernel: [error_code+79/96]
>>Dec 31 16:11:35 localhost kernel: [bttv_buffer_risc+1371/1696]
>>Dec 31 16:11:35 localhost kernel: [bttv_prepare_buffer+268/464]
>>Dec 31 16:11:35 localhost kernel: [buffer_prepare+69/80]
>>Dec 31 16:11:35 localhost kernel: [videobuf_read_zerocopy+108/304]
>>Dec 31 16:11:35 localhost kernel: [videobuf_read_one+522/560]
>>Dec 31 16:11:35 localhost kernel: [bttv_read+272/352]
>>Dec 31 16:11:35 localhost kernel: [vfs_read+213/432]
>>Dec 31 16:11:35 localhost kernel: [sys_read+75/128]
>>Dec 31 16:11:35 localhost kernel: [syscall_call+7/11]
>>Dec 31 16:11:35 localhost kernel: Code: 00 0d 00 00 00 10 89 01 8b 43 08 83
>>c1 04 89 01 8b 43 0c 83 c1 04 83 c3 10 29 c2 8b 43 0c 39 c2 77 df 89 d0 89
>>d6 0d 00 00 00 14 <89> 01 8b 43 08 83 c1 04 89 01 83 c1 04 eb 8a 8d b4 26 00
>>00 00
>
>
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]
Dec 31 17:38:32 localhost kernel: SMP DEBUG_PAGEALLOC
Dec 31 17:38:32 localhost kernel: Modules linked in:
Dec 31 17:38:32 localhost kernel: CPU: 3
Dec 31 17:38:32 localhost kernel: EIP:
0060:[bttv_risc_packed+394/432] Not tainted VLI
Dec 31 17:38:32 localhost kernel: EFLAGS: 00210202 (2.6.14.5)
Dec 31 17:38:32 localhost kernel: eax: 14000008 ebx: d3a09800 ecx:
c8111000 edx: 00000008
Dec 31 17:38:32 localhost kernel: esi: 00000008 edi: 000000ff ebp:
d3c0be38 esp: d3c0be20
Dec 31 17:38:32 localhost kernel: ds: 007b es: 007b ss: 0068
Dec 31 17:38:32 localhost kernel: Process xawtv (pid: 1703,
threadinfo=d3c0a000 task=cfba2aa0)
Dec 31 17:38:32 localhost kernel: Stack: df80bbf8 c6a5cfbc 00000fd0
00000c00 000d8000 c6a5cef8 d3c0be90 c0361b0b
Dec 31 17:38:32 localhost kernel: c06ccba0 c6a5cfbc d3a08000
00000c00 00000c00 00000c00 00000120 000001b1
Dec 31 17:38:32 localhost kernel: 00000008 c6a5cf1c c06cd168
00000000 d3c0be90 c037022a df80bbf8 c6a5cf1c
Dec 31 17:38:32 localhost kernel: Call Trace:
Dec 31 17:38:32 localhost kernel: [show_stack+127/160]
Dec 31 17:38:32 localhost kernel: [show_registers+347/448]
Dec 31 17:38:32 localhost kernel: [die+256/384]
Dec 31 17:38:32 localhost kernel: [do_page_fault+1084/2083]
Dec 31 17:38:32 localhost kernel: [error_code+79/96]
Dec 31 17:38:32 localhost kernel: [bttv_buffer_risc+1371/1696]
Dec 31 17:38:32 localhost kernel: [bttv_prepare_buffer+268/464]
Dec 31 17:38:32 localhost kernel: [buffer_prepare+69/80]
Dec 31 17:38:32 localhost kernel: [videobuf_read_zerocopy+108/304]
Dec 31 17:38:32 localhost kernel: [videobuf_read_one+522/560]
Dec 31 17:38:32 localhost kernel: [bttv_read+272/352]
Dec 31 17:38:32 localhost kernel: [vfs_read+213/432]
Dec 31 17:38:32 localhost kernel: [sys_read+75/128]
Dec 31 17:38:32 localhost kernel: [syscall_call+7/11]
Dec 31 17:38:32 localhost kernel: Code: 00 0d 00 00 00 10 89 01 8b 43 08
83 c1 04 89 01 8b 43 0c 83 c1 04 83 c3 10 29 c2 8b 43 0c 39 c2 77 df 89
d0 89 d
next prev parent reply other threads:[~2005-12-31 16:48 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:05 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 [this message]
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
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=43B6B669.6020500@ns666.com \
--to=trilight@ns666.com \
--cc=7atbggg02@sneakemail.com \
--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
Powered by JetHome