From: Ben Greear <greearb@candelatech.com>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: ixgbe: schedule while atomic bug during dev_disable_lro 2.6.31-rc3
Date: Thu, 16 Jul 2009 14:08:58 -0700 [thread overview]
Message-ID: <4A5F96EA.9010008@candelatech.com> (raw)
In-Reply-To: <4A5F8062.6090009@candelatech.com>
On 07/16/2009 12:32 PM, Ben Greear wrote:
> It is 100% reproducible on the system I'm testing. I haven't tried other
> servers
> or other ixgbe NICs yet.
>
> I'll try w/out pre-empt, should have results later today.
I set pre-empt to Voluntary and I no longer see these warnings
in dmesg.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2009-07-16 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 23:00 ixgbe: schedule while atomic bug during dev_disable_lro 2.6.31-rc3 Ben Greear
2009-07-15 23:35 ` Ben Hutchings
2009-07-15 23:50 ` Ben Greear
2009-07-16 17:39 ` Ben Greear
2009-07-16 19:13 ` Waskiewicz Jr, Peter P
2009-07-16 19:32 ` Ben Greear
2009-07-16 19:58 ` Jesper Dangaard Brouer
2009-07-16 20:17 ` David Miller
2009-07-16 21:08 ` Ben Greear [this message]
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=4A5F96EA.9010008@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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;
as well as URLs for NNTP newsgroup(s).