Re: Linux 3.2.19 kernel panic does not enter KDB

[Alan Cox]

On Sun, 10 Jun 2012 13:22:35 +0200
Eric Valette <eric.valette@xxxxxxx> wrote:

> 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?

I think you are on the wrong list. Nvidia have kernel source code, we
don't have code to their proprietary stuff. Only they can help you.

It's quite possible the box is hanging so hard that kdb can't help you.
In that case you'll again need someone with their proprietary Nvidia
source to help you.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/