From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Tue, 05 Aug 2003 03:18:09 -0400 [thread overview]
Message-ID: <1060067889.7118.7.camel@blaze.homeip.net> (raw)
In-Reply-To: <1352160000.1060025773@aslan.btc.adaptec.com>
[-- Attachment #1: Type: text/plain, Size: 3529 bytes --]
On Mon, 2003-08-04 at 15:36, Justin T. Gibbs 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?
>
> You might be able to get useful information without using a serial
> console if you turn off your CDROM drives so they don't add extra output,
> but your best bet is to use a serial console.
>
> --
> Justin
>
>
Hi Justin,
This time with both plextor cdroms removed i get this in console:
scsi scan: INQUIRY to host 0 chanel 0 id0 lun 0
scsi scan: 1st INQUIRY failed with code 0x10000
and this repeats for all 15 id's on the cards with same 0x10000 code.
When using aic7xxx_old driver i get this in dmesg:
(scsi0) <Adaptec AHA-294X Ultra2 SCSI host adapter> found at PCI 1/10/0
(scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 398 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.6/5.2.0
<Adaptec AHA-294X Ultra2 SCSI host adapter>
scsi scan: INQUIRY to host 0 channel 0 id 0 lun 0
scsi scan: 1st INQUIRY successful with code 0x0
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 00
scsi scan: Sequential scan of host 0 channel 0 id 0
scsi scan: INQUIRY to host 0 channel 0 id 1 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 1 lun 0
scsi scan: 1st INQUIRY failed with code 0x6030000
scsi scan: INQUIRY to host 0 channel 0 id 2 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 3 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 4 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 5 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 6 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 8 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 9 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 10 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 11 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 12 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 13 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 14 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 15 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
SCSI device sda: 71687340 512-byte hdwr sectors (36704 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Once i get null modem serial cable i will try to get more info from
serial console.
Regards,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-08-05 7:18 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
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 [this message]
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=1060067889.7118.7.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.