From: "David S. Miller" <davem@davemloft.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: netdev@oss.sgi.com
Subject: Re: [BUG] sundance "Something Wicked happened!" (IntrPCIErr)
Date: Mon, 31 Jan 2005 11:38:34 -0800 [thread overview]
Message-ID: <20050131113834.440faca8.davem@davemloft.net> (raw)
In-Reply-To: <20050131165947.GJ6878@sunbeam.de.gnumonks.org>
On Mon, 31 Jan 2005 17:59:48 +0100
Harald Welte <laforge@gnumonks.org> wrote:
> Looking at the source code, the error message only happens if IntrPCIErr
> is set.
Try adding a printout here of the PCI status register in config
space when this happens, something like:
{
u16 val;
pci_read_config_word(np->pci_dev, PCI_STATUS, &val);
printk("%s: PCI status is %x\n", dev->name, val);
}
What we'll be looking for are bits set there such as
PCI_STATUS_SIG_TARGET_ABORT, PCI_STATUS_REC_TARGET_ABORT,
PCI_STATUS_REC_MASTER_ABORT, PCI_SIG_SYSTEM_ERROR, or
PCI_STATUS_DETECTED_PARITY.
That will tell us who is seeing the error and thus
signalling the event (either PCI bus or the sundance
chip itself).
I don't know anything specific about the sundance
hardware though, sorry.
prev parent reply other threads:[~2005-01-31 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 16:59 [BUG] sundance "Something Wicked happened!" (IntrPCIErr) Harald Welte
2005-01-31 19:38 ` David S. Miller [this message]
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=20050131113834.440faca8.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).