Hi all,
[A report from Mark's buildbot]
After merging the net-next tree, today's linux-next build (arm allmodconfig) failed like thisi (this has actually been failing for a few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Caused by commit
49425dfc7451 ("ixgbe: Add support for x550em_a 10G MAC type")
arm only allows udelay()s up to 2 milliseconds. This commit adds a 5 ms udelay in ixgbe_acquire_swfw_sync_x550em_a() in drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c.
From: Stephen Rothwell sfr@canb.auug.org.au Date: Wed, 13 Apr 2016 17:50:28 +1000
After merging the net-next tree, today's linux-next build (arm allmodconfig) failed like thisi (this has actually been failing for a few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Caused by commit
49425dfc7451 ("ixgbe: Add support for x550em_a 10G MAC type")
arm only allows udelay()s up to 2 milliseconds. This commit adds a 5 ms udelay in ixgbe_acquire_swfw_sync_x550em_a() in drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c.
Jeff, please have your folks look into this. Probably just a simple conversion to mdelay().
Thanks!
On Wednesday 13 April 2016 11:15:13 David Miller wrote:
From: Stephen Rothwell sfr@canb.auug.org.au Date: Wed, 13 Apr 2016 17:50:28 +1000
After merging the net-next tree, today's linux-next build (arm allmodconfig) failed like thisi (this has actually been failing for a few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Caused by commit
49425dfc7451 ("ixgbe: Add support for x550em_a 10G MAC type")
arm only allows udelay()s up to 2 milliseconds. This commit adds a 5 ms udelay in ixgbe_acquire_swfw_sync_x550em_a() in drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c.
Jeff, please have your folks look into this. Probably just a simple conversion to mdelay().
I sent a patch, pretty sure we can use msleep() here rather than a wasteful mdelay().
Arnd
On Wed, Apr 13, 2016 at 11:15:13AM -0400, David Miller wrote:
From: Stephen Rothwell sfr@canb.auug.org.au
After merging the net-next tree, today's linux-next build (arm allmodconfig) failed like thisi (this has actually been failing for a few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Caused by commit
49425dfc7451 ("ixgbe: Add support for x550em_a 10G MAC type")
arm only allows udelay()s up to 2 milliseconds. This commit adds a 5 ms udelay in ixgbe_acquire_swfw_sync_x550em_a() in drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c.
Jeff, please have your folks look into this. Probably just a simple conversion to mdelay().
This is still present, it's been breaking ARM allmodconfig builds for about two weeks now.
On Fri, 2016-04-22 at 10:20 +0100, Mark Brown wrote:
On Wed, Apr 13, 2016 at 11:15:13AM -0400, David Miller wrote:
From: Stephen Rothwell sfr@canb.auug.org.au
After merging the net-next tree, today's linux-next build (arm allmodconfig) failed like thisi (this has actually been failing
for a
few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko]
undefined!
Caused by commit
49425dfc7451 ("ixgbe: Add support for x550em_a 10G MAC type")
arm only allows udelay()s up to 2 milliseconds. This commit adds a 5 ms udelay in ixgbe_acquire_swfw_sync_x550em_a() in drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c.
Jeff, please have your folks look into this. Probably just a
simple
conversion to mdelay().
This is still present, it's been breaking ARM allmodconfig builds for about two weeks now.
Interesting that no one spoke up until just a week ago. I have a fix and I ready to push it to David Miller.
On Fri, Apr 22, 2016 at 04:20:43PM -0700, Jeff Kirsher wrote:
On Fri, 2016-04-22 at 10:20 +0100, Mark Brown wrote:
Jeff, please have your folks look into this. Probably just a
simple
conversion to mdelay().
This is still present, it's been breaking ARM allmodconfig builds for about two weeks now.
Interesting that no one spoke up until just a week ago. I have a fix and I ready to push it to David Miller.
Like Stephen said it had been there for a couple of days already at the time it was reported; I happened to be busy at the time it came up so wasn't looking at the build reports myself. If you've got a fix please get it submitted ASAP, having common test configurations broken for any length of time does get disruptive.
linaro-kernel@lists.linaro.org
-
Arnd Bergmann -
David Miller -
Jeff Kirsher -
Mark Brown -
Stephen Rothwell