From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: ixgbe issues in 2.6.29.3
Date: Tue, 19 May 2009 08:51:37 -0700 [thread overview]
Message-ID: <4A12D589.7040002@candelatech.com> (raw)
I'm using 2.6.29.3 (plus my hacks, but no changes to ixgbe for what that's worth).
I just got some new hardware: Dual Intel E5530 processors, 12GB RAM, etc
and put in a dual-port 10G NIC with Intel chipset (though made by Silicom).
I tried changing MTU from 1500 to 9000 and started pktgen, and I noticed that a process
that does ethtool ioctls was using 99% of a CPU and strace showed
nothing (and would not ctrl-C to exit). I have modified pktgen, btw.
Some other applications hung as well, and I found this in the logs.
There is a lot of new stuff in my setup, and this could be symptom instead
of cause, but thought I'd post the trace in case it helps.
ixgbe: eth1: ixgbe_change_mtu: changing MTU from 1500 to 9000
------------[ cut here ]------------
WARNING: at /home/greearb/git/linux-2.6.dev.28/net/sched/sch_generic.c:226 dev_watchdog+0xe7/0x148()
Hardware name: X8DTU
NETDEV WATCHDOG: eth1 (ixgbe): transmit timed out
Modules linked in: nf_defrag_ipv4 nfs lockd nfs_acl auth_rpcgss 8021q garp redirdev arc4 michael_mic macvlan wanlink(P) pktgen stp bnep sco l2cap bluetooth
sunrpc ipv6 cpufreq_ondemand acpi_cpufreq freq_table loop dm_multipath scsi_dh uinput pcspkr sg i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support e1000e ixgbe igb
dca inet_lro button sr_mod cdrom joydev dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_piix ata_generic pata_acpi libata sd_mod scsi_mod ext3
jbd mbcache uhci_hcd ohci_hcd ssb ehci_hcd [last unloaded: x_tables]
Pid: 0, comm: swapper Tainted: P W 2.6.29.3 #4
Call Trace:
<IRQ> [<ffffffff8103e67a>] warn_slowpath+0xd3/0xf2
[<ffffffff810306bb>] ? __enqueue_entity+0x74/0x76
[<ffffffff81032369>] ? enqueue_entity+0x1a0/0x1a9
[<ffffffff8103240a>] ? enqueue_task_fair+0x3e/0x43
[<ffffffff812c49ce>] ? _spin_unlock_irqrestore+0x40/0x44
[<ffffffff8102fd3a>] ? task_rq_unlock+0xc/0xe
[<ffffffff8103a39b>] ? try_to_wake_up+0x2a7/0x2b9
[<ffffffff810519e0>] ? autoremove_wake_function+0x11/0x38
[<ffffffff81011a1c>] ? __cycles_2_ns+0x23/0x42
[<ffffffff812c46d0>] ? _spin_lock+0x1e/0x22
[<ffffffff812c4925>] ? _spin_unlock+0x2d/0x38
[<ffffffff812526a0>] ? __netif_tx_unlock+0x14/0x16
[<ffffffff812526ef>] ? netif_tx_lock+0x4d/0x66
[<ffffffff81252772>] ? dev_watchdog+0x0/0x148
[<ffffffff81252859>] dev_watchdog+0xe7/0x148
[<ffffffff81053d28>] ? hrtimer_hres_active+0x1a/0x30
[<ffffffff8104728b>] run_timer_softirq+0x126/0x19c
[<ffffffff81043332>] __do_softirq+0x66/0xe8
[<ffffffff8100d36c>] call_softirq+0x1c/0x34
[<ffffffff8100e5b4>] do_softirq+0x34/0x78
[<ffffffff8104321f>] irq_exit+0x36/0x8a
[<ffffffff8101bea4>] smp_apic_timer_interrupt+0x76/0x83
[<ffffffff8100cda3>] apic_timer_interrupt+0x13/0x20
<EOI> [<ffffffff811a1009>] ? acpi_idle_enter_bm+0x236/0x26d
[<ffffffff811a0fff>] ? acpi_idle_enter_bm+0x22c/0x26d
[<ffffffff8121d5cc>] ? cpuidle_idle_call+0x80/0xb8
[<ffffffff8100ab77>] ? cpu_idle+0x4f/0x92
[<ffffffff812be8b3>] ? start_secondary+0x181/0x186
---[ end trace 8256d1ae7f76313d ]---
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2009-05-19 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A12D589.7040002@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.