Comment # 2 on bug 905863 from Per Jessen

(In reply to Bernhard Wiedemann from comment #1)
> I can not reproduce the error here, even with your initrd.
> 
> Did you pipe the lsinitrd output somewhere (e.g. less or head)?

No, just output to the console. 

> Can you still reproduce the problem?

I'm just reinstalling that system, I'll try it again later. 

> IMHO it might not be a bad one anyway
> because "Broken pipe" only means that someone is writing
> but the output file-descriptor was already closed on the other end.

Yeah, lsinitrd seems to work fine, it just looked odd to me.