From: Jean Delvare <khali@linux-fr.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux I2C <i2c@lm-sensors.org>,
LKML <linux-kernel@vger.kernel.org>,
Ben Dooks <ben-linux@fluff.org>, Greg KH <gregkh@suse.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [crash, bisected] I2C, kobject (ffff81003e8c4160): tried to init an initialized object (was: Re: [GIT PULL] i2c updates for 2.6.27, round 1)
Date: Wed, 16 Jul 2008 11:07:02 +0200 [thread overview]
Message-ID: <20080716110702.3ca61eb2@hyperion.delvare> (raw)
In-Reply-To: <20080716082352.GA30483@elte.hu>
Hi Ingo,
On Wed, 16 Jul 2008 10:23:52 +0200, Ingo Molnar wrote:
>
> hi Jean,
>
> * Jean Delvare <khali@linux-fr.org> wrote:
>
> > i2c-nforce2: Add support for multiplexing on the Tyan S4985
>
> -tip random boot testing started triggering the following upstream boot
> crash, starting two days ago when the i2c tree was merged:
>
> [ 11.772002] kobject (ffff81003e8c4160): tried to init an initialized object, something is seriously wrong.
> [ 11.784004] Pid: 1, comm: swapper Not tainted 2.6.26-00007-g279e902-dirty #19896
> [ 11.793651]
> [ 11.793651] Call Trace:
> [ 11.793651] [<ffffffff8054471a>] kobject_init+0x7a/0x80
> [ 11.798969] [<ffffffff805f0f9d>] device_initialize+0x2d/0xd0
> [ 11.806323] [<ffffffff805f19a1>] device_register+0x11/0x20
> [ 11.811903] [<ffffffff8087ee3b>] i2c_register_adapter+0xab/0x1d0
> [ 11.817666] [<ffffffff8087f0e6>] i2c_add_adapter+0x96/0xb0
> [ 11.823761] [<ffffffff81196372>] nforce2_s4985_init+0x272/0x370
> [ 11.829358] [<ffffffff8027516a>] ? getnstimeofday+0x3a/0xc0
> [ 11.835365] [<ffffffff802728ba>] ? ktime_get_ts+0x4a/0x60
> [ 11.840853] [<ffffffff81196100>] ? nforce2_s4985_init+0x0/0x370
> [ 11.846859] [<ffffffff81160aa3>] kernel_init+0x123/0x300
> [ 11.852261] [<ffffffff81160140>] ? early_idt_handler+0x0/0x74
> [ 11.857957] [<ffffffff80228548>] child_rip+0xa/0x12
> [ 11.863781] [<ffffffff81160140>] ? early_idt_handler+0x0/0x74
> [ 11.868757] [<ffffffff81160980>] ? kernel_init+0x0/0x300
> [ 11.874160] [<ffffffff8022853e>] ? child_rip+0x0/0x12
> [ 11.879989]
> [ 11.881141] general protection fault: 0000 [1] SMP
> [ 11.881141] CPU 1
>
> with this config:
>
> http://redhat.com/~mingo/misc/config-Wed_Jul_16_02_26_04_CEST_2008.bad
>
> today i had time to do a bisection run, and it came up with this commit:
>
> | 279e902445557897707d325182916a6e28ba80de is first bad commit
> | commit 279e902445557897707d325182916a6e28ba80de
> | Author: Jean Delvare <khali@linux-fr.org>
> | Date: Mon Jul 14 22:38:21 2008 +0200
> |
> | i2c-nforce2: Add support for multiplexing on the Tyan S4985
>
> the crash is reproducible and i can test any fix patch in short order.
> As a quick temporary hack i've reverted this patch for now via the patch
> below, to keep the tests going. (Can send more details about the
> test-system if needed.)
Probably the same problem as reported by John Stultz:
http://lkml.org/lkml/2008/7/15/720
I'll look into it once I am done with higher priority tasks (read:
baby's bath ;)).
> btw., Greg, the kobject debugging check and output is really nice,
> informative and useful! It likely pinpoints the real bug here.
Is this something new in 2.6.26-gitX? I want to know if the bug is
something new or if it could be already present in 2.6.26 and earlier
kernels and went unnoticed so far.
Thanks,
--
Jean Delvare
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux I2C <i2c@lm-sensors.org>,
LKML <linux-kernel@vger.kernel.org>,
Ben Dooks <ben-linux@fluff.org>, Greg KH <gregkh@suse.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [crash, bisected] I2C, kobject (ffff81003e8c4160): tried to init an initialized object (was: Re: [GIT PULL] i2c updates for 2.6.27, round 1)
Date: Wed, 16 Jul 2008 11:07:02 +0200 [thread overview]
Message-ID: <20080716110702.3ca61eb2@hyperion.delvare> (raw)
In-Reply-To: <20080716082352.GA30483@elte.hu>
Hi Ingo,
On Wed, 16 Jul 2008 10:23:52 +0200, Ingo Molnar wrote:
>
> hi Jean,
>
> * Jean Delvare <khali@linux-fr.org> wrote:
>
> > i2c-nforce2: Add support for multiplexing on the Tyan S4985
>
> -tip random boot testing started triggering the following upstream boot
> crash, starting two days ago when the i2c tree was merged:
>
> [ 11.772002] kobject (ffff81003e8c4160): tried to init an initialized object, something is seriously wrong.
> [ 11.784004] Pid: 1, comm: swapper Not tainted 2.6.26-00007-g279e902-dirty #19896
> [ 11.793651]
> [ 11.793651] Call Trace:
> [ 11.793651] [<ffffffff8054471a>] kobject_init+0x7a/0x80
> [ 11.798969] [<ffffffff805f0f9d>] device_initialize+0x2d/0xd0
> [ 11.806323] [<ffffffff805f19a1>] device_register+0x11/0x20
> [ 11.811903] [<ffffffff8087ee3b>] i2c_register_adapter+0xab/0x1d0
> [ 11.817666] [<ffffffff8087f0e6>] i2c_add_adapter+0x96/0xb0
> [ 11.823761] [<ffffffff81196372>] nforce2_s4985_init+0x272/0x370
> [ 11.829358] [<ffffffff8027516a>] ? getnstimeofday+0x3a/0xc0
> [ 11.835365] [<ffffffff802728ba>] ? ktime_get_ts+0x4a/0x60
> [ 11.840853] [<ffffffff81196100>] ? nforce2_s4985_init+0x0/0x370
> [ 11.846859] [<ffffffff81160aa3>] kernel_init+0x123/0x300
> [ 11.852261] [<ffffffff81160140>] ? early_idt_handler+0x0/0x74
> [ 11.857957] [<ffffffff80228548>] child_rip+0xa/0x12
> [ 11.863781] [<ffffffff81160140>] ? early_idt_handler+0x0/0x74
> [ 11.868757] [<ffffffff81160980>] ? kernel_init+0x0/0x300
> [ 11.874160] [<ffffffff8022853e>] ? child_rip+0x0/0x12
> [ 11.879989]
> [ 11.881141] general protection fault: 0000 [1] SMP
> [ 11.881141] CPU 1
>
> with this config:
>
> http://redhat.com/~mingo/misc/config-Wed_Jul_16_02_26_04_CEST_2008.bad
>
> today i had time to do a bisection run, and it came up with this commit:
>
> | 279e902445557897707d325182916a6e28ba80de is first bad commit
> | commit 279e902445557897707d325182916a6e28ba80de
> | Author: Jean Delvare <khali@linux-fr.org>
> | Date: Mon Jul 14 22:38:21 2008 +0200
> |
> | i2c-nforce2: Add support for multiplexing on the Tyan S4985
>
> the crash is reproducible and i can test any fix patch in short order.
> As a quick temporary hack i've reverted this patch for now via the patch
> below, to keep the tests going. (Can send more details about the
> test-system if needed.)
Probably the same problem as reported by John Stultz:
http://lkml.org/lkml/2008/7/15/720
I'll look into it once I am done with higher priority tasks (read:
baby's bath ;)).
> btw., Greg, the kobject debugging check and output is really nice,
> informative and useful! It likely pinpoints the real bug here.
Is this something new in 2.6.26-gitX? I want to know if the bug is
something new or if it could be already present in 2.6.26 and earlier
kernels and went unnoticed so far.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2008-07-16 9:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 20:49 [GIT PULL] i2c updates for 2.6.27, round 1 Jean Delvare
2008-07-14 20:49 ` Jean Delvare
2008-07-16 8:23 ` [crash, bisected] I2C, kobject (ffff81003e8c4160): tried to init an initialized object (was: Re: [GIT PULL] i2c updates for 2.6.27, round 1) Ingo Molnar
2008-07-16 9:07 ` Jean Delvare [this message]
2008-07-16 9:07 ` Jean Delvare
2008-07-16 10:08 ` [crash, bisected] I2C, kobject (ffff81003e8c4160): tried to init an initialized object Jean Delvare
2008-07-16 12:18 ` Jean Delvare
2008-07-17 9:26 ` Ingo Molnar
2008-07-17 9:33 ` Ingo Molnar
2008-07-17 9:48 ` Alexey Dobriyan
[not found] ` <20080717094858.GA18687-QDJVlCTZ4KWTKS93B3g+7KFoa47nwP16@public.gmane.org>
2008-07-17 9:59 ` Ingo Molnar
2008-07-17 9:59 ` Ingo Molnar
2008-08-06 20:21 ` Jean Delvare
2008-08-06 20:21 ` Jean Delvare
[not found] ` <20080717092655.GA6115-X9Un+BFzKDI@public.gmane.org>
2008-07-17 9:49 ` Ingo Molnar
2008-07-17 9:49 ` Ingo Molnar
2008-07-17 9:54 ` Ingo Molnar
2008-07-17 22:42 ` [crash, bisected] I2C, kobject (ffff81003e8c4160): tried to init an initialized object (was: Re: [GIT PULL] i2c updates for 2.6.27, round 1) Greg KH
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=20080716110702.3ca61eb2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=ben-linux@fluff.org \
--cc=gregkh@suse.de \
--cc=i2c@lm-sensors.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.