From: Tom Weber <l_linux-kernel@mail2news.4t2.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: "Michael Büker" <m.bueker@berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too
Date: Tue, 10 Mar 2009 06:42:03 +0100 [thread overview]
Message-ID: <1236663723.29428.33.camel@morgoth.abyss.4t2.com> (raw)
In-Reply-To: <1236508032.14878.1.camel@morgoth.abyss.4t2.com>
Am Sonntag, den 08.03.2009, 11:27 +0100 schrieb Tom Weber:
> Happens at least with 2.6.28, 2.6.28.4, 2.6.28.6 and 2.6.29-rc7.
>
> This is a diskless box (on NFS) on GigE LAN, used for DVB-S
> recordings/playback with vdr.
[...]
> Every once in while, more likely with heavy usage of the vdr stuff (like
> recording two shows and/or cutting a recording) these show up. Of course
> the impact is realy bad on a diskless system. It takes the system from
> 10 seconds to 3 minutes to recover.
After running 2.6.29-rc7 for more than a day now with lots of data moved
around I got the impression that it is more stable than 2.6.28.6.
I only got one warning so far and a few
r8169: eth0: link up
messages.
I know this is a vague statement, but I think I would have seen more
warnings with 2.6.28.6 and all the stuff I've done.
Below is the latest / only Call trace I've got since my earlier mail.
Note the 'eth0: link up' messages. This is where most likely the
2.6.28.6 would have barfed on me (cutting of recordings).
This is the complete dmesg output since the first warning. I didn't
remove anything before or between the 'link up' messages.
[2.6.29-rc7 - same configs etc as described in my earlier mail]
[ 320.501076] nfs: server 192.168.1.8 not responding, still trying
[ 321.031065] nfs: server 192.168.1.8 not responding, still trying
[ 321.997042] ------------[ cut here ]------------
[ 321.997050] WARNING: at net/sched/sch_generic.c:226 dev_watchdog+0x1f1/0x200()
[ 321.997056] Hardware name: System Product Name
[ 321.997060] NETDEV WATCHDOG: eth0 (r8169): transmit timed out
[ 321.997063] Modules linked in: autofs4 powernow_k8 cpufreq_stats cpufreq_ondemand cpufreq_conservative cpufreq_performance freq_table pci_slot sbs ac battery video backlight output sbshc container sbp2 loop lnbp21 stv0299 snd_hda_codec_atihdmi snd_seq_dummy snd_seq_oss snd_hda_codec_realtek snd_seq_midi snd_hda_intel dvb_ttpci snd_hda_codec dvb_core snd_pcm_oss saa7146_vv saa7146 snd_rawmidi snd_mixer_oss videobuf_dma_sg evdev videobuf_core serio_raw psmouse videodev snd_seq_midi_event v4l1_compat ttpci_eeprom k8temp snd_pcm pcspkr snd_seq rtc_cmos rtc_core rtc_lib i2c_piix4 i2c_core snd_timer snd_seq_device button snd wmi soundcore snd_page_alloc af_packet pata_acpi ata_generic sg sr_mod cdrom ohci1394 pata_atiixp ehci_hcd ohci_hcd ahci ieee1394 libata usbcore scsi_mod raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod dm_mirror dm_region_hash dm_log dm_snapshot dm_mod thermal processor fan thermal_sys hwmon fuse
[ 321.997191] Pid: 0, comm: swapper Not tainted 2.6.29-rc7 #1
[ 321.997195] Call Trace:
[ 321.997207] [<c0229587>] warn_slowpath+0x87/0xe0
[ 321.997216] [<c0402177>] pskb_copy+0x27/0x160
[ 321.997222] [<c0402177>] pskb_copy+0x27/0x160
[ 321.997229] [<c0214829>] ack_apic_level+0x59/0x260
[ 321.997236] [<c0269c00>] rcu_sched_grace_period+0x1e0/0x2c0
[ 321.997242] [<c026897b>] handle_fasteoi_irq+0x8b/0xe0
[ 321.997249] [<c022eefd>] irq_exit+0x2d/0x90
[ 321.997256] [<c0204e6d>] do_IRQ+0x4d/0x90
[ 321.997266] [<c0246b41>] getnstimeofday+0x51/0x110
[ 321.997272] [<c02039e7>] common_interrupt+0x27/0x2c
[ 321.997279] [<c0369d1f>] strlcpy+0x1f/0x60
[ 321.997285] [<c0419711>] dev_watchdog+0x1f1/0x200
[ 321.997291] [<c0240039>] posix_cpu_timer_set+0x409/0x450
[ 321.997298] [<c0243d5d>] sched_clock_cpu+0x14d/0x1a0
[ 321.997306] [<c02126a0>] lapic_next_event+0x10/0x20
[ 321.997312] [<c02493e3>] clockevents_program_event+0xa3/0x170
[ 321.997320] [<c0232f8d>] cascade+0x5d/0x80
[ 321.997326] [<c0233160>] run_timer_softirq+0x130/0x1f0
[ 321.997332] [<c0419520>] dev_watchdog+0x0/0x200
[ 321.997337] [<c0419520>] dev_watchdog+0x0/0x200
[ 321.997342] [<c022ec3f>] __do_softirq+0x7f/0x130
[ 321.997361] [<c022ed45>] do_softirq+0x55/0x60
[ 321.997366] [<c022ef45>] irq_exit+0x75/0x90
[ 321.997373] [<c0212eb7>] smp_apic_timer_interrupt+0x67/0xa0
[ 321.997384] [<c0203b00>] apic_timer_interrupt+0x28/0x30
[ 321.997392] [<c0209292>] default_idle+0x42/0x50
[ 321.997398] [<c020941f>] c1e_idle+0x2f/0xf0
[ 321.997403] [<c0202353>] cpu_idle+0x63/0xa0
[ 321.997412] [<c04ac293>] start_secondary+0x19e/0x2eb
[ 321.997417] [<c020b9ce>] user_enable_single_step+0xe/0x10
[ 321.997422] ---[ end trace c509771bca9f9e70 ]---
[ 322.009305] nfs: server 192.168.1.8 OK
[ 322.009589] r8169: eth0: link up
[ 323.152320] nfs: server 192.168.1.8 OK
[ 323.152397] nfs: server 192.168.1.8 OK
[ 323.152508] nfs: server 192.168.1.8 OK
[68818.001610] r8169: eth0: link up
[69004.003443] r8169: eth0: link up
[90178.001567] r8169: eth0: link up
Tom
next prev parent reply other threads:[~2009-03-10 5:42 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 17:28 Michael Büker
2009-03-04 22:43 ` Francois Romieu
2009-03-06 0:17 ` Michael Büker
2009-03-08 10:27 ` Tom Weber
2009-03-10 5:42 ` Tom Weber [this message]
2009-03-09 12:07 ` Rui Santos
2009-03-13 18:29 ` Rui Santos
2009-03-16 13:07 ` Rui Santos
2009-03-22 21:12 ` Francois Romieu
2009-03-22 21:19 ` Michael Buesch
2009-03-22 22:00 ` Francois Romieu
2009-03-22 22:09 ` Michael Buesch
2009-03-22 22:27 ` Francois Romieu
2009-03-22 22:38 ` Michael Buesch
2009-03-23 11:47 ` Michael Buesch
2009-03-23 12:47 ` Michael Buesch
2009-03-23 23:47 ` Francois Romieu
2009-03-24 9:43 ` Michael Buesch
2009-03-23 14:29 ` Michael Büker
2009-03-23 14:57 ` Rui Santos
2009-03-23 15:04 ` Michael Büker
2009-03-25 11:40 ` Rui Santos
2009-04-04 17:50 ` Michael Buesch
2009-05-10 13:38 ` Michael Riepe
2009-05-10 15:01 ` Michael S. Zick
2009-05-10 15:10 ` Michael S. Zick
2009-05-10 15:53 ` Michael Buesch
2009-05-10 16:27 ` Michael Riepe
2009-05-10 17:09 ` Michael S. Zick
2009-05-11 0:29 ` David Dillow
2009-05-11 20:48 ` Michael Buesch
2009-05-11 21:10 ` Michael Buesch
2009-05-11 21:29 ` David Dillow
2009-05-11 21:59 ` Michael Buesch
2009-05-12 20:29 ` Michael Riepe
2009-05-14 2:38 ` David Dillow
2009-05-14 18:37 ` Michael Riepe
2009-05-14 19:14 ` David Dillow
2009-05-14 19:42 ` Michael Riepe
2009-05-23 1:29 ` [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts David Dillow
2009-05-23 9:24 ` Michael Buesch
2009-05-23 14:35 ` Michael Riepe
2009-05-23 14:44 ` Michael Buesch
2009-05-23 15:01 ` Michael Riepe
2009-05-23 16:40 ` Michael Buesch
2009-05-23 14:51 ` David Dillow
2009-05-23 16:12 ` Michael Riepe
2009-05-23 16:45 ` Michael Buesch
2009-05-23 16:46 ` David Dillow
2009-05-23 16:50 ` Michael Buesch
2009-05-23 16:53 ` Michael Riepe
2009-05-23 17:03 ` David Dillow
2009-05-24 21:15 ` Francois Romieu
2009-05-24 22:55 ` David Dillow
2009-05-26 5:55 ` David Miller
2009-05-26 18:22 ` Michael Buesch
2009-05-26 21:52 ` David Miller
2009-05-26 22:14 ` David Miller
2009-05-26 22:40 ` Michael Riepe
2009-05-26 22:43 ` David Miller
2009-05-26 23:10 ` David Miller
2009-05-27 16:19 ` Michael Buesch
2009-06-16 19:32 ` Rui Santos
2009-08-21 20:57 ` Eric W. Biederman
2009-08-21 21:22 ` Michael Riepe
2009-08-21 22:59 ` David Dillow
2009-08-21 23:34 ` David Dillow
2009-08-22 0:24 ` Eric W. Biederman
2009-08-22 11:48 ` Eric W. Biederman
2009-08-22 12:07 ` Eric W. Biederman
2009-08-22 20:43 ` David Dillow
2009-08-23 17:17 ` Jarek Poplawski
2009-08-23 17:43 ` Michal Soltys
2009-08-23 17:54 ` Jarek Poplawski
2009-08-24 2:37 ` Eric W. Biederman
2009-08-25 0:51 ` Eric W. Biederman
2009-08-25 2:59 ` David Dillow
2009-08-25 20:22 ` Eric W. Biederman
2009-08-25 20:40 ` David Dillow
2009-08-25 21:24 ` Eric W. Biederman
2009-08-25 21:46 ` David Dillow
2009-08-25 22:19 ` Francois Romieu
2009-08-26 3:47 ` Eric W. Biederman
2009-08-26 7:58 ` [PATCH] r8169: Reduce looping in the interrupt handler Eric W. Biederman
2009-08-26 13:56 ` David Dillow
2009-08-26 13:59 ` David Dillow
2009-08-26 20:02 ` Eric W. Biederman
2009-08-26 21:30 ` Francois Romieu
2009-08-26 21:40 ` Eric W. Biederman
2009-08-27 5:24 ` Francois Romieu
2009-08-27 5:38 ` Eric W. Biederman
2009-08-27 23:20 ` Francois Romieu
2009-08-28 1:17 ` Eric W. Biederman
2009-08-28 1:29 ` David Dillow
2009-08-30 20:37 ` Francois Romieu
2009-08-30 20:53 ` Eric W. Biederman
2009-09-01 3:33 ` David Dillow
2009-09-01 9:20 ` Francois Romieu
2009-08-25 21:37 ` [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts Eric W. Biederman
2009-08-25 21:54 ` David Dillow
2009-08-25 23:11 ` Francois Romieu
2009-05-12 11:10 ` 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too Krzysztof Halasa
2009-05-12 21:45 ` Michael Riepe
2009-05-13 6:11 ` Francois Romieu
2009-05-13 6:27 ` Michael Riepe
2009-05-13 19:34 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1236663723.29428.33.camel@morgoth.abyss.4t2.com \
--to=l_linux-kernel@mail2news.4t2.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.bueker@berlin.de \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®