From: Neil Horman on
On Wed, Mar 31, 2010 at 01:21:42PM +0300, Sergey Senozhatsky wrote:
> Hello,
> I have the following problem:
>
> [ 296.337510] ------------[ cut here ]------------
> [ 296.337523] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xc1/0x125()
> [ 296.337527] Hardware name: F3JC
> [ 296.337530] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> [ 296.337533] Modules linked in: pktgen ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek sdhci_pci sdhci asus_laptop sparse_keymap mmc_core led_class snd_hda_intel
> snd_hda_codec psmouse snd_pcm snd_timer snd soundcore snd_page_alloc serio_raw i2c_i801 rng_core evdev sg r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore
> ata_piix
> [ 296.337586] Pid: 0, comm: swapper Not tainted 2.6.34-rc3-dbg #74
> [ 296.337589] Call Trace:
> [ 296.337597] [<c102e71f>] warn_slowpath_common+0x65/0x7c
> [ 296.337603] [<c126e30c>] ? dev_watchdog+0xc1/0x125
> [ 296.337608] [<c102e76a>] warn_slowpath_fmt+0x24/0x27
> [ 296.337613] [<c126e30c>] dev_watchdog+0xc1/0x125
> [ 296.337620] [<c1040039>] ? prepare_to_wait_exclusive+0x52/0x5b
> [ 296.337627] [<c1037053>] ? run_timer_softirq+0x120/0x1eb
> [ 296.337632] [<c10370a9>] run_timer_softirq+0x176/0x1eb
> [ 296.337637] [<c1037053>] ? run_timer_softirq+0x120/0x1eb
> [ 296.337643] [<c126e24b>] ? dev_watchdog+0x0/0x125
> [ 296.337650] [<c10331c9>] __do_softirq+0x8d/0x117
> [ 296.337655] [<c103327e>] do_softirq+0x2b/0x43
> [ 296.337660] [<c10333a3>] irq_exit+0x38/0x75
> [ 296.337667] [<c1015138>] smp_apic_timer_interrupt+0x6d/0x7b
> [ 296.337673] [<c12cbada>] apic_timer_interrupt+0x36/0x3c
> [ 296.337679] [<c104007b>] ? prepare_to_wait+0x39/0x57
> [ 296.337685] [<c11dd835>] ? acpi_idle_enter_simple+0x119/0x144
> [ 296.337692] [<c124d358>] cpuidle_idle_call+0x6d/0xa5
> [ 296.337697] [<c1001b51>] cpu_idle+0x92/0xc1
> [ 296.337704] [<c12c63d0>] start_secondary+0x1f3/0x1fa
> [ 296.337708] ---[ end trace cd4a1b50139837df ]---
>
>
> Reproducing 100% with pktgen tests.
>
What kind of packets are you sending with pktgen?
Neil

>
> Sergey


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Sergey Senozhatsky on
Hello,

On (03/31/10 07:19), Neil Horman wrote:
> On Wed, Mar 31, 2010 at 01:21:42PM +0300, Sergey Senozhatsky wrote:
> > Hello,
> > I have the following problem:
> >
> > [ 296.337510] ------------[ cut here ]------------
> > [ 296.337523] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xc1/0x125()
> > [ 296.337527] Hardware name: F3JC
> > [ 296.337530] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> > [ 296.337533] Modules linked in: pktgen ipv6 snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek sdhci_pci sdhci asus_laptop sparse_keymap mmc_core led_class snd_hda_intel
> > snd_hda_codec psmouse snd_pcm snd_timer snd soundcore snd_page_alloc serio_raw i2c_i801 rng_core evdev sg r8169 mii usbhid hid uhci_hcd ehci_hcd sr_mod cdrom sd_mod usbcore
> > ata_piix
> > [ 296.337586] Pid: 0, comm: swapper Not tainted 2.6.34-rc3-dbg #74
> > [ 296.337589] Call Trace:
> > [ 296.337597] [<c102e71f>] warn_slowpath_common+0x65/0x7c
> > [ 296.337603] [<c126e30c>] ? dev_watchdog+0xc1/0x125
> > [ 296.337608] [<c102e76a>] warn_slowpath_fmt+0x24/0x27
> > [ 296.337613] [<c126e30c>] dev_watchdog+0xc1/0x125
> > [ 296.337620] [<c1040039>] ? prepare_to_wait_exclusive+0x52/0x5b
> > [ 296.337627] [<c1037053>] ? run_timer_softirq+0x120/0x1eb
> > [ 296.337632] [<c10370a9>] run_timer_softirq+0x176/0x1eb
> > [ 296.337637] [<c1037053>] ? run_timer_softirq+0x120/0x1eb
> > [ 296.337643] [<c126e24b>] ? dev_watchdog+0x0/0x125
> > [ 296.337650] [<c10331c9>] __do_softirq+0x8d/0x117
> > [ 296.337655] [<c103327e>] do_softirq+0x2b/0x43
> > [ 296.337660] [<c10333a3>] irq_exit+0x38/0x75
> > [ 296.337667] [<c1015138>] smp_apic_timer_interrupt+0x6d/0x7b
> > [ 296.337673] [<c12cbada>] apic_timer_interrupt+0x36/0x3c
> > [ 296.337679] [<c104007b>] ? prepare_to_wait+0x39/0x57
> > [ 296.337685] [<c11dd835>] ? acpi_idle_enter_simple+0x119/0x144
> > [ 296.337692] [<c124d358>] cpuidle_idle_call+0x6d/0xa5
> > [ 296.337697] [<c1001b51>] cpu_idle+0x92/0xc1
> > [ 296.337704] [<c12c63d0>] start_secondary+0x1f3/0x1fa
> > [ 296.337708] ---[ end trace cd4a1b50139837df ]---
> >
> >
> > Reproducing 100% with pktgen tests.
> >
> What kind of packets are you sending with pktgen?


