From: Sean Young <sean@mess.org>
To: Martin Burnicki <martin.burnicki@burnicki.net>
Cc: Rolf Pedersen <rolfpedersen@mindspring.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Brad Love <brad@nextdimension.cc>
Subject: Re: HauppaugeTV-quadHD DVB-T mpeg risc op code error
Date: Thu, 30 Apr 2020 17:49:34 +0100 [thread overview]
Message-ID: <20200430164934.GA16730@gofer.mess.org> (raw)
In-Reply-To: <0fc5d43f-7928-1649-220b-45916b189d8f@burnicki.net>
On Tue, Apr 28, 2020 at 08:24:20PM +0200, Martin Burnicki wrote:
> Hi,
>
> Am 27.04.20 um 10:59 schrieb Martin Burnicki:
> > Sean Young wrote:
> >> Would you mind testing this patch please?
> >
> > I'm going to try it this evening.
> >
> > I'll have to find out how to do an out-of-tree build for a copy of the
> > cx module that includes the patch.
> >
> > My own kernel driver is always and only built out-of-tree, but for the
> > cx driver I need to see which files I need to copy to a local directory,
> > and if there is anything else that needs to be done to build a copy of
> > it out-of-tree.
>
> Sorry, I haven't managed to test the patch, yet.
>
> Currently I have the driver loaded with
>
> options cx23885 dma_reset_workaround=2
>
> but today there were 3 occurrences of the risc opcode error:
>
> root@pc:~# dmesg | grep risc
> [166528.023263] cx23885: cx23885[0]: mpeg risc op code error
> [166528.023273] cx23885: cx23885[0]: cmds: init risc lo : 0xff667000
> [166528.023277] cx23885: cx23885[0]: cmds: init risc hi : 0x00000000
> [166528.023293] cx23885: cx23885[0]: cmds: risc pc lo : 0xff667018
> [166528.023296] cx23885: cx23885[0]: cmds: risc pc hi : 0x00000000
> [166528.023319] cx23885: cx23885[0]: risc0:
> [166528.023324] cx23885: cx23885[0]: risc1:
> [166528.023330] cx23885: cx23885[0]: risc2:
> [166528.023334] cx23885: cx23885[0]: risc3:
> [180595.947077] cx23885: cx23885[0]: mpeg risc op code error
> [180595.947087] cx23885: cx23885[0]: cmds: init risc lo : 0xfc6ee000
> [180595.947090] cx23885: cx23885[0]: cmds: init risc hi : 0x00000000
> [180595.947107] cx23885: cx23885[0]: cmds: risc pc lo : 0xfc6ee018
> [180595.947110] cx23885: cx23885[0]: cmds: risc pc hi : 0x00000000
> [180595.947133] cx23885: cx23885[0]: risc0:
> [180595.947138] cx23885: cx23885[0]: risc1:
> [180595.947143] cx23885: cx23885[0]: risc2:
> [180595.947147] cx23885: cx23885[0]: risc3:
> [180595.947263] cx23885: cx23885[0]: mpeg risc op code error
> [180595.947270] cx23885: cx23885[0]: cmds: init risc lo : 0xfc6ee000
> [180595.947274] cx23885: cx23885[0]: cmds: init risc hi : 0x00000000
> [180595.947290] cx23885: cx23885[0]: cmds: risc pc lo : 0xfc6ee018
> [180595.947293] cx23885: cx23885[0]: cmds: risc pc hi : 0x00000000
> [180595.947315] cx23885: cx23885[0]: risc0:
> [180595.947319] cx23885: cx23885[0]: risc1:
> [180595.947324] cx23885: cx23885[0]: risc2:
> [180595.947328] cx23885: cx23885[0]: risc3:
>
> My wife is very happy that the recordings of the TV shows she wanted to
> see later were aborted. ;-)
Drats.
> So the workaround doesn't seem to fix the problem anyway, and the patch
> would just enable the workaround with out the specific option, right?
Yes, that's right.
> The effect of the workaround looks just like debug levels lower than 7,
> it just seems to reduce the probability that the bug occurs, but doesn't
> really fix it.
>
> So my conclusion is still that that this smells like a missing memory
> barrier or so in the driver.
>
> Since the driver seems to work properly with older mainboards/CPU types,
> this doesn't sound like a problem in the CX chip, IMO.
I would agree with that. I would suspect same issue was being papered over
by the patch; now what that issue is, I don't know. Certainly some ordering
or barrier issue seems likely.
Actually I suspected this all along, but the workaround is the best we have.
I think, some time spent hunting down the issue would really be helpful
here. Hopefully that doesn't mean too many aborted recordings..
Thanks,
Sean
next prev parent reply other threads:[~2020-04-30 16:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 12:32 HauppaugeTV-quadHD DVB-T mpeg risc op code error Rolf Pedersen
2020-04-23 15:35 ` Sean Young
2020-04-23 15:49 ` Rolf Pedersen
2020-04-23 15:59 ` Sean Young
2020-04-23 16:09 ` Rolf Pedersen
2020-04-23 16:35 ` Sean Young
2020-04-24 17:46 ` Martin Burnicki
2020-04-25 11:41 ` Sean Young
2020-04-25 14:06 ` Martin Burnicki
2020-04-27 7:03 ` Martin Burnicki
2020-04-27 8:07 ` Sean Young
2020-04-27 8:59 ` Martin Burnicki
2020-04-28 18:24 ` Martin Burnicki
2020-04-30 16:49 ` Sean Young [this message]
2022-05-23 22:36 ` HauppaugeTV-quadHD DVB-T & HVR5525 " Ken Smith
2022-05-24 7:51 ` Martin Burnicki
2022-05-26 17:06 ` Ken Smith
2022-06-06 13:59 ` Ken Smith
2022-06-30 9:59 ` Ken Smith
2022-05-24 8:36 ` Ken Smith
2022-05-26 9:52 ` Ken Smith
2022-05-26 11:33 ` Ken Smith
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=20200430164934.GA16730@gofer.mess.org \
--to=sean@mess.org \
--cc=brad@nextdimension.cc \
--cc=linux-media@vger.kernel.org \
--cc=martin.burnicki@burnicki.net \
--cc=rolfpedersen@mindspring.com \
/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.