From: Mike Phillips <phillim2@home.com>
To: Kent E Yoder <yoder1@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IBM Lanstreamer bugfixes
Date: Sat, 19 Jan 2002 12:14:19 -0500 [thread overview]
Message-ID: <20020119171418.GA14412@home.com> (raw)
In-Reply-To: <OF0DC8C676.D07D3CD8-ON85256B45.007E1B7C@raleigh.ibm.com>
In-Reply-To: <OF0DC8C676.D07D3CD8-ON85256B45.007E1B7C@raleigh.ibm.com>
On Fri, Jan 18, 2002 at 05:02:57PM -0600 or sometime in the same epoch, Kent E Yoder scribbled:
> Ok, I thought of one thing that might make things clearer here: when I
> say "the write failed", I mean that we saw the write go out on the PCI bus
> and then the box locked up. We were looking at it on a PCI bus analyzer.
> That, and it wasn't just this write, or just writes in general, it really
> seemed random.
>
Kent,
We had this on olympic for certain high end IBM boxen. Spent forever
trying to trap it as I couldn't emulate the behaviour on my test
boxes. We weren't getting correct values from pci reads/write and we
were running out of buffers as they weren't getting flushed. The
machine wouldn't lock but the adapter would stop tx/rx.
Turned out the pci bridge on the machine itself was causing the
problems. Tweaking the pci bus fixed the problem.
--
Mike Phillips
Linux Token Ring Project
http://www.linuxtr.net
mailto: mikep@linuxtr.net
next prev parent reply other threads:[~2002-01-19 18:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 23:02 [PATCH] IBM Lanstreamer bugfixes Kent E Yoder
2002-01-18 23:19 ` Alan Cox
2002-01-18 23:52 ` Gérard Roudier
2002-01-19 17:14 ` Mike Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-01 20:53 Kent E Yoder
2002-02-01 23:38 ` Alan Cox
2002-02-01 23:40 ` Alan Cox
2002-01-30 19:27 Kent E Yoder
2002-01-30 19:48 ` Jeff Garzik
2002-01-30 19:58 ` David Weinehall
2002-01-30 20:43 ` Alan Cox
2002-01-30 20:04 ` Mike Phillips
2002-01-30 20:47 ` Alan Cox
2002-01-21 16:44 Kent E Yoder
2002-01-21 17:46 ` Mike Phillips
2002-01-18 22:39 Kent E Yoder
2002-01-18 22:32 Kent E Yoder
2002-01-18 22:47 ` Alan Cox
2002-01-18 20:52 Kent E Yoder
2002-01-18 21:35 ` Alan Cox
2002-01-17 15:29 Kent E Yoder
2002-01-16 19:42 Kent E Yoder
2002-01-17 10:57 ` Jeff Garzik
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=20020119171418.GA14412@home.com \
--to=phillim2@home.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yoder1@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.