On Thu, Mar 7, 2013 at 10:50 AM, Michael Wang
wrote:
> On 03/07/2013 04:50 PM, Linda Walsh wrote:
>>
>> I am *not* seeing the bug in 3.8.2 with the 2nd patch applied (in
>> addition to the first)...
>
> So that means bond lock is the reason, nice, but this is really not a
> good fix if we just unl
On 03/07/2013 04:50 PM, Linda Walsh wrote:
>
> I am *not* seeing the bug in 3.8.2 with the 2nd patch applied (in
> addition to the first)...
So that means bond lock is the reason, nice, but this is really not a
good fix if we just unlock it...
The better way is to move the cycle wait logical out
On 03/07/2013 03:05 PM, Linda Walsh wrote:
[snip]
> [ 24.820010] BUG: scheduling while atomic: kworker/u:2/109/0x0002
> [ 24.826415] 4 locks held by kworker/u:2/109:
> [ 24.826425] #0: ((bond_dev->name)){..}, at:
> [] process_one_work+0x13d/0x5d0
> [ 24.826428] #1: ((&(&bond->mi
On 03/07/2013 03:05 PM, Linda Walsh wrote:
>
>
>
>
> Michael Wang wrote:
>> On 03/02/2013 01:21 PM, Linda Walsh wrote:
>> Update -- it *used* to stop the messages in 3.6.7.
>>
>> It no longer stops the messages in 3.8.1 -- (and isn't present by
>> default -- tried
>> adding the unlock/lock -- n
Michael Wang wrote:
> On 03/02/2013 01:21 PM, Linda Walsh wrote:
> Update -- it *used* to stop the messages in 3.6.7.
>
> It no longer stops the messages in 3.8.1 -- (and isn't present by
> default -- tried
> adding the unlock/lock -- no difference.
>
> Weird. *sigh*
>
> Hi, Linda
>
> Do you ha
On 03/02/2013 01:21 PM, Linda Walsh wrote:
>
>
>
>
> Linda Walsh wrote:
>>
>>
>> This patch is not in the latest kernel. I don't know if it is the
>> 'best' way, but it does stop BUG error messages.
> ---
> Update -- it *used* to stop the messages in 3.6.7.
>
> It no longer stops the messages
Linda Walsh wrote:
>
>
> This patch is not in the latest kernel. I don't know if it is the
> 'best' way, but it does stop BUG error messages.
---
Update -- it *used* to stop the messages in 3.6.7.
It no longer stops the messages in 3.8.1 -- (and isn't present by
default -- tried
adding the un
On Fri, 2013-03-01 at 00:15 -0800, Linda Walsh wrote:
> Just installed 3.8.1
>
> Thought this had been fixed? Note it causes the kernel to
> show up as tainted after the 1st...
>
CC netdev & Jay Vosburgh & Jeff Kirsher
>
>
> As the system was coming up and initializing the bond0 driver:
Just installed 3.8.1
Thought this had been fixed? Note it causes the kernel to
show up as tainted after the 1st...
As the system was coming up and initializing the bond0 driver:
[ 19.847743] ixgbe :06:00.0: registered PHC device on eth_s2_0
[ 20.258245] BUG: scheduling while ato
9 matches
Mail list logo
