mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Bruno <sean.bruno@dsl-only.net>
To: JiSheng Zhang <jszhang3@mail.ustc.edu.cn>
Cc: stefanr@s5r6.in-berlin.de, krh@redhat.com,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt
Date: Thu, 22 May 2008 15:45:24 -0700	[thread overview]
Message-ID: <1211496325.1374.99.camel@home-desk> (raw)
In-Reply-To: <411458028.04591@ustc.edu.cn>


On Thu, 2008-05-22 at 20:07 +0800, JiSheng Zhang wrote:
> Hi,
> 
> 
> >From: Stefan Richter <stefanr@s5r6.in-berlin.de>
> >Reply-To: 
> >To: jszhang3@mail.ustc.edu.cn
> >Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt
> >Date:Wed, 21 May 2008 17:28:25 +0200
> >
> >jszhang3@mail.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


  parent reply	other threads:[~2008-05-22 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:07 JiSheng Zhang
2008-05-22 13:38 ` Stefan Richter
2008-05-22 22:45 ` Sean Bruno [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-23 13:17 JiSheng Zhang
2008-05-21 13:08 jszhang3
2008-05-21 15:28 ` Stefan Richter
2008-05-21 22:56   ` Stefan Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211496325.1374.99.camel@home-desk \
    --to=sean.bruno@dsl-only.net \
    --cc=jszhang3@mail.ustc.edu.cn \
    --cc=krh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®