From: "koos vriezen" <koos.vriezen@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mplayer v4l hangs in 2.6.25.2/4
Date: Sat, 17 May 2008 21:11:35 +0200 [thread overview]
Message-ID: <d4e708d60805171211q1a1966a3i78dc3dc98d275dd1@mail.gmail.com> (raw)
In-Reply-To: <20080517111639.21a3e177@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
2008/5/17 Arjan van de Ven <arjan@infradead.org>:
> Is it possible for you to enable lockdep (CONFIG_PROVE_LOCKING)?
> With that on, the kernel will print nicely which locks are being waited
> on, and if there's a deadlock, it'll print that too. Speaking of that,
> since this looks like a mutex related issue, it's worth enabling
> CONFIG_DEBUG_MUTEXES as well.... more debug checks in this area.
> If you also enable CONFIG_FRAME_POINTER then the backtrace will get
> better too (but it's not totally required, just easier for diagnostics)
See attachments.
FWIW, while mplayer is hanging, I can use another Xvideo based tv player.
Regards,
Koos Vriezen
[-- Attachment #2: mplayer.out.gz --]
[-- Type: application/x-gzip, Size: 7980 bytes --]
[-- Attachment #3: config-2.6.25.4-2.gz --]
[-- Type: application/x-gzip, Size: 17193 bytes --]
[-- Attachment #4: dmesg.out-2.gz --]
[-- Type: application/x-gzip, Size: 9041 bytes --]
next prev parent reply other threads:[~2008-05-17 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 16:54 koos vriezen
2008-05-17 18:16 ` Arjan van de Ven
2008-05-17 19:11 ` koos vriezen [this message]
2008-05-17 19:26 ` mplayer v4l hangs in 2.6.25.2/4 (likely regression) Arjan van de Ven
2008-05-17 19:34 ` Arjan van de Ven
2008-05-17 20:06 ` koos vriezen
2008-05-17 20:20 ` Arjan van de Ven
2008-05-17 20:45 ` Willy Tarreau
2008-05-20 11:49 ` Mauro Carvalho Chehab
2008-05-20 16:53 ` Arjan van de Ven
2008-05-17 21:09 ` koos vriezen
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=d4e708d60805171211q1a1966a3i78dc3dc98d275dd1@mail.gmail.com \
--to=koos.vriezen@gmail.com \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®