Boot very slow and plenty of error messages

PTBM133A4X · 2015-03-26 20:58:21

I recently upgraded my motherboard BIOS and after rebooting I noticed some error messages appearing - similar to these:

10.793182] ata1: SRST failed (errno=-16)
[   10.793679] ata2: SRST failed (errno=-16)
[   10.793723] ata7: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   10.793725] ata7: irq_stat 0x00400000, PHY RDY changed
[   10.793726] ata7: SError: { PHYRdyChg }
[   10.793730] ata7: hard resetting link
[   10.796043] ata8: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   10.796883] ata8: irq_stat 0x00400000, PHY RDY changed
[   10.797472] ata8: SError: { PHYRdyChg }

Even though these errors were showing on screen (and a lot of ACPI messages in dmesg), the boot process continued non-stop. Then just a few days ago there was a kernel update. Since then my booting takes about 1 minute to get passed these errors. First the above messages show, then these:

20.803461] ata1: SRST failed (errno=-16)
[   20.803957] ata2: SRST failed (errno=-16)
[   20.804000] ata7: limiting SATA link speed to 1.5 Gbps
[   20.804003] ata7: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   20.804004] ata7: irq_stat 0x00400000, PHY RDY changed
[   20.804005] ata7: SError: { PHYRdyChg }
[   20.804009] ata7: hard resetting link
[   20.806341] ata8: limiting SATA link speed to 1.5 Gbps
[   20.806347] ata8: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   20.807184] ata8: irq_stat 0x00400000, PHY RDY changed
[   20.807773] ata8: SError: { PHYRdyChg }

and then a third batch of errors:

55.802807] ata1: SRST failed (errno=-16)
[   55.803272] ata1: limiting SATA link speed to 1.5 Gbps
[   55.803295] ata2: SRST failed (errno=-16)
[   55.803353] ata7.00: limiting speed to UDMA/100:PIO4
[   55.803356] ata7: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   55.803357] ata7: irq_stat 0x00400000, PHY RDY changed
[   55.803359] ata7: SError: { PHYRdyChg }
[   55.803362] ata7: hard resetting link
[   55.805629] ata2: limiting SATA link speed to 1.5 Gbps
[   55.805708] ata8.00: limiting speed to UDMA/100:PIO4
[   55.805713] ata8: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   55.806553] ata8: irq_stat 0x00400000, PHY RDY changed
[   55.807142] ata8: SError: { PHYRdyChg }

In between the batches of errors there are heaps of ACPI errors:

11.517786] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20141107/psargs-359)
[   11.517795] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff8802160be230), AE_NOT_FOUND (20141107/psparse-536)
[   11.518871] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20141107/psargs-359)
[   11.518880] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8802160be1b8), AE_NOT_FOUND (20141107/psparse-536)
[   11.519970] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20141107/psargs-359)
[   11.519979] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff8802160be230), AE_NOT_FOUND (20141107/psparse-536)
[   11.520077] ata8.00: configured for UDMA/133
[   11.520083] ata8: EH complete
[   11.525663] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20141107/psargs-359)
[   11.525672] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff8802160be1b8), AE_NOT_FOUND (20141107/psparse-536)

The above errors are repeated in-between each batch of ata error messages. I've tried replacing one or two SATA cables and removing surplus drives but makes no difference.

Could someone offer any advice?

Knute · 2015-03-26 21:05:39

After flashing your bios, did you reset it so that it can reinitialize all the variables?

PTBM133A4X · 2015-03-26 21:08:59

You mean reset the computer?

After the BIOS update the computer reset itself once or twice.

Knute · 2015-03-26 21:21:43

No. I mean reset the bios or cmos. There are 2 ways to do it. Most bios's that I have seen have a "Reset CMOS" or something similar in the bios itself. The other is a jumper on the motherboard.

PTBM133A4X · 2015-03-26 21:29:41

Mmmm no I didn't reset the BIOS. I didn't think that was necessary. I'll give it a try and see if it helps any.

alphaniner · 2015-03-26 21:30:15

In my experience flashing the BIOS results in either an automatic reset to defaults or a prompt (at the very end of POST) to reset it or enter the BIOS configuration.

And I've never seen a BIOS configuration that didn't have a 'reset to defaults' option, so unless you can't get into the BIOS configuration there's usually no need to use the jumper to reset.

PTBM133A4X · 2015-03-26 21:39:49

After the update the BIOS was back to a default state, for example SATA 1-6 were not in AHCI mode (as they were before the update), the boot priority had changed etc. I'll maybe try clearing it again to be sure. It just seems strange that the recent kernel update caused the boot process to slow to a crawl.

Knute · 2015-03-26 21:44:26

If you know what those settings were before, you might try setting them back to what they were before.

PTBM133A4X · 2015-03-26 21:52:24

I have done so already as the computer wouldn't boot with the HDs not in AHCI mode. I've been through the BIOS several times to see if something is not as it was before but I can't see anything obvious.

PTBM133A4X · 2015-03-26 22:15:01

Just reset BIOS and still the same.

Knute · 2015-03-26 22:51:19

So then it's probably not the bios. Have you tried recompiling the kernel again?

I ask, because I've noticed that sometimes when the kernel is upgrading, it ends up not compiling everything due to the headers not being there.

Šaran · 2015-03-26 23:25:21

Can you tell us which motherboard and HDD(s) you are using?
My educated guess would be that motherboard supports only SATA 1, while
drive is SATA 2 or 3. Are there any jumpers on HDD?

A while back I had to
put jumper on HDD to SATA 1 mode in order to get recognized by motherboard.
Drives without mode switch jumper wouldn't even show up in BIOS.

@Knute, I don't think he is running custom kernel, and not having headers installed
really isn't necessary for running vanilla Arch kernel.

Knute · 2015-03-26 23:41:30

@Saran, I wasn't talking about a custom kernel. I use yaourt for installing/upgrading packages, and when it comes to a kernel upgrade, linux is installed and mkinitcpio is called, and then the headers are installed afterwards. mkinitcpio generates an error message that not everything may have been compiled or that the image may be incomplete. To avoid that problem, I just run mkinitcpio myself afterwards and haven't worried about it.
But it's good to know that they aren't critical for it to run.

Arch Linux

#1 2015-03-26 20:58:21

Boot very slow and plenty of error messages

#2 2015-03-26 21:05:39

Re: Boot very slow and plenty of error messages

#3 2015-03-26 21:08:59

Re: Boot very slow and plenty of error messages

#4 2015-03-26 21:21:43

Re: Boot very slow and plenty of error messages

#5 2015-03-26 21:29:41

Re: Boot very slow and plenty of error messages

#6 2015-03-26 21:30:15

Re: Boot very slow and plenty of error messages

#7 2015-03-26 21:39:49

Re: Boot very slow and plenty of error messages

#8 2015-03-26 21:44:26

Re: Boot very slow and plenty of error messages

#9 2015-03-26 21:52:24

Re: Boot very slow and plenty of error messages

#10 2015-03-26 22:15:01

Re: Boot very slow and plenty of error messages

#11 2015-03-26 22:51:19

Re: Boot very slow and plenty of error messages

#12 2015-03-26 23:25:21

Re: Boot very slow and plenty of error messages

#13 2015-03-26 23:41:30

Re: Boot very slow and plenty of error messages

Board footer