Soft reset failed, AMD SB750

[Jeff Galli]

Hardware Background: Using a ASUS M3A78-T (AMD 790gx with 3200 igp and AMD SB750 southbridge). 4 Hard drives plugged into the onboard sata (3 seagate 1.5tb and 1 5400rpm laptop drive for boot)

While booting into Jaunty (happens when installing from the livecd/liveusb as well) I get the errors:
ata#: Soft reset Failed (Device not Ready) where # is a number 1-4 corresponding to one of the hard drives I have plugging into the motherboard sata ports. Tried to run in both AHCI and IDE mode and pass "all_generic_ide" and "pci=nomsi" to the kernel at boot and still the same messages. While this doesn't stop me from booting, it it a bit scary to see.

$ uname -a
Linux ubuntu904 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:23 UTC 2009 i686 GNU/Linux
$ cat /proc/version_signature
Ubuntu 2.6.28-11.37-generic

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: System manufacturer System Product Name
NonfreeKernelModules: fglrx
Package: linux-image-2.6.28-11-generic 2.6.28-11.37
ProcCmdLine: root=UUID=3d3b610d-07b8-4e09-bbd7-fbd2a5db6442 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
SourcePackage: linux

[Jeff Galli (eljeferocks)]

looks like ubuntu-bug already attached most of the stuff, but here is lspci -vnvn just for kicks.

[lavinog (lavinog)]

I have the same errors:
Motherboard: Gigabyte GA-MA78GM-S2H rev 1.0 (ATI 780G chipset)

There is a bios update that I can do, I will give that a try and see if there are any changes.

[lavinog (lavinog)]

uname -a: Linux Shredder 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 x86_64 GNU/Linux
(don't know how to post multiple files in one comment)

[Malte S. Stretz (mss)]

Probably just a scary message, see http://ubuntuforums.org/showpost.php?p=6990421&postcount=17

[burkaygenc (burkaygenc)]

Not just a scary message. It prevents my machine to boot for at least 2 minutes. Then I get a "modules.dep" not found error. Then booting continues as if nothing happened.