http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |sfalken@opensuse.org Assignee|bnc-team-screening@forge.pr |trenn@suse.com |ovo.novell.com | --- Comment #1 from Bernhard Wiedemann --- I can not reproduce the error here, even with your initrd. Did you pipe the lsinitrd output somewhere (e.g. less or head)? Can you still reproduce the problem? 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #3 from Per Jessen --- (In reply to Per Jessen from comment #2)

...

Can you still reproduce the problem?

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

Just now tried on a different 13.2 system, same message. with working dir = /boot, I run "lsinitrd initrd-3.16.6-2-desktop". lsinitrd is from dracut-037-17.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #5 from Per Jessen --- (In reply to Bjørn Lie from comment #4)

Per:

Are you by any chance using a scandinavian locale?

Hej Bjørn, haha, not a bad guess, but no, we're using en_GB.utf8. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #9 from Per Jessen --- (In reply to Julian Wolf from comment #8)

Yes, please, if it is possible update your system and let's see whether this still happens.

Okay, system was upgraded with all the latest updates. I now still see the "broken pipe" when I run "lsinitrd" - a) in a konsole window or b) on a virtual console. When logged in via ssh, I see no "broken pipe".

If that still happens after the update you could run lsinitrd with debugging options and provide the ouput so that we at least see at which point that happens:

bash -x lsinitrd $image

I'll attach the output in a minute. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #11 from Julian Wolf --- Thank you for that. The problem in this case appears when extracting the early-microcode in the list_files() function: cat -- testinitrd | cpio --extract --verbose --quiet --list I assume cpio exits after reading the early-microcode (as the rest of the file is a xz archive) which then causes SIGPIPE to be delivered to cat. That's also exactly what I see when checking the exit-code of cat after running above command:

cat -- testinitrd | cpio --extract --verbose --quiet --list [...] echo ${PIPESTATUS[0]} ${PIPESTATUS[1]} 141 0

Exit code 141 (>128) is, afaik, pointing to 128 + Signal-Number, which gives in this case "13 SIGPIPE". Same exit code when running cat and killing it with SIGPIPE manually. So, in my opinion, SIGPIPE is absolutely okay here and the point is more about why the shell (bash?) does report that for you (when running it on a console). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net -- You are receiving this mail because: You are on the CC list for the bug.