Hi Pasi,
> ata_port_alloc: ENTER
> __ata_port_freeze: ata4294967295 port frozen
>
> I guess I have to start reading the source to figure out why the port is
> 'frozen'.. 
Just checked. It is frozen after a bad error that put the port into a
bad state (in order to avoid corruption or any sort of mess I guess).
It is unfrozen after a successful reset.
The code initially freezes a port before probing. That's why it doesn't
even have an id assigned (hence -1 or 4294967295 if you interpret is as
unsigned). Haven't checked, but this message should also appear if
everything works as it should. It starts the probing only after that
message.
So I guess we need a better lead. Would start debugging myself, but I
don't have time...
Cheers,
 Christophe
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel