All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Ben Hutchings <bhutchings@solarflare.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 10:39:28 -0700	[thread overview]
Message-ID: <4A5F65D0.9080202@candelatech.com> (raw)
In-Reply-To: <4A5E6B37.2080605@candelatech.com>

On 07/15/2009 04:50 PM, Ben Greear wrote:
> On 07/15/2009 04:35 PM, Ben Hutchings wrote:
>> On Wed, 2009-07-15 at 16:00 -0700, Ben Greear wrote:
>>> I just got a fancy new 10G NIC and tried it out in a (patched
>>> elsewhere, but stock ixgbe driver) 2.6.31-rc3) kernel.
>>
>> And what exactly are those patches?
>
> various and sundry, but so far I only see this problem with ixgbe
> (the 1G NICs don't complain at least).
>
> I'll build an un-patched kernel and see if I can reproduce them.

I see the same problem on a stock kernel.  I'm running a pre-empt kernel..think
that might have some bearing on the problem?

Full dmesg here:
http://www.candelatech.com/oss/i7_dmesg.txt

Kernel config file here:
http://www.candelatech.com/oss/i7_config.txt

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2009-07-16 17:39 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 [this message]
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

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=4A5F65D0.9080202@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bhutchings@solarflare.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.