linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Andries.Brouwer@cwi.nl
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: 2.5.63/64 do not boot: loop in scsi_error
Date: Wed, 5 Mar 2003 22:49:21 -0800	[thread overview]
Message-ID: <20030306064921.GA1425@beaverton.ibm.com> (raw)
In-Reply-To: <UTC200303060639.h266dIo22884.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl [Andries.Brouwer@cwi.nl] wrote:
> > See if this fixes it..
> 
> No, I am afraid not. My infinite loop does not pass through
> scsi_eh_ready_devs().
> 

Can you send me your console log. If you have scsi_logging=1 that would
be greate also.

-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2003-03-06  6:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06  6:39 2.5.63/64 do not boot: loop in scsi_error Andries.Brouwer
2003-03-06  6:49 ` Mike Anderson [this message]
2003-03-06  7:59   ` Zwane Mwaikambo
2003-03-06  8:30     ` Mike Anderson
2003-03-06  8:35       ` Zwane Mwaikambo
2003-03-06  8:55         ` Mike Anderson
2003-03-06  9:00           ` Zwane Mwaikambo
2003-03-06  9:18             ` Mike Anderson
2003-03-06  9:58               ` Zwane Mwaikambo
2003-03-06 16:31                 ` James Bottomley
2003-03-06 17:15                   ` Zwane Mwaikambo
2003-03-06 17:21                     ` James Bottomley
2003-03-06 17:39                       ` Zwane Mwaikambo
2003-03-06 18:14                         ` Mike Anderson
2003-03-06 17:24                     ` Mike Anderson
2003-03-06  8:37       ` Mike Anderson
  -- strict thread matches above, loose matches on Subject: below --
2003-03-06  9:22 Andries.Brouwer
2003-03-06  1:01 Andries.Brouwer
2003-03-06  1:13 ` Patrick Mansfield
2003-03-06  1:22 ` Linus Torvalds
2003-03-06  4:15 ` Rob Radez

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=20030306064921.GA1425@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@transmeta.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).