public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 3.2.19 kernel panic does not enter KDB
Date: Sun, 10 Jun 2012 13:22:35 +0200	[thread overview]
Message-ID: <4FD4837B.5040200@free.fr> (raw)

Hi,

I'm currently chasing a kernel panic (dual keyboard led actually 
blinking) when playing HD using XBMC on a debian unstable X86_64 
distribution.

I'm stuck with 3.2.X kernel line until maintainer of dvbhdhomerun 
integrates 3.3 DVB api changes.

I'm stuck to nvidia 302.x because this is the only nvidia driver version 
that supports xrandr and XBMC does not support nvidia proprietary 
protocol that replaces xrandr for refresh rate selection...

Its probably dues to a bad interaction between nvidia driver/vdpau/XBMC 
because VLC can play same content without panicking but with vaapi 
acceleration API instead of VDPAU.

I have a working KGDB/KDB setup (at least hitting ALT SYST q on a tty 
show KDB help). I still get the blinking led without entering KDB. When 
video freeze, I get the a fix video image, a audio loop and the blinking 
leds but cannot get access to KDB console. Any hint?

PS: please CC me I'm not subscribed.

--eric

             reply	other threads:[~2012-06-10 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10 11:22 Eric Valette [this message]
2012-06-10 11:34 ` Linux 3.2.19 kernel panic does not enter KDB Alan Cox
2012-06-10 11:38   ` Eric Valette
2012-06-10 12:37     ` richard -rw- weinberger
2012-06-10 14:15       ` Eric Valette
2012-06-11 10:54     ` Alan Cox
2012-06-11 11:11       ` Eric Valette

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=4FD4837B.5040200@free.fr \
    --to=eric.valette@free.fr \
    --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