All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Tulio Magno Quites Machado Filho <tuliom@gmail.com>,
	Nick Kossifidis <mick@madwifi-project.org>,
	ath5k-devel <ath5k-devel@lists.ath5k.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Thanks for TX power patch
Date: Thu, 12 Mar 2009 23:25:11 +0200	[thread overview]
Message-ID: <1236893111.30325.10.camel@maxim-laptop> (raw)
In-Reply-To: <b6c5339f0903120714rda8ec3ev2c2fbfaaf0b21351@mail.gmail.com>

On Thu, 2009-03-12 at 10:14 -0400, Bob Copeland wrote:
> On Wed, Mar 11, 2009 at 4:15 AM, Tulio Magno Quites Machado Filho
> <tuliom@gmail.com> wrote:
> > On Wed, Mar 11, 2009 at 12:39 AM, Maxim Levitsky
> > <maximlevitsky@gmail.com> wrote:
> >> If I unload/reload the ath5k, it seems to work. but at next suspend to
> >> disk, once  system hung, other time it showed many panic, in something
> >> related to page allocator (one even was in page_alloc_pages or so)
> >
> > I'm getting some Kernel oopses after unloading ath5k with Nick patches.
> > But I'm still debugging it to find where is the problem.
> 
> Ditto here.. looks like a bug in ath5k_eeprom_free_pcal_info(), which has:
> 
>     struct ath5k_pdgain_info *pd = &chinfo->pd_curves[pdg];
> 
>     if (pd != NULL) {
>         kfree(pd->pd_step);
>         kfree(pd->pd_pwr);
>         kfree(pd);
>     }
> 
> kfree(pd) looks wrong, because pd_curves is the kzalloc()ed part, not
> the array elements themselves.  But I tried removing that and freeing
> the pd_curves array outside of the loop and got more slab debugging
> poop.  So, I punt for now.
> 
> Also, every alloc of pd_step, and pd_pwr can potentially leak earlier
> allocated memory on ENOMEM.
> 

Just to be clear, I got oopses, and hangs after resume from disk by just
using compat-wireless-2009-03-10 _without_ Nick's patches.

It seems that a memory corruption happens somewhere.
On the other hand if I avoid S2disk and module reload, everything seems
to be stable and fast (2.4 MB/s in both directions)

Best regards,
	Maxim Levitsky


  reply	other threads:[~2009-03-12 21:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 23:39 Thanks for TX power patch Maxim Levitsky
2009-03-11  0:12 ` Nick Kossifidis
2009-03-11  8:15 ` Tulio Magno Quites Machado Filho
2009-03-12 14:14   ` Bob Copeland
2009-03-12 21:25     ` Maxim Levitsky [this message]
2009-03-12 21:32       ` [ath5k-devel] " Bob Copeland
2009-03-12 21:33         ` Bob Copeland
2009-03-12 22:04           ` Maxim Levitsky
2009-03-13 10:38             ` Maxim Levitsky
2009-03-13 18:23               ` Bob Copeland
2009-03-13 18:29                 ` Nick Kossifidis
2009-03-13 19:06                 ` Maxim Levitsky
2009-03-13  0:30     ` Bob Copeland

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=1236893111.30325.10.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=mick@madwifi-project.org \
    --cc=tuliom@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 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.