public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc3 b44 resume problem
Date: Tue, 7 Dec 2004 13:11:05 +0200	[thread overview]
Message-ID: <20041207111105.GA28092@ee.oulu.fi> (raw)
In-Reply-To: <200412071025.32825.robin.rosenberg.lists@dewire.com>

On Tue, Dec 07, 2004 at 10:25:31AM +0100, Robin Rosenberg wrote:
> Hi,
> 
> I can't get my wired network running after resume from suspend to ram:
> 
> Dec  7 18:48:36 xine kernel: ifconfig: page allocation failure. order:8, 
> mode:0x21
> After stopping the network, and netplugd and rmmodding b44 and mii I still get
> this when trying to start my network (when b44 is activate
Hi

For a quick "fix", you can set B44_DMA_MASK to 0xffffffff. But this 
is not really a fix (and will make your machine crash and burn if you have
more than a gig of memory and use something other than a 3:1 memory layout,
but it is essentially the pre-2.6.10 situation so if the driver worked
for you before it will do so again)

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118165, 

"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)."

      reply	other threads:[~2004-12-07 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  9:25 2.6.10-rc3 b44 resume problem Robin Rosenberg
2004-12-07 11:11 ` Pekka Pietikainen [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=20041207111105.GA28092@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    /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