On Mon, 21 Jul 2008, Ingo Molnar wrote:Ok, it is now a WARN_ON_ONCE() in my tree (which I _just_ pushed out). So it's going to cause irritating messages (once), but the machine should hopefully work. It's going to bisect down to the same commit you already bisected once, it's the networking code that changed some of the rules, so various network drivers that didn't follow the expected rules are now unhappy. Maybe the network drivers are few enough that it will get fixed, or maybe the WARN_ON_ONCE() will just be removed and the rule not reinforced. I personally suspect the latter, since it seems to happen with just about _any_ random network driver, including the common and well-maintained ones (ie the Gods only help us for the truly odd/random cases) Linus -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Kamalesh Babulal | [BUILD-FAILURE] 2.6.26-rc8-mm1 - build failure at drivers/char/hvc_rtas.c |
| Luciano Rocha | usb hdd problems with 2.6.27.2 |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
git: | |
