All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Raimonds Cicans <ray@apollo.lv>, hans.verkuil@cisco.com
Cc: linux-media@vger.kernel.org
Subject: Re: [REGRESSION] media: cx23885 broken by commit 453afdd "[media] cx23885: convert to vb2"
Date: Thu, 29 Jan 2015 08:33:12 +0100	[thread overview]
Message-ID: <54C9E238.9090101@xs4all.nl> (raw)
In-Reply-To: <54B24370.6010004@apollo.lv>

Hi Raimonds,

On 01/11/2015 10:33 AM, Raimonds Cicans wrote:
> Hello.
> 
> I contacted you because I am hit by regression caused by your commit:
> 453afdd "[media] cx23885: convert to vb2"
> 
> 
> My system:
> AMD Athlon(tm) II X2 240e Processor on Asus M5A97 LE R2.0 motherboard
> TBS6981 card (Dual DVB-S/S2 PCIe receiver, cx23885 in kernel driver)
> 
> After upgrade from kernel 3.13.10 (do not have commit) to 3.17.7
> (have commit) I started receiving following IOMMU related messages:
> 
> 1)
> AMD-Vi: Event logged [IO_PAGE_FAULT device=0a:00.0 domain=0x001d 
> address=0x000000000637c000 flags=0x0000]
> 
> where device=0a:00.0 is TBS6981 card

As far as I can tell this has nothing to do with the cx23885 driver but is
a bug in the amd iommu/BIOS. See e.g.:

https://bbs.archlinux.org/viewtopic.php?pid=1309055

I managed to reproduce the Intel equivalent if I enable CONFIG_IOMMU_SUPPORT.

Most likely due to broken BIOS/ACPI/whatever information that's read by the
kernel. I would recommend disabling this kernel option.

Regards,

	Hans

> 
> sometimes this message was followed by storm of following messages:
> cx23885[0]: mpeg risc op code error
> ...


  parent reply	other threads:[~2015-01-29  7:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11  9:33 [REGRESSION] media: cx23885 broken by commit 453afdd "[media] cx23885: convert to vb2" Raimonds Cicans
2015-01-12 10:55 ` Hans Verkuil
2015-01-12 15:27   ` Raimonds Cicans
2015-01-13 16:07     ` Antti Palosaari
2015-01-29  7:33 ` Hans Verkuil [this message]
2015-01-29 11:51   ` Raimonds Cicans
2015-01-29 12:12     ` Hans Verkuil
2015-02-01 13:06       ` Raimonds Cicans
2015-02-02  9:36         ` Hans Verkuil
2015-02-02 14:43           ` Jurgen Kramer
2015-02-04 16:06           ` Jurgen Kramer
2015-02-04 16:19             ` Hans Verkuil
2015-02-04 17:21               ` Jurgen Kramer
2015-02-13  9:12                 ` Hans Verkuil
2015-02-13  9:24                   ` Hans Verkuil
2015-02-13 16:29                     ` Jurgen Kramer
2015-02-15  7:53                     ` Jurgen Kramer
2015-02-15 10:28                     ` Raimonds Cicans
2015-02-13 16:14                   ` Jurgen Kramer
2015-02-13 16:42                     ` Hans Verkuil
2015-02-13 17:20                       ` Jurgen Kramer
2015-02-04 19:53               ` Raimonds Cicans
2015-02-06 16:02                 ` Raimonds Cicans

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=54C9E238.9090101@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ray@apollo.lv \
    /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.