> So my questions are:
> • Is this just an unlucky flash problem or could there be something
> more sinister?
Your logs seem to show flash issues:
--
kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
kernel: ata1: irq_stat 0x00400000, PHY RDY changed
kernel: ata1: SError: { RecovComm Persist PHYRdyChg 10B8B }
kernel: ata1: hard resetting link
kernel: ata1: SATA link down (SStatus 0 SControl 300)
kernel: ata1: hard resetting link
--
Though your hard reboot forced a e2fsck and seemed to (temporarily ?) fix
things.
On my healthy APU2, the "ata1" logs should be minimal:
--
pbx4 ~ # dmesg | grep ata1
[ 0.942110] ata1: SATA max UDMA/133 abar m1024@0xfeb25000 port 0xfeb25100
irq 19
[ 1.263014] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.268165] ata1.00: ATA-10: SB mSATA SSD, S9FM02.8, max UDMA/133
[ 1.272969] ata1.00: 31277232 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.279020] ata1.00: configured for UDMA/133
--
> • Why did it need to do a Memtest when it rebooted. Is this a BiOS
> thing?
>
Judging by the "Memtest86+ 5.01 coreboot" version, that is a part of the
coreboot BIOS of the APU2 ... somehow it got triggered, usually a keypress,
possibly random noise off the serial cable.
BTW, once Memtest86+ is started to runs forever until the <ESC> or such key is
hit.
Not related, but for production I like to comment-out the /etc/rc.modules NIC
drivers that are not used.
For the APU2's /etc/rc.modules (edit directly) only the "igb" NIC is needed,
you can comment-out the others.
Lonnie
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
