Bug#446832: marked as done (No network after suspend on linux-image-2.6.22-2-k7)
Your message dated Wed, 2 Jul 2008 15:47:13 +0200
with message-id <20080702134713.GE25863@stro.at>
and subject line re: No network after suspend on linux-image-2.6.22-2-k7
has caused the Debian Bug report #446832,
regarding No network after suspend on linux-image-2.6.22-2-k7
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.)
--
446832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446832
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: No network after suspend on linux-image-2.6.22-2-k7
- From: Adalbert Dawid <jagga@rinux.net>
- Date: Tue, 16 Oct 2007 01:38:32 +0200
- Message-id: <1192491512.4373.4.camel@pluto>
Package: linux-image-2.6.22-2-k7
Version: 2.6.22-4
Severity: important
After resuming from suspend there is no network.
'ip add' only outputs the loopback device.
'/etc/init.d/networking restart' doesn't help either.
This bug does not occur with earlier kernel versions (i.e. <=2.6.21).
My machine is an HP compaq nx9005 notebook.
$ lspci | grep -i ether
00:12.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
Please tell me when you need further information.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.22-2-k7 depends on:
ii initramfs-tools [linux-initr 0.90a tools for generating an initramfs
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.22-2-k7 recommends:
ii libc6-i686 2.6.1-1+b1 GNU C Library: Shared libraries [i
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.22-2-k7/preinst/lilo-initrd-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/preinst/lilo-has-ramdisk:
linux-image-2.6.22-2-k7/preinst/already-running-this-2.6.22-2-k7:
linux-image-2.6.22-2-k7/postinst/depmod-error-initrd-2.6.22-2-k7: false
linux-image-2.6.22-2-k7/postinst/kimage-is-a-directory:
linux-image-2.6.22-2-k7/postinst/bootloader-test-error-2.6.22-2-k7:
linux-image-2.6.22-2-k7/postinst/bootloader-error-2.6.22-2-k7:
linux-image-2.6.22-2-k7/preinst/abort-overwrite-2.6.22-2-k7:
linux-image-2.6.22-2-k7/preinst/elilo-initrd-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/prerm/removing-running-kernel-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/preinst/abort-install-2.6.22-2-k7:
linux-image-2.6.22-2-k7/prerm/would-invalidate-boot-loader-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/preinst/failed-to-move-modules-2.6.22-2-k7:
linux-image-2.6.22-2-k7/preinst/overwriting-modules-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/postinst/old-system-map-link-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/postinst/create-kimage-link-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/preinst/bootloader-initrd-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/postinst/depmod-error-2.6.22-2-k7: false
linux-image-2.6.22-2-k7/postinst/old-initrd-link-2.6.22-2-k7: true
linux-image-2.6.22-2-k7/preinst/initrd-2.6.22-2-k7:
linux-image-2.6.22-2-k7/postinst/old-dir-initrd-link-2.6.22-2-k7: true
--- End Message ---
--- Begin Message ---
- To: 446832-done@bugs.debian.org
- Subject: re: No network after suspend on linux-image-2.6.22-2-k7
- From: maximilian attems <max@stro.at>
- Date: Wed, 2 Jul 2008 15:47:13 +0200
- Message-id: <20080702134713.GE25863@stro.at>
Version: 2.6.24-1
closing as we have no longer a k7 image, but 686 should work fine
and no longer have that behaviour.
thanks for the report
--
maks
--- End Message ---
Reply to: