From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754544AbdHVGA7 (ORCPT ); Tue, 22 Aug 2017 02:00:59 -0400 Received: from ozlabs.org ([103.22.144.67]:39955 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751279AbdHVGA5 (ORCPT ); Tue, 22 Aug 2017 02:00:57 -0400 From: Michael Ellerman To: Meelis Roos Cc: Linux Kernel list , linux-fbdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed In-Reply-To: References: <87mv6xjc2g.fsf@concordia.ellerman.id.au> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Tue, 22 Aug 2017 16:00:55 +1000 Message-ID: <87a82sb0q0.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Meelis Roos writes: >> Meelis Roos 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? OK thanks. Unfortunately I can't really help on the graphics side of things. Hopefully someone on Cc has more clues than me. cheers