Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed
From: Andreas Schwab <hidden>
Date: 2017-08-22 16:17:13
Also in:
linux-fbdev, lkml
Possibly related (same subject, not in this thread)
- 2017-08-22 · Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed · Michael Ellerman <mpe@ellerman.id.au>
- 2017-08-19 · Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed · Meelis Roos <hidden>
- 2017-08-18 · Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed · Meelis Roos <hidden>
- 2017-08-18 · Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed · Michael Ellerman <mpe@ellerman.id.au>
- 2017-08-18 · 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed · Meelis Roos <hidden>
On Aug 18 2017, Meelis Roos [off-list ref] wrote:
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. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."