linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Langlois <olivier@trillion01.com>
To: James Cameron <quozl@laptop.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ISSUE] rtl8192ce appears to interfere with ALSA playback
Date: Mon, 27 Jan 2014 02:08:32 -0500	[thread overview]
Message-ID: <1390806512.2436.180.camel@Wailaba2> (raw)
In-Reply-To: <20140127065412.GA25313@us.netrek.org>

On Mon, 2014-01-27 at 17:54 +1100, James Cameron wrote:
> On Mon, Jan 27, 2014 at 01:32:03AM -0500, Olivier Langlois wrote:
> > Here is the sequence of events that I have traced that seem to cause my
> > audio playback underrun.
> > 
> > 1. wpa_supplicant send a start_scan request to the nl80211 driver
> > 2. mac80211 module call rtl_op_config with IEEE80211_CONF_CHANGE_IDLE
> > 3.   rtl_ips_nic_on is called which disable local irqs
> > 4.     rtl92c_phy_set_rf_power_state() is called
> > 5.       rtl_ps_enable_nic() is called and enable interrupts on the
> > device
> > 6.   as soon as local irqs are reenabled before exiting rtl_ips_nic_on,
> > a RX interrupt is handled and _rtl_pci_interrupt appears to be taking
> > about 340 ms to process the interrupt.
> 
> Good data.  This discovery now points more firmly at the wireless
> driver as a contributing cause.
> 
> You might further diagnose this by tracing the timing of the interrupt
> handler, to see if it is something the handler calls that causes the
> delay, or if it is device access that does it.
> 
Are printk timestamps considered accurate inside irq handlers? I'm a bit
suspicious about that point because I have added a printk immediatly
after entering _rtl_pci_interrupt() (that I have omitted to show in my
previous e-mail) and it has appeared out of order in the dmesg output:

[   69.376012] rtl8192ce:rtl92ce_sw_led_on():<0-1> LedAddr:4E ledpin=1
[   69.711882] rtl_pci:_rtl_pci_interrupt():<10000-1> entering handler
[   69.376012] rtlwifi:rtl_ips_nic_on():<0-1> before
spin_unlock_irqrestore
[   69.711909] rtl_pci:_rtl_pci_interrupt():<10000-1> after
interrupt_recognized
[   69.711920] rtl_pci:_rtl_pci_interrupt():<10000-1> Rx ok interrupt!
[   69.711948] rtlwifi:rtl_ips_nic_on():<0-0> after
spin_unlock_irqrestore

Is there any kernel debug CONFIGs that could be useful to track down irq
issues?



      reply	other threads:[~2014-01-27  7:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  6:37 [ISSUE] rtl8192ce appears to interfere with ALSA playback Olivier Langlois
2014-01-15 17:01 ` Larry Finger
2014-01-16  5:25   ` Olivier Langlois
2014-01-16  5:55     ` James Cameron
2014-01-23  8:13       ` Olivier Langlois
2014-01-23  8:51         ` [alsa-devel] " Takashi Iwai
2014-01-23 16:15           ` LANGLOIS Olivier PIS -EXT
2014-01-23 16:29             ` Takashi Iwai
2014-01-24  5:32               ` Olivier Langlois
2014-01-27  6:32   ` Olivier Langlois
2014-01-27  6:54     ` James Cameron
2014-01-27  7:08       ` Olivier Langlois [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=1390806512.2436.180.camel@Wailaba2 \
    --to=olivier@trillion01.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quozl@laptop.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;
as well as URLs for NNTP newsgroup(s).