From: Meelis Roos <mroos@linux.ee>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-fbdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed
Date: Sat, 19 Aug 2017 08:39:40 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1708190007310.26479@math.ut.ee> (raw)
In-Reply-To: <87mv6xjc2g.fsf@concordia.ellerman.id.au>
> Meelis Roos <mroos@linux.ee> writes:
>
> > I was trying 4.13.0-rc5-00075-gac9a40905a61 on my PowerMac G4 with 1G
> > RAM and after some time of sddm respawning and X trying to restart,
> > dmesg is full of messages about vmap allocation failures.
>
> Did it just start happening? ie. did rc4 work?
It goes back to at least 4.0 - that's the oldest kernel I had laying
around precompiled. The messages about ROM signature changed somewehere
between 4.0 and 4.7 (4.7 is already like 4.13) but after some time, the
same vmalloc errors appear.
Maybe the userspace has changed with more respawning that brings the
problem out.
I tried to read the code but I do not understand it yet. The warning
seems to come from generic pci_map_rom() checking ROM size, and
returning rom pointer to aty128fb (it returns resource size too but that
is ignored). aty128fb starts to look at the x86 PCI ROM signature again
but does not tell that the signature is missing. How come?
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-08-19 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 5:37 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed Meelis Roos
2017-08-18 12:27 ` Michael Ellerman
2017-08-18 12:29 ` Meelis Roos
2017-08-19 5:39 ` Meelis Roos [this message]
2017-08-22 6:00 ` Michael Ellerman
2017-08-22 16:17 ` Andreas Schwab
2017-08-22 16:29 ` Meelis Roos
2017-08-22 19:45 ` Meelis Roos
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=alpine.LRH.2.20.1708190007310.26479@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).