linux-kernel - Re: [PATCH] firewire: fix some broken hardware NMI interrupt

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: <48343F99.4030803@s5r6.in-berlin.de>
Date:	Wed, 21 May 2008 17:28:25 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	jszhang3@...l.ustc.edu.cn
CC:	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net, krh@...hat.com
Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt

jszhang3@...l.ustc.edu.cn wrote:
> Some broken pci-1394 card does not clear completely on-chip memory during boot, it
> may cause pci parity error, then NMI interrupt.

Which card?

Is the problem still present in linux-2.6.26-rc3?

Or if you don't want to test 2.6.26-rc yet, please test 2.6.25.4 with
the firewire patchkit from
http://me.in-berlin.de/~s5r6/linux1394/updates/.  There were changes to
fw-ohci which influence chip initialization.
-- 
Stefan Richter
-=====-==--- -=-= =-=-=
http://arcgraph.de/sr/
--
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/