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] [day] [month] [year] [list]
Date:	Thu, 22 May 2008 15:45:24 -0700
From:	Sean Bruno <sean.bruno@...-only.net>
To:	JiSheng Zhang <jszhang3@...l.ustc.edu.cn>
Cc:	stefanr@...6.in-berlin.de, krh@...hat.com,
	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt


On Thu, 2008-05-22 at 20:07 +0800, JiSheng Zhang wrote:
> Hi,
> 
> 
> >From: Stefan Richter <stefanr@...6.in-berlin.de>
> >Reply-To: 
> >To: jszhang3@...l.ustc.edu.cn
> >Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt
> >Date:Wed, 21 May 2008 17:28:25 +0200
> >
> >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
> > 
> > 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/
> >
> 
> 
I've got a VIA board causing the same error reported here.

If someone at Redhat has the time to roll a test kernel for this issue I
can test it in about 15 minutes.

Right now I'm running RHEL 5, 2.6.18-53.1.21.el5

Se

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