All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Regression since 2.6.30-rc1 - Page allocation failures
Date: Thu, 30 Apr 2009 01:39:02 +0200	[thread overview]
Message-ID: <1241048343.25477.7.camel@johannes.local> (raw)
In-Reply-To: <49F8E145.1050708@lwfinger.net>

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

(dropped lkml, added netdev)

> I get the "failed to reallocate TX buffer" message. Not all are related to the
> page allocation failure. I am also getting "b43-phy0 debug: DMA RX:
> setup_rx_descbuffer() failed" messages.
> 
> So far, the numbers printed by the revised printk are:
> 
> kernel: phy0: failed to reallocate TX buffer 0, 404, need 0, 0
> kernel: protocol 0008 is buggy, dev eth1
> 
> kernel: phy0: failed to reallocate TX buffer 0, 1728, need 0, 18
> 
> Device eth1 is the b43 wireless device.

Thanks.

This is a little odd -- I don't see why
	pskb_expand_head(skb, 0, 0)
or
	pskb_expand_head(skb, 0, 18)

would try to do an order 1 allocation when skb->len is 404 or 1728. It
looks like something is forcing larger alignments than should be
necessary, but I have no idea what.

(for netdev: http://mid.gmane.org/49F8C03D.6040909@lwfinger.net has more
information)

johannes

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

  reply	other threads:[~2009-04-29 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 21:01 Regression since 2.6.30-rc1 - Page allocation failures Larry Finger
2009-04-29 21:09 ` Johannes Berg
2009-04-29 21:27   ` Johannes Berg
2009-04-29 23:22     ` Larry Finger
2009-04-29 23:39       ` Johannes Berg [this message]
2009-05-15 21:49       ` Rafael J. Wysocki
2009-05-15 22:16         ` Larry Finger

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=1241048343.25477.7.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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.