All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR5008 hanging computer
Date: Thu, 11 Mar 2010 02:56:55 -0500	[thread overview]
Message-ID: <1268294215.4089.10.camel@mj> (raw)
In-Reply-To: <20100305230438.GA4942@lazo.ca>

On Fri, 2010-03-05 at 15:04 -0800, Mark Sutton wrote:

> Is it possible this is a hardware issue?

It looks like a hardware issue, but maybe it can be worked around.

> BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
> Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
> 
> Pid: 604, comm: phy0 Tainted: P           (2.6.32.7 #4) Portable PC
> EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
> EIP is at ioread32+0x32/0x40
> EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c48258
> ESI: edc40000 EDI: 00001000 EBP: 00000000 ESP: ed899d24
>  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
> CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400
> Call Trace:
>  [<f0bfc656>] ? ath9k_hw_procmibevent+0x36/0x140 [ath9k]

I believe the register number is in DX.  Register 0x8258 is
AR_SLP_MIB_CTRL, and it's indeed being read in ath9k_hw_procmibevent().
Somehow reading that register causes a CPU lockup.

An easy workaround would be to comment out this line in ani.c:

if (!(REG_READ(ah, AR_SLP_MIB_CTRL) & AR_SLP_MIB_PENDING))

Leave the new line so that the register is cleared unconditionally.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-03-11  7:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 20:31 [ath9k-devel] AR5008 hanging computer Mark Sutton
2010-02-18 21:58 ` Mark Sutton
2010-02-19  1:36   ` Pavel Roskin
2010-03-05 23:04     ` Mark Sutton
2010-03-11  7:56       ` Pavel Roskin [this message]
2010-03-11 10:38         ` Peter Stuge
2010-04-17 17:49         ` Tomi Orava
2010-02-21  8:31   ` Tomi Orava
2010-02-22 18:02     ` Luis R. Rodriguez
2010-02-22 18:24       ` Tomi Orava
2010-02-22 18:34         ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2010-02-12 15:25 James Grossmann
2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35   ` James Grossmann
2010-02-12 23:42   ` hong zhang
2010-02-15  7:03     ` Pavel Roskin
     [not found]       ` <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com>
     [not found]         ` <1266296860.17808.2.camel@mj>
2010-02-16 23:54           ` James Grossmann
2010-02-17 17:47             ` Pavel Roskin
2010-02-17 17:56             ` hong zhang
2010-02-17 18:15               ` Pavel Roskin
2010-02-23  6:45                 ` James Grossmann
2010-02-23  7:02                   ` James Grossmann
2010-03-11  8:01                     ` Pavel Roskin

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=1268294215.4089.10.camel@mj \
    --to=proski@gnu.org \
    --cc=ath9k-devel@lists.ath9k.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.