From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Bug with (maybe not *in*) sysfs
Date: Sun, 23 Feb 2003 11:31:55 -0800 [thread overview]
Message-ID: <5480000.1046028715@[10.10.2.4]> (raw)
Customer is getting a panic from x440 w/ sysfs. May well not be
sysfs's fault ... but it's difficult to tell without knowing
what's meant to happen here ;-) debug is turned on.
Looks like kobject_register is just getting an error from kobject_add,
but as we don't see this:
pr_debug("kobject %s: registering. parent: %s, set: %s\n",
kobj->name, parent ? parent->name : "<NULL>",
kobj->kset ? kobj->kset->kobj.name : "<NULL>" );
presumably we're hitting:
if (!(kobj = kobject_get(kobj)))
return -ENOENT;
But withh no real context on all the kobject stuff it's hard to tell what
that really means ;-)
M.
Type: Processor ANSI SCSI revision: 02
DEV: registering device: ID = '1:0:9:0', name = ZIBM GNHv1 S2 0
kobject 1:0:9:0: registering. parent: 01:03.1, set: devices
bus scsi: add device 1:0:9:0
sysfs_create_link: depth = 3, size = 38
sysfs_create_link: path = '../../../devices/pci1/01:03.1/1:0:9:0'
(scsi1:A:12): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: IBM-ESXS Model: ST336607LC F Rev: B258
Type: Direct-Access ANSI SCSI revision: 03
DEV: registering device: ID = '1:0:12:0', name = SIBM-ESXSST336607LC F
3JA0JR
4X000073235STN
kobject 1:0:12:0: registering. parent: 01:03.1, set: devices
bus scsi: add device 1:0:12:0
sysfs_create_link: depth = 3, size = 39
sysfs_create_link: path = '../../../devices/pci1/01:03.1/1:0:12:0'
scsi1:A:12:0: Tagged Queuing enabled. Depth 32
(scsi1:A:13): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: IBM-ESXS Model: ST336607LC F Rev: B258
Type: Direct-Access ANSI SCSI revision: 03
DEV: registering device: ID = '1:0:13:0', name = SIBM-ESXSST336607LC F
3JA0J7
EV000073235W9F
kobject 1:0:13:0: registering. parent: 01:03.1, set: devices
bus scsi: add device 1:0:13:0
(scsi1:A:13): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: IBM-ESXS Model: ST336607LC F Rev: B258
Type: Direct-Access ANSI SCSI revision: 03
DEV: registering device: ID = '1:0:13:0', name = SIBM-ESXSST336607LC F
3JA0J7
EV000073235W9F
kobject 1:0:13:0: registering. parent: 01:03.1, set: devices
bus scsi: add device 1:0:13:0
sysfs_create_link: depth = 3, size = 39
sysfs_create_link: path = '../../../devices/pci1/01:03.1/1:0:13:0'
scsi1:A:13:0: Tagged Queuing enabled. Depth 32
bus pci: add driver ips
kobject ips: registering. parent: <NULL>, set: drivers
bus pci: add driver ips
kobject ips: registering. parent: <NULL>, set: drivers
Badness in kobject_register at lib/kobject.c:152
Call Trace:
[<c019a47b>] kobject_register+0x3b/0x50
[<c01bf3f5>] bus_add_driver+0x65/0xe0
[<c019cec6>] pci_register_driver+0x46/0x60
[<c0209b8a>] ips_detect+0x8a/0xc0
[<c01e82c6>] __scsi_add_host+0x56/0x70
[<c01e8679>] scsi_register_host+0x39/0x80
[<c01050ae>] init+0x4e/0x1c0
[<c0105060>] init+0x0/0x1c0
next reply other threads:[~2003-02-23 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 19:31 Martin J. Bligh [this message]
2003-02-23 19:14 ` Patrick Mochel
2003-02-23 20:24 ` Mike Anderson
2003-02-23 20:33 ` Martin J. Bligh
2003-02-23 23:45 ` Mike Anderson
2003-02-23 23:50 ` Martin J. Bligh
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='5480000.1046028715@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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
all inboxes | Powered by JetHome®