Here is the sh file to run pktgen.

=====
#!/bin/sh

function pgset() {
local result

echo $1 > $PGDEV

result=`cat $PGDEV | fgrep "Result: OK:"`
if [ "$result" = "" ]; then
cat $PGDEV | fgrep Result:
fi
}

function pg() {
echo inject > $PGDEV
cat $PGDEV
}

# Config Start Here -----------------------------------------------------------


# thread config
# Each CPU has own thread. Two CPU exammple. We add eth1, eth2 respectivly.

PGDEV=/proc/net/pktgen/kpktgend_0
echo "Removing all devices"
pgset "rem_device_all"
echo "Adding eth0"
pgset "add_device eth0"
echo "Setting max_before_softirq 10000"
pgset "max_before_softirq 10000"


# device config
# delay 0 means maximum speed.

CLONE_SKB="clone_skb 500"
# NIC adds 4 bytes CRC
PKT_SIZE="pkt_size 2048"

# COUNT 0 means forever
#COUNT="count 0"
COUNT="count 110110"
DELAY="delay 3"

PGDEV=/proc/net/pktgen/eth0
echo "Configuring $PGDEV"
pgset "$COUNT"
pgset "$CLONE_SKB"
pgset "$PKT_SIZE"
pgset "$DELAY"
pgset "dst ???????"
pgset "dst_mac ????????"


# Time to run
PGDEV=/proc/net/pktgen/pgctrl

echo "Running... ctrl^C to stop"
pgset "start"
echo "Done"

====


Sergey
From: Eric Dumazet on
Le mercredi 31 mars 2010 à 15:14 +0300, Sergey Senozhatsky a écrit :


> PKT_SIZE="pkt_size 2048"
>

If you use 1024 bytes pktgen messages, do you still have the problem ?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Neil Horman on
On Wed, Mar 31, 2010 at 02:29:29PM +0200, Eric Dumazet wrote:
> Le mercredi 31 mars 2010 � 15:14 +0300, Sergey Senozhatsky a �crit :
>
>
> > PKT_SIZE="pkt_size 2048"
> >
>
> If you use 1024 bytes pktgen messages, do you still have the problem ?
>
+1 I wouldn't be suprised if using something over the nominal 1522 byte frame
length on r8169 caused tx errors. The driver doesn't seem to support Jumbo
frames, so my guess is you have to keep the packet size below 1522 bytes.
Neil

>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Sergey Senozhatsky on
On (03/31/10 09:35), Neil Horman wrote:
> On Wed, Mar 31, 2010 at 02:29:29PM +0200, Eric Dumazet wrote:
> > Le mercredi 31 mars 2010 à 15:14 +0300, Sergey Senozhatsky a écrit :
> >
> >
> > > PKT_SIZE="pkt_size 2048"
> > >
> >
> > If you use 1024 bytes pktgen messages, do you still have the problem ?
> >
> +1 I wouldn't be suprised if using something over the nominal 1522 byte frame
> length on r8169 caused tx errors. The driver doesn't seem to support Jumbo
> frames, so my guess is you have to keep the packet size below 1522 bytes.
> Neil

Hm. Good point. I'll test a bit later today.


Sergey
 |  Next  |  Last
Pages: 1 2
Prev: (none)
Next: vbus: update gfp/slab.h includes