All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Paul Blazejowski <paulb@blazebox.homeip.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	"Justin T. Gibbs" <gibbs@scsiguy.com>
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Mon, 4 Aug 2003 11:57:25 -0700	[thread overview]
Message-ID: <20030804115725.A26812@beaverton.ibm.com> (raw)
In-Reply-To: <1060021614.889.6.camel@blaze.homeip.net>; from paulb@blazebox.homeip.net on Mon, Aug 04, 2003 at 02:26:54PM -0400

On Mon, Aug 04, 2003 at 02:26:54PM -0400, Paul Blazejowski wrote:
> 
> Patrick,
> 
> I enabled CONFIG_SCSI_LOGGING=y in kernel then i used
> scsi_mod.scsi_logging_level=0x140 and scsi_mod.max_scsi_luns=1 when
> booting the kernel from lilo.I can see some debug information scroll on
> the screen and i did see ID0 LUN0 get probed even the correct transfer
> rate for the SCSI disk is set.I forgot but isn't there a key sequence
> when pressed it will stop the screen output like pause/break key?
> 
> I have few screen snaps which can be viewed at 
> http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/aic7xxx/

Yep, the shot that might have useful information is blurred.

I assume you are unable to use a serial console.

I can usually "Shift + page-up" as long as there is not too much data, and
depending on your console, AFAIR I can't pause my console output.

Also, does the adapter bios show the drive at boot time?

Hopefully Justin will add more useful suggestions for debugging.

-- Patrick Mansfield

  reply	other threads:[~2003-08-04 18:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 18:22 Badness in device_release at drivers/base/core.c:84 Diffie
2003-08-01 21:27 ` Greg KH
2003-08-02  5:40   ` Diffie
2003-08-01 21:44 ` Andrew Morton
2003-08-01 23:27   ` Mike Anderson
2003-08-02  5:57     ` Diffie
2003-08-02  5:53   ` Diffie
2003-08-03  1:55   ` Diffie
2003-08-03  2:07     ` Andrew Morton
2003-08-03 21:47       ` Diffie
2003-08-03 21:52         ` Andrew Morton
2003-08-03 22:23           ` Diffie
2003-08-03 22:31             ` Diffie
2003-08-04 16:30               ` Patrick Mansfield
2003-08-04 17:48                 ` Paul Blazejowski
2003-08-04 18:26                 ` Paul Blazejowski
2003-08-04 18:57                   ` Patrick Mansfield [this message]
2003-08-04 19:36                   ` Justin T. Gibbs
2003-08-05  2:21                     ` Paul Blazejowski
2003-08-05 10:20                       ` wb
2003-08-05 16:10                         ` Ishikawa
2003-08-06 16:58                           ` Paul Blazejowski
2003-08-06 17:20                             ` Chiaki
2003-08-13  2:03                               ` Chiaki
2003-08-06 16:55                         ` Paul Blazejowski
2003-08-05  7:18                     ` Paul Blazejowski

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=20030804115725.A26812@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=paulb@blazebox.homeip.net \
    /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.