[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100311.100519.124285161.davem@davemloft.net>
Date: Thu, 11 Mar 2010 10:05:19 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: mchan@...adcom.com
Cc: brian.haley@...com, bonbons@...ux-vserver.org, benli@...adcom.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: BNX2: Kernel crashes with 2.6.31 and 2.6.31.9
From: "Michael Chan" <mchan@...adcom.com>
Date: Thu, 11 Mar 2010 09:49:56 -0800
>
> On Wed, 2010-03-10 at 18:09 -0800, Brian Haley wrote:
>> >> I'm able to cause a netdev_watchdog timeout by changing the coalesce
>> >> settings on my bnx2, I built a little test program for it:
>> >
>> > Do you run this program in a loop? How quickly do you see the NETDEV
>> > WATCHDOG?
>>
>> It's run once, and we see it almost immediately after ETHTOOL_SCOALESCE.
>
> What's the difference between running the test program and doing ethtool
> -C? Do you see the issue in either case? I don't see the issue here
> with ethtool -C.
Probably because the independent program runs faster and thus
can trigger races more easily.
In any case, you should be trying to reproduce his problem with
his test program since he went through the effort of providing
one.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists