Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-29 Thread Hannes Frederic Sowa
On 29.12.2015 00:21, Cong Wang wrote: On Thu, Dec 24, 2015 at 2:25 AM, Hannes Frederic Sowa wrote: Hi, On 24.12.2015 00:03, Calvin Owens wrote: This patch addresses the issue cited in 7332a13b038be05c by making vxlan actually check if ipv6 is loaded, and reverts it to module_init() so that it

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-28 Thread Cong Wang
On Wed, Dec 23, 2015 at 3:03 PM, Calvin Owens wrote: > Commit 7332a13b038be05c ("vxlan: defer vxlan init as late as possible") > changed vxlan to use late_initcall(), because vxlan relies on ipv6 being > loaded when a new device is opened. > > This causes netconsole to panic at boot when configure

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-28 Thread Cong Wang
On Thu, Dec 24, 2015 at 2:25 AM, Hannes Frederic Sowa wrote: > Hi, > > On 24.12.2015 00:03, Calvin Owens wrote: >> This patch addresses the issue cited in 7332a13b038be05c by making vxlan >> actually check if ipv6 is loaded, and reverts it to module_init() so >> that it becomes device_initcall() w

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-24 Thread Hannes Frederic Sowa
Hi, On 24.12.2015 00:03, Calvin Owens wrote: > On Thursday 12/17 at 17:46 -0800, Calvin Owens wrote: >> On Thursday 12/17 at 17:08 -0800, Eric Dumazet wrote: >>> On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote: With built-in netconsole and IXGBE, configuring netconsole via the kernel >>

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-23 Thread Calvin Owens
On Thursday 12/17 at 17:46 -0800, Calvin Owens wrote: > On Thursday 12/17 at 17:08 -0800, Eric Dumazet wrote: > > On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote: > > > With built-in netconsole and IXGBE, configuring netconsole via the kernel > > > cmdline results in the following panic at bo

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-17 Thread Calvin Owens
On Thursday 12/17 at 17:08 -0800, Eric Dumazet wrote: > On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote: > > With built-in netconsole and IXGBE, configuring netconsole via the kernel > > cmdline results in the following panic at boot: > > > > netpoll: netconsole: device eth0 not up yet,

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-17 Thread Calvin Owens
On Thursday 12/17 at 17:10 -0800, Stephen Hemminger wrote: > On Thu, 17 Dec 2015 15:52:39 -0800 > Calvin Owens wrote: > > > With built-in netconsole and IXGBE, configuring netconsole via the kernel > > cmdline results in the following panic at boot: > > > > netpoll: netconsole: device eth0 n

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-17 Thread Stephen Hemminger
On Thu, 17 Dec 2015 15:52:39 -0800 Calvin Owens wrote: > With built-in netconsole and IXGBE, configuring netconsole via the kernel > cmdline results in the following panic at boot: > > netpoll: netconsole: device eth0 not up yet, forcing it > usb 2-1: new high-speed USB device number 2 u

Re: [PATCH] netconsole: Initialize after all core networking drivers

2015-12-17 Thread Eric Dumazet
On Thu, 2015-12-17 at 15:52 -0800, Calvin Owens wrote: > With built-in netconsole and IXGBE, configuring netconsole via the kernel > cmdline results in the following panic at boot: > > netpoll: netconsole: device eth0 not up yet, forcing it > usb 2-1: new high-speed USB device number 2 usi

[PATCH] netconsole: Initialize after all core networking drivers

2015-12-17 Thread Calvin Owens
With built-in netconsole and IXGBE, configuring netconsole via the kernel cmdline results in the following panic at boot: netpoll: netconsole: device eth0 not up yet, forcing it usb 2-1: new high-speed USB device number 2 using ehci-pci ixgbe :03:00.0: registered PHC device on eth0