Bug 733313 - Fedora 16 kernel-3.0.1-3 running on EC2 makes devices ordering wrong
Summary: Fedora 16 kernel-3.0.1-3 running on EC2 makes devices ordering wrong
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-25 12:56 UTC by Marek Goldmann
Modified: 2011-08-28 05:38 UTC (History)
6 users (show)

Fixed In Version: kernel-3.1.0-0.rc3.git0.0.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-28 05:38:06 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 729340 None None None Never

Internal Links: 729340

Description Marek Goldmann 2011-08-25 12:56:32 UTC
Description of problem:

This is the exactly same issue described here with the difference that now Fedora 16 was hit by it:

https://bugzilla.redhat.com/show_bug.cgi?id=729340

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

kernel-3.0.1-3.fc16.x86_64

How reproducible:

Always

Comment 1 Josh Boyer 2011-08-25 13:05:23 UTC
F16 is moving to the 3.1 kernel.  This is fixed in the kernel queued for updates testing:

http://koji.fedoraproject.org/koji/buildinfo?buildID=259980

If you have a chance, please test and provide karma in bodhi.

Comment 2 Marek Goldmann 2011-08-25 14:00:38 UTC
I've tested this just now - works as expected, bumped the karma. Thanks!

Comment 3 Fedora Update System 2011-08-25 14:33:13 UTC
kernel-3.1.0-0.rc3.git0.0.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/kernel-3.1.0-0.rc3.git0.0.fc16

Comment 4 Fedora Update System 2011-08-28 05:37:19 UTC
kernel-3.1.0-0.rc3.git0.0.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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