When booting the 2.6.30-r8 kernel i receive messages like ata1: SRST failed (errno=-16) ata1: link is slow to respond, please be patient (ready=0) repeats the above again... after that it tries to put the link into 1.5 Gbps mode and after a moment succeeds and the boot continues. kernel 2.6.31-r6 ata1: SRST failed (errno=-16) ata1: link is slow to respond, please be patient (ready=0) ata1: SRST failed (errno=-19) ata1: link is slow to respond, please be patient (ready=0) then it tries to put the link into 1.5 Gbps mode and gives the message ata1: SRST failed, giving up. sometimes after that message it will find sda and most of the time it will not. even when it finds sda using kernel 2.6.31-r6 it will not mount it, instead it attempts to mount my next drive /dev/sdb1 (ntfs partition) as root and fails. it then tells me to pass the correct init= line to the kernel and gives a kernel dump. I have tried this with only one drive attached, with the same results. Reproducible: Always Steps to Reproduce: 1. compile the 2.6.31-r6 kernel with reiserfs and the sata_nv kernel drivers built in (*) 2. attempt to boot into gentoo linux. 3. Actual Results: the system loaded the kernel and got as far as attempting to mount the root partition Expected Results: mounted the root partition and started init
Please post the full dmesg, I wonder if this is failing hardware. What is the make and model of this hard drive.
Can you try the "pci=nomsi" kernel boot parameter
adding pci=nomsi worked, kernel booted. Hard drive info: product: WDC WD2500JS-75N vendor: Western Digital bus info: scsi@0:0.0.0 logical name: /dev/sda version: 10.0 size: 250GB
I use the v86d splash screen at startup... how can i get you the dmesg info?
although the kernel booted, it still gave the messages listed in my first post, but instead of giving up it seemed to find sda faster
I tried an older kernel, linux-2.6.29-gentoo-r6, i don't want to think that it's failing hardware but the possibility exists... if it is failing it's the drive.. not the controller.. the controller is less than 6 months old. linux-2.6.29-gentoo-r6 told me: ata1: link online but device misclassified, retrying ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
so with the workaround, it's working?
yes, with pci=nomsi it's working
i'm re-compiling both 30 and 31 kernels so i can get you dmesg for them should have them in about 10 minutes
No need for the dmesg's. We've identified the kernel parameter you need to use. Apparently, the AHCI controller does not work on certain chipsets when MSI is enabled due to a hardware error. For AHCI to work, users must provide the "pci=nomsi" kernel boot parameter. With MSI disabled in this way, the PCIe bus can only act as a faster PCI bus with hotplug capabilities.
well, apparently the pci=nomsi option worked once... it however is failing now every boot... tried 6 times with no success... here is what i get (at least what i can see, can't scroll up after kernel dump) (manually typing this from another computer) sd 1:0:0:0: [sda] Write Protect is off scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 01.0 PQ: 0 ANSI: 5 sd 2:0:0:0: [sdb] 976673168 512-byte logical blocks: (500 GB/465 GiB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: Attached scsi generic sg3 type 0 sdb: sdb1 sdb2 sdb3 sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sdb] Attached SCSI disk sda: sda1 sd 1:0:0:0 [sda] Attached SCSI disk ata4: SATA link down (SStatus 0 SControl 300) ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata6.00: HPA detected: current 156299375, native 156301488 ata6.00: ATA-6: ST380817AS, 3.42, max UDMA/133 ata6.00: 156299375 sectors, multi 16: LBA48 NCQ (not used) ata6.00: configured for UDMA/133 scsi 5:0:0:0: Direct-Access ATA ST380817AS 3.42 PQ: 0 ANSI: 5 sd 5:0:0:0: [sdc] 156299375 512-byte logical blocks: (80.0 GB/74.5 GiB) sd 5:0:0:0: Attached scsi generic sg4 type 0 sd 5:0:0:0: [sdc] Write Protect is off sd 5:0:0:0: [sdc} Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) sdc1 sd 5:0:0:0: [sdc] Attached SCSI disk ata1.00: ATA-7: WDC WD2500JS-75NCB3, 10.02E04, max UDMA/133 ata1.00: 488281250 sectors, multi 16: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 ata1: EH complete NTFS volume version 3.1 VFS: Mounted root (ntfs filesystem) readonly on device 8:1 Freeing unused kernel memory: 604k freed Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. Pid: 1, comm: swapper Not tainted 2.6.31-gentoo-r6-MetaPhaze-KVM-R1 #4 call Trace: [<c186b589a>] ? panic+0x5a/0x100 [<c10012f2>] ? init_post+0x112/0x180 [<c1b5b4ff>] ? kernel_init+0x17a/0x1a1 [<c1b5b385>] ? kernel_init+0x0/0x1a1 [<c1003d87>] ? kernel_thread_helper+0x7/0x10 that is all i can see and the machine is done, only power off or reset button press restarts the system, this is using pci=nomsi boot option which seemed to work the first time you asked me to try it but not again since that time.
kernel 2.6.30-r8 still boots fine after the SRST failures
Created attachment 220251 [details] dmesg 2.6.31-r6 this is the dmesg for 2.6.30-r8 please note that this is the same for 2.6.31-r6 except for the tail end which i have typed out in comment #11
took message signaled interupts out of the kernel... Put only options needed to boot into the kernel 1. disabled module loading 2. inserted reiserfs file system 3. inserted sata_nv NVidia Sata drivers removed any and all advanced features from the kernel and only provided what was necessary to boot a reiser file system on this machine. this is as basic a kernel as it gets... this kernel will not boot... kernel tells me that it will hard reset the port, then nv tells me that it won't hard reset on an occupied port.
are you able to boot later kernels?
(In reply to comment #15) > are you able to boot later kernels? > sorry, this was a hardware problem that i resolved i think. I changed to other sata ports on the motherboard and the issue went away. I believe the connections on those two ports are bad. I forgot to come back here and report this. thanks for checking back.
