Bug#549606: [linux-image-2.6.30-1-amd64] VIA-Rhine II network interface lost connectivity
Antonio Marcos López Alonso
Version: 2.6.30-6
Severity: important
--- Please enter the report below this line. ---
I own an Asus A8VM SE motherboard with an integrated VIA-Rhine II ethernet
interface.
Now and then network connectivity is totally lost (having to reboot),
specially whenever there is not a continuous network traffic flow (i.e. P2P
connections), but sometimes even in that condition. Passing either irqfixup or
irqpoll options to the kernel help a bit but not fix the problem.
dmesg output:
[ 5691.816016] ------------[ cut here ]------------
[ 5691.816026] WARNING: at /build/buildd-linux-2.6_2.6.30-6-amd64-
s9DPiZ/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226
dev_watchdog+0xc7/0x164()
[ 5691.816030] Hardware name: System Product Name
[ 5691.816032] NETDEV WATCHDOG: eth0 (via-rhine): transmit timed out
[ 5691.816034] Modules linked in: xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE
xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state nvidia(P) ppdev
lp vboxnetadp vboxnetflt vboxdrv powernow_k8 cpufreq_powersave cpufreq_stats
cpufreq_userspace cpufreq_conservative iptable_nat nf_nat nf_conntrack_ipv4
nf_conntrack nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables x_tables
xfs exportfs fuse w83627ehf hwmon_vid loop mt2060 snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device
snd serio_raw pcspkr evdev soundcore snd_page_alloc dvb_usb_dib0700 dib7000p
dib7000m dvb_usb psmouse usblp k8temp dvb_core dib3000mc dibx000_common
dib0070 i2c_viapro i2c_core asus_atk0110 processor button parport_pc parport
shpchp pci_hotplug reiserfs sd_mod crc_t10dif ide_cd_mod cdrom ata_generic
ide_pci_generic sata_via via82cxxx libata via_rhine mii uhci_hcd ide_core
scsi_mod ehci_hcd floppy thermal fan thermal_sys [last unloaded:
scsi_wait_scan]
[ 5691.816102] Pid: 0, comm: swapper Tainted: P 2.6.30-1-amd64 #1
[ 5691.816104] Call Trace:
[ 5691.816106] <IRQ> [<ffffffff804231b6>] ? dev_watchdog+0xc7/0x164
[ 5691.816114] [<ffffffff804231b6>] ? dev_watchdog+0xc7/0x164
[ 5691.816119] [<ffffffff8024237f>] ? warn_slowpath_common+0x77/0xa3
[ 5691.816123] [<ffffffff804230ef>] ? dev_watchdog+0x0/0x164
[ 5691.816126] [<ffffffff80242407>] ? warn_slowpath_fmt+0x51/0x59
[ 5691.816131] [<ffffffff802342fe>] ? enqueue_task+0x5c/0x65
[ 5691.816136] [<ffffffff8024accf>] ? lock_timer_base+0x26/0x4c
[ 5691.816139] [<ffffffff804230c3>] ? netif_tx_lock+0x3d/0x69
[ 5691.816144] [<ffffffff8040fb8c>] ? netdev_drivername+0x3b/0x40
[ 5691.816147] [<ffffffff804231b6>] ? dev_watchdog+0xc7/0x164
[ 5691.816151] [<ffffffff804230ef>] ? dev_watchdog+0x0/0x164
[ 5691.816154] [<ffffffff8024aa63>] ? run_timer_softirq+0x193/0x210
[ 5691.816159] [<ffffffff8025b4d5>] ? getnstimeofday+0x55/0xaf
[ 5691.816163] [<ffffffff80246f85>] ? __do_softirq+0xac/0x173
[ 5691.816167] [<ffffffff80210bcc>] ? call_softirq+0x1c/0x30
[ 5691.816171] [<ffffffff802125fa>] ? do_softirq+0x3a/0x7e
[ 5691.816174] [<ffffffff80246d02>] ? irq_exit+0x3f/0x80
[ 5691.816178] [<ffffffff80220e73>] ? smp_apic_timer_interrupt+0x87/0x94
[ 5691.816181] [<ffffffff802105d3>] ? apic_timer_interrupt+0x13/0x20
[ 5691.816183] <EOI> [<ffffffff8064e140>] ? early_idt_handler+0x0/0x71
[ 5691.816190] [<ffffffff80256fa5>] ? hrtimer_cancel+0xc/0x16
[ 5691.816194] [<ffffffff80227520>] ? native_safe_halt+0x2/0x3
[ 5691.816198] [<ffffffff80216995>] ? default_idle+0x40/0x68
[ 5691.816201] [<ffffffff8064e140>] ? early_idt_handler+0x0/0x71
[ 5691.816206] [<ffffffff8020edda>] ? cpu_idle+0x50/0x91
[ 5691.816209] [<ffffffff8064ec62>] ? start_kernel+0x37a/0x386
[ 5691.816212] [<ffffffff8064e3b7>] ? x86_64_start_kernel+0xf9/0x106
[ 5691.816215] ---[ end trace 5e95d6a18d9da96e ]---
[ 5691.816364] eth0: Transmit timed out, status 1003, PHY status 786d,
resetting...
[ 5691.817078] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5695.816214] eth0: Transmit timed out, status 1003, PHY status 786d,
resetting...
[ 5695.816930] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5699.816182] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5699.816873] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5703.816166] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5703.816858] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5707.816184] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5707.816910] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5711.816177] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5711.816874] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5715.816189] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5715.816930] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5719.816175] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5719.816865] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5723.816178] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5723.816916] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5727.816173] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5727.816868] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5731.816175] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5731.816917] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5735.816177] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5735.816876] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5739.816169] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5739.816827] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5743.816184] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5743.816889] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5747.816166] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5747.816819] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5751.816161] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5751.816869] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5755.816165] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5755.816861] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5759.816165] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5759.816819] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5763.816205] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5763.816912] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5767.816164] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5767.816817] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5771.816204] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5771.816910] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 5775.816170] eth0: Transmit timed out, status 0003, PHY status 786d,
resetting...
[ 5775.816870] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
*******************************************************
I would gladly send further info upon request.
Kind regards,
Antonio
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.30-1-amd64
Debian Release: squeeze/sid
600 testing www.debian-multimedia.org
600 testing security.debian.org
600 testing ftp.es.debian.org
550 unstable www.debian-multimedia.org
550 unstable ftp.es.debian.org
500 stable dl.google.com
500 sid www.lamaresh.net
--- Package information. ---
Depends (Version) | Installed
=====================================-+-=============
module-init-tools | 3.10-3
initramfs-tools (>= 0.55) | 0.93.4
OR yaird (>= 0.0.13) |
OR linux-initramfs-tool |
Package's Recommends field is empty.
Suggests (Version) | Installed
===============================-+-===========
linux-doc-2.6.30 |
grub | 0.97-58
OR lilo |
-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
/tmp/reportbug-ng-linux-image-2.6.30-1-amd64-cpIOIO.txt
to the mail. I'd do it myself if the output wasn't too long to handle.
Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--
Ben Hutchings
> Package: linux-image-2.6.30-1-amd64
> Version: 2.6.30-6
> Severity: important
>
> --- Please enter the report below this line. ---
> I own an Asus A8VM SE motherboard with an integrated VIA-Rhine II ethernet
> interface.
>
> Now and then network connectivity is totally lost (having to reboot),
> specially whenever there is not a continuous network traffic flow (i.e. P2P
> connections), but sometimes even in that condition. Passing either irqfixup or
> irqpoll options to the kernel help a bit but not fix the problem.
Is this a new problem or did it occur with earlier kernel versions?
Can you try to reproduce this without the nvidia or virtualbox modules
loaded?
Ben.
--
Ben Hutchings
I say we take off; nuke the site from orbit. It's the only way to be sure.
Jens-Michael Hoffmann
> On Sun, 2009-10-04 at 20:36 +0100, Antonio Marcos López Alonso wrote:
> > Package: linux-image-2.6.30-1-amd64
> > Version: 2.6.30-6
> > Severity: important
> >
> > --- Please enter the report below this line. ---
> > I own an Asus A8VM SE motherboard with an integrated VIA-Rhine II
> > ethernet interface.
> >
> > Now and then network connectivity is totally lost (having to reboot),
> > specially whenever there is not a continuous network traffic flow (i.e.
> > P2P connections), but sometimes even in that condition. Passing either
> > irqfixup or irqpoll options to the kernel help a bit but not fix the
> > problem.
>
> [...]
>
> Is this a new problem or did it occur with earlier kernel versions?
>
> Can you try to reproduce this without the nvidia or virtualbox modules
> loaded?
I think I'm experiencing the same problem, however with linux-image-2.6.30-bpo.1-amd64.
Oct 4 22:42:01 histor2 kernel: [11731.804020] ------------[ cut here ]------------
Oct 4 22:42:01 histor2 kernel: [11731.804060] WARNING: at /tmp/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226 dev_watc
hdog+0xc7/0x164()
Oct 4 22:42:01 histor2 kernel: [11731.804107] Hardware name: SK22V10
Oct 4 22:42:01 histor2 kernel: [11731.804127] NETDEV WATCHDOG: eth2 (via-rhine): transmit timed out
Oct 4 22:42:01 histor2 kernel: [11731.804151] Modules linked in: iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ppdev parport_pc lp parport
cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc powernow_k8 loop snd_pcm snd_timer snd soundcore
snd_page_alloc i2c_viapro k8temp pcspkr evdev i2c_core processor button shpchp pci_hotplug ext3 jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mirror
dm_region_hash dm_log dm_snapshot dm_mod raid10 raid456 raid6_pq async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod sd_mod crc_t10dif ide_cd_mod cdrom
ide_pci_generic via82cxxx ide_core sata_via ata_generic libata via_rhine ehci_hcd uhci_hcd scsi_mod 8139too firewire_ohci firewire_core crc_itu_t 8139cp mii thermal fan thermal_sys [last
unloaded: scsi_wait_scan]
Oct 4 22:42:01 histor2 kernel: [11731.804551] Pid: 0, comm: swapper Not tainted 2.6.30-bpo.1-amd64 #1
Oct 4 22:42:01 histor2 kernel: [11731.804576] Call Trace:
Oct 4 22:42:01 histor2 kernel: [11731.804595] <IRQ> [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 4 22:42:01 histor2 kernel: [11731.804629] [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 4 22:42:01 histor2 kernel: [11731.804659] [<ffffffff80242387>] ? warn_slowpath_common+0x77/0xa3
Oct 4 22:42:01 histor2 kernel: [11731.804687] [<ffffffff80423477>] ? dev_watchdog+0x0/0x164
Oct 4 22:42:01 histor2 kernel: [11731.804714] [<ffffffff8024240f>] ? warn_slowpath_fmt+0x51/0x59
Oct 4 22:42:01 histor2 kernel: [11731.804743] [<ffffffff802342fe>] ? enqueue_task+0x5c/0x65
Oct 4 22:42:01 histor2 kernel: [11731.804771] [<ffffffff8025474b>] ? autoremove_wake_function+0x9/0x2e
Oct 4 22:42:01 histor2 kernel: [11731.804799] [<ffffffff8042344b>] ? netif_tx_lock+0x3d/0x69
Oct 4 22:42:01 histor2 kernel: [11731.804827] [<ffffffff8040fef0>] ? netdev_drivername+0x3b/0x40
Oct 4 22:42:01 histor2 kernel: [11731.804854] [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 4 22:42:01 histor2 kernel: [11731.804881] [<ffffffff80230065>] ? gup_huge_pmd+0x36/0x94
Oct 4 22:42:01 histor2 kernel: [11731.804908] [<ffffffff80423477>] ? dev_watchdog+0x0/0x164
Oct 4 22:42:01 histor2 kernel: [11731.804936] [<ffffffff8024aa6f>] ? run_timer_softirq+0x193/0x210
Oct 4 22:42:01 histor2 kernel: [11731.804966] [<ffffffff8025b4d1>] ? getnstimeofday+0x55/0xaf
Oct 4 22:42:01 histor2 kernel: [11731.804993] [<ffffffff80246f91>] ? __do_softirq+0xac/0x173
Oct 4 22:42:01 histor2 kernel: [11731.805021] [<ffffffff80210bcc>] ? call_softirq+0x1c/0x30
Oct 4 22:42:01 histor2 kernel: [11731.805048] [<ffffffff802125fa>] ? do_softirq+0x3a/0x7e
Oct 4 22:42:01 histor2 kernel: [11731.805073] [<ffffffff80246d0e>] ? irq_exit+0x3f/0x80
Oct 4 22:42:01 histor2 kernel: [11731.805100] [<ffffffff80220e63>] ? smp_apic_timer_interrupt+0x87/0x94
Oct 4 22:42:01 histor2 kernel: [11731.805127] [<ffffffff802105d3>] ? apic_timer_interrupt+0x13/0x20
Oct 4 22:42:01 histor2 kernel: [11731.805152] <EOI> [<ffffffff80227520>] ? native_safe_halt+0x2/0x3
Oct 4 22:42:01 histor2 kernel: [11731.805186] [<ffffffff80216995>] ? default_idle+0x40/0x68
Oct 4 22:42:01 histor2 kernel: [11731.805213] [<ffffffff80257d0d>] ? notifier_call_chain+0x29/0x4c
Oct 4 22:42:01 histor2 kernel: [11731.805240] [<ffffffff80216d6a>] ? c1e_idle+0x107/0x10d
Oct 4 22:42:01 histor2 kernel: [11731.805268] [<ffffffff8020edda>] ? cpu_idle+0x50/0x91
Oct 4 22:42:01 histor2 kernel: [11731.805292] ---[ end trace 8ae589af262f9af9 ]---
Oct 4 22:42:01 histor2 kernel: [11731.805460] eth2: Transmit timed out, status 1003, PHY status 786d, resetting...
Oct 4 22:42:01 histor2 kernel: [11731.806253] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 4 22:42:05 histor2 kernel: [11735.804167] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 4 22:42:05 histor2 kernel: [11735.804966] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 4 22:42:09 histor2 kernel: [11739.804164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 4 22:42:09 histor2 kernel: [11739.804958] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 4 22:42:13 histor2 kernel: [11743.804164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 4 22:42:13 histor2 kernel: [11743.804963] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 4 22:42:17 histor2 kernel: [11747.804163] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 4 22:42:17 histor2 kernel: [11747.804958] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
If you need more information, please do not hesitate to ask.
Best Regards,
Jens-Michael
--
To UNSUBSCRIBE, email to debian-ker...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Antonio Marcos López Alonso
No, it happened also in previous versions. But at least irqpoll/irqfixup
worked pretty well. Now this behavior seems to get worsened even using these
kernel options.
>
> Can you try to reproduce this without the nvidia or virtualbox modules
> loaded?
I can but just to make things faster:
Jens-Michael,
Have you got any nvidia/virtualbox modules running in your host? Just to
discard...
Antonio.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
Jens-Michael Hoffmann
> > Is this a new problem or did it occur with earlier kernel versions?
>
> No, it happened also in previous versions. But at least irqpoll/irqfixup
> worked pretty well. Now this behavior seems to get worsened even using
> these kernel options.
>
> > Can you try to reproduce this without the nvidia or virtualbox modules
> > loaded?
>
> I can but just to make things faster:
>
> Jens-Michael,
>
> Have you got any nvidia/virtualbox modules running in your host? Just to
> discard...
no, neither nvidia nor virtualbox.
Best regards,
Jens-Michael
Ben Hutchings
> > Is this a new problem or did it occur with earlier kernel versions?
>
> No, it happened also in previous versions. But at least irqpoll/irqfixup
> worked pretty well. Now this behavior seems to get worsened even using these
> kernel options.
>
> >
> > Can you try to reproduce this without the nvidia or virtualbox modules
> > loaded?
>
> I can but just to make things faster:
>
> Jens-Michael,
>
> Have you got any nvidia/virtualbox modules running in your host? Just to
> discard...
The warning message shows all loaded modules, and those aren't included,
so this question is answered.
I had a look at the code and the values in the 'transmit timed out'
message, and it seems that the NIC has reported a transmit completion
but this hasn't been handled. Perhaps another device sharing its IRQ is
misbehaving and causing the IRQ to be disabled. Please can you send
more of the kernel log from before the TX watchdog warning? Also, if
this happens again, please send the contents of /proc/interrupts.
Jens-Michael Hoffmann
/proc/interrupts:
CPU0 CPU1
0: 42 0 IO-APIC-edge timer
1: 0 82 IO-APIC-edge i8042
8: 0 0 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
14: 0 109 IO-APIC-edge ide0
17: 5 581 IO-APIC-fasteoi firewire_ohci
18: 350432 19112694 IO-APIC-fasteoi eth1
20: 6365 143067 IO-APIC-fasteoi sata_via
21: 0 0 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, uhci_hcd:usb5
23: 150373 6348653 IO-APIC-fasteoi eth2
NMI: 0 0 Non-maskable interrupts
LOC: 1346329 1327512 Local timer interrupts
SPU: 0 0 Spurious interrupts
RES: 835039 35715 Rescheduling interrupts
CAL: 89 110 Function call interrupts
TLB: 782 741 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
ERR: 2
MIS: 0
kern.log:
Oct 5 04:07:43 histor2 kernel: [ 1244.566658] martian source 87.193.192.142 from 117.192.224.4, on dev eth2
Oct 5 04:07:43 histor2 kernel: [ 1244.566731] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 04:07:44 histor2 kernel: [ 1245.341532] martian source 87.193.192.142 from 125.161.193.46, on dev eth2
Oct 5 04:07:44 histor2 kernel: [ 1245.341605] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 04:07:45 histor2 kernel: [ 1246.937539] martian source 87.193.192.142 from 130.15.19.206, on dev eth2
Oct 5 04:07:45 histor2 kernel: [ 1246.937609] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 04:08:04 histor2 kernel: [ 1265.481435] martian source 87.193.192.142 from 93.88.4.171, on dev eth2
Oct 5 04:08:04 histor2 kernel: [ 1265.481508] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 04:08:07 histor2 kernel: [ 1268.517808] martian source 87.193.192.142 from 93.88.4.171, on dev eth2
Oct 5 04:08:07 histor2 kernel: [ 1268.517882] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 04:08:09 histor2 kernel: [ 1270.940643] martian source 87.193.192.142 from 130.15.19.206, on dev eth2
Oct 5 04:08:09 histor2 kernel: [ 1270.940716] ll header: 00:30:1b:41:e1:89:00:14:a9:9e:b4:28:08:00
Oct 5 06:59:42 histor2 kernel: [11563.805018] ------------[ cut here ]------------
Oct 5 06:59:42 histor2 kernel: [11563.805058] WARNING: at /tmp/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226 dev_watchdog+0xc7/0x164()
Oct 5 06:59:42 histor2 kernel: [11563.805105] Hardware name: SK22V10
Oct 5 06:59:42 histor2 kernel: [11563.805125] NETDEV WATCHDOG: eth2 (via-rhine): transmit timed out
Oct 5 06:59:42 histor2 kernel: [11563.805148] Modules linked in: iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ppdev parport_pc lp
parport cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc powernow_k8 loop snd_pcm snd_timer snd
soundcore evdev snd_page_alloc k8temp i2c_viapro i2c_core pcspkr button processor shpchp pci_hotplug ext3 jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt
dm_mirror dm_region_hash dm_log dm_snapshot dm_mod raid10 raid456 raid6_pq async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod sd_mod crc_t10dif
ide_cd_mod cdrom ide_pci_generic sata_via via82cxxx ide_core ata_generic libata ehci_hcd scsi_mod via_rhine uhci_hcd 8139too firewire_ohci firewire_core crc_itu_t 8139cp mii thermal fan
thermal_sys [last unloaded: scsi_wait_scan]
Oct 5 06:59:42 histor2 kernel: [11563.809598] Pid: 0, comm: swapper Not tainted 2.6.30-bpo.1-amd64 #1
Oct 5 06:59:42 histor2 kernel: [11563.809623] Call Trace:
Oct 5 06:59:42 histor2 kernel: [11563.809642] <IRQ> [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 5 06:59:42 histor2 kernel: [11563.809678] [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 5 06:59:42 histor2 kernel: [11563.809708] [<ffffffff80242387>] ? warn_slowpath_common+0x77/0xa3
Oct 5 06:59:42 histor2 kernel: [11563.809736] [<ffffffff80423477>] ? dev_watchdog+0x0/0x164
Oct 5 06:59:42 histor2 kernel: [11563.809763] [<ffffffff8024240f>] ? warn_slowpath_fmt+0x51/0x59
Oct 5 06:59:42 histor2 kernel: [11563.809792] [<ffffffff802342fe>] ? enqueue_task+0x5c/0x65
Oct 5 06:59:42 histor2 kernel: [11563.809820] [<ffffffff8025474b>] ? autoremove_wake_function+0x9/0x2e
Oct 5 06:59:42 histor2 kernel: [11563.809848] [<ffffffff8042344b>] ? netif_tx_lock+0x3d/0x69
Oct 5 06:59:42 histor2 kernel: [11563.809877] [<ffffffff8040fef0>] ? netdev_drivername+0x3b/0x40
Oct 5 06:59:42 histor2 kernel: [11563.809904] [<ffffffff8042353e>] ? dev_watchdog+0xc7/0x164
Oct 5 06:59:42 histor2 kernel: [11563.809931] [<ffffffff80230065>] ? gup_huge_pmd+0x36/0x94
Oct 5 06:59:42 histor2 kernel: [11563.809957] [<ffffffff80423477>] ? dev_watchdog+0x0/0x164
Oct 5 06:59:42 histor2 kernel: [11563.809985] [<ffffffff8024aa6f>] ? run_timer_softirq+0x193/0x210
Oct 5 06:59:42 histor2 kernel: [11563.810015] [<ffffffff8025b4d1>] ? getnstimeofday+0x55/0xaf
Oct 5 06:59:42 histor2 kernel: [11563.810042] [<ffffffff80246f91>] ? __do_softirq+0xac/0x173
Oct 5 06:59:42 histor2 kernel: [11563.810070] [<ffffffff80210bcc>] ? call_softirq+0x1c/0x30
Oct 5 06:59:42 histor2 kernel: [11563.810097] [<ffffffff802125fa>] ? do_softirq+0x3a/0x7e
Oct 5 06:59:42 histor2 kernel: [11563.810123] [<ffffffff80246d0e>] ? irq_exit+0x3f/0x80
Oct 5 06:59:42 histor2 kernel: [11563.810150] [<ffffffff80220e63>] ? smp_apic_timer_interrupt+0x87/0x94
Oct 5 06:59:42 histor2 kernel: [11563.810178] [<ffffffff802105d3>] ? apic_timer_interrupt+0x13/0x20
Oct 5 06:59:42 histor2 kernel: [11563.810202] <EOI> [<ffffffff80256fa9>] ? hrtimer_cancel+0xc/0x16
Oct 5 06:59:42 histor2 kernel: [11563.810235] [<ffffffff80227520>] ? native_safe_halt+0x2/0x3
Oct 5 06:59:42 histor2 kernel: [11563.810263] [<ffffffff80216995>] ? default_idle+0x40/0x68
Oct 5 06:59:42 histor2 kernel: [11563.810290] [<ffffffff80257d0d>] ? notifier_call_chain+0x29/0x4c
Oct 5 06:59:42 histor2 kernel: [11563.810318] [<ffffffff80216d6a>] ? c1e_idle+0x107/0x10d
Oct 5 06:59:42 histor2 kernel: [11563.810346] [<ffffffff8020edda>] ? cpu_idle+0x50/0x91
Oct 5 06:59:42 histor2 kernel: [11563.810371] ---[ end trace d486a35a41d2f448 ]---
Oct 5 06:59:42 histor2 kernel: [11563.810538] eth2: Transmit timed out, status 1003, PHY status 786d, resetting...
Oct 5 06:59:42 histor2 kernel: [11563.811381] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 5 06:59:46 histor2 kernel: [11567.804166] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 5 06:59:46 histor2 kernel: [11567.805004] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 5 06:59:50 histor2 kernel: [11571.804168] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 5 06:59:50 histor2 kernel: [11571.805007] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 5 06:59:54 histor2 kernel: [11575.804166] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 5 06:59:54 histor2 kernel: [11575.804997] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 5 06:59:58 histor2 kernel: [11579.804166] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 5 06:59:58 histor2 kernel: [11579.805011] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 5 07:00:02 histor2 kernel: [11583.804169] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
Oct 5 07:00:02 histor2 kernel: [11583.805009] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
Best regards,
Jens-Michael
--
To UNSUBSCRIBE, email to debian-ker...@lists.debian.org
Antonio Marcos López Alonso
>
> I had a look at the code and the values in the 'transmit timed out'
> message, and it seems that the NIC has reported a transmit completion
> but this hasn't been handled. Perhaps another device sharing its IRQ is
> misbehaving and causing the IRQ to be disabled. Please can you send
> more of the kernel log from before the TX watchdog warning? Also, if
> this happens again, please send the contents of /proc/interrupts.
Hope this helps:
/proc/interrupts:
CPU0
0: 42 IO-APIC-edge timer
1: 15545 IO-APIC-edge i8042
3: 2 IO-APIC-edge
6: 5 IO-APIC-edge floppy
7: 1 IO-APIC-edge parport0
8: 0 IO-APIC-edge rtc0
9: 0 IO-APIC-fasteoi acpi
12: 548810 IO-APIC-edge i8042
14: 579201 IO-APIC-edge ide0
15: 0 IO-APIC-edge ide1
17: 1025391 IO-APIC-fasteoi uhci_hcd:usb3, HDA Intel
18: 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 12757455 IO-APIC-fasteoi ehci_hcd:usb1
20: 49 IO-APIC-fasteoi uhci_hcd:usb5
21: 1117594 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb7, sata_via
22: 0 IO-APIC-fasteoi uhci_hcd:usb6
23: 13921438 IO-APIC-fasteoi uhci_hcd:usb8, eth0
24: 134291 IO-APIC-fasteoi nvidia
NMI: 0 Non-maskable interrupts
LOC: 31577802 Local timer interrupts
SPU: 0 Spurious interrupts
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
ERR: 2
MIS: 0
kern.log (output previous to warning):
Oct 5 11:23:08 tamaran kernel: [54396.472050] usb 5-2: USB disconnect,
address 2
Oct 5 11:23:08 tamaran kernel: [54396.472291] usblp0: removed
Oct 5 17:14:29 tamaran kernel: [75477.891995] mt2060 I2C read failed
Oct 5 19:54:09 tamaran kernel: [85057.263674] atkbd.c: Unknown key pressed
(translated set 2, code 0xd7 on isa0060/serio0).
Oct 5 19:54:09 tamaran kernel: [85057.263681] atkbd.c: Use 'setkeycodes e057
<keycode>' to make it known.
Oct 5 19:54:09 tamaran kernel: [85057.423841] atkbd.c: Unknown key released
(translated set 2, code 0xd7 on isa0060/serio0).
Oct 5 19:54:09 tamaran kernel: [85057.423849] atkbd.c: Use 'setkeycodes e057
<keycode>' to make it known.
Oct 5 19:56:20 tamaran kernel: [85188.793549] eth0: link down
Oct 5 19:56:23 tamaran kernel: [85191.954849] eth0: link up, 100Mbps, full-
duplex, lpa 0x41E1
Oct 5 19:56:38 tamaran kernel: [85206.177470] eth0: link down
Oct 5 19:56:41 tamaran kernel: [85209.654113] eth0: link up, 100Mbps, full-
duplex, lpa 0x41E1
Oct 5 19:56:46 tamaran kernel: [85214.105583] Inbound IN=eth0 OUT=
MAC=ff:ff:ff:ff:ff:ff:00:15:58:31:81:1e:08:00 SRC=192.168.1.35
DST=255.255.255.255 LEN=346 TOS=0x00 PREC=0x00 TTL=128 ID=16939 PROTO=UDP
SPT=68 DPT=67 LEN=326
Oct 5 21:46:07 tamaran kernel: [91775.816016] ------------[ cut here
]------------
Oct 5 21:46:07 tamaran kernel: [91775.816032] WARNING: at /build/buildd-
linux-2.6_2.6.30-6-amd64-
s9DPiZ/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226
dev_watchdog+0xc7/0x164()
Oct 5 21:46:07 tamaran kernel: [91775.816040] Hardware name: System Product
Name
Oct 5 21:46:07 tamaran kernel: [91775.816044] NETDEV WATCHDOG: eth0 (via-
rhine): transmit timed out
>
> Ben.
Antonio Marcos López Alonso
Sure. Here is /proc/interrupts using irqpoll + noapic (yet no much time
has passed to reproduce the failure):
CPU0
0: 32 XT-PIC-XT timer
1: 1084 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 1 XT-PIC-XT
4: 23569 XT-PIC-XT ehci_hcd:usb1, uhci_hcd:usb8
5: 63936 XT-PIC-XT ehci_hcd:usb2, uhci_hcd:usb4,
uhci_hcd:usb5, uhci_hcd:usb7, eth0
6: 5 XT-PIC-XT floppy
7: 412 XT-PIC-XT parport0
8: 0 XT-PIC-XT rtc0
9: 0 XT-PIC-XT acpi
10: 409 XT-PIC-XT nvidia
11: 30797 XT-PIC-XT uhci_hcd:usb3, uhci_hcd:usb6, sata_via,
HDA Intel
12: 15090 XT-PIC-XT i8042
14: 3043 XT-PIC-XT ide0
15: 0 XT-PIC-XT ide1
NMI: 0 Non-maskable interrupts
LOC: 117311 Local timer interrupts
SPU: 0 Spurious interrupts
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
THR: 0 Threshold APIC interrupts
ERR: 1
MIS: 0
Antonio
Ben Hutchings
> On Tue, Oct 6, 2009 at 1:26 AM, Ben Hutchings <b...@decadent.org.uk>
> wrote:
> > Could you try adding 'noapic' to the kernel command line?
>
> Sure. Here is /proc/interrupts using irqpoll + noapic (yet no much time
> has passed to reproduce the failure):
Do you mean this bug still occurs when you use 'noapic'?
Ben.
--
Ben Hutchings
To err is human; to really foul things up requires a computer.
Antonio Marcos López Alonso
On Tue, 2009-10-06 at 23:26 +0100, Antonio Marcos López Alonso wrote:[...]
> On Tue, Oct 6, 2009 at 1:26 AM, Ben Hutchings <b...@decadent.org.uk>
> wrote:
> > Could you try adding 'noapic' to the kernel command line?[...]
>
> Sure. Here is /proc/interrupts using irqpoll + noapic (yet no much time
> has passed to reproduce the failure):
Do you mean this bug still occurs when you use 'noapic'?
Ben.
No, I mean I'm still waiting for the bug to occur. I will do it for around 72 hours (crossing fingers). Anyway, what is your opinion about what is happening? I guess this is not very common.
Ben Hutchings
>
>
> 2009/10/6 Ben Hutchings <b...@decadent.org.uk>
> On Tue, 2009-10-06 at 23:26 +0100, Antonio Marcos López Alonso
> wrote:
> > On Tue, Oct 6, 2009 at 1:26 AM, Ben Hutchings
> <b...@decadent.org.uk>
> > wrote:
>
> [...]
> > > Could you try adding 'noapic' to the kernel command line?
> >
> > Sure. Here is /proc/interrupts using irqpoll + noapic (yet
> no much time
> > has passed to reproduce the failure):
>
> [...]
>
> Do you mean this bug still occurs when you use 'noapic'?
>
> Ben.
>
>
> No, I mean I'm still waiting for the bug to occur.
Excellent.
> I will do it for around 72 hours (crossing fingers). Anyway, what is
> your opinion about what is happening? I guess this is not very common.
I think that there may be a bug in the way the BIOS sets up the IO-APIC,
but I don't really understand what sorts of things can go wrong with
this.
Antonio Marcos López Alonso
Still waiting :-).
Googling around I found this bug is quite old:
http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
And this:
http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
It seems the fix is not the same for everyone.
Supposing the only fix by now is a kernel option, should I close this bug?
Antonio
Ben Hutchings
[...]
> Googling around I found this bug is quite old:
>
> http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
>
> And this:
>
> http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
>
> It seems the fix is not the same for everyone.
I don't think those are the same bug as this.
> Supposing the only fix by now is a kernel option, should I close this bug?
No, it should stay open until there is a proper fix.
Antonio Marcos López Alonso
> On Thu, 2009-10-08 at 00:03 +0100, Antonio Marcos López Alonso wrote:
> [...]
>
> > Googling around I found this bug is quite old:
> >
> > http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
> >
> > And this:
> >
> > http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
> >
> > It seems the fix is not the same for everyone.
>
> I don't think those are the same bug as this.
>
> > Supposing the only fix by now is a kernel option, should I close this
> > bug?
>
> No, it should stay open until there is a proper fix.
>
> Ben.
>
It seems the network is behaving quite well with noapic (and no
irqfixup/irqpoll) :-).
So I shall keep this open until news are available.
Ben Hutchings
> El Jueves 08 Octubre 2009, Ben Hutchings escribió:
> > On Thu, 2009-10-08 at 00:03 +0100, Antonio Marcos López Alonso wrote:
> > [...]
> >
> > > Googling around I found this bug is quite old:
> > >
> > > http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
> > >
> > > And this:
> > >
> > > http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
> > >
> > > It seems the fix is not the same for everyone.
> >
> > I don't think those are the same bug as this.
> >
> > > Supposing the only fix by now is a kernel option, should I close this
> > > bug?
> >
> > No, it should stay open until there is a proper fix.
> >
> > Ben.
> >
>
> It seems the network is behaving quite well with noapic (and no
> irqfixup/irqpoll) :-).
>
> So I shall keep this open until news are available.
Please can you report this bug at <http://bugzilla.kernel.org>,
including the fact that 'noapic' works around it. The product should be
'Platform Specific/Hardware' and the component 'i386'. Let us know the
bug number so we can keep track of it.
Ben.
--
Ben Hutchings
DNRC Motto: I can please only one person per day.
Today is not your day. Tomorrow isn't looking good either.
Moritz Muehlenhoff
> On Sun, 2009-10-11 at 14:10 +0100, Antonio Marcos L�pez Alonso wrote:
> > El Jueves 08 Octubre 2009, Ben Hutchings escribi�:
> > > On Thu, 2009-10-08 at 00:03 +0100, Antonio Marcos L�pez Alonso wrote:
> > > [...]
> > >
> > > > Googling around I found this bug is quite old:
> > > >
> > > > http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
> > > >
> > > > And this:
> > > >
> > > > http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
> > > >
> > > > It seems the fix is not the same for everyone.
> > >
> > > I don't think those are the same bug as this.
> > >
> > > > Supposing the only fix by now is a kernel option, should I close this
> > > > bug?
> > >
> > > No, it should stay open until there is a proper fix.
> > >
> > > Ben.
> > >
> >
> > It seems the network is behaving quite well with noapic (and no
> > irqfixup/irqpoll) :-).
> >
> > So I shall keep this open until news are available.
>
> Please can you report this bug at <http://bugzilla.kernel.org>,
> including the fact that 'noapic' works around it. The product should be
> 'Platform Specific/Hardware' and the component 'i386'. Let us know the
> bug number so we can keep track of it.
Antonio, did you report this upstream?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20100215010...@galadriel.inutil.org
Antonio Marcos López Alonso
> On Sun, Oct 11, 2009 at 05:53:39PM +0100, Ben Hutchings wrote:
> > > El Jueves 08 Octubre 2009, Ben Hutchings escribió:
> > > > On Thu, 2009-10-08 at 00:03 +0100, Antonio Marcos López Alonso wrote:
> > > > [...]
> > > >
> > > > > Googling around I found this bug is quite old:
> > > > >
> > > > > http://lkml.indiana.edu/hypermail/linux/kernel/0302.1/0966.html
> > > > >
> > > > > And this:
> > > > >
> > > > > http://fixunix.com/suse/125711-problem-via-rhine-ii-eth0.html
> > > > >
> > > > > It seems the fix is not the same for everyone.
> > > >
> > > > I don't think those are the same bug as this.
> > > >
> > > > > Supposing the only fix by now is a kernel option, should I close
> > > > > this bug?
> > > >
> > > > No, it should stay open until there is a proper fix.
> > > >
> > > > Ben.
> > >
> > > It seems the network is behaving quite well with noapic (and no
> > > irqfixup/irqpoll) :-).
> > >
> > > So I shall keep this open until news are available.
> >
> > Please can you report this bug at <http://bugzilla.kernel.org>,
> > including the fact that 'noapic' works around it. The product should be
> > 'Platform Specific/Hardware' and the component 'i386'. Let us know the
> > bug number so we can keep track of it.
>
> Antonio, did you report this upstream?
>
> Cheers,
> Moritz
>
I'm very sorry, I completely forgot this bug tracking. I shall try kernel
2.6.32 in order to see if this bug persists, and if so I will report upstream.
I'll keep you posted.
Regards,
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201002151610.223...@gmail.com
Antonio Marcos López Alonso
with this issue:
http://patchwork.kernel.org/patch/69308/
If so, this bug should be fixed in 2.6.33:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.33-rc3
Any suggestion/confirmation?
Regards
Antonio
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201002171601.390...@gmail.com
maximilian attems
> I'm not sure about reporting upstream as the following patch seems to deal
> with this issue:
>
> http://patchwork.kernel.org/patch/69308/
>
> If so, this bug should be fixed in 2.6.33:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.33-rc3
>
> Any suggestion/confirmation?
thanks for this direct pointer, sent fix to sta...@kernel.org
so should appear in one of the next stable release.
if not a candidate we gona pick it up. for now we just need to wait.
good evening.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20100217163...@baikonur.stro.at
Jens-Michael Hoffmann
It today happened again after months. The system is an uptodate squeeze with only kernel from sid.
May 27 14:31:29 histor2 kernel: [724199.816021] ------------[ cut here ]------------
May 27 14:31:29 histor2 kernel: [724199.816061] WARNING: at /build/mattems-linux-2.6_2.6.32-13-amd64-ybUaaU/linux-2.6-2.6.32-13/debian/build/source_amd64_none/net/sched/sch_generic.c:261 dev_watchdog+0xe2/0x194()
May 27 14:31:29 histor2 kernel: [724199.816123] Hardware name: SK22V10
May 27 14:31:29 histor2 kernel: [724199.816143] NETDEV WATCHDOG: eth2 (via-rhine): transmit queue 0 timed out
May 27 14:31:29 histor2 kernel: [724199.816169] Modules linked in: iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables tcp_diag inet_diag ppdev lp parport cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc powernow_k8 loop snd_pcsp snd_pcm snd_timer snd i2c_viapro soundcore shpchp edac_core tpm_tis i2c_core edac_mce_amd evdev snd_page_alloc pci_hotplug k8temp tpm button processor tpm_bios ext3 jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod sg sr_mod cdrom sd_mod crc_t10dif 8139too ata_generic uhci_hcd fan sata_via thermal thermal_sys 8139cp via_rhine mii ehci_hcd pata_via libata usbcore scsi_mod nls_base firewire_ohci firewire_core crc_itu_t [last unloaded: scsi_wait_scan]
May 27 14:31:29 histor2 kernel: [724199.816589] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1
May 27 14:31:29 histor2 kernel: [724199.816614] Call Trace:
May 27 14:31:29 histor2 kernel: [724199.816633] <IRQ> [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816668] [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816696] [<ffffffff8104dc58>] ? warn_slowpath_common+0x77/0xa3
May 27 14:31:29 histor2 kernel: [724199.816724] [<ffffffff81260b14>] ? dev_watchdog+0x0/0x194
May 27 14:31:29 histor2 kernel: [724199.816750] [<ffffffff8104dce0>] ? warn_slowpath_fmt+0x51/0x59
May 27 14:31:29 histor2 kernel: [724199.816779] [<ffffffff8101f2b4>] ? mce_setup+0xb0/0xbe
May 27 14:31:29 histor2 kernel: [724199.816806] [<ffffffff81260ae8>] ? netif_tx_lock+0x3d/0x69
May 27 14:31:29 histor2 kernel: [724199.816834] [<ffffffff8124b9b8>] ? netdev_drivername+0x3b/0x40
May 27 14:31:29 histor2 kernel: [724199.816861] [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816888] [<ffffffff8101fbcc>] ? mcheck_timer+0x0/0xf2
May 27 14:31:29 histor2 kernel: [724199.816917] [<ffffffff8105a26b>] ? run_timer_softirq+0x1c9/0x268
May 27 14:31:29 histor2 kernel: [724199.816947] [<ffffffff810539e6>] ? __do_softirq+0xdd/0x19f
May 27 14:31:29 histor2 kernel: [724199.816975] [<ffffffff81024d62>] ? lapic_next_event+0x18/0x1d
May 27 14:31:29 histor2 kernel: [724199.817003] [<ffffffff81011cac>] ? call_softirq+0x1c/0x30
May 27 14:31:29 histor2 kernel: [724199.817030] [<ffffffff81013903>] ? do_softirq+0x3f/0x7c
May 27 14:31:29 histor2 kernel: [724199.817057] [<ffffffff81053855>] ? irq_exit+0x36/0x76
May 27 14:31:29 histor2 kernel: [724199.817083] [<ffffffff81025827>] ? smp_apic_timer_interrupt+0x87/0x95
May 27 14:31:29 histor2 kernel: [724199.821114] [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20
May 27 14:31:29 histor2 kernel: [724199.821139] <EOI> [<ffffffff8102c574>] ? native_safe_halt+0x2/0x3
May 27 14:31:29 histor2 kernel: [724199.821176] [<ffffffff81017cc1>] ? default_idle+0x34/0x51
May 27 14:31:29 histor2 kernel: [724199.821203] [<ffffffff8101804d>] ? c1e_idle+0xf5/0xfb
May 27 14:31:29 histor2 kernel: [724199.821231] [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda
May 27 14:31:29 histor2 kernel: [724199.821260] [<ffffffff814ec140>] ? early_idt_handler+0x0/0x71
May 27 14:31:29 histor2 kernel: [724199.821288] [<ffffffff814eccd1>] ? start_kernel+0x3dc/0x3e8
May 27 14:31:29 histor2 kernel: [724199.821315] [<ffffffff814ec3b7>] ? x86_64_start_kernel+0xf9/0x106
May 27 14:31:29 histor2 kernel: [724199.821341] ---[ end trace da285d2d0aca2156 ]---
May 27 14:31:29 histor2 kernel: [724199.821508] eth2: Transmit timed out, status 1003, PHY status 786d, resetting...
May 27 14:31:29 histor2 kernel: [724199.823146] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:31:41 histor2 kernel: [724211.816164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:31:41 histor2 kernel: [724211.817112] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:31:51 histor2 kernel: [724221.816161] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:31:51 histor2 kernel: [724221.817088] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:01 histor2 kernel: [724231.816164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:01 histor2 kernel: [724231.817100] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:17 histor2 kernel: [724247.816168] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:17 histor2 kernel: [724247.817118] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:27 histor2 kernel: [724257.816171] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:27 histor2 kernel: [724257.818631] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:39 histor2 kernel: [724269.816175] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:39 histor2 kernel: [724269.817120] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:49 histor2 kernel: [724279.816167] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:49 histor2 kernel: [724279.817106] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
Kind regards,
Jens-Michael
Moritz Muehlenhoff
notforwarded 549606
reassign 549606 src:linux
thanks
On Thu, May 27, 2010 at 05:11:55PM +0200, Jens-Michael Hoffmann wrote:
> Looks like the bug still is there in 2.6.32-13-amd64, however frequency is greatly reduced.
> It today happened again after months. The system is an uptodate squeeze with only kernel from sid.
Cheers,
Moritz
Jens-Michael Hoffmann
Am Dienstag, 9. Juli 2013, 17:43:54 schrieb Moritz Muehlenhoff:
> tags 549606
> notforwarded 549606
> reassign 549606 src:linux
> thanks
>
> On Thu, May 27, 2010 at 05:11:55PM +0200, Jens-Michael Hoffmann wrote:
> > Looks like the bug still is there in 2.6.32-13-amd64, however frequency is
> > greatly reduced. It today happened again after months. The system is an
> > uptodate squeeze with only kernel from sid.
> Does this still occur with the kernel from Debian Wheezy (or later)?
Unfortunately I'm not able to check anymore as both of my machines with VIA chipsets died.
kind regards,
Jens-Michael