Loading ...
Sorry, an error occurred while loading the content.
 

Re: Call with twinkle freeze my Linux box.

Expand Messages
  • Christof Meerwald
    ... I am seeing pretty much the same since I have upgraded to Ubuntu 12.10 (Linux kernel 3.5.0-18-generic). There is no pulseaudio on my system and it only
    Message 1 of 14 , Nov 1, 2012
      On Fri, 26 Oct 2012 13:37:08 -0000, fakjujahuu wrote:
      > My suspicion is, that problem is in USB audio, not in Twinkle, but I haven't started with Alsa debugging yet.
      >
      > Can anybody confirm the problem or I am the only one?

      I am seeing pretty much the same since I have upgraded to Ubuntu 12.10
      (Linux kernel 3.5.0-18-generic). There is no pulseaudio on my system
      and it only freezes if the USB headset is connected via a USB hub (it
      doesn't freeze if I connect it directly to one of the USB ports). BTW,
      none of the magic SysRq keys works in that state any more.


      Christof

      --

      http://cmeerw.org sip:cmeerw at cmeerw.org
      mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
    • Christof Meerwald
      ... Did a bit more testing/debugging on this now. The test code in http://pastebin.com/aHGe1S1X completely freezes my Linux box when I am passing plughw:Set
      Message 2 of 14 , Nov 2, 2012
        On Thu, 1 Nov 2012 08:25:59 +0100, Christof Meerwald wrote:
        > I am seeing pretty much the same since I have upgraded to Ubuntu 12.10
        > (Linux kernel 3.5.0-18-generic). There is no pulseaudio on my system
        > and it only freezes if the USB headset is connected via a USB hub (it
        > doesn't freeze if I connect it directly to one of the USB ports). BTW,
        > none of the magic SysRq keys works in that state any more.

        Did a bit more testing/debugging on this now. The test code in
        http://pastebin.com/aHGe1S1X completely freezes my Linux box when I am
        passing plughw:Set (which is a USB headset connected via a USB hub),
        but it's fine when passing plughw:SB (which is the internal sound
        device).

        Anyone else seeing a freeze with that test case?


        Christof

        --

        http://cmeerw.org sip:cmeerw at cmeerw.org
        mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
      • Ďoďo
        BTW, I just realized that I have no pulseautio on my system. I have to get USB hub to test if it is then O.K. .... On Mon, Oct 29, 2012 at 12:32 AM, David
        Message 3 of 14 , Nov 4, 2012
          BTW, I just realized that I have no pulseautio on my system.
          I have to get USB hub to test if it is then O.K. ....

          On Mon, Oct 29, 2012 at 12:32 AM, David Benfell
          <benfell@...> wrote:
          > -----BEGIN PGP SIGNED MESSAGE-----
          > Hash: SHA1
          >
          > On 10/28/2012 05:44 AM, joerg wrote:
          >
          >>
          >> Your options: use different audio hw that's better supported by
          >> PA. open a ticket against PA and hope for Lennart to fix his
          >> stuff. wipe PA off your system and revert to proper plain vanilla
          >> ALSA, which never caused any problems after initial configuration
          >> phase which isn't always as simple as "click install in that
          >> requester".
          >>
          >> Sorry you became another victim of the PA abomination, but there's
          >> just so much twinkle could do about it.
          >>
          > I doubt anyone has an adequate count on the number of flame wars that
          > have arisen over PulseAudio. The administrator(s) of the Arch Linux
          > list recently had to clamp down hard due to a flame war that seemed
          > like it would never end over systemd (another of Lennart Poettering's
          > projects) that had arisen in part because of people's experience with
          > PulseAudio. (For the record, I actually like systemd, though I did get
          > into a quandary with my desktop system that forced me to abandon it,
          > and Arch Linux on it, because Arch is moving rapidly in that direction.)
          >
          > In my experience, the only distribution I have not had to wipe
          > PulseAudio off my system with is Linux Mint. There are many
          > distributions I haven't tried; perhaps there are others. But before I
          > tried Mint, it had gotten to the point where I would discover sound
          > wasn't working, and wiping PulseAudio would be my first, and very
          > often only necessary response.
          >
          > There are apparently also some technical issues that audiophiles have
          > with PulseAudio; these got aired on the Arch Linux list just as the
          > flame war really started heating up, and I honestly wish I knew more
          > about the topic, because it looked interesting, and if these posters
          > were correct, it seems that PulseAudio is fundamentally flawed from an
          > audiophile perspective. As it is, all I can recall, is that it had
          > something to do with mixing--and people who had run soundboards
          > professionally were chiming in.
          >
          > So I'm inclined to agree that a first response would be to remove
          > pulseaudio. ALSA runs just fine--actually better--without it.
          >
          > - --
          > David Benfell
          > benfell@...
          > -----BEGIN PGP SIGNATURE-----
          > Version: GnuPG v1.4.12 (GNU/Linux)
          > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
          >
          > iQIcBAEBAgAGBQJQjcChAAoJEP0r2H01qrjgjWIP/j65YepfvawVoB+oHf8zwGZW
          > IhmLI0lVMwOsKMjVF3iQYLtcPJVFC2YBWX2Vb5XcpI/eSGgISsjP3B/tgJR1VqOF
          > wdodba9kbYBOiS9bfXQ0cbbnWteZCXpeYNAsgqqQNyg0qV5XTrReMlDGpGaiAUP0
          > G3Sxq78GjR/A1a+uo3TaVp0FwAkkWZkWFpsHNZMhiyWivVx8ZiAIivCRQcQdKF23
          > eR+MuHKpX2ikeYaFrz0Dfac2BrtA7kAH8/06I4LMTFgdiNTku1mFkQIOcVPnkPZN
          > F1gwdY90lwtUJvSZWX/O7IO+qLxcIxE4VQV14KmLcu2J/+YG85NBVEOX+wUeB5Mj
          > wfW95VKPfs6kqoIRhA+2Ez4zHCgR0U+aDt7AcwUHG4Zs22m5JRlSXK413L9d66Wo
          > B/OiUEqhGZ/dCb18PfZrod4z42LXoXG6cVETammHmtBJzk2FEq78umaKFvBMwJEX
          > DX3N3X7Gn7o+RjYQaRzOwcxNvybTSvH1xji6dd9xDwRlSWf11g90+M7nsnBp7Jyu
          > mGneFNe7s9iTmeAz2mhXfRtqjGCUevDOq3Ml5K0xxu/DC4lyWWaKZDh9SOrqn9Ya
          > DcDXJEUCiNbs/JHljqhxdmwPNDNdYmCrKyxRDji192RdnmqnA9ZMylGOrYkXN/IN
          > NyZJLBKEiRisS9T+avEK
          > =EY/4
          > -----END PGP SIGNATURE-----
          >
          >
          > ------------------------------------
          >
          > Yahoo! Groups Links
          >
          >
          >
        • Christof Meerwald
          ... Does that mean your USB headset is currently directly connected to the PC (not via a USB hub)? Because on my machine I only see a freeze if I connect the
          Message 4 of 14 , Nov 4, 2012
            On Sun, 4 Nov 2012 21:58:48 +0100, Ďoďo wrote:
            > BTW, I just realized that I have no pulseautio on my system.
            > I have to get USB hub to test if it is then O.K. ....

            Does that mean your USB headset is currently directly connected to the
            PC (not via a USB hub)?

            Because on my machine I only see a freeze if I connect the headset via
            a USB 2.0 hub, but it's fine if I use a USB 1.1 hub or connect it
            directly to one of the USB ports.

            BTW, could you post the output of "lsusb -t"? This is how it looks on
            my machine:

            /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
            |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 12M
            |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
            |__ Port 4: Dev 5, If 0, Class=vend., Driver=option, 12M
            |__ Port 4: Dev 5, If 1, Class=vend., Driver=cdc_wdm, 12M
            |__ Port 4: Dev 5, If 2, Class=vend., Driver=qmi_wwan, 12M
            |__ Port 4: Dev 5, If 3, Class=vend., Driver=option, 12M
            |__ Port 4: Dev 5, If 4, Class=vend., Driver=option, 12M
            |__ Port 4: Dev 5, If 5, Class=stor., Driver=usb-storage, 12M
            |__ Port 4: Dev 5, If 6, Class=stor., Driver=usb-storage, 12M
            /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
            /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
            /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
            /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
            |__ Port 2: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 4, If 0, Class=audio, Driver=snd-usb-audio, 12M
            |__ Port 1: Dev 4, If 1, Class=audio, Driver=snd-usb-audio, 12M
            |__ Port 1: Dev 4, If 2, Class=HID, Driver=usbhid, 12M
            |__ Port 2: Dev 5, If 0, Class=stor., Driver=usb-storage, 480M
            |__ Port 3: Dev 7, If 0, Class=audio, Driver=snd-usb-audio, 12M
            |__ Port 3: Dev 7, If 1, Class=audio, Driver=snd-usb-audio, 12M
            |__ Port 3: Dev 7, If 2, Class=audio, Driver=snd-usb-audio, 12M
            |__ Port 3: Dev 7, If 3, Class=HID, Driver=usbhid, 12M
            |__ Port 4: Dev 8, If 0, Class=stor., Driver=usb-storage, 480M
            |__ Port 4: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
            |__ Port 4: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M


            Christof

            --

            http://cmeerw.org sip:cmeerw at cmeerw.org
            mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
          • Ďoďo
            You are right, internal hub is involved: Bus# 2 `-Dev# 1 Vendor 0x1d6b Product 0x0002 `-Dev# 2 Vendor 0x8087 Product 0x0024 `-Dev# 52 Vendor 0x1395
            Message 5 of 14 , Nov 5, 2012
              You are right, internal hub is involved:

              Bus# 2
              `-Dev# 1 Vendor 0x1d6b Product 0x0002
              `-Dev# 2 Vendor 0x8087 Product 0x0024
              `-Dev# 52 Vendor 0x1395 Product 0x3554
              Bus# 1
              `-Dev# 1 Vendor 0x1d6b Product 0x0002
              `-Dev# 2 Vendor 0x8087 Product 0x0024
              |-Dev# 12 Vendor 0x0a5c Product 0x217f
              `-Dev# 3 Vendor 0x04f2 Product 0xb217

              My headset is 1395:3553


              On Mon, Nov 5, 2012 at 8:18 AM, Christof Meerwald <cmeerw@...> wrote:
              > On Sun, 4 Nov 2012 21:58:48 +0100, Ďoďo wrote:
              >> BTW, I just realized that I have no pulseautio on my system.
              >> I have to get USB hub to test if it is then O.K. ....
              >
              > Does that mean your USB headset is currently directly connected to the
              > PC (not via a USB hub)?
              >
              > Because on my machine I only see a freeze if I connect the headset via
              > a USB 2.0 hub, but it's fine if I use a USB 1.1 hub or connect it
              > directly to one of the USB ports.
              >
              > BTW, could you post the output of "lsusb -t"? This is how it looks on
              > my machine:
              >
              > /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
              > |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 12M
              > |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
              > |__ Port 4: Dev 5, If 0, Class=vend., Driver=option, 12M
              > |__ Port 4: Dev 5, If 1, Class=vend., Driver=cdc_wdm, 12M
              > |__ Port 4: Dev 5, If 2, Class=vend., Driver=qmi_wwan, 12M
              > |__ Port 4: Dev 5, If 3, Class=vend., Driver=option, 12M
              > |__ Port 4: Dev 5, If 4, Class=vend., Driver=option, 12M
              > |__ Port 4: Dev 5, If 5, Class=stor., Driver=usb-storage, 12M
              > |__ Port 4: Dev 5, If 6, Class=stor., Driver=usb-storage, 12M
              > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
              > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
              > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
              > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
              > |__ Port 2: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
              > |__ Port 1: Dev 4, If 0, Class=audio, Driver=snd-usb-audio, 12M
              > |__ Port 1: Dev 4, If 1, Class=audio, Driver=snd-usb-audio, 12M
              > |__ Port 1: Dev 4, If 2, Class=HID, Driver=usbhid, 12M
              > |__ Port 2: Dev 5, If 0, Class=stor., Driver=usb-storage, 480M
              > |__ Port 3: Dev 7, If 0, Class=audio, Driver=snd-usb-audio, 12M
              > |__ Port 3: Dev 7, If 1, Class=audio, Driver=snd-usb-audio, 12M
              > |__ Port 3: Dev 7, If 2, Class=audio, Driver=snd-usb-audio, 12M
              > |__ Port 3: Dev 7, If 3, Class=HID, Driver=usbhid, 12M
              > |__ Port 4: Dev 8, If 0, Class=stor., Driver=usb-storage, 480M
              > |__ Port 4: Dev 3, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
              > |__ Port 4: Dev 3, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
              >
              >
              > Christof
              >
              > --
              >
              > http://cmeerw.org sip:cmeerw at cmeerw.org
              > mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
              >
              >
              > ------------------------------------
              >
              > Yahoo! Groups Links
              >
              >
              >
            • Christof Meerwald
              ... There are now kernel patches available for this problem from the linux-usb developers: http://permalink.gmane.org/gmane.linux.kernel/1390310
              Message 6 of 14 , Nov 7, 2012
                On Mon, 5 Nov 2012 10:30:12 +0100, Ďoďo wrote:
                > You are right, internal hub is involved:

                There are now kernel patches available for this problem from the
                linux-usb developers:

                http://permalink.gmane.org/gmane.linux.kernel/1390310
                http://permalink.gmane.org/gmane.linux.kernel/1390332


                Christof

                --

                http://cmeerw.org sip:cmeerw at cmeerw.org
                mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
              • fakjujahuu
                It does not help. With 3.6.6 kernel it is still the same.
                Message 7 of 14 , Nov 15, 2012
                  It does not help. With 3.6.6 kernel it is still the same.

                  --- In twinklephone@yahoogroups.com, Christof Meerwald <cmeerw@...> wrote:
                  >
                  > On Mon, 5 Nov 2012 10:30:12 +0100, Ďoďo wrote:
                  > > You are right, internal hub is involved:
                  >
                  > There are now kernel patches available for this problem from the
                  > linux-usb developers:
                  >
                  > http://permalink.gmane.org/gmane.linux.kernel/1390310
                  > http://permalink.gmane.org/gmane.linux.kernel/1390332
                  >
                  >
                  > Christof
                  >
                  > --
                  >
                  > http://cmeerw.org sip:cmeerw at cmeerw.org
                  > mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
                  >
                • Christof Meerwald
                  ... Did you apply any patches to 3.6.6 as the fix isn t included in 3.6.6 - it should be included in 3.7-rc5 and will hopefully also make it into future 3.6
                  Message 8 of 14 , Nov 16, 2012
                    On Thu, 15 Nov 2012 12:30:17 -0000, fakjujahuu wrote:
                    > It does not help. With 3.6.6 kernel it is still the same.

                    Did you apply any patches to 3.6.6 as the fix isn't included in 3.6.6
                    - it should be included in 3.7-rc5 and will hopefully also make it
                    into future 3.6 point releases.


                    > --- In twinklephone-hHKSG33TihhbjbujkaE4pw@..., Christof Meerwald <cmeerw@...> wrote:
                    >> There are now kernel patches available for this problem from the
                    >> linux-usb developers:
                    >>
                    >> http://permalink.gmane.org/gmane.linux.kernel/1390310
                    >> http://permalink.gmane.org/gmane.linux.kernel/1390332


                    Christof

                    --

                    http://cmeerw.org sip:cmeerw at cmeerw.org
                    mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org
                  • Ďoďo
                    No, I did not, but 3.7. is already O.K.
                    Message 9 of 14 , Dec 12, 2012
                      No, I did not, but 3.7. is already O.K.


                      On Fri, Nov 16, 2012 at 9:49 PM, Christof Meerwald <cmeerw@...> wrote:
                      On Thu, 15 Nov 2012 12:30:17 -0000, fakjujahuu wrote:
                      > It does not help. With 3.6.6 kernel it is still the same.

                      Did you apply any patches to 3.6.6 as the fix isn't included in 3.6.6
                      - it should be included in 3.7-rc5 and will hopefully also make it
                      into future 3.6 point releases.


                      > --- In twinklephone-hHKSG33TihhbjbujkaE4pw@..., Christof Meerwald <cmeerw@...> wrote:
                      >> There are now kernel patches available for this problem from the
                      >> linux-usb developers:
                      >>
                      >> http://permalink.gmane.org/gmane.linux.kernel/1390310
                      >> http://permalink.gmane.org/gmane.linux.kernel/1390332


                      Christof

                      --

                      http://cmeerw.org                              sip:cmeerw at cmeerw.org
                      mailto:cmeerw at cmeerw.org                   xmpp:cmeerw at cmeerw.org


                      ------------------------------------

                      Yahoo! Groups Links

                      <*> To visit your group on the web, go to:
                          http://groups.yahoo.com/group/twinklephone/

                      <*> Your email settings:
                          Individual Email | Traditional

                      <*> To change settings online go to:
                          http://groups.yahoo.com/group/twinklephone/join
                          (Yahoo! ID required)

                      <*> To change settings via email:
                          twinklephone-digest@yahoogroups.com
                          twinklephone-fullfeatured@yahoogroups.com

                      <*> To unsubscribe from this group, send an email to:
                          twinklephone-unsubscribe@yahoogroups.com

                      <*> Your use of Yahoo! Groups is subject to:
                          http://docs.yahoo.com/info/terms/


                    Your message has been successfully submitted and would be delivered to recipients shortly.