On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > Hi, > > I ugraded my laptop from sources to -current yesterday. Since then > firefox stops resolving host names after a dozen of minutes or so.
What do you mean with "stops resolving host names"? What happens? What do you see? How did figure out it was a name resolution problem? A firefox error page? You saw some syscalls failing via ktrace? You looked at tcpdump outputs? Some network counters were increasing? > It's not the firefox port itself, since it started after I rebooted a > the new kernel, while base and xenocara were rebuilding. My previous > kernel was from jan, 31. So you're saying that *some* kernels newer than jan, 31 expose this regression? Could you bisect when it has been introduced? > Other programs are fine (including chromium), but appart may be chromium > nothing I run is using threads and name resolution at the same time . You're assuming it's related to threaded applications, why? > Any idea of what's causing this, or should I start bisecting ? A bisection would be great.
