linux-kernel - Re: Prevent softlockup triggering in nvidiafb

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070423161848.GA27649@redhat.com>
Date:	Mon, 23 Apr 2007 12:18:48 -0400
From:	Dave Jones <davej@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Antonino Daplas <adaplas@....net>
Subject: Re: Prevent softlockup triggering in nvidiafb

On Mon, Apr 23, 2007 at 04:55:05PM +0100, Alan Cox wrote:
 > On Mon, 23 Apr 2007 11:36:30 -0400
 > Dave Jones <davej@...hat.com> wrote:
 > 
 > > If the chip locks up, we get into a long polling loop,
 > > where the softlockup detector kicks in.
 > > See https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=151878
 > > for an example.
 > 
 > Surely in this situation the softlockup report and trap out is precisely
 > what should be occurring.

We can't do anything useful with the trace.  It already prints out
info that the hardware locked up.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/