Bug 18767 - kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Summary: kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Low minor
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 6sta2
Depends on:
Blocks:
 
Reported: 2016-06-23 04:05 CEST by Bit Twister
Modified: 2022-12-21 22:52 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
radeon and journal info (3.03 KB, text/plain)
2016-06-23 04:07 CEST, Bit Twister 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-06-23 04:05:51 CEST 
Description of problem:

kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. clean install non-free and tainted media enabled
2.   journalctl -b | grep signature
Comment 1 Bit Twister 2016-06-23 04:07:19 CEST 
Created attachment 8053 [details]
radeon and journal info
Marja Van Waes 2016-06-23 08:37:18 CEST

CC: (none) => marja11
Assignee: bugsquad => tmb

Comment 2 Marja Van Waes 2016-08-26 12:48:49 CEST 
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field.

Please reassign if needed, or add kernel to the SRPM field if this is correct.

Assignee: tmb => kernel

Bit Twister 2017-01-24 12:32:27 CET

Status comment: (none) => 6_s2
Summary: 6_s1: kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff => kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Comment 3 Thierry Vignaud 2017-01-24 14:05:48 CET 
That's just a warning IMHO.
It could be a firmware bug.

Priority: Normal => Low
Severity: normal => minor
CC: (none) => thierry.vignaud

Bit Twister 2017-01-31 18:35:43 CET

Status comment: 6_s2 => (none)
Keywords: (none) => 6sta2

Comment 4 sturmvogel 2022-12-21 22:52:32 CET 
Closing OLD as Mageia 6 reached EOL September 2019.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.