Leo Arias, thanks for your response.
Here is the Information you requested:
As i dont know which program crashes, it is not easy for me to do a backtrace as mentioned in [1], because the problem occurs both with network manager and without.
The machine "breakes" while waking up. When I tried to reproduce the problem, i recognized, the it it was not more present after recovering from hibernation (S4 - Suspend to Disk). eth0 worked perfectly and could get its ip from dhcp via nm and tho old fashioned way via /etc/network/interfaces. I tried that 10 times and it always worked perfectly. As i mentioned i did a fresh install of 10.04 after i checked if STR and STD works with 'Windows7', which did.
The Problem still occures after resuming from suspend (S3 - Suspend to RAM), which i reproduced 10 times. eth0 is trying to connect, but will fail to do so, both with and without network-manager. So I will continue with the steps in [2]
sudo pm-suspend gave no information, only effect, eth0 fails to connect.
Then i did the "resume-trace" debugging procedure for finding buggy drivers as described in [3]. resuming worked, besides eth0 was not able to get an ip again. The resulting dmesg.txt you ll find attached.
Leo Arias, thanks for your response. interfaces. I tried that 10 times and it always worked perfectly. As i mentioned i did a fresh install of 10.04 after i checked if STR and STD works with 'Windows7', which did.
Here is the Information you requested:
As i dont know which program crashes, it is not easy for me to do a backtrace as mentioned in [1], because the problem occurs both with network manager and without.
The machine "breakes" while waking up. When I tried to reproduce the problem, i recognized, the it it was not more present after recovering from hibernation (S4 - Suspend to Disk). eth0 worked perfectly and could get its ip from dhcp via nm and tho old fashioned way via /etc/network/
The Problem still occures after resuming from suspend (S3 - Suspend to RAM), which i reproduced 10 times. eth0 is trying to connect, but will fail to do so, both with and without network-manager. So I will continue with the steps in [2]
sudo pm-suspend gave no information, only effect, eth0 fails to connect.
Then i did the "resume-trace" debugging procedure for finding buggy drivers as described in [3]. resuming worked, besides eth0 was not able to get an ip again. The resulting dmesg.txt you ll find attached.
[1] http:// wiki.ubuntu. com/DebuggingPr ogramCrash /wiki.ubuntu. com/DebuggingKe rnelSuspendHibe rnateResume# Suspending% 20from% 20text% 20mode /wiki.ubuntu. com/DebuggingKe rnelSuspend
[2] https:/
[3] https:/