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: Wed, 16 Sep 2009 08:57:01 +0200 [thread overview]
Message-ID: <20090916085701.6e883600@hyperion.delvare> (raw)
In-Reply-To: <200909160300.28382.pluto-PIIpFW8S9c0@public.gmane.org>
Hi Pawel,
On Wed, 16 Sep 2009 03:00:28 +0200, Paweł Sikora wrote:
> the latest 2.6.31 kernel oopses in ir-kbd-i2c on my box:
> afaics the 2.6.28.10 is also affected.
>
> http://imgbin.org/index.php?page=image&id=776
> http://imgbin.org/index.php?page=image&id=777
> http://imgbin.org/index.php?page=image&id=778
>
> installed pinnacle tv card with infra-red receiver:
>
> 05:00.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135
> Video Broadcast Decoder (rev d1)
> Subsystem: Pinnacle Systems Inc. PCTV 110i (saa7133)
> Kernel driver in use: saa7134
> Kernel modules: saa7134
>
> if you need i'll provide more information.
> please, CC me on reply.
This would have best been posted to linux-media... Cc'd.
I think this would be fixed by the following patch:
http://patchwork.kernel.org/patch/45707/
Can you please give it a try?
If I am correct then only kernel 2.6.31 would be affected, 2.6.30
wouldn't be.
--
Jean Delvare
next prev parent reply other threads:[~2009-09-16 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 1:00 [2.6.31] ir-kbd-i2c oops Paweł Sikora
[not found] ` <200909160300.28382.pluto-PIIpFW8S9c0@public.gmane.org>
2009-09-16 6:57 ` Jean Delvare [this message]
[not found] ` <20090916085701.6e883600-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-16 8:03 ` Paweł Sikora
[not found] ` <200909161003.33090.pluto-PIIpFW8S9c0@public.gmane.org>
2009-09-29 14:16 ` Jean Delvare
[not found] ` <20090929161629.2a5c8d30-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-29 23:26 ` Hermann Pitton
2009-09-30 8:16 ` 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=20090916085701.6e883600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).