mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: eric.valette@free.fr
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2.19 kernel panic does not enter KDB
Date: Mon, 11 Jun 2012 11:54:14 +0100	[thread overview]
Message-ID: <20120611115414.06759ae3@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <4FD48744.3000602@free.fr>

> type of answer helps nothing. I know nobody there is going to debug 
> nvidia driver but I'm not even sure its not something else. Neither are you.
> 
> So the bug is still that KDB is not entered.

There are lots of ways kdb may not get entered on a driver crash.
This is especially true from complex DMA capable hardware than can do
anything. For a lot of stuff you'd run it under something like qemu so
you could debug that way but for graphics drivers that doesn't really
work.

So to debug it you'd start by commenting out bits of the driver code to
see if it still does it if those parts are not executed. You can't do
that with the Nvidia blob so you'll have to get Nvidia to do the work.

If it was occurring with the Nouveau driver you'd be able to comment
stuff out and try and work out which particular paths triggered the
problem.

kdb not getting entered is not itself a bug - its a limitation.

Alan

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10 11:22 Eric Valette
2012-06-10 11:34 ` 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 [this message]
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=20120611115414.06759ae3@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=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

Powered by JetHome