From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k deadbeef
Date: Fri, 07 Jan 2011 10:15:33 -0800 [thread overview]
Message-ID: <4D275845.704@candelatech.com> (raw)
In-Reply-To: <20110107180549.2137.qmail@stuge.se>
On 01/07/2011 10:05 AM, Peter Stuge wrote:
> Brian Prodoehl wrote:
>> I'm adding the WARN_ON that I talked about to my tree,
>
> Where can I grab that commit?
>
>
>> and will post whatever code paths I'm seeing traversed while the
>> chip is sleeping.
>
> They end up in kernel log, right?
>
>
> I'm inspired by the recent dialogue and am just about to reboot to
> wireless-testing master-2011-01-05 and try to live with it for a
> while.
>
>
> Linus' 2010-12-30 master locks up hard.
>
> Happened within one second of associating while in X, tried first
> with iw connect, then with wpa_supplicant. I use KMS.
>
> Third try I remained in console mode, shut down X, and could then
> work over wifi and listen to streaming for a while, maybe ten or
> fifteen minutes. After the third hard lock and a power cycle the
> kernel says:
>
> [ 0.375411] pci 0000:02:02.0: [0000:0004] type 4 class 0x000004
> [ 0.375416] pci 0000:02:02.0: unknown header type 04, ignoring device
>
> After this I usually need to power cycle a couple of times to get the
> card responding again on the bus. This card was installed brand new
> from ESD bag, clearly without marks on the miniPCI card edge
> contacts.
>
> Hard lock of course means no debug messages. :\ Note not kernel
> panic, just CPU stop. Suspect PCI problem. Would be nice to have
> a miniPCI proxy card that I could hook logic analyzer to.
>
> Well, this is as it has been, more to come with wireless-testing..
I assume you tried sysrq when it locked hard?
Also, can you try that same NIC in different hardware?
What NIC are you using?
Thanks,
Ben
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-01-07 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 16:34 [ath9k-devel] ath9k deadbeef Brian Prodoehl
2011-01-07 16:55 ` Senthilkumar Balasubramanian
2011-01-07 17:24 ` Ben Greear
2011-01-07 17:44 ` Brian Prodoehl
2011-01-07 18:05 ` Peter Stuge
2011-01-07 18:14 ` [ath9k-devel] unknown header type 04, ignoring device Peter Stuge
2011-01-11 15:30 ` Mohammed Shafi
2011-01-07 18:15 ` Ben Greear [this message]
2011-01-07 23:53 ` [ath9k-devel] ath9k deadbeef Peter Stuge
2011-01-08 0:10 ` Ben Greear
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=4D275845.704@candelatech.com \
--to=greearb@candelatech.com \
--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.