Bug 313641

Summary:	Latest kernels wont boot on SATA drive connected to AMD SB600
Product:	[Fedora] Fedora	Reporter:	Roman Kisilenko <rkisilenko>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	7	CC:	chris.brown, ehabkost
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-14 19:21:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roman Kisilenko 2007-10-01 10:38:38 UTC

Description of problem:
Latest fedora kernels panic during boot from SATA drive connected to SB600
telling that they are not able to find any volume groups.
On older kernels I was able to make them boot by reducing memory size below 4
GB, on latest kernels this trick does not work.
Once I installed a Sil SATA controller and connected hard disk to it everything
boots up correctly.

Version-Release number of selected component (if applicable):
kernel-2.6.22.9-91.fc7.x86_64
kernel-2.6.22.7-85.fc7.x86_64
kernel-xen-2.6.20-2936.fc7.x86_64
kernel-xen-2.6.20-2934.fc7.x86_64
kernel-xen-2.6.20-2931.fc7.x86_64
Probably other latest kernels also.

Also some other latest kernels.

Steps to Reproduce:
1. Connect HDD to SB600 SATA controller.
2. Try to boot up from it.
  
Actual results:
Kernel panic - unable to find volume groups.

Additional info:
GIGABYTE GA-MA69VM-S2 motherboard (tried on BIOS Rev. F2, F4, F6a, others not
tested)
I'm sure the problem lies somewhere in AMD SB600 controller used by this board
as system works perfectly once hdd is connected to a Sil SATA controller plugged
in as a PCI card.
I'm ready to provide any additional information, so tell me what else should I post.

Thank you,
Roman

Comment 1 Eduardo Habkost 2007-10-01 13:47:13 UTC

Changing component to 'kernel', as it is reported to happen on non-xen kernel.

Comment 2 Christopher Brown 2008-01-14 18:12:55 UTC

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Comment 3 Roman Kisilenko 2008-01-14 18:39:57 UTC

Hello,

I'm not sure about fedora 7 kernels, but I installed fedora 8 recently and it
works fine. I guess this bug can be closed but I can check it with fedora 7 if
required.

Thank you,
Roman

Comment 4 Christopher Brown 2008-01-14 19:21:51 UTC

Hi Roman,

I will close this as NEXTRELEASE but if you are able to test that would be
greatly appreciated. If it exists in F7 (which I doubt) then please re-open.
Thanks again for filing the original bug.