From: Andreas Schwab <schwab@linux-m68k.org>
To: Meelis Roos <mroos@linux.ee>
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 16:17:07 +0000 [thread overview]
Message-ID: <87378ja870.fsf@linux-m68k.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1708180825590.15982@math.ut.ee> (Meelis Roos's message of "Fri, 18 Aug 2017 08:37:46 +0300 (EEST)")
On Aug 18 2017, Meelis Roos <mroos@linux.ee> 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."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Meelis Roos <mroos@linux.ee>
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 18:17:07 +0200 [thread overview]
Message-ID: <87378ja870.fsf@linux-m68k.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1708180825590.15982@math.ut.ee> (Meelis Roos's message of "Fri, 18 Aug 2017 08:37:46 +0300 (EEST)")
On Aug 18 2017, Meelis Roos <mroos@linux.ee> 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."
next prev parent reply other threads:[~2017-08-22 16:17 UTC|newest]
Thread overview: 16+ 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 5:37 ` Meelis Roos
2017-08-18 12:27 ` Michael Ellerman
2017-08-18 12:27 ` Michael Ellerman
2017-08-18 12:29 ` Meelis Roos
2017-08-18 12:29 ` Meelis Roos
2017-08-19 5:39 ` Meelis Roos
2017-08-19 5:39 ` Meelis Roos
2017-08-22 6:00 ` Michael Ellerman
2017-08-22 6:00 ` Michael Ellerman
2017-08-22 16:17 ` Andreas Schwab [this message]
2017-08-22 16:17 ` Andreas Schwab
2017-08-22 16:29 ` Meelis Roos
2017-08-22 16:29 ` Meelis Roos
2017-08-22 19:45 ` Meelis Roos
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=87378ja870.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.