linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Chouquet-Stringer <mchouque@free.fr>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	James.Bottomley@SteelEye.com
Subject: Re: class_device_add error in SCSI with 2.6.17-rc2-g52824b6b
Date: Thu, 20 Apr 2006 00:17:56 +0200	[thread overview]
Message-ID: <20060419221756.GA12149@localhost> (raw)
In-Reply-To: <20060419215803.6DE5BDBA1@gherkin.frus.com>

On Wed, Apr 19, 2006 at 04:58:03PM -0500, Bob Tracy wrote:
> Similar error previously reported by me for 2.6.17-rc1, except sda got
> added fine: error occurred when attempting to add/register sdb. 

Actually you're right. I'm rereading the logs and the first device on a
scsi bus is always registered correctly. The sh*t hits the fan when you
have more than one sd device per bus. (I've got 2 devices on one, and 3
on the other and only the first one on each got registered correctly).

> Thankfully, you were able to append a trace...

I used the serial console.

> I'll be trying the just-released 2.6.17-rc2 this evening.  Report to
> follow, and if there's a problem, I'll attempt to provide the trace
> (will have to be transcribed by hand, as system won't come up far
> enough for syslog to capture anything).

If syslog doesn't come up and depending on the state of your system you
could redirect dmesg output to a file.
-- 
Mathieu Chouquet-Stringer                           mchouque@free.fr


  reply	other threads:[~2006-04-19 22:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 21:31 class_device_add error in SCSI with 2.6.17-rc2-g52824b6b Mathieu Chouquet-Stringer
2006-04-19 21:58 ` Bob Tracy
2006-04-19 22:17   ` Mathieu Chouquet-Stringer [this message]
2006-04-20 10:14   ` Mathieu Chouquet-Stringer
2006-04-20 10:57     ` Mathieu Chouquet-Stringer
2006-04-20 17:11     ` strncpy (maybe others) broken on Alpha Mathieu Chouquet-Stringer
2006-04-20 20:55       ` Mathieu Chouquet-Stringer
2006-04-20 21:24         ` Ivan Kokshaysky
2006-04-20 21:27           ` Mathieu Chouquet-Stringer
2006-04-20 21:40           ` Bob Tracy
2006-04-20 21:57           ` Mathieu Chouquet-Stringer
2006-04-21  2:43             ` Bob Tracy
2006-04-21  8:15               ` Mathieu Chouquet-Stringer
2006-04-21  9:21                 ` Mathieu Chouquet-Stringer
2006-04-21  9:50                   ` Mathieu Chouquet-Stringer
2006-04-21 11:41                     ` Bob Tracy
2006-04-21 11:55                       ` Mathieu Chouquet-Stringer
2006-04-21 14:22                         ` Ivan Kokshaysky
2006-04-21 19:37                           ` Bob Tracy
2006-04-21 21:12                             ` Ivan Kokshaysky
2006-04-21 22:49                               ` Bob Tracy
2006-04-22  8:47                                 ` Mathieu Chouquet-Stringer
2006-04-22  8:45                           ` Mathieu Chouquet-Stringer
2006-04-22 10:39                     ` Bryan Østergaard
2006-04-20 21:22       ` Ivan Kokshaysky
2006-04-20 21:25         ` Mathieu Chouquet-Stringer

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=20060419221756.GA12149@localhost \
    --to=mchouque@free.fr \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rct@gherkin.frus.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).