Bug#687515: Coredumped after wakeup from suspend, mentioning ifconfig
Hello Ben,
thanks for taking the time to look into this.
This special bug has happened alltogether two times. The one time I have
reported this and a day later (friday). Then I upgraded net-tools to
unstable since this was mentioned in the bugreport. After that I had
this coredump no more. But it is only two days since then this is not
finally, I guess.
For configuring the network I use wicd-client. I only have xfce
installed on this machine, so wicd-client is about the only usable gui
for configuring wlan.
I had a similar problem with this machine, again related to suspend.
Don't know if it is related or not, but I'll describe it anyway.
When putting the machine to sleep via closing the lid then every two
days or so the machine used to freeze instead of going to sleep. I then
had to reopen the lid and was presented with an unresponsive X-windows.
Mouse was working, keyboard was almost dead except the commands like
switching to console. Had to press ctrl-alt-f1 to reboot.
I've described this in
"http://forums.debian.net/viewtopic.php?f=5&t=83462";.
At this time I had KDE running on the machine, which I then removed and
switched to xfce. Which did not help. Then I configured the energy
settings so that pressing the power-button performed the suspend to ram.
Since then I no longer have the problem of freezing before suspend. But
now the coredump after wakeup appeared. Sort of trading cholera for
measles...
Since this seems to be related to networking: I often use different wlan
networks. So it can happen that I put the maching to sleep when
connected with wlan a, resume when wlan a is no longer present. Or I put
it to sleep and at the same time turn of my own mobile hotspot, so wlan
is disappearing at this moment.
Anyway, if there is anything I can do then contact me.
Yours,
Gunnar
Reply to: