public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <linux-kernel@borntraeger.net>
To: linux-kernel@vger.kernel.org
Cc: andreamrl@tiscali.it, ipw2100-admin@linux.intel.com
Subject: Re: PROBLEM:kernel BUG at mm/page_alloc.c:786!
Date: Thu, 3 Jun 2004 22:02:46 +0200	[thread overview]
Message-ID: <200406032203.00290.linux-kernel@borntraeger.net> (raw)
In-Reply-To: <200406032118.32794.linux-kernel@borntraeger.net>

Christian Borntraeger wrote:
> This function looks bogus: If ipw2100_tx_allocate fails, ipw2100_rx_free
> is called. Unfortunately the ipw2100_rx_allocate function was never
> called.

I just check the original mail:
actually ipw2100_rx_allocate fails to allocate memory. ipw2100_rx_free is 
called nevertheless, which IMHO caused the bug message.

andreamrl@tiscali.it wrote:
> modprobe: page allocation failure. order:0, mode:0x20
> Call Trace:
>  [<c013afc1>] __alloc_pages+0x2e1/0x320
>  [<c013b01f>] __get_free_pages+0x1f/0x40
>  [<c013e507>] cache_grow+0xa7/0x290
>  [<c013e7be>] cache_alloc_refill+0xce/0x210
>  [<c013ebe9>] __kmalloc+0x69/0x70
>  [<c03252f7>] alloc_skb+0x47/0xf0
>  [<d0f3c880>] ipw2100_rx_allocate+0x140/0x2f0 [ipw2100]
>  [<d0f3dfaf>] ipw2100_queues_allocate+0x1f/0x60 [ipw2100]
>  [<d0f3fc97>] ipw2100_pci_init_one+0x367/0x5a0 [ipw2100]
>  [<c0187f0e>] sysfs_new_inode+0x5e/0xb0
>  [<c021c202>] pci_device_probe_static+0x52/0x70
>  [<c021c25c>] __pci_device_probe+0x3c/0x50



      reply	other threads:[~2004-06-03 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 18:01 PROBLEM:kernel BUG at mm/page_alloc.c:786! andreamrl
2004-06-03 19:18 ` Christian Borntraeger
2004-06-03 20:02   ` Christian Borntraeger [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=200406032203.00290.linux-kernel@borntraeger.net \
    --to=linux-kernel@borntraeger.net \
    --cc=andreamrl@tiscali.it \
    --cc=ipw2100-admin@linux.intel.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox