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

Bug#296721: kernel-source-2.6.10: a third instance of unregister_netdevice: waiting for eth0 to become free. Usage count = <integer>



Package: kernel-source-2.6.10
Version: 2.6.10-5
Severity: important


I am experiencing the same symptoms as bugs #291029, #290964 and #291940. This time the device
is just an ordinary eth0 (happens to be a prism54) - no tunnels, bridges or anything. I even
removed all IPv6- and tunneling support from the kernel (that's why my kernel is not Debian's
own kernel-image - the .config is identical except swsusp is turned on and the forementioned
parts off).

This happens almost every time there is a network connection established when I try to ifdown
the interface or remove the pccard or unload the module. I say almost: it looks like only ssh
connections and actively refreshed http-connections actually make this happen. Perhaps those
queues' Recv-Q or Send'Q are non-empty? (A connection established means here that netstat says
it's established.)

The problem sometimes goes away by terminating the offending process - if I can find which one
it is. This does not happen every time, though.

Shutting down works fine, since the processes are terminated before ifdown is run. The problem
is that using ACPI sleep states (swsusp, S3, hibernate etc) take ethernet devices down first
and hang there - with the line in subject.



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (999, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10+juhaj+v1.7
Locale: LANG=C, LC_CTYPE=fi_FI@euro (charmap=ISO-8859-15)

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  bzip2                         1.0.2-5    high-quality block-sorting file co
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 

-- no debconf information



Reply to: