change "tcp: randomize tcp timestamp offsets for each connection" broke networking

s (even to localhost) would just time out in many cases. See https://bugzilla.kernel.org/show_bug.cgi?id=194723 for a detailed description and the "git bisect" log. Thanks for considering any fix in advance, best regards, Lutz Vieweg

connect() stalls after 4.9 -> 4.10 upgrade

completely different hardware. Didn't anybody else experience the same symptom? (I also created https://bugzilla.kernel.org/show_bug.cgi?id=194723 on this topic.) Regards, Lutz Vieweg

Re: [PATCH 2/2] staging: rts5139: Use correct USB transfer interval to fix syslog spamming

he SDXC card I was using most was a SanDisk Extreme Pro 64GB SDXC.) Your comment on the change says it is meant to get rid of syslog messages like: "xhci_queue_intr_tx: 74 callbacks suppressed" I do not have such messages, neither with or without the above change. Regards, Lutz Vieweg

Re: What happened to TRIM support for raid linear/0/1/10?

t has to allocate most of the free space on a filesystem for at least a little while (to know what blocks it can discard). Without periodic discard runs, our SSD-equipped servers suffer a ~50% write performance penalty, so this feature is not just a cosmetic issue to us. Regards, Lutz Vieweg

POSIX_FADV_DONTNEED causing excessive amounts of block I/O

is written out the next time it's convenient for the I/O scheduler - but the multiplication of actual I/O is certainly not what the application programmer could have expected, given the documentation of posix_fadvise... Regards, Lutz Vieweg -- To unsubscribe from this list: send the line "unsubscr

Re: select() not returning though pipe became readable

Lutz Vieweg <[EMAIL PROTECTED]> wrote: I'm currently investigating the following problem, which seems to indicate a misbehaviour of the kernel: A server software we implemented is sporadically "hanging" in a select() call since we upgraded from kernel 2.4 to (currently) 2.6.9

Re: select() not returning though pipe became readable

Andrew Morton wrote: Lutz Vieweg <[EMAIL PROTECTED]> wrote: I'm currently investigating the following problem, which seems to indicate a misbehaviour of the kernel: A server software we implemented is sporadically "hanging" in a select() call since we upgraded from kernel 2.4

select() not returning though pipe became readable

Any ideas? Any hints on what to do to investigate the problem further? Regards, Lutz Vieweg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/