On Tue, 27 May 2008, Alejandro Riveira Fernández wrote:Can you give more details about where it stops? .. again, please give the full oops, without that we just know that "an oops happened". I assume it's related to the oops above - the oops probably happened while holding some mutex or other lock, which is why network-related stuff then blocks on that lock (which will never be released, since the oops killed the process that held it). I suspect the oops is also why the bootup breaks, so it's likely all the same issue. Please save the dmesg into a file, reboot into a working setup, and send that. Along with hw information (it's likely related to your network device driver, since I've not seen an uproar of these kinds of problems from everybody else..). More details, please, again. Linus --
| Linus Torvalds | Re: LSM conversion to static interface |
| Ingo Molnar | [patch 03/13] syslets: generic kernel bits |
| Ingo Molnar | Re: [PATCH 6/6] sched: disabled rt-bandwidth by default |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| David Miller | [GIT]: Networking |
| Gregory Haskins | [RFC PATCH 00/17] virtual-bus |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
