Ticket #115 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Interface reference counter "leak"

Reported by: dpc Assigned to: xmxwx
Priority: high Milestone: 3.0
Component: Kernel Version: 0.2rc2
Severity: critical Keywords:
Cc:

Description

root@host1:/etc/ifquald.d# /etc/rc.d/rc.eth eth0 restart
Stopping Ethernet interface: eth0
Deleting VLAN device vlan0
[ 9605.233983] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9615.232009] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9625.442268] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9635.648403] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9645.682317] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9655.892388] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1
[ 9666.102614] unregister_netdevice: waiting for vlan0 to become free. Usage count = 1

Change History

10/13/06 19:13:29 changed by xmxwx

Probably the same issue:

root@quirk:~# modprobe -r ath_pci
[  487.003976] unregister_netdevice: waiting for ath0 to become free. Usage count = 1
[  497.246425] unregister_netdevice: waiting for ath0 to become free. Usage count = 1
[  507.488874] unregister_netdevice: waiting for ath0 to become free. Usage count = 1

10/13/06 19:30:54 changed by pjf

  • summary changed from Posible problem with setting down vlan device. to Possible problem when setting down a networking device.
  • milestone set to 3.0.

01/20/07 14:21:00 changed by pjf

  • priority changed from normal to high.
  • summary changed from Possible problem when setting down a networking device to Interface reference counter "leak".
  • component changed from General networking to Kernel.
  • severity changed from normal to critical.
  • milestone changed from 3.0 to 2.1.

Has a duplicate of #145.

02/21/07 00:24:17 changed by xmxwx

  • owner changed from pjf to xmxwx.

The problem seems not to be inflicted by any of Lintrack kernel patches, because it appears to occur even on vanilla 2.6.17.14 and (currently newest) 2.6.20.1 kernel packages. This is a bit surprising. Maybe I am making a mistake somewhere?

02/21/07 00:55:15 changed by xmxwx

  • status changed from new to assigned.

02/25/07 00:56:48 changed by xmxwx

  • status changed from assigned to closed.
  • resolution set to fixed.

fixed in r1231

03/15/08 15:49:29 changed by pjf

  • milestone changed from 2.1rc1 to 3.0.

Milestone 2.1rc1 deleted