linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi <shafi.wireless@gmail.com>
To: Tony Houghton <h@realh.co.uk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Could ath9k and rt2800pci bugs be related?
Date: Tue, 15 Mar 2011 13:17:40 +0530	[thread overview]
Message-ID: <AANLkTimSZrGCzBaB9K=WVO7faGNM-+qeKEE2qzjkPnSD@mail.gmail.com> (raw)
In-Reply-To: <20110314164812.4c0cfc29@toddler>

On Mon, Mar 14, 2011 at 10:18 PM, Tony Houghton <h@realh.co.uk> wrote:
> [I am no longer subscribed to the list so please Cc me]
>
> I'm the person who reported that my system kept freezing when shutting
> down my AR9285 wireless with kernel 2.6.35 or newer.
>
> I've just bought an Acer Aspire Revo 3700 and this had very similar
> symptoms with a different adapter. Luckily another customer had posted
> about it on the vendor's website and his fix works for me. The fix is to
> blacklist the rt2800pci module and the rt2860sta driver seems to work
> quite happily without it.
>
> It looks as if rt2800pci was introduced somewhere between 2.6.32 and
> 2.6.34 and I experienced the crashes with 2.6.35 (Mint 10/Ubuntu 10.10)
> and 2.6.37 (Debian unstable), but not with 2.6.32 (Debian squeeze) which
> doesn't have that module.

can you please check by disabling the supicious rt modules and see
whether this problems happens.
for quick check please try with the latest compat wireless.

>
> It's probably just coincidence, but I was struck by how similar the
> symptoms are and wondered whether these different drivers have anything
> in common?
>
> lspci output:
>
> 02:00.0 Network controller [0280]: RaLink RT3090 Wireless 802.11n 1T/1R PCIe [1814:3090]
>        Subsystem: Lite-On Communications Inc Device [11ad:6622]
>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>        Latency: 0, Cache Line Size: 32 bytes
>        Interrupt: pin A routed to IRQ 18
>        Region 0: Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
>        Capabilities: <access denied>
>        Kernel driver in use: rt2860
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2011-03-15  7:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 18:20 ath9k causes lockups since kernel 2.6.33 Tony Houghton
2011-02-24 20:02 ` ath9k causes lockups since kernel 2.6.35 Jonathan Nieder
2011-02-25  7:51   ` [ath9k-devel] " Mohammed Shafi
2011-02-25  8:44     ` Mohammed Shafi
2011-02-25 14:47     ` Tony Houghton
2011-02-25 16:07       ` Mohammed Shafi
2011-02-25 16:57         ` Tony Houghton
2011-02-26 18:35           ` Tony Houghton
2011-02-28  5:36             ` Mohammed Shafi
2011-03-02 16:30               ` Tony Houghton
2011-03-03  5:21                 ` Mohammed Shafi
2011-03-03 14:31                   ` Tony Houghton
2011-03-03 15:57                     ` Mohammed Shafi
2011-03-03 19:16                       ` Tony Houghton
2011-03-04 15:50                         ` Mohammed Shafi
2011-03-06 22:04                           ` Tony Houghton
2011-03-03  7:05             ` Vivek Natarajan
2011-02-25  7:57   ` Sedat Dilek
2011-02-25 14:35     ` Tony Houghton
2011-03-14 16:48   ` Could ath9k and rt2800pci bugs be related? Tony Houghton
2011-03-15  7:47     ` Mohammed Shafi [this message]
2011-03-15 13:19       ` Tony Houghton
2011-03-15 13:35         ` Mohammed Shafi
2011-03-15 15:17           ` Tony Houghton
2011-03-15 16:17             ` Mohammed Shafi
2011-03-15 17:15               ` Tony Houghton
2011-03-16  5:09                 ` Mohammed Shafi
2011-03-15 15:24           ` Tony Houghton
2011-06-10  6:48   ` ath9k causes lockups since kernel 2.6.35 Adrian Chadd
2011-06-13 11:00     ` Stanislaw Gruszka
2011-06-27 10:33   ` Adrian Chadd

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='AANLkTimSZrGCzBaB9K=WVO7faGNM-+qeKEE2qzjkPnSD@mail.gmail.com' \
    --to=shafi.wireless@gmail.com \
    --cc=h@realh.co.uk \
    --cc=linux-wireless@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 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).