Hi Thorsten, Ben Hutchings wrote:
> Affected: > 1. e1000e on 2.6.32 connecting to site on different network segment > 2. e1000e backport from 2.6.38 connecting to site on different network > segment > > Not affected: > 3. e1000e on 2.6.26 > 4. e1000e on 2.6.32 connecting to site on same network segment > 5. e1000e on 2.6.32 during first few minutes after boot > 6. e1000e on 2.6.39 > 7. r8169 on 2.6.32 (not same system) > > Case 7 strongly suggests that this issue is related to the driver or the > environment and not the stack (or not only the stack). But then there > don't seem to be any relevant changes to this driver between 2.6.38 and > 2.6.39, so why the difference beween cases 2 and 6? > > Case 5 is interesting. Is there some service started at boot, that may > start to access the network after a few minutes? In cases 3 and 6, did > you test in the first few minutes after boot, or did you wait a while? I was looking back over this bug and don't see the answer to that last question in the log. Could you provide it? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
