linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@newmail.ru>
To: Dan Williams <dcbw@redhat.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	orinoco-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, linux-pcmcia@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: rc9 + orinoco WPA patchset: BUG: scheduling while atomic loading firmware with PCMCIA adapter
Date: Thu, 9 Oct 2008 20:13:54 +0400	[thread overview]
Message-ID: <200810092013.55476.arvidjaar@newmail.ru> (raw)
In-Reply-To: <1223568410.18104.42.camel@dhcp-100-3-195.bos.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

On Thursday 09 October 2008, Dan Williams wrote:
> 
> On Thu, 2008-10-09 at 19:59 +0400, Andrey Borzenkov wrote:
> > On Thursday 09 October 2008, Matthew Wilcox wrote:
> > > 
> > > On Thu, Oct 09, 2008 at 05:22:55PM +0400, Andrey Borzenkov wrote:
> > > > After loading orinoco and "inserting" adapter I get either BUG with
> > > > endless loop (attached) or kernel panic on NULL pointer dereference
> > > > (was not able capture). Adapter works fine with wlags49 driver.
> > > 
> > > It looks like you've fallen off the bottom of the kernel stack.  Do you
> > > have 4k stacks enabled in your config?
> > > 
> > 
> > You are right. Using 8K stacks load and runs fine. Hmm ... not nice
> > from it :p
> 
> == driver bug; the driver should not require large stacks and this
> should get fixed.
> 
I'll check for obvious places, still ...

/* Download either STA or AP firmware into the card. */
static int
orinoco_dl_firmware(struct orinoco_private *priv,
                    const struct fw_info *fw,
                    int ap)
{
        /* Plug Data Area (PDA) */
        __le16 pda[512] = { 0 };

allocating 1K on stack is not nice; but what has eaten 3K more?

Is there any instrumentation to analyze stack usage?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-09 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 13:22 rc9 + orinoco WPA patchset: BUG: scheduling while atomic loading firmware with PCMCIA adapter Andrey Borzenkov
2008-10-09 13:31 ` Matthew Wilcox
2008-10-09 15:59   ` Andrey Borzenkov
2008-10-09 16:06     ` Dan Williams
2008-10-09 16:13       ` Andrey Borzenkov [this message]
2008-10-09 19:21       ` Andrey Borzenkov
2008-10-09 19:40         ` Dan Williams
2008-10-09 22:47         ` Dave
2008-10-10  7:41           ` Andrey Borzenkov
2008-10-10 17:03             ` Dave
2008-10-10 17:14               ` Andrey Borzenkov
2008-10-10 17:16                 ` Dave
2008-10-10 17:26                   ` Andrey Borzenkov
2008-10-10 21:19                     ` Dave
2008-10-17 20:44                     ` Dominik Brodowski

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=200810092013.55476.arvidjaar@newmail.ru \
    --to=arvidjaar@newmail.ru \
    --cc=dcbw@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=orinoco-devel@lists.sourceforge.net \
    /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).