1969:1062 network manager would not connect lan after resume from hibernate (wlan works) on dell inspiron 11z

[Hans-Christian Payer]

On my Dell Inspiron 11z resuming from hibernating works, except network manager would not reconnect via eth0. WLAN reconnects without any trouble. Gnome nm-applet icon in tray tried to connect, but obviosly does not get IP throu dhcp and stops with the message: "You are now disconnected from auto-eth0". After reboot it connects without problem to the wirde network (eth0). I tried to restart network-manger when problem after resuming occurred, without any success. Additionally i tried to connect manually via bypassing network manager in configuring /etc/network/interfaces both for dhcp or fixed ip address and restarting network - again without any success. Only rebooting helps to get a wired connection.
I am using Ubuntu 10.04. I reinstalled Win7 to see, if there is the same problem, which is not. Wired Network works well after resuming from hibernate. (I am on Ubuntu again, dont worry...)
lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hans 1813 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0700000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:10ec0272,10280409,00100001 HDA:80862802,80860101,00100000'
   Controls : 18
   Simple ctrls : 9
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=3ce7874c-11d2-4b70-a346-1b66fe0821a4
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Inspiron 1110
NonfreeKernelModules: wl
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic-pae root=/dev/mapper/ubuntu-root ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=de_AT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
Tags: lucid hibernate resume regression-potential needs-upstream-testing
Uname: Linux 2.6.32-22-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0T644R
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/01/2009:svnDellInc.:pnInspiron1110:pvrA06:rvnDellInc.:rn0T644R:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 1110
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.
(With many applications, you can report a future bug directly on the appropriate package by opening the application's "Help" menu and choosing "Report a Problem". https://wiki.ubuntu.com/ReportingBugs)

[Leo Arias (elopio)]

Hans-Christian Payer, thanks for attaching the files to your report. But for future reports please note that on [1] they say:

"These four files should be attached separately to the bug report (not pasted into comments or tar and zipped). Please note that dmesg output should be captured as early as possible after bootup to avoid extraneous output. "

As an alternative, you can run apport-collect 597847

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

At [2] you can find the specific instructions for your problem. Please make sure to answer all the questions that you will find there, and attach the corresponding files.
In case of doubt, don't hesitate to ask commenting this bug.

thanks,
pura vida.

[1] https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Adding%20debug%20info%20to%20a%20bug%20report
[2] https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

apport information

[Hans-Christian Payer (hanspayer)]

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.

[1] http://wiki.ubuntu.com/DebuggingProgramCrash
[2] https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Suspending%20from%20text%20mode
[3] https://wiki.ubuntu.com/DebuggingKernelSuspend

[Hans-Christian Payer (hanspayer)]

Output of dmesg immediately after resuming from suspend.

[Leo Arias (elopio)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[penalvch (penalvch)]

Hans-Christian Payer, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]