* Ingo Molnar <[EMAIL PROTECTED]> wrote: > > i'll now check whether removing ignore_on_loglevel (no other > > changes) makes the hang go away. Maybe ignore_on_loglevel is buggy - > > or it produces an immediate printk (going out to the interface) > > during a particularly sensitive period of network initialization. > > nope, that didnt have any effect. I have another theory: i had a > network-intense stress-test going on in the past few hours on the same > network (not involving the laptop) and i stopped it recently. Perhaps > that network-intense test also produced periodic broadcast packets > that got the e1000 out of its weird state before the tx timeout could > hit. Now that i've stopped the test, the network is quiescent again > and the e1000 hangs.
yep - i can confirm this theory now: if i start a broadcast ping on another box while the laptop is booting up, the network hang does not happen. If i stop the ping and do another bootup with the very same kernel, it hangs. So for the hang to happen, the network has to be very quiet. At least one mystery solved :-/ Ingo - 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/