From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
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, 04 Aug 2003 14:26:54 -0400 [thread overview]
Message-ID: <1060021614.889.6.camel@blaze.homeip.net> (raw)
In-Reply-To: <20030804093035.A24860@beaverton.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
On Mon, 2003-08-04 at 12:30, Patrick Mansfield wrote:
> On Sun, Aug 03, 2003 at 06:31:15PM -0400, Diffie wrote:
> > On Sun, Aug 03, 2003 at 06:23:13PM -0400, Diffie wrote:
>
> > > Thank you for all your help.Sorry but i gave the wrong URL in previous
> > > email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/
> > >
>
> Per your screen dump - it found the cd-rom's on id 3 and 4, but not your
> disk drive that was at id 0, and the adapter found something at id 6 (host
> adapter is at id 7).
>
> You could try turning on scan logging, it might give more information.
> You can turn on the logging at boot time, make sure you have
> CONFIG_SCSI_LOGGING on, the information of interest (scan of host 0 chan 0
> id 0 lun 0) likely will scroll off screen.
>
> For scan logging, add to your boot line:
>
> scsi_mod.scsi_logging_level=0x140
>
> To limit the logging info, make sure max_scsi_luns=1 via config or boot
> time option scsi_mod.max_scsi_luns=1.
>
> -- Patrick Mansfield
>
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/
Thanks for your help.
Paul B.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-04 18:24 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 [this message]
2003-08-04 18:57 ` Patrick Mansfield
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=1060021614.889.6.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.net \
--cc=akpm@osdl.org \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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 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.