From: Mateusz Berezecki <mateuszb@gmail.com>
To: Stefan Knoblich <stkn@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: b44 ifconfig fails with ENOMEM
Date: Wed, 29 Dec 2004 14:44:20 +0100 [thread overview]
Message-ID: <41D2B4B4.6090608@gmail.com> (raw)
In-Reply-To: <200412290557.29114.stkn@gentoo.org>
Stefan Knoblich wrote:
>Hi,
>
>ifconfig eth0 192.168.1.2 up returns the following error message:
>
>laptop ~ # ifconfig eth0 192.168.1.2 up
>SIOCSIFFLAGS: Cannot allocate memory
>SIOCSIFFLAGS: Cannot allocate memory
>
>output of dmesg:
>
>ifconfig: page allocation failure. order:8, mode:0x21
> [<c01382f2>] __alloc_pages+0x1d2/0x3a0
> [<c01384df>] __get_free_pages+0x1f/0x40
> [<c010923a>] dma_alloc_coherent+0xca/0x100
> [<e00dec87>] b44_alloc_consistent+0xc7/0x1a0 [b44]
> [<e00df1a1>] b44_open+0x21/0xd0 [b44]
> [<c035e3ae>] schedule+0x2be/0x4e0
> [<c02e0445>] dev_open+0x85/0xa0
> [<c02e1953>] dev_change_flags+0x53/0x130
> [<c031ec17>] devinet_ioctl+0x257/0x5b0
> [<c0320f36>] inet_ioctl+0x66/0xb0
> [<c02d76c9>] sock_ioctl+0xd9/0x2b0
> [<c0162215>] sys_ioctl+0xd5/0x220
> [<c0107417>] do_syscall_trace+0x47/0x90
> [<c0102f43>] syscall_call+0x7/0xb
>
>there's plenty of free memory available:
>
>laptop ~ # free
> total used free shared buffers cached
>Mem: 506320 499728 6592 0 20036 274712
>-/+ buffers/cache: 204980 301340
>Swap: 987988 3144 984844
>
>unloading and reloading the module didn't help, only a reboot fixed it (after
>~36hours uptime)
>
>
same problem here. i left my laptop on for a longer time and ifconfig
failed too
kernel backtrace same as above. kernel looked like it didn't swap out
some memory.
lots of swap free no phys mem free. i dont know if this helps.
reloading the module didn't help too.
if you want more info please let me know
next prev parent reply other threads:[~2004-12-29 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 4:57 b44 ifconfig fails with ENOMEM Stefan Knoblich
2004-12-29 13:44 ` Mateusz Berezecki [this message]
2004-12-29 14:03 ` Pekka Pietikainen
2004-12-30 23:39 ` Stefan Knoblich
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=41D2B4B4.6090608@gmail.com \
--to=mateuszb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stkn@gentoo.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