[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#433454: marked as done (hibernate: Network stop working after resume)

Your message dated Fri, 26 Dec 2008 14:16:30 +0100
with message-id <20081226131630.GC3622@galadriel.inutil.org>
and subject line Re: hibernate: Network stop working after resume
has caused the Debian Bug report #433454,
regarding hibernate: Network stop working after resume
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
433454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433454
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: hibernate
Version: 1.96~pre-svn.r1125-1
Severity: normal

My network stop working after resume (suspend-to-ram). I have this
network card:

00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)

and I use module forcedeth. I can see this on terminal after resume:

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device

I use eth1 device with forcedeth module. After resume, it try to use
eth0 device (as I can see in dmesg):

PCI: Setting latency timer of device 0000:00:0a.0 to 64
forcedeth: using HIGHDMA
0000:00:0a.0: Invalid Mac address detected: c3:f9:40:e6:16:00
Please complain to your hardware vendor. Switching to a random MAC.
eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:0a.0

but it does not work again (eth0 and eth1 are dead), I can only
restart pc to start network working again. I find only one text
about this on address:

http://lists.atrpms.net/pipermail/atrpms-users/2005-December/004176.html

and the problem is the same, I think. I have tryied module unloading
before suspend too, with no success. I cannot bring up network device
after resume.

Suspend-to-disk works fine.

Thanks for any solution,
Martin Sin.

-- Package-specific info:

--- configuration
==> /etc/hibernate/common.conf <==
Verbosity 0
LogFile /var/log/hibernate.log
LogVerbosity 1
Distribution debian
SaveClock restore-only
UnloadBlacklistedModules yes
LoadModules auto
UpInterfaces auto eth1
SwitchToTextMode yes
==> /etc/hibernate/disk.conf <==
TryMethod ususpend-disk.conf
TryMethod sysfs-disk.conf
==> /etc/hibernate/hibernate.conf <==
TryMethod suspend2.conf
TryMethod disk.conf
TryMethod ram.conf
==> /etc/hibernate/ram.conf <==
TryMethod ususpend-ram.conf
TryMethod sysfs-ram.conf
EnableVbetool yes
VbetoolPost yes
==> /etc/hibernate/suspend2.conf <==
UseSuspend2 yes
Reboot no
EnableEscape yes
DefaultConsoleLevel 1
Compressor lzf
Encryptor none
SuspendDevice swap:/dev/sda1:0x1204dc8
FilewriterLocation /suspend_file 1000
VerifyFilewriterResume2 yes
 ProcSetting userui_program /usr/local/sbin/suspend2ui_text
FullSpeedCPU yes
Include common.conf
==> /etc/hibernate/sysfs-disk.conf <==
UseSysfsPowerState disk
Include common.conf
==> /etc/hibernate/sysfs-ram.conf <==
UseSysfsPowerState mem
Include common.conf
==> /etc/hibernate/ususpend-both.conf <==
USuspendMethod both
Include common.conf
==> /etc/hibernate/ususpend-disk.conf <==
USuspendMethod disk
Include common.conf
==> /etc/hibernate/ususpend-ram.conf <==
USuspendMethod ram
USuspendRamForce yes
Include common.conf

--- /sys/power
==> /sys/power/disk <==
platform
==> /sys/power/image_size <==
524288000
==> /sys/power/resume <==
0:0
==> /sys/power/state <==
mem disk 

--- log
Starting suspend at Út čec 17 12:30:25 CEST 2007
hibernate-ram: [01] Executing CheckLastResume ... 
hibernate-ram: [01] Executing CheckRunlevel ... 
hibernate-ram: [01] Executing LockFileGet ... 
hibernate-ram: [01] Executing NewKernelFileCheck ... 
hibernate-ram: [10] Executing EnsureUSuspendCapable ... 
hibernate-ram: [11] Executing XHacksSuspendHook1 ... 
hibernate-ram: [59] Executing RemountXFSBootRO ... 
hibernate-ram: [60] Executing NetworkStop ... 
hibernate-ram: [89] Executing SaveKernelModprobe ... 
hibernate-ram: [91] Executing ModulesUnloadBlacklist ... 
Some modules failed to unload: nvidia
hibernate-ram: [95] Executing XHacksSuspendHook2 ... 
hibernate-ram: [97] Executing VbetoolSaveState ... 
hibernate-ram: [98] Executing CheckRunlevel ... 
hibernate-ram: [99] Executing DoUSuspend ... 
hibernate-ram: Running /usr/sbin/s2ram  -f ...
hibernate-ram: [97] Executing VbetoolRestoreState ... 
hibernate-ram: [90] Executing ModulesLoad ... 
hibernate-ram: [89] Executing RestoreKernelModprobe ... 
hibernate-ram: [85] Executing XHacksResumeHook2 ... 
hibernate-ram: [70] Executing ClockRestore ... 
hibernate-ram: [60] Executing NetworkStart ... 
hibernate-ram: [59] Executing RemountXFSBootRW ... 
hibernate-ram: [11] Executing XHacksResumeHook1 ... 
hibernate-ram: [01] Executing NoteLastResume ... 
Failed to bring up eth1.
hibernate-ram: [01] Executing LockFilePut ... 
Resumed at Út čec 17 12:30:40 CEST 2007

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages hibernate depends on:
ii  console-tools              1:0.2.3dbs-65 Linux console and font utilities

Versions of packages hibernate recommends:
ii  dash                   0.5.3-7           The Debian Almquist Shell
ii  hdparm                 7.5-1             tune hard disk parameters for high
ii  uswsusp                0.6~cvs20070618-1 tools to use userspace software su
ii  vbetool                0.7-1.1           run real-mode video BIOS code to a

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Fri, Dec 26, 2008 at 01:50:32PM +0100, Martin Šín wrote:
> Hi,
> I bought another network card, so I stopped using this one.
> I am sorry, I cannot verify recent kernel versions for now.

Thanks, closing the bug then.

Cheers,
        Moritz

--- End Message ---
Reply to: