public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: scott <scott@dsbcpas.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PATCH: dpt_i2o memory leak comments
Date: Wed, 11 Jun 2003 15:48:00 -0400	[thread overview]
Message-ID: <3EE78770.2070704@dsbcpas.com> (raw)

Question/Help:
Our threading indexer routinely crashes our Adaptec 2400A. How can I 
duplicate that activity for the Adaptec team as they request below?
Scott Beane

-------- Original Message --------
Subject: 	RE: [Fwd: Re: dpt_i2o memory leak]
Date: 	Wed, 11 Jun 2003 13:49:27 -0400
From: 	Salyzyn, Mark <mark_salyzyn@adaptec.com>
To: 	'scott' <scott@dsbcpas.com>
CC: 	'tcallawa@redhat.com' <tcallawa@redhat.com>



Thanks, I believe this confirms my understanding at least regarding the
`leak'. I will try to `make it better' in the future.

The panic you forwarded is a source of consternation. It occurs in the
scsi_done command which takes it out of the driver making it difficult of
debug (remote as we are).

Being able to duplicate this problem locally becomes necessary. If you can
provide to me a simplified set of tools and description on how to duplicate
this, I will get this sent off to our software test team to bash on.

Sincerely -- Mark Salyzyn




             reply	other threads:[~2003-06-11 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 19:48 scott [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-11 14:01 [PATCH] PATCH: dpt_i2o memory leak comments scott
     [not found] <200304012105.h31L5vG11354@hera.kernel.org>
2003-04-01 13:15 ` Randy.Dunlap
2003-04-01 21:26   ` Richard B. Johnson
2003-04-01 21:26     ` Nigel Cunningham
2003-04-01 23:12       ` jw schultz
2003-04-02 11:32         ` Alan Cox
2003-04-02 10:11   ` Jörn Engel
2003-04-02 11:58   ` Alan Cox

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=3EE78770.2070704@dsbcpas.com \
    --to=scott@dsbcpas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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