From: Meelis Roos <mroos@linux.ee>
To: Andreas Schwab <schwab@linux-m68k.org>
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: Tue, 22 Aug 2017 19:29:51 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1708221925270.23061@math.ut.ee> (raw)
In-Reply-To: <87378ja870.fsf@linux-m68k.org>
> > Aug 17 23:53:57 pohl kernel: [ 2940.146546] aty128fb 0000:00:10.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x1111
> > Aug 17 23:54:02 pohl kernel: [ 2944.804838] aty128fb 0000:00:10.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x1110
>
> I think these messages are harmless and expected. This device has no
> x86 option ROM but a OpenFirmware one. This is likely unrelated to the
> sddm crash.
Yes, but after these crashes have happened for a while, vmalloc
problems appear.
sddm crash might be related to X server dying under it, or it crashes
for it own problems (varying signals and addresses beacuse of some
ASLR?) and causes X server restart that triggers another ROM allocation
round.
I did read the kernel code and I do not see how the dmesg lines are
possible without corresponding aty128fb lines about the same ROM
signature, or why the ROM signature is sometimes 0x1111 and sometimes
0x1110 instead of x86 ROM signature (that clearly is not there,
but this is expected).
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-08-22 16:29 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
2017-08-22 6:00 ` Michael Ellerman
2017-08-22 16:17 ` Andreas Schwab
2017-08-22 16:29 ` Meelis Roos [this message]
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.1708221925270.23061@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=schwab@linux-m68k.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