From: Bob Tracy <rct@gherkin.frus.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG] 2.6.27-rc5: kobject: tried to init an initialized object...
Date: Tue, 2 Sep 2008 00:17:05 -0500 [thread overview]
Message-ID: <20080902051704.GA2261@gherkin.frus.com> (raw)
I'm getting the following when I boot 2.6.27-rc5. Completely reproducible.
Kernel is stock -rc5 except for Krzysztof Helt's AMD K6 mtrr patch.
("cat /proc/mtrr" no longer generates an I/O error, but there's no output
either). If more context is needed, I can forward a complete "dmesg" log.
(...)
Floppy drive(s): fd0 is 1.2M, fd1 is 1.44M
FDC 0 is a post-1991 82077
kobject (d7991e44): tried to init an initialized object, something is seriously wrong.
Pid: 1, comm: swapper Not tainted 2.6.27-rc5 #1
[<c01f547f>] kobject_init+0x2b/0x55
[<c01f586c>] kobject_init_and_add+0x10/0x2c
[<c01e9483>] elv_register_queue+0x52/0x58
[<c01efa03>] blk_register_filter+0x39/0x44
[<c01ee8e2>] add_disk+0x3a/0x85
[<c01ee294>] exact_match+0x0/0x7
[<c01ee684>] exact_lock+0x0/0xd
[<c03f6d34>] floppy_init+0x7d2/0xa59
[<c010103a>] _stext+0x3a/0x12a
[<c03f6562>] floppy_init+0x0/0xa59
[<c018a44c>] create_proc_entry+0x69/0x7b
[<c013ecfe>] register_irq_proc+0x74/0x8c
[<c03e6669>] kernel_init+0x5e/0xa9
[<c03e660b>] kernel_init+0x0/0xa9
[<c0102f77>] kernel_thread_helper+0x7/0x10
=======================
natsemi dp8381x driver, version 2.1, Sept 11, 2006
originally by Donald Becker <becker@scyld.com>
2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
PCI: setting IRQ 12 as level-triggered
(...)
--
------------------------------------------------------------------------
Bob Tracy | "I was a beta tester for dirt. They never did
rct@frus.com | get all the bugs out." - Steve McGrew on /.
------------------------------------------------------------------------
next reply other threads:[~2008-09-02 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 5:17 Bob Tracy [this message]
2008-09-02 5:26 ` FUJITA Tomonori
2008-09-02 6:33 ` Jens Axboe
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=20080902051704.GA2261@gherkin.frus.com \
--to=rct@gherkin.frus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome