Bug 194533 - Invalid PCI ROM header signature: expecting 0xaa55, got 0x9125
Summary: Invalid PCI ROM header signature: expecting 0xaa55, got 0x9125
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-09 21:19 UTC by nucrap
Modified: 2017-02-16 23:41 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.9.8
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (65.25 KB, text/plain)
2017-02-09 21:19 UTC, nucrap 		Details
lspci -vv (24.07 KB, text/plain)
2017-02-09 21:19 UTC, nucrap 		Details
Add an attachment (proposed patch, testcase, etc.)

Description nucrap 2017-02-09 21:19:04 UTC 
Created attachment 254691 [details]
dmesg

I get "Invalid PCI ROM header signature: expecting 0xaa55, got 0x9125" upon booting my PC with my new Sapphire RX 470 OC graphics card.
Also there seem to be numerous errors in the dmesg.
I do not experience any major issues, but I also haven't tested any heavy 3d application so far...
Comment 1 nucrap 2017-02-09 21:19:44 UTC 
Created attachment 254693 [details]
lspci -vv
Comment 2 Alex Deucher 2017-02-10 05:12:33 UTC 
(In reply to nucrap from comment #0)
> I get "Invalid PCI ROM header signature: expecting 0xaa55, got 0x9125" upon
> booting my PC with my new Sapphire RX 470 OC graphics card.

This is harmless.  The driver is ultimately able to find the vbios image.  If it was not able to, the driver would fail to load.  There is no bug here.
Comment 3 nucrap 2017-02-10 05:14:25 UTC 
So this error warning will never disappear?
Comment 4 Alex Deucher 2017-02-10 05:25:40 UTC 
(In reply to nucrap from comment #3)
> So this error warning will never disappear?

Correct.  The message is not actually from the driver.  It's printed by the core pci rom code.
Comment 5 nucrap 2017-02-16 23:41:11 UTC 
Ok thanks for the insight.
Just out of cutiosity, why does the core pci rom code print this?
Note You need to log in before you can comment on or make changes to this bug.