From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Mateusz Berezecki <mateuszb@gmail.com>
Cc: Stefan Knoblich <stkn@gentoo.org>, linux-kernel@vger.kernel.org
Subject: Re: b44 ifconfig fails with ENOMEM
Date: Wed, 29 Dec 2004 16:03:33 +0200 [thread overview]
Message-ID: <20041229140333.GA27964@ee.oulu.fi> (raw)
In-Reply-To: <41D2B4B4.6090608@gmail.com>
On Wed, Dec 29, 2004 at 02:44:20PM +0100, Mateusz Berezecki wrote:
> >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
Hiya... Known feature :-( See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118165 for details.
"See last paragraph of comment #66. The problem is that the driver
needs about 750k of memory that has to be located under 1GB physically
to not trigger the hardware bug that causes crashes and other fun. The
driver tries to allocate that kind of memory
(pci_set_consistent_dma_mask(pdev, 0x3fffffff) ). There should be
plenty, right?
Unfortunately the way it's implemented right now in the generic x86
pci code is that if you ask for some memory with a dma mask of < 4GB,
it falls back to giving you memory from the first 16MB. Now that's a
pretty limited resource :-(. There seems to be 3 drivers that need
similar workarounds (wanxl, aacraid and b44)"
Quickest "fix" is to use a B44_DMA_MASK of 0xffffffff . Which is the
pre-2.6.9 behaviour and is fine if you have <= 1GB of memory or use the
standard 1:3 kernel:user split.
next prev parent reply other threads:[~2004-12-29 14:03 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
2004-12-29 14:03 ` Pekka Pietikainen [this message]
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=20041229140333.GA27964@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.com \
--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