From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: "Paweł Sikora" <pluto-PIIpFW8S9c0@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LMML <linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.
Date: Tue, 29 Sep 2009 16:16:29 +0200 [thread overview]
Message-ID: <20090929161629.2a5c8d30@hyperion.delvare> (raw)
In-Reply-To: <200909161003.33090.pluto-PIIpFW8S9c0@public.gmane.org>
On Wed, 16 Sep 2009 10:03:32 +0200, Paweł Sikora wrote:
> On Wednesday 16 September 2009 08:57:01 Jean Delvare wrote:
> > Hi Pawel,
> >
> > I think this would be fixed by the following patch:
> > http://patchwork.kernel.org/patch/45707/
>
> still oopses. this time i've attached full dmesg.
Any news on this? Do you have a refined list of kernels which have the
bug and kernels which do not? Tried 2.6.32-rc1? Tried the v4l-dvb
repository?
Anyone else seeing this bug?
Your kernel stack trace doesn't look terribly reliable and I am not
able to come to any conclusion. The crash is supposed to happen in
ir_input_init(), but the stack trace doesn't lead there. I am also
skeptical about the +0x64/0x1a52, ir_input_init() is a rather small
function and I fail to see how it could be 6738 bytes in binary size.
Might be that the bug caused a stack corruption. Building a debug
kernel may help.
--
Jean Delvare
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
LMML <linux-media@vger.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.
Date: Tue, 29 Sep 2009 16:16:29 +0200 [thread overview]
Message-ID: <20090929161629.2a5c8d30@hyperion.delvare> (raw)
In-Reply-To: <200909161003.33090.pluto@agmk.net>
On Wed, 16 Sep 2009 10:03:32 +0200, Paweł Sikora wrote:
> On Wednesday 16 September 2009 08:57:01 Jean Delvare wrote:
> > Hi Pawel,
> >
> > I think this would be fixed by the following patch:
> > http://patchwork.kernel.org/patch/45707/
>
> still oopses. this time i've attached full dmesg.
Any news on this? Do you have a refined list of kernels which have the
bug and kernels which do not? Tried 2.6.32-rc1? Tried the v4l-dvb
repository?
Anyone else seeing this bug?
Your kernel stack trace doesn't look terribly reliable and I am not
able to come to any conclusion. The crash is supposed to happen in
ir_input_init(), but the stack trace doesn't lead there. I am also
skeptical about the +0x64/0x1a52, ir_input_init() is a rather small
function and I fail to see how it could be 6738 bytes in binary size.
Might be that the bug caused a stack corruption. Building a debug
kernel may help.
--
Jean Delvare
next prev parent reply other threads:[~2009-09-29 14:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 1:00 [2.6.31] ir-kbd-i2c oops Paweł Sikora
2009-09-16 1:00 ` Paweł Sikora
[not found] ` <200909160300.28382.pluto-PIIpFW8S9c0@public.gmane.org>
2009-09-16 6:57 ` Jean Delvare
2009-09-16 6:57 ` Jean Delvare
[not found] ` <20090916085701.6e883600-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-16 8:03 ` Paweł Sikora
2009-09-16 8:03 ` Paweł Sikora
[not found] ` <200909161003.33090.pluto-PIIpFW8S9c0@public.gmane.org>
2009-09-29 14:16 ` Jean Delvare [this message]
2009-09-29 14:16 ` Jean Delvare
[not found] ` <20090929161629.2a5c8d30-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-29 23:26 ` Hermann Pitton
2009-09-29 23:26 ` Hermann Pitton
2009-09-30 8:16 ` Paweł Sikora
2009-09-30 10:57 ` Jean Delvare
2009-09-30 11:52 ` Paweł Sikora
2009-09-30 12:25 ` Jean Delvare
2009-09-30 16:22 ` Paweł Sikora
2009-09-30 23:52 ` Andy Walls
2009-10-01 11:43 ` Jean Delvare
2009-10-03 10:08 ` Paweł Sikora
2009-10-03 12:04 ` Jean Delvare
2009-10-03 12:57 ` [PATCH 1/3] gspca_gl860 Olivier Lorin
2009-10-03 13:01 ` [PATCH 2/3] gspca_gl860 Olivier Lorin
2009-10-03 13:03 ` [PATCH 3/3] gspca_gl860 Olivier Lorin
[not found] ` <200910031730.45021.pluto@agmk.net>
2009-10-03 18:15 ` [2.6.31] ir-kbd-i2c oops Jean Delvare
2009-10-03 19:09 ` Paweł Sikora
2009-10-03 22:52 ` Hermann Pitton
2009-10-04 4:19 ` hermann pitton
2009-10-04 7:08 ` Paweł Sikora
2009-10-04 22:34 ` Hermann Pitton
2009-09-30 23:42 ` Andy Walls
2009-10-01 10:06 ` Jean Delvare
2009-10-01 10:17 ` Paweł Sikora
2009-10-01 10:42 ` Jean Delvare
2009-10-01 10:47 ` Paweł Sikora
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=20090929161629.2a5c8d30@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pluto-PIIpFW8S9c0@public.gmane.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.