From: Jarod Wilson <jarod@redhat.com>
To: W R <gridmuncher@hotmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Fintek driver linux
Date: Tue, 14 Feb 2012 16:55:23 -0500 [thread overview]
Message-ID: <4F3AD84B.1030800@redhat.com> (raw)
In-Reply-To: <BLU145-W31DB93CC932394E4E288E2BD7C0@phx.gbl>
On 02/14/2012 04:25 PM, W R wrote:
> Thanks for your quick reply. It does seem like I have the old version:
>
> cat /proc/bus/input/devices
>
> *I: Bus=0019 Vendor=1934 Product=0004 Version=0008*
Hm, okay, so the changes for newer hardware shouldn't matter at all.
> N: Name="Fintek LPC SuperIO Consumer IR Transceiver"
> P: Phys=fintek/cir0
...
> Is there anything out of the ordinary? Any way to find out which modules
> that cause the problem and can maybe be removed?
Nothing out of the ordinary, no. You'd have to capture serial console
output or a vmcore from the time of the crash to really get a better
idea of where its falling down. The panic trace ought to give a clue
where to start looking.
I can't recall, have you tried using this under Windows, and if so, was
it stable there? A hardware fault is always a possibility, especially
when there's only a single report of something like this. Then again,
this is a fairly young driver. But I never saw anything like this in my
own testing during driver devel, nor did Fintek. :\
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2012-02-14 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU145-W35C32BF2C2E1EDFD8DC5F4BD800@phx.gbl>
[not found] ` <4F2822AE.1020705@redhat.com>
[not found] ` <BLU145-W31A99136480C1FBA4E0AC7BD770@phx.gbl>
[not found] ` <4F356866.6090208@redhat.com>
[not found] ` <BLU145-W1658A220E336DBC96C53D7BD7C0@phx.gbl>
2012-02-14 20:08 ` Fintek driver linux Jarod Wilson
[not found] ` <BLU145-W31DB93CC932394E4E288E2BD7C0@phx.gbl>
2012-02-14 21:55 ` Jarod Wilson [this message]
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=4F3AD84B.1030800@redhat.com \
--to=jarod@redhat.com \
--cc=gridmuncher@hotmail.com \
--cc=linux-media@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.