Bug 694390 - does not boot on amd 4050e [NEEDINFO]
does not boot on amd 4050e
Status: CLOSED DUPLICATE of bug 690928
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-04-07 04:00 EDT by Tobias Florek
Modified: 2011-04-18 02:30 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-04-18 02:30:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
me: needinfo?

Attachments (Terms of Use)
/proc/cpuinfo (1.49 KB, application/octet-stream)
2011-04-07 04:00 EDT, Tobias Florek
no flags Details
lcpci -vvv (11.28 KB, application/octet-stream)
2011-04-07 04:01 EDT, Tobias Florek
no flags Details

  None (edit)
Description Tobias Florek 2011-04-07 04:00:27 EDT
Created attachment 490491 [details]

Description of problem:

it does boot a while, asks for password for luks encrypted filesystem and then logs:

microcode: CPU0: AMD CPU family 15 not supported

many, many times.

i do not have the exact lines and module line handy, because it did not make it to disk, older kernel report the following, but continue to boot.
 Apr  7 09:38:24 muesli kernel: [   35.160227] microcode: microcode: CPU0: AMD CPU family 0xf not supported

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

up-to-date (for my mirror) f15-updates-testing userland from april, 7th.

How reproducible:

Comment 1 Tobias Florek 2011-04-07 04:01:15 EDT
Created attachment 490492 [details]
lcpci -vvv
Comment 2 John Ellson 2011-04-14 09:15:13 EDT
See also: #690928 and #690930 -- possible dups
Comment 3 Tobias Florek 2011-04-18 02:30:41 EDT
yes, looks like the same bug. i have marked as duplicate.

*** This bug has been marked as a duplicate of bug 690928 ***

Note You need to log in before you can comment on or make changes to this bug.