From: Sebastian Steinhuber <sebastian.steinhuber@googlemail.com>
To: unlisted-recipients:; (no To-header on input)@canuck.infradead.org
Cc: linux-media@vger.kernel.org
Subject: Re: Regression with kernel 3.1 and bt87x?
Date: Sun, 20 Nov 2011 22:44:34 +0100 [thread overview]
Message-ID: <4EC974C2.1040500@gmail.com> (raw)
In-Reply-To: <ja3cpe$6qm$1@dough.gmane.org>
Am 17.11.2011 17:29, schrieb Sebastian Steinhuber:
> Hi all,
>
> I've got a Hauppauge WinTV pci board that used to be working until
> kernel 3.1 was used; I tried 3.1.1, too, without luck. 3.0.7 is working,
> with the same config as the 3.1s regarding the media parts.
>
> I'm compiling my customized kernel from vanilla sources and a
> linux-vserver patch, and I also tested the 3.1.0-1-amd64 from debian
> stock with very result.
>
>
> On starting up Zapping, I got these messages:
> 'Unable to open /dev/video0.'
> 'The device cannot be attached to any controller.'
> Tvtime simply complained about 'No signal'.
>
> I couldn't find further messages or any errors in syslog nor in
> messages, so I'm feeling there might be a bug somewhere.
>
>
> The same modules are loaded into the kernel with 3.0.7 (working, with
> the same config as the 3.1s regarding the media parts), 3.1 and also 3.1.1:
> bttv
> btcx_risc
> rc_core
> tuner
> tuner_simple
> tuner_types
> videobuf_dma_sg
> videobuf_core
> tveeprom
>
>
> $lspci -vv
> …
> 05:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video
> Capture (rev 02)
> Subsystem: Hauppauge computer works Inc. WinTV Series
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 64 (4000ns min, 10000ns max)
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at d0001000 (32-bit, prefetchable) [size=4K]
> Kernel driver in use: bttv
>
> 05:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
> (rev 02)
> Subsystem: Hauppauge computer works Inc. WinTV Series
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 64 (1000ns min, 63750ns max)
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at d0000000 (32-bit, prefetchable) [size=4K]
> Kernel driver in use: Bt87x
Update: There are no issues with 3.0.9.
If someone has an idea which commit could cause the problem, I would
like to check it out. I have cloned the stable kernel repository and
despite of being new to git, I can test every commit with the hardware.
Thanks in advance,
Sebastian
prev parent reply other threads:[~2011-11-20 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 16:29 Regression with kernel 3.1 and bt87x? Sebastian Steinhuber
2011-11-20 21:44 ` Sebastian Steinhuber [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=4EC974C2.1040500@gmail.com \
--to=sebastian.steinhuber@googlemail.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.