From: Johannes Stezenbach <js@linuxtv.org>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
linux-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org
Cc: Patrick Boettcher <pb@linuxtv.org>
Subject: Re: [linux-dvb-maintainer] Multiple USB DVB devices cause hard lockups
Date: Sun, 20 Nov 2005 03:17:19 +0100 [thread overview]
Message-ID: <20051120021719.GC8157@linuxtv.org> (raw)
In-Reply-To: <20051109135925.GF12751@localhost.localdomain>
On Wed, Nov 09, 2005 Hugo Mills wrote:
> I'm trying to get a pair of Twinhan Alpha II DVB-USB devices
> working on the same machine. With a single device plugged in, I can
> quite easily receive and stream data.
>
> With both devices connected to the machine, both are recognised.
> However, use of either device causes some form of stack backtrace (I
> can't see the top of it to verify what kind) from the kernel, and a
> hard lock-up. Magic SysRQ is non-functional after the lock-up. Failure
> cases that I've seen are:
Maybe Patrick can comment, I believe he tested with multiple
USB devices.
I can't do much with this report without the kernel messages :-(
Johannes
> - Streaming from device 0 is OK for a few seconds, and then the
> system locks hard.
>
> - Streaming from device 0 is OK. Streaming from device 1 before
> device 0 crashes locks the device 1 process in D state, and then
> locks the system hard a few seconds later.
>
> I've observed this behaviour on both 2.6.12.2 and 2.6.14. No logs
> were left from the crashes, and only incomplete information on screen,
> so I presume that I'll need to get a serial console set up to capture
> output. A log of the devices being identified on boot-up is attached
> below, for what it's worth (probably not much).
>
> Hugo.
>
> Nov 9 11:49:48 src@vlad kernel: ehci_hcd 0000:00:0c.2: EHCI Host Controller
> Nov 9 11:49:48 src@vlad kernel: ehci_hcd 0000:00:0c.2: new USB bus registered, assigned bus number 1
> Nov 9 11:49:48 src@vlad kernel: ehci_hcd 0000:00:0c.2: irq 12, io mem 0xd4000000
> Nov 9 11:49:48 src@vlad kernel: ehci_hcd 0000:00:0c.2: park 0
> Nov 9 11:49:48 src@vlad kernel: ehci_hcd 0000:00:0c.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
> Nov 9 11:49:48 src@vlad kernel: hub 1-0:1.0: USB hub found
> Nov 9 11:49:48 src@vlad kernel: hub 1-0:1.0: 5 ports detected
> Nov 9 11:49:48 src@vlad kernel: usb 1-2: new high speed USB device using ehci_hcd and address 2
> Nov 9 11:49:48 src@vlad kernel: usb 1-3: new high speed USB device using ehci_hcd and address 3
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: found a 'Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)' in warm state.
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> Nov 9 11:49:48 src@vlad kernel: DVB: registering new adapter (Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)).
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: MAC address: 08:ff:ff:ff:ff:ff
> Nov 9 11:49:48 src@vlad kernel: DVB: registering frontend 0 (Twinhan VP7045/46 USB DVB-T)...
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: schedule remote query interval to 400 msecs.
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II) successfully initialized and connected.
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: found a 'Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)' in warm state.
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> Nov 9 11:49:48 src@vlad kernel: DVB: registering new adapter (Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)).
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: MAC address: 08:ff:ff:ff:ff:ff
> Nov 9 11:49:48 src@vlad kernel: DVB: registering frontend 1 (Twinhan VP7045/46 USB DVB-T)...
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: schedule remote query interval to 400 msecs.
> Nov 9 11:49:48 src@vlad kernel: dvb-usb: Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II) successfully initialized and connected.
> Nov 9 11:49:48 src@vlad kernel: usbcore: registered new driver dvb_usb_vp7045
> Nov 9 11:49:48 src@vlad kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
>
> --
> === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
> PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
> --- "Your problem is that you have a negative personality." ---
> "No, I don't!"
> _______________________________________________
> linux-dvb-maintainer mailing list
> linux-dvb-maintainer@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb-maintainer
next prev parent reply other threads:[~2005-11-20 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 13:59 Hugo Mills
2005-11-09 14:33 ` [linux-dvb-maintainer] " hunold
2005-11-20 2:17 ` Johannes Stezenbach [this message]
2005-11-21 8:52 ` Patrick Boettcher
2005-11-21 15:10 ` Hugo Mills
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=20051120021719.GC8157@linuxtv.org \
--to=js@linuxtv.org \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pb@linuxtv.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
Powered by JetHome