From: Thomas Steudten <alpha@steudten.com>
To: linux-kernel@vger.kernel.org
Subject: Badness in kernel 2.6.4 SG/SCSI
Date: Fri, 12 Mar 2004 16:43:40 +0100 [thread overview]
Message-ID: <4051DAAC.9000603@steudten.com> (raw)
Hi
I got this from 2.6.4 kernel first after boot:
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Badness in kobject_get at lib/kobject.c:429
fffffc0013947d98 0000000000000000 fffffc00004ace54 0000000000000001
fffffc000037c564 0000000000000001 fffffc001cb1a8c0 0000000001500001
fffffc0013947e08 0000000000000000 fffffffc00234fe4 0000000000000001
0000000000000000 fffffffc001aa000 0000000001500001 0000000000000000
0000000000000000 fffffc001e7d4388 fffffc00004f2b78 fffffc00001251f0
fffffffc0023d260 fffffc0000731ef0 fffffc0000731f88 fffffc0000731f70
Trace:fffffc00004ace54 fffffc000037c564 fffffc00004f2b78 fffffc00004f1fd0
fffffc0000533154 fffffc0000346018 fffffc0000312b84
Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 0, type 0
Badness in kobject_get at lib/kobject.c:429
fffffc0013947d98 0000000000000000 fffffc00004ace54 0000000000000002
fffffc000037c564 0000000000000002 fffffc001cb1a828 0000000001500002
fffffc0013947e08 0000000000000000 fffffffc00234fe4 0000000000000002
0000000000000000 fffffffc001ae000 0000000001500002 0000000000000000
0000000000000000 fffffc001e7d4388 fffffc00004f2b78 fffffc0000125e38
fffffffc0023d260 fffffc0000731ef0 fffffc0000731f88 fffffc0000731f70
Trace:fffffc00004ace54 fffffc000037c564 fffffc00004f2b78 fffffc00004f1fd0
fffffc0000533154 fffffc0000346018 fffffc0000312b84
Attached scsi generic sg2 at scsi0, channel 0, id 2, lun 0, type 0
Badness in kobject_get at lib/kobject.c:429
fffffc0013947d98 0000000000000000 fffffc00004ace54 0000000000000003
fffffc000037c564 0000000000000003 fffffc001cb1a790 0000000001500003
fffffc0013947e08 0000000000000000 fffffffc00234fe4 0000000000000003
0000000000000000 fffffffc001b2000 0000000001500003 0000000000000000
0000000000000000 fffffc001e7d4388 fffffc00004f2b78 fffffc0000126db8
fffffffc0023d260 fffffc0000731ef0 fffffc0000731f88 fffffc0000731f70
Trace:fffffc00004ace54 fffffc000037c564 fffffc00004f2b78 fffffc00004f1fd0
fffffc0000533154 fffffc0000346018 fffffc0000312b84
Attached scsi generic sg3 at scsi0, channel 0, id 3, lun 0, type 0
Trace; fffffc00004ace54 <kobject_rename+64/80>
Trace; fffffc000037c564 <base_probe+4/a0>
Trace; fffffc00004acca8 <kobject_set_name+38/180>
Trace; fffffc00004f2b78 <class_simple_destroy+48/60>
Trace; fffffc00004f1fd0 <class_dev_release+50/b0>
Trace; fffffc0000533154 <scsi_sysfs_register+64/a0>
Trace; fffffc0000346018 <module_address_lookup+78/c0>
Trace; fffffc0000312b84 <entSys+a4/c0>
Trace; fffffc00004ace54 <kobject_rename+64/80>
Trace; fffffc000037c564 <base_probe+4/a0>
Trace; fffffc00004f2b78 <class_simple_destroy+48/60>
Trace; fffffc00004f1fd0 <class_dev_release+50/b0>
Trace; fffffc0000533154 <scsi_sysfs_register+64/a0>
Trace; fffffc0000346018 <module_address_lookup+78/c0>
Trace; fffffc0000312b84 <entSys+a4/c0>
Trace; fffffc00004ace54 <kobject_rename+64/80>
Trace; fffffc000037c564 <base_probe+4/a0>
Trace; fffffc00004f2b78 <class_simple_destroy+48/60>
Trace; fffffc00004f1fd0 <class_dev_release+50/b0>
Trace; fffffc0000533154 <scsi_sysfs_register+64/a0>
Trace; fffffc0000346018 <module_address_lookup+78/c0>
Trace; fffffc0000312b84 <entSys+a4/c0>
Trace; fffffc00004ace54 <kobject_rename+64/80>
Trace; fffffc000037c564 <base_probe+4/a0>
Trace; fffffc00004f2b78 <class_simple_destroy+48/60>
Trace; fffffc00004f1fd0 <class_dev_release+50/b0>
Trace; fffffc0000533154 <scsi_sysfs_register+64/a0>
Trace; fffffc0000346018 <module_address_lookup+78/c0>
Trace; fffffc0000312b84 <entSys+a4/c0>
00:07.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 01)
Subsystem: Adaptec AHA-2940UW SCSI Host Adapter
Flags: bus master, medium devsel, latency 32, IRQ 26
I/O ports at 8400 [size=256]
Memory at 000000000a051000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 000000000a040000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
Can anyone please fix this in the kernel code.
--
Tom
next reply other threads:[~2004-03-12 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 15:43 Thomas Steudten [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 21:51 Badness in kernel 2.6.4 SG/SCSI Thomas Steudten
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=4051DAAC.9000603@steudten.com \
--to=alpha@steudten.com \
--cc=linux-kernel@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 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.