| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAFLxGvwtCDCdWoXCBr2nytm93Kyei-pLoioGGxhu_+TMFfdNzQ@mail.gmail.com> Date: Sun, 10 Jun 2012 14:37:58 +0200 From: richard -rw- weinberger <richard.weinberger@...il.com> To: eric.valette@...e.fr Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 3.2.19 kernel panic does not enter KDB On Sun, Jun 10, 2012 at 1:38 PM, Eric Valette <eric.valette@...e.fr> wrote: > On 10/06/2012 13:34, Alan Cox wrote: > >> >> 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. > > > Maybe you are still annoyed by the picture linus has posted but that 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. The problem with proprietary code is that *anything* can happen. If the crash happened within the Nvidia binary blob you are toasted... -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists