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>] [day] [month] [year] [list]

Message-ID: <411548657.14585@ustc.edu.cn>
Date:	Fri, 23 May 2008 21:17:37 +0800
From:	"JiSheng Zhang" <jszhang3@...l.ustc.edu.cn>
To:	stefanr@...6.in-berlin.de
Cc:	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net, krh@...hat.com
Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt

Hi,
after a lot of test today, the problem appears again. Now it also emit a similar
message even applied my patch. Tested on 2.6.25-4 and 2.6.26-rc3.
The via chip is VT6306. How can I dig into this problem more?

CU,
JiSheng

>From: Stefan Richter <stefanr@...6.in-berlin.de>
>Reply-To: 
>To: JiSheng Zhang <jszhang3@...l.ustc.edu.cn>
>Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt
>Date:Thu, 22 May 2008 15:38:30 +0200
>
>JiSheng Zhang wrote:
> >> From: Stefan Richter <stefanr@...6.in-berlin.de>
> >> 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?
> > hmm, one card using VIA chip.
> >> 
> >> Is the problem still present in linux-2.6.26-rc3?
> > It seems that the problem disappeared. Thanks
> 
> Great, thanks for testing.
> 
> I hope this is now permanently fixed.  Should it ever appear again, just
> tell us.
> -- 
> Stefan Richter
> -=====-==--- -=-= =-==-
>


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