From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Nick Kossifidis <mick@madwifi-project.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, jirislaby@gmail.com
Subject: Re: [ath5k-devel] [PATCH 1/5] ath5k: PHY code cleanup
Date: Wed, 04 Feb 2009 00:41:21 +0200 [thread overview]
Message-ID: <1233700881.9297.7.camel@maxim-laptop> (raw)
In-Reply-To: <40f31dec0902031006o6d0dd6ffkf6aae6d39cf078a5@mail.gmail.com>
On Tue, 2009-02-03 at 20:06 +0200, Nick Kossifidis wrote:
> 2009/2/3 Maxim Levitsky <maximlevitsky@gmail.com>:
> > On Tue, 2009-02-03 at 18:24 +0200, Nick Kossifidis wrote:
> >> 2009/2/3 Nick Kossifidis <mickflemm@gmail.com>:
> >> > 2009/2/3 Maxim Levitsky <maximlevitsky@gmail.com>:
> >> >> I just tried your 5 patches, as they could fix hangs in the device,
> >> >> that I experience occasionally, when resuming my aspire one from
> >> ram.
> >> >>
> >> >> I applied the patches, and I got very unstable system, that tended
> >> to
> >> >> hang even before X.
> >> >>
> >> >> When it didn't hang, I tried suspend to ram cycle, but it hanged
> >> then.
> >> >>
> >> >>
> >> >> Best regards,
> >> >> Maxim Levitsky
> >> >>
> >> >>
> >> >
> >> > It's related to unhandled BMISS interrupts, Bob is working on it to
> >> > see what triggers them. A quick solution is to disable them (as we
> >> > don't handle them anyway) but it would be better to know the
> >> problem.
> >> >
> >
> > Acer aspire one.
> >
> > -wireless-testing tree + 5 patches
> > I test without X running, maybe I could spot an oops or so,
> > currently, system just hangs cold.
> >
>
> What's your AP, your RSSI etc ?
AP?, just some Siemens b/g device
signal quality is around 100%, ap is in nearby room
WPA2 is used.
I did further test, by switching to console and doing there a
pm-suspend, and system did hand exactly same way, but I did see a
message about softlockup in ath5k.
(in phy-...)
Also have seen a message about 'not being able to query synaptic...'
and eveything was dead including keyboard and touchpad. (even sysrq
didn't work )
>
> >
> > PS:
> >
> > Atheros devices consist of MAC and PHY (which sometimes is called radio)
> >
> > It seems that my device has 2425 MAC, but what radio it has?
> > It also seems that most of the driver treats it as a AR5112.
> > I thought before that 5112 was the MAC and 2425 was the radio, but it
> > doesn't seem to be true, can you explain this?
> >
> >
>
> A card consists (among other things) of a MAC chip (includes PCU, QCU,
> DCU, DMA unit), a radio chip (has synth, bias control etc) and in
> between there is baseband (what's called PHY) that drives the radio
> chip and provides data i/o to the MAC chip.
>
> First Atheros cards (before 2413) have MAC and PHY on the same chip
> and radio on a separate chip, MAC/BB chips are named AR52XX and radio
> chips RF51XX.
> Newer Atheros cards have all parts on the same chip, MAC is mostly the
> same as AR5212 (that's why we mark them as AR5K_AR5212) but PHY and
> (especially) RF change so the whole chip gets the name of the radio
> chip (RFX4XX -> ARX4XX). So AR2425 has an AR5212 MAC with minor
> modifications and an RF2425 radio chip. SREV register marks the whole
> chip (since it's not only a MAC/BB chip anymore) so this might be
> confusing.
Thanks a lot for explanation, now it is all clear.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2009-02-03 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 2:23 [PATCH 1/5] ath5k: PHY code cleanup Nick Kossifidis
2009-01-31 2:43 ` Felix Fietkau
2009-01-31 3:12 ` Nick Kossifidis
2009-02-03 14:08 ` [ath5k-devel] " Maxim Levitsky
2009-02-03 14:45 ` Bob Copeland
2009-02-03 16:17 ` Nick Kossifidis
2009-02-03 16:24 ` Nick Kossifidis
2009-02-03 16:41 ` Maxim Levitsky
2009-02-03 18:06 ` Nick Kossifidis
2009-02-03 22:41 ` Maxim Levitsky [this message]
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=1233700881.9297.7.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mick@madwifi-project.org \
--cc=mickflemm@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