From: "JiSheng Zhang" <jszhang3@mail.ustc.edu.cn>
To: stefanr@s5r6.in-berlin.de
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, krh@redhat.com
Subject: Re: [PATCH] firewire: fix some broken hardware NMI interrupt
Date: Fri, 23 May 2008 21:17:37 +0800 [thread overview]
Message-ID: <411548657.14585@ustc.edu.cn> (raw)
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@s5r6.in-berlin.de>
>Reply-To:
>To: JiSheng Zhang <jszhang3@mail.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@s5r6.in-berlin.de>
> >> 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
>
> Great, thanks for testing.
>
> I hope this is now permanently fixed. Should it ever appear again, just
> tell us.
> --
> Stefan Richter
> -=====-==--- -=-= =-==-
>
next reply other threads:[~2008-05-23 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 13:17 JiSheng Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-22 12:07 [PATCH] firewire: fix some broken hardware NMI interrupt JiSheng Zhang
2008-05-22 13:38 ` Stefan Richter
2008-05-22 22:45 ` Sean Bruno
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=411548657.14585@ustc.edu.cn \
--to=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