> > 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@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
