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
--