public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] instrument ide-scsi in 2.5.68
Date: Wed, 7 May 2003 11:16:34 -0700	[thread overview]
Message-ID: <20030507111634.2cb1fe95.rddunlap@osdl.org> (raw)
In-Reply-To: <3EB90867.6050803@torque.net>

Hi Doug-

On Wed, 07 May 2003 23:21:43 +1000 Douglas Gilbert <dougg@torque.net> wrote:

| Randy.Dunlap wrote:
| > On Tue, 06 May 2003 18:38:39 +1000 Douglas Gilbert <dougg@torque.net> wrote:
| > 
| > | > Are there any docs on SCSI logging?
| 
| Do your failures only occur in an SMP environment?

Yes, I've been testing only SMP.
I just rebooted 2.5.68 + your first ide-scsi patch with "nosmp"
and it faults during the boot sequence at
EIP is at scsi_eh_offline_sdevs+0x21/0x78.
Full log available if wanted.

I'll try 2.5.69 plus your patch ver. 2.

| and the pattern continues with the two atapi devices changing
| positions. So much for device naming stability.

8:(

--
~Randy

  reply	other threads:[~2003-05-07 18:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 13:02 [PATCH] instrument ide-scsi in 2.5.68 Douglas Gilbert
2003-05-01 22:52 ` Randy.Dunlap
2003-05-01 22:57   ` Randy.Dunlap
2003-05-01 23:29   ` Douglas Gilbert
2003-05-01 23:44     ` Willem Riede
2003-05-02  0:38     ` Randy.Dunlap
2003-05-02  1:10       ` Douglas Gilbert
2003-05-02  8:40 ` Douglas Gilbert
2003-05-02 16:55   ` Randy.Dunlap
2003-05-03  9:03     ` Douglas Gilbert
2003-05-05  8:46       ` Mike Anderson
2003-05-05 16:57       ` Randy.Dunlap
2003-05-06  8:38         ` Douglas Gilbert
2003-05-06 14:39           ` Randy.Dunlap
2003-05-07 13:21             ` Douglas Gilbert
2003-05-07 18:16               ` Randy.Dunlap [this message]
2003-05-07 21:20                 ` Randy.Dunlap
2003-05-08  0:00                   ` Douglas Gilbert

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=20030507111634.2cb1fe95.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dougg@torque.net \
    --cc=linux-scsi@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