On Wed, May 07, 2014 at 03:58:53PM +0200, Thomas Petazzoni wrote:
Dear Jason Cooper,
On Wed, 7 May 2014 08:11:30 -0400, Jason Cooper wrote:
iirc, these boot into an initrd. If so, are the errors below an artifact of the boot farm?
Gregory, Thomas, Ezequiel,
If these are legitimate errors, can you please take a look and tell me if anything needs backported?
Weird. I don't think anything has changed in terms of initrd handling recently, at least nothing specific to mvebu platforms. I remember discussing some U-Boot configuration tips at ELC with Kevin. Maybe he has changed his boot scripts/configurations a bit and it breaks on these platforms now? I'd like to hear from Kevin about this.
Also, it's unrelated, but I find the IPMI driver a bit annoying:
IPMI System Interface driver. ipmi_si: Adding default-specified kcs state machine ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <0000000000000ca2-0000000000000ca2> Trying to free nonexistent resource <0000000000000ca3-0000000000000ca3> ipmi_si: Adding default-specified smic state machine ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <0000000000000ca9-0000000000000ca9> Trying to free nonexistent resource <0000000000000caa-0000000000000caa> Trying to free nonexistent resource <0000000000000cab-0000000000000cab> ipmi_si: Adding default-specified bt state machine ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <00000000000000e4-00000000000000e4> Trying to free nonexistent resource <00000000000000e5-00000000000000e5> Trying to free nonexistent resource <00000000000000e6-00000000000000e6> ipmi_si: Unable to find any System Interface(s)
It apparently pokes into random register areas. Seems weird and not very pleasant.
Yes, I noticed that as well. It seemed unrelated to the failure, so I didn't mention it. I'll fire off a separate email.
thx,
Jason.