From: "Grégoire Favre" <gregoire.favre@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [gregoire.favre@gmail.com: What breaks aic7xxx in post 2.6.12-rc2 ?]
Date: Mon, 16 May 2005 17:54:09 +0200 [thread overview]
Message-ID: <20050516155409.GE9558@gmail.com> (raw)
In-Reply-To: <1116258401.5040.14.camel@mulgrave>
On Mon, May 16, 2005 at 10:46:41AM -0500, James Bottomley wrote:
> As I read it, nothing is going wrong ... the trace indicates that the
> device is eventually configured async by DV, so the system comes up with
> it's full complement of devices. Which device is this by the way, the
> inquiry information is missing from the top.
>
> The bug is that the DV code should shut the driver up while it probes to
> avoid frightening users (particularly as the aic7xxx driver prints lots
> of scary messages while its in error handling).
What's DV ?
With 2.6.12-rc4 the system finally boots, but it took about 30
minutes... so it must be some changes introduced in 2.6.12-rc3 that my
computer don't like.
Here's my /proc/scsi/scsi :
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DDRS-39130D Rev: DC1B
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 15 Lun: 00
Vendor: SEAGATE Model: ST336706LW Rev: 0108
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: TOSHIBA Model: DVD-ROM SD-M1201 Rev: 1R08
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.08
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.08
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 00
Vendor: SMSC Model: 223 U HS-CF Rev: 3.60
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi7 Channel: 00 Id: 00 Lun: 01
Vendor: SMSC Model: 223 U HS-MS Rev: 3.60
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi7 Channel: 00 Id: 00 Lun: 02
Vendor: SMSC Model: 223 U HS-SM Rev: 3.60
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi7 Channel: 00 Id: 00 Lun: 03
Vendor: SMSC Model: 223 U HS-SD/MMC Rev: 3.60
Type: Direct-Access ANSI SCSI revision: 02
Which info should I sent in order to find what's the problem is ?
Thank you and please keep CC to me as I am not in this ml.
--
Grégoire Favre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-05-16 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 15:26 [gregoire.favre@gmail.com: What breaks aic7xxx in post 2.6.12-rc2 ?] Christoph Hellwig
2005-05-16 15:46 ` James Bottomley
2005-05-16 15:54 ` Grégoire Favre [this message]
2005-05-16 16:33 ` James Bottomley
2005-05-16 18:05 ` Grégoire Favre
2005-05-16 21:07 ` James Bottomley
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=20050516155409.GE9558@gmail.com \
--to=gregoire.favre@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--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