[Bug 254412] New: Network is sometimes not correctly restarted after resume
https://bugzilla.novell.com/show_bug.cgi?id=254412 Summary: Network is sometimes not correctly restarted after resume Product: openSUSE 10.3 Version: Alpha 1plus Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Mobile Devices AssignedTo: seife@novell.com ReportedBy: mhopf@novell.com QAContact: qa@suse.de CC: behlert@novell.com On this D410, the network doesn't seem to be correctly restarted after resume. Sometimes (approx. 1 out of 4 tries) the networkmanager tries to get an IP address, and turns up with 169.254.x.x (local ad-hoc network) after a timeout. Explicitly asking the networkmanager to connect to wired network again solves the issue, but this is especially annoying if the screensaver has popped up, because it won't allow you to log in in order to restart network detection, if you are not working on a local account, because YP doesn't work (no network ;), and the screensaver doesn't allow you to log in with the root password (some desktop guys apparently consider this a security feature...). What logs do you need when this happens again? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 ------- Comment #1 from mboman@novell.com 2007-03-14 06:01 MST ------- Log for nm is /var/log/NetworkManager -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com Component|Mobile Devices |Network ------- Comment #3 from seife@novell.com 2007-03-14 07:09 MST ------- this is not a Mobile devices bug, it is a Network Manager bug. We tell NM to suspend and to resume, however, NM does usually do something completely bogus. E.g. starting the wired interface although there is no cable plugged in and other weird stuff. I guess that this bug falls into the same category. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|seife@novell.com |bnc-team-gnome@forge.provo.novell.com Severity|Minor |Normal ------- Comment #4 from mhopf@novell.com 2007-03-14 07:38 MST ------- Agreed. Assigning to networkmanager maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 ------- Comment #5 from mhopf@novell.com 2007-03-14 07:58 MST ------- Created an attachment (id=124331) --> (https://bugzilla.novell.com/attachment.cgi?id=124331&action=view) Logfile of NetworkManager This logfile contains the last two resumes. After the first resume, NetworkManager got a valid IP, after the second it didn't. Especially noteworthy is the line Couldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again later.'. This sounds like a race condition. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |tambet@novell.com |gnome@forge.provo.novell.com| -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical ------- Comment #6 from mhopf@novell.com 2007-04-05 03:37 MST ------- Raising severity, as this doesn't seems to be looked at. Note that sometimes even on boot network isn't correctly detected. This is especially bad for NIS configurations (noone except root can log in to restart network detection). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 ------- Comment #7 from bperry@novell.com 2007-04-18 17:37 MST ------- Isn't this the same as bug 246966? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=254412 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #8 from mhopf@novell.com 2007-04-19 04:05 MST ------- Seems to be. I'll try the rpms there. *** This bug has been marked as a duplicate of bug 246966 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com