From: Michael Reed <mdr@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-scsi@vger.kernel.org, rct@gherkin.frus.com
Subject: Re: Fw: [BUG] 2.6.17-rc1: SCSI kobject_add problems
Date: Mon, 24 Apr 2006 10:07:18 -0500 [thread overview]
Message-ID: <444CE9A6.6030304@sgi.com> (raw)
In-Reply-To: <20060407171433.06e454bd.akpm@osdl.org>
See my post on 4/21:
"2.6.17-rc2: kobject_add failed"
http://marc.theaimsgroup.com/?l=linux-scsi&m=114563629810793&w=2
Perhaps this is related?
http://marc.theaimsgroup.com/?t=114443491400001&r=1&w=2
Mike
Andrew Morton wrote:
>
> Begin forwarded message:
>
> Date: Fri, 7 Apr 2006 13:31:05 -0500 (CDT)
> From: rct@gherkin.frus.com (Bob Tracy)
> To: linux-kernel@vger.kernel.org
> Subject: [BUG] 2.6.17-rc1: SCSI kobject_add problems
>
>
> System is a DEC Alpha 433au with two SCSI disks. SCSI controller is a
> QLA1040 supported by the qla1280 driver. Runs 2.6.16 fine. Tried
> booting 2.6.17-rc1 and got
>
> kobject_add failed for 0:0: with -EEXIST, don't try to register things with the same name in the same directory
>
> and a fairly long trace output when the system attempted to add sdb.
> Not surprisingly, sdb was inaccessible.
>
> Normally (for 2.6.16 anyway), the following relationship exists:
>
> sd 0:0:0:0 sda
> sd 0:0:1:0 sdb
>
> More information *might* be available if needed, but will have to be
> transcribed by hand. My /usr partition is on sdb, so I don't get very
> far with 2.6.17-rc1 on Alpha :-). The problem is probably specific to
> the qla1280 or the Alpha, as I have a x86 Adaptec SCSI-based system
> with multiple spindles that works fine with 2.6.17-rc1.
>
next prev parent reply other threads:[~2006-04-24 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 0:14 Fw: [BUG] 2.6.17-rc1: SCSI kobject_add problems Andrew Morton
2006-04-24 15:07 ` Michael Reed [this message]
2006-04-24 18:55 ` Bob Tracy
2006-04-24 20:15 ` Andrew Morton
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=444CE9A6.6030304@sgi.com \
--to=mdr@sgi.com \
--cc=akpm@osdl.org \
--cc=andrew.vasquez@qlogic.com \
--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 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.