public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sym2 oops in 2.6.9-rc2-BK
Date: Wed, 29 Sep 2004 01:25:48 +1000	[thread overview]
Message-ID: <20040928152548.GD3373@krispykreme.ozlabs.ibm.com> (raw)
In-Reply-To: <20040928145638.GY16153@parcelfarce.linux.theplanet.co.uk>

 
> Yes, this looks like the right solution to me.
> 
> Can you tell me what circumstances you see it under, and do you
> successfully negotiate 160MB/s with this patch?

There is a bunch of bad hardware in it, so Im having a bit of trouble
working out exactly what is going on :) I'll look through the logs and
see if I can make sense of them.

Anton

  reply	other threads:[~2004-09-28 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 13:58 sym2 oops in 2.6.9-rc2-BK Anton Blanchard
2004-09-28 14:21 ` Anton Blanchard
2004-09-28 15:17   ` Matthew Wilcox
2004-09-28 14:56 ` Matthew Wilcox
2004-09-28 15:25   ` Anton Blanchard [this message]
2004-09-28 15:38 ` James Bottomley
2004-09-30 13:05   ` Anton Blanchard
2004-09-30 13:52     ` James Bottomley
2004-09-30 14:05       ` Anton Blanchard

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=20040928152548.GD3373@krispykreme.ozlabs.ibm.com \
    --to=anton@samba.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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