linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Houghton <h@realh.co.uk>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Could ath9k and rt2800pci bugs be related?
Date: Tue, 15 Mar 2011 15:24:22 +0000	[thread overview]
Message-ID: <20110315152422.610b8434@toddler> (raw)
In-Reply-To: <AANLkTi=Gub1JAO21qtRjxVWrtc6Masp1siF3NHntgcvp@mail.gmail.com>

On Tue, 15 Mar 2011 19:05:27 +0530
Mohammed Shafi <shafi.wireless@gmail.com> wrote:

> No its nothing to do with kernel hacking, its just a wireless package.
> instead of compiling the whole kernel or wireless testing, we can
> install a wireless package within our linux distribution in few
> minutes. This package is called compat-wireless which includes latest
> fixes in wireless testing.
> more information in:
> http://wireless.kernel.org/en/users/Download

I tried that and I can confirm that it still crashes. I used the
compat-wireless-2011-03-14 snapshot with a Debian stock 2.6.37-2 kernel.

BTW one of the files had an error with TASK_INTERRUPTIBLE undefined. I
can't remember which file because I forgot to make a note of it before
make wlunload caused the expected crash. The apparent cause was that
/usr/include/linux/sched.h contains far less than sched.h in the kernel
source. I worked around it by defining the macro as 1 at the top of the
affected file.


  parent reply	other threads:[~2011-03-15 15:24 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
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 [this message]
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=20110315152422.610b8434@toddler \
    --to=h@realh.co.uk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shafi.wireless@gmail.com \
    /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).