Hi. Can you provide more details for this BTS report? Did fping fail to work when the kernel emitted this message, or did it retry and succeed after the fact? Was the machine running low on memory? Did it have much load? How did you call fping (which arguments)? In short, how can the issue you saw be reproduced?
Why do you believe this is a bug in fping and not the kernel? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
