Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Kevin Hilman
On Wed, May 7, 2014 at 1:28 PM, Jason Cooper wrote: [...] > On a broader topic, if we have users in the field running v3.10.y on ARM > systems, then I think it's worth backporting the defconfig changes to > boot-test those systems. Yeah, especially since v3.10 is LTS, it's probably worth doing,

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Jason Cooper
On Wed, May 07, 2014 at 12:36:20PM -0700, Kevin Hilman wrote: > Jason Cooper writes: > > > On Wed, May 07, 2014 at 04:44:42PM +0200, Arnd Bergmann wrote: > >> On Wednesday 07 May 2014 10:20:56 Jason Cooper wrote: > >> > > ipmi message handler version 39.2 > >> > > IPMI System Interface driver. >

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Kevin Hilman
Jason Cooper writes: > On Wed, May 07, 2014 at 04:44:42PM +0200, Arnd Bergmann wrote: >> On Wednesday 07 May 2014 10:20:56 Jason Cooper wrote: >> > > ipmi message handler version 39.2 >> > > IPMI System Interface driver. >> > > ipmi_si: Adding default-specified kcs state machine >> > > ipmi_si: T

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Jason Cooper
On Wed, May 07, 2014 at 04:44:42PM +0200, Arnd Bergmann wrote: > On Wednesday 07 May 2014 10:20:56 Jason Cooper wrote: > > > ipmi message handler version 39.2 > > > IPMI System Interface driver. > > > ipmi_si: Adding default-specified kcs state machine > > > ipmi_si: Trying default-specified kcs st

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Jason Cooper
Corey, On Wed, May 07, 2014 at 09:31:22AM -0500, Corey Minyard wrote: > You probably don't have an IPMI controller on your system. You can just > remove the driver from the config. Kernel 3.15 will have the default > probing removed, and you won't see these messages any more. ahh, here it is:

[Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Jason Cooper
Cory, all, On our ARM boot farm, we've started seeing the following: On Tue, May 06, 2014 at 08:56:47AM -0700, Kevin's boot bot wrote: > > Tree/Branch: stable > Git describe: v3.10.39 > Failed boot tests (console logs at the end) > === >

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Arnd Bergmann
On Wednesday 07 May 2014 10:20:56 Jason Cooper wrote: > > ipmi message handler version 39.2 > > IPMI System Interface driver. > > ipmi_si: Adding default-specified kcs state machine > > ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, > > slave address 0x0, irq 0 > > ipmi_

Re: [Openipmi-developer] IPMI misbehaving on ARM defconfigs, was [Re: stable boot: 18 pass, 4 fail (v3.10.39)]

2014-05-07 Thread Corey Minyard
You probably don't have an IPMI controller on your system. You can just remove the driver from the config. Kernel 3.15 will have the default probing removed, and you won't see these messages any more. -corey On 05/07/2014 09:20 AM, Jason Cooper wrote: > Cory, all, > > On our ARM boot farm, we'v

[Openipmi-developer] #71 Error parsing command arguments, argument 4: Invalid argument

2014-05-07 Thread Tadas
Hello, I'm having some problems while compiling/using openipmi 2.0.21 (and git version). OS: debian 7 (wheezy). Config params: ./configure --prefix=/usr --exec-prefix=/usr --with-openssl=yes First of all, openipmi does not compile and gives you error about: undefined reference to `clock_gettime'