From: Frank Scheiner <frank.scheiner@web.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Regression in 543cea9a - was: Re: Kernel problem on rx2800 i2
Date: Tue, 25 Jun 2019 10:46:39 +0000 [thread overview]
Message-ID: <e6b720e2-e603-a867-e738-f9e6b9f906e1@web.de> (raw)
In-Reply-To: <1d62aadd-67b6-da13-53cc-4b5213de8937@physik.fu-berlin.de>
On 6/25/19 12:32, Christoph Hellwig wrote:
> Thanks Frank.
>
> It seems like there is something odd going on with the zonelist
> on your system. Maybe there is not actual ZONE_DMA32, or something
> is messed with the numa node setup.
Do you suspect a firmware issue? Because the firmware of that machine is
actually quite old (the model was retired in 2015):
```
***********************************************************
* ROM Version : 01.93
* ROM Date : Wed Sep 12 22:10:03 PDT 2012
***********************************************************
```
...but since HP has a different opinion about what is considered part of
the hardware and hence should be "corrected" by the manufacturer in any
case without asking for large amounts of money, I have no means to
upgrade it.
> Below is a band aid patch to
> try theory number two above:
>
>
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> index fcdb23e8d2fc..8e3f7b8bdb33 100644
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -119,7 +119,7 @@ struct page *__dma_direct_alloc_pages(struct device *dev, size_t size,
> }
> }
> if (!page)
> - page = alloc_pages_node(dev_to_node(dev), gfp, page_order);
> + page = alloc_pages(gfp, page_order);
>
> if (page && !dma_coherent_ok(dev, page_to_phys(page), size)) {
> __free_pages(page, page_order);
>
Ok, will try that patch - actually (1) in addition or (2) without the
first one?
next prev parent reply other threads:[~2019-06-25 10:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 6:40 Regression in 543cea9a - was: Re: Kernel problem on rx2800 i2 John Paul Adrian Glaubitz
2019-06-25 6:42 ` Christoph Hellwig
2019-06-25 6:46 ` John Paul Adrian Glaubitz
2019-06-25 6:50 ` Christoph Hellwig
2019-06-25 6:54 ` John Paul Adrian Glaubitz
2019-06-25 6:59 ` Christoph Hellwig
2019-06-25 7:26 ` Frank Scheiner
2019-06-25 8:16 ` Frank Scheiner
2019-06-25 8:18 ` Christoph Hellwig
2019-06-25 8:38 ` Frank Scheiner
2019-06-25 9:30 ` Frank Scheiner
2019-06-25 10:32 ` Christoph Hellwig
2019-06-25 10:46 ` Frank Scheiner [this message]
2019-06-25 10:47 ` Christoph Hellwig
2019-06-25 11:19 ` Frank Scheiner
2019-06-25 11:21 ` John Paul Adrian Glaubitz
2019-06-25 12:00 ` Christoph Hellwig
2019-06-25 12:08 ` Frank Scheiner
2019-06-25 14:40 ` Christoph Hellwig
2019-06-25 15:52 ` Frank Scheiner
2019-06-28 6:26 ` Christoph Hellwig
2019-06-28 7:35 ` Frank Scheiner
2019-08-05 7:10 ` Christoph Hellwig
2019-08-05 8:16 ` Frank Scheiner
2020-08-05 19:43 ` John Paul Adrian Glaubitz
2020-08-05 20:27 ` Jessica Clarke
2020-08-05 21:27 ` John Paul Adrian Glaubitz
2020-08-05 22:41 ` John Paul Adrian Glaubitz
2021-03-23 15:02 ` John Paul Adrian Glaubitz
2021-03-23 15:14 ` Frank Scheiner
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=e6b720e2-e603-a867-e738-f9e6b9f906e1@web.de \
--to=frank.scheiner@web.de \
--cc=linux-ia64@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