Re: 2.6.30 et r8169

Pàgina inicial

Reply to this message
Autor: Jerome Kieffer
Data:  
A: guilde
CC: Christian Marillat
Assumpte: Re: 2.6.30 et r8169
On Sun, 27 Sep 2009 12:50:33 +0200
Christian Marillat <marillat@???> wrote:

> Rien de spécial ici avec une Realtek RTL-8169 en 2.6.30-2-amd64 Debian
> qui est un source 2.6.30.7


ici un 2.6.31.1, pour info
eth0 et eth1 = dlink r8169
eth2 = nforce
eth3 = via-rhine

à 13h24 je débranche la via-rhine 100MB pour brancher une des deux r8169
dix minutes plus tard «oups» du kernel alors que je suis en trains de me balader ...

Sep 27 13:24:54 islay kernel: eth3: link down
Sep 27 13:24:54 islay kernel: br0: port 3(eth3) entering disabled state
Sep 27 13:24:54 islay kernel: br0: topology change detected, propagating
Sep 27 13:24:56 islay kernel: r8169: eth0: link up
Sep 27 13:24:56 islay kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 27 13:24:56 islay kernel: br0: port 1(eth0) entering listening state
Sep 27 13:24:58 islay kernel: br0: port 1(eth0) entering learning state
Sep 27 13:25:00 islay kernel: br0: topology change detected, sending tcn bpdu
Sep 27 13:25:00 islay kernel: br0: port 1(eth0) entering forwarding state
Sep 27 13:34:20 islay kernel: ------------[ cut here ]------------
Sep 27 13:34:20 islay kernel: WARNING: at net/sched/sch_generic.c:246 dev_watchdog+0x201/0x210()
Sep 27 13:34:20 islay kernel: Hardware name: K8N
Sep 27 13:34:20 islay kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Sep 27 13:34:20 islay kernel: Modules linked in: xt_length xt_MARK xt_owner cls_fw sch_htb iptable_mangle cpufreq_userspace xt_state xt_tcpudp ipt_REJECT iptable_filter ipt_ULOG ipt_MASQUERADE nf_nat_ftp iptable_nat nf_nat nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables bridge stp llc ipv6 cpufreq_ondemand powernow_k8 freq_table it87 hwmon_vid reiserfs 3c59x sbp2 serio_raw via_rhine ohci1394 r8169 bitrev crc32 ieee1394 psmouse pcspkr k8temp hwmon ide_cd_mod cdrom floppy ehci_hcd ohci_hcd forcedeth usbcore i2c_nforce2 i2c_core
Sep 27 13:34:20 islay kernel: Pid: 0, comm: swapper Not tainted 2.6.31.1-islay #1
Sep 27 13:34:20 islay kernel: Call Trace:
Sep 27 13:34:20 islay kernel: <IRQ> [<ffffffff81229141>] ? dev_watchdog+0x201/0x210
Sep 27 13:34:20 islay kernel: [<ffffffff81229141>] ? dev_watchdog+0x201/0x210
Sep 27 13:34:20 islay kernel: [<ffffffff810349b9>] ? warn_slowpath_common+0x79/0xd0
Sep 27 13:34:20 islay kernel: [<ffffffff81228f40>] ? dev_watchdog+0x0/0x210
Sep 27 13:34:20 islay kernel: [<ffffffff81034a71>] ? warn_slowpath_fmt+0x51/0x60
Sep 27 13:34:20 islay kernel: [<ffffffff8102dc50>] ? activate_task+0x40/0x70
Sep 27 13:34:20 islay kernel: [<ffffffff8113a2d1>] ? strlcpy+0x41/0x50
Sep 27 13:34:20 islay kernel: [<ffffffff8121492b>] ? netdev_drivername+0x3b/0x40
Sep 27 13:34:20 islay kernel: [<ffffffff81229141>] ? dev_watchdog+0x201/0x210
Sep 27 13:34:20 islay kernel: [<ffffffff81044310>] ? delayed_work_timer_fn+0x0/0x20
Sep 27 13:34:20 islay kernel: [<ffffffff8103dbfe>] ? run_timer_softirq+0x10e/0x1c0
Sep 27 13:34:20 islay kernel: [<ffffffff8104aa50>] ? ktime_get_ts+0x30/0x60
Sep 27 13:34:20 islay kernel: [<ffffffff8103951d>] ? __do_softirq+0x8d/0x120
Sep 27 13:34:20 islay kernel: [<ffffffff8100c08a>] ? call_softirq+0x1a/0x30
Sep 27 13:34:20 islay kernel: [<ffffffff8100db6d>] ? do_softirq+0x2d/0x70
Sep 27 13:34:20 islay kernel: [<ffffffff8101d04e>] ? smp_apic_timer_interrupt+0x4e/0x80
Sep 27 13:34:20 islay kernel: [<ffffffff8100bbe3>] ? apic_timer_interrupt+0x13/0x20
Sep 27 13:34:20 islay kernel: <EOI> [<ffffffff8101204a>] ? default_idle+0x3a/0x40
Sep 27 13:34:20 islay kernel: [<ffffffff8100a4bf>] ? cpu_idle+0x3f/0x70
Sep 27 13:34:20 islay kernel: [<ffffffff813e5aed>] ? start_kernel+0x2dc/0x31d
Sep 27 13:34:20 islay kernel: [<ffffffff813e534c>] ? x86_64_start_kernel+0xe1/0xf2
Sep 27 13:34:20 islay kernel: ---[ end trace 293252d76995b357 ]---
Sep 27 13:34:20 islay kernel: r8169: eth0: link up


--
Jérôme KIEFFER
http://www.terre-adelie.org