linux-kernel - Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168 failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.20.1708221925270.23061@math.ut.ee>
Date:   Tue, 22 Aug 2017 19:29:51 +0300 (EEST)
From:   Meelis Roos <mroos@...ux.ee>
To:     Andreas Schwab <schwab@...ux-m68k.org>
cc:     Linux Kernel list <linux-kernel@...r.kernel.org>,
        linux-fbdev@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: 32-bit powerpc, aty128fb: vmap allocation for size 135168
 failed

> > 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@...ux.ee)