From: Mohammed Shafi <shafi.ath9k@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>, Tony Houghton <h@realh.co.uk>
Cc: ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Jouni Malinen <jmalinen@atheros.com>,
Senthil Balasubramanian <senthilkumar@atheros.com>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Vivek Natarajan <vnatarajan@atheros.com>
Subject: Re: [ath9k-devel] ath9k causes lockups since kernel 2.6.35
Date: Fri, 25 Feb 2011 14:14:21 +0530 [thread overview]
Message-ID: <AANLkTim8GSfuN5+zMyLWczy2YdSwxXsegtjLnGYVQsAG@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiksoeKhMaFarSDVCbcDbZx6iWHkYzrg--1NcKKA@mail.gmail.com>
On Fri, Feb 25, 2011 at 1:21 PM, Mohammed Shafi <shafi.ath9k@gmail.com> wrote:
> On Fri, Feb 25, 2011 at 1:32 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> (just cc-ing some people listed in MAINTAINERS)
>> Hi,
>>
>> Tony Houghton wrote:
>>
>>> With 2.6.37 I can not use suspend on my Compaq/HP 311c (Intel Atom
>>> N270/NVidia Ion LE). Originally the machine just kept locking up without
>>> even blanking the display when I tried to suspend (using the GNOME menu
>>> or by shutting the lid). I upgraded upower and gnome-power-manager etc
>>> to experimental and after that the machine suspended OK but could not
>>> resume. The backlight came on but the screen stayed blank and I could
>>> not get to a console or anything with Alt+Fn.
>> [...]
>>> I tried replacing network-manager with wicd but that crashed the system
>>> when it connected instead of when disconnected.
>> [...]
>>> While testing different kernels I found it would crash at different
>>> times, usually before the screen turned off for suspending, but
>>> sometimes it would crash on resuming and occasionally it locked up while
>>> booting, but it's always a complete lock-up ie the keyboard is
>>> completely responsive, including caps lock, the mouse won't move if the
>>> display is still on, and the only way out is to hold down the power
>>> button.
>> [...]
>>> I haven't tried looking in logs because the crashes are so severe I
>>> don't think they'd be able to record anything useful. But using git
>>> bisect I think I have tracked down the change that started causing this
>>> problem:
>>>
>>> 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f is the first bad commit
>>> commit 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f
>>> Author: Vivek Natarajan <vnatarajan@atheros.com>
>>> Date: Mon Apr 5 14:48:04 2010 +0530
>>>
>>> ath9k: Add support for newer AR9285 chipsets.
>>>
>>> This patch adds support for a modified newer version of AR9285
>>> chipsets.
>>>
>>> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
>>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>
>> The adaptor is an AR9285[1].
>>
>> That commit is based against v2.6.33 and was merged in v2.6.35-rc1
>>
>> $ git describe 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f
>> v2.6.33-3523-g53bc7aa
>> $ git name-rev --tags 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f
>> 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f tags/v2.6.35-rc1~473^2~167^2~346
>>
>> Any ideas for tracking this down?
>
> is this issue still reproducible ?
> Apart from this reporting I have not seen any other issues for AR9285.
sorry just now saw's Tonys message in linux wireless mailing list
>
>>
>> Thanks,
>> Jonathan
>>
>> [1]
>>> 84: udi = '/org/freedesktop/Hal/devices/pci_168c_2b'
>>> pci.device_protocol = 0 (0x0) (int)
>>> pci.vendor = 'Atheros Communications Inc.' (string)
>>> info.vendor = 'Atheros Communications Inc.' (string)
>>> pci.product = 'AR9285 Wireless Network Adapter
>>> (PCI-Express)' (string) linux.sysfs_path =
>>> '/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0' (strin g)
>>> info.parent = '/org/freedesktop/Hal/devices/pci_10de_ac6' (string)
>>> info.linux.driver = 'ath9k' (string)
>>> pci.subsys_vendor = 'Hewlett-Packard Company' (string)
>>> linux.hotplug_type = 2 (0x2) (int)
>>> linux.subsystem = 'pci' (string)
>>> info.subsystem = 'pci' (string)
>>> info.product = 'AR9285 Wireless Network Adapter
>>> (PCI-Express)' (string) info.udi =
>>> '/org/freedesktop/Hal/devices/pci_168c_2b' (string)
>>> pci.linux.sysfs_path =
>>> '/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0' (string)
>>> pci.product_id = 43 (0x2b) (int) pci.vendor_id = 5772 (0x168c)
>>> (int) pci.subsys_product_id = 12352 (0x3040) (int)
>>> pci.subsys_vendor_id = 4156 (0x103c) (int) pci.device_class = 2
>>> (0x2) (int) pci.device_subclass = 128 (0x80) (int)
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel@lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
next prev parent reply other threads:[~2011-02-25 8:44 UTC|newest]
Thread overview: 32+ 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 [this message]
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
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
[not found] <AANLkTikvcwQx9p1O49DZDJBmWPte9_VVrwJOQgBjPri4@mail.gmail.com>
2011-03-10 11:41 ` [ath9k-devel] " Mohammed Shafi
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=AANLkTim8GSfuN5+zMyLWczy2YdSwxXsegtjLnGYVQsAG@mail.gmail.com \
--to=shafi.ath9k@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=h@realh.co.uk \
--cc=jmalinen@atheros.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.com \
--cc=vnatarajan@atheros.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).