ipmi kernel modules not detecting OCPv3 AMD Roadrunner BMC

[David Duffey]

In order for the ipmi kernel modules to work on the OCPv3 AMD Roadrunner machine I need to run the attached script.

Here is the output of the device information:

test@precise2:~$ PCIADDRESS=`lspci | grep 16b9 | awk '{print $1}'`

test@precise2:~# echo "BMC PCI Address is "$PCIADDRESS
BMC PCI Address is 02:00.6

test@precise2:~$ lspci -s $PCIADDRESS -vvv
02:00.6 IPMI SMIC interface: Broadcom Corporation Device 16b9 (prog-if 01)
 Subsystem: Broadcom Corporation Device 96b9
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Region 0: Memory at d0010000 (64-bit, prefetchable) [size=64K]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=64K]
 Capabilities: <access denied>
 Kernel driver in use: ipmi_si
 Kernel modules: ipmi_si

[David Duffey (dduffey)]

cert blocker

[David Duffey (dduffey)]

I've now tried this in Suacey as well with the same result, commands like "ipmitool lan print" do not work as no BMC is found unless you run the script above so that the ipmi_si kernel model will be able to find the BMC.

I'm not sure how that kernel model works, but I suspect it may need an updated entry for the PCIid alias table, or update to an address table?

[David Duffey (dduffey)]

Related to this same component: https://bugs.launchpad.net/opencompute/+bug/1178899.

[Stefan Bader (smb)]

David, could you add (or replace above output) the output of "lspci -vvvnn -s 02:00.6" so we can see all the id numbers. It seems the ipmi part can be done by adding a pci id to the ipmi_si driver. Are we aware of anybody else being on this already?

[David Duffey (dduffey)]

Here is the output of lspci -vvvv on that device. Notice the address change... I'm guessing this may be because I removed an add-on PCI card in the process.

01:00.6 IPMI SMIC interface: Broadcom Corporation Device 16b9 (prog-if 01)
 Subsystem: Broadcom Corporation Device 96b9
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Region 0: Memory at d0010000 (64-bit, prefetchable) [size=64K]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=64K]
 Capabilities: [48] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
 Capabilities: [ac] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
   MaxPayload 128 bytes, MaxReadReq 4096 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <2us
   ClockPM+ Surprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -3.5dB
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
 Capabilities: [150 v1] Power Budgeting <?>
 Capabilities: [160 v1] Virtual Channel
  Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
  Arb: Fixed- WRR32- WRR64- WRR128-
  Ctrl: ArbSelect=Fixed
  Status: InProgress-
  VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
   Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
   Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
   Status: NegoPending- InProgress-
 Kernel driver in use: ipmi_si
 Kernel modules: ipmi_si

[Stefan Bader (smb)]

On 25.06.2013 18:32, David Duffey wrote:
> Here is the output of lspci -vvvv on that device. Notice the address
> change... I'm guessing this may be because I removed an add-on PCI card
> in the process.
>
>
> 01:00.6 IPMI SMIC interface: Broadcom Corporation Device 16b9 (prog-if 01)
> Subsystem: Broadcom Corporation Device 96b9
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Region 0: Memory at d0010000 (64-bit, prefetchable) [size=64K]
> Region 2: Memory at d0000000 (64-bit, prefetchable) [size=64K]
> Capabilities: [48] Power Management version 3
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
> Capabilities: [ac] Express (v2) Endpoint, MSI 00
> DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
> MaxPayload 128 bytes, MaxReadReq 4096 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
> LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <2us
> ClockPM+ Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
> DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
> LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
> Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
> Compliance De-emphasis: -6dB
> LnkSta2: Current De-emphasis Level: -3.5dB
> Capabilities: [100 v1] Advanced Error Reporting
> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
> AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
> Capabilities: [150 v1] Power Budgeting <?>
> Capabilities: [160 v1] Virtual Channel
> Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
> Arb: Fixed- WRR32- WRR64- WRR128-
> Ctrl: ArbSelect=Fixed
> Status: InProgress-
> VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
> Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
> Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
> Status: NegoPending- InProgress-
> Kernel driver in use: ipmi_si
> Kernel modules: ipmi_si
>
The address won't be important. I was more looking for the complete numeric
values of the pci vendor and model number. And that would actually need a ...

[David Duffey (dduffey)]

When testing a related bug for the tg3 driver (https://bugs.launchpad.net/opencompute/+bug/1178899) using this kernel (http://people.canonical.com/~ogasawara/lp1178899/) the ipmi_si module successfully worked.

[David Duffey (dduffey)]

@ Stefan, brainfart on my side and missed the correct commands... here is the correct output of lspci -vvvnn. Also note this is running on the working kernel from comment #8, if that matters.

02:00.6 IPMI SMIC interface [0c07]: Broadcom Corporation Device [14e4:16b9] (prog-if 01)
 Subsystem: Broadcom Corporation Device [14e4:96b9]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Region 0: Memory at d0010000 (64-bit, prefetchable) [size=64K]
 Region 2: Memory at d0000000 (64-bit, prefetchable) [size=64K]
 Capabilities: [48] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
 Capabilities: [ac] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
   MaxPayload 128 bytes, MaxReadReq 4096 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <2us
   ClockPM+ Surprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -3.5dB
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
 Capabilities: [150 v1] Power Budgeting <?>
 Capabilities: [160 v1] Virtual Channel
  Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
  Arb: Fixed- WRR32- WRR64- WRR128-
  Ctrl: ArbSelect=Fixed
  Status: InProgress-
  VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
   Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
   Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
   Status: NegoPending- InProgress-
 Kernel driver in use: ipmi_si
 Kernel modules: ipmi_si

[David Duffey (dduffey)]

Also here is the output of the ipmi_si module being loaded with the stock kernel (failed) and the leann kernel (works)

failed:

Jun 25 09:38:42 precise2 kernel: [ 186.940809] IPMI System Interface driver.
Jun 25 09:38:42 precise2 kernel: [ 186.940857] ipmi_si 0000:02:00.6: probing via PCI
Jun 25 09:38:42 precise2 kernel: [ 186.940871] ipmi_si 0000:02:00.6: [mem 0xd0010000-0xd001ffff 64bit pref] regsize 1 spacing 1 irq 0
Jun 25 09:38:42 precise2 kernel: [ 186.940877] ipmi_si: Adding PCI-specified kcs state machine
Jun 25 09:38:42 precise2 kernel: [ 186.940929] ipmi_si: probing via SMBIOS
Jun 25 09:38:42 precise2 kernel: [ 186.940935] ipmi_si: SMBIOS: mem 0x0 regsize 1 spacing 1 irq 0
Jun 25 09:38:42 precise2 kernel: [ 186.940939] ipmi_si: Adding SMBIOS-specified kcs state machine
Jun 25 09:38:42 precise2 kernel: [ 186.940946] ipmi_si: probing via SPMI
Jun 25 09:38:42 precise2 kernel: [ 186.940951] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jun 25 09:38:42 precise2 kernel: [ 186.940954] ipmi_si: Adding SPMI-specified kcs state machine
Jun 25 09:38:42 precise2 kernel: [ 186.940961] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0010000, slave address 0x0, irq 0
Jun 25 09:38:42 precise2 kernel: [ 186.941060] ipmi_si: There appears to be no BMC at this location
Jun 25 09:38:42 precise2 kernel: [ 187.000213] ipmi_si: Trying SMBIOS-specified kcs state machine at mem address 0x0, slave address 0x20, irq 0
Jun 25 09:38:42 precise2 kernel: [ 187.000221] ipmi_si: Could not set up I/O space
Jun 25 09:38:42 precise2 kernel: [ 187.064302] ipmi_si: Trying SPMI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jun 25 09:38:42 precise2 kernel: [ 187.064315] ipmi_si: Interface detection failed

works:

Jun 25 09:52:26 precise2 kernel: [ 71.395877] IPMI System Interface driver.
Jun 25 09:52:26 precise2 kernel: [ 71.395908] ipmi_si 0000:02:00.6: probing via PCI
Jun 25 09:52:26 precise2 kernel: [ 71.395982] ipmi_si 0000:02:00.6: [mem 0xd0010000-0xd001ffff 64bit pref] regsize 1 spacing 4 irq 0
Jun 25 09:52:26 precise2 kernel: [ 71.395984] ipmi_si: Adding PCI-specified kcs state machine
Jun 25 09:52:26 precise2 kernel: [ 71.396019] ipmi_si: probing via SMBIOS
Jun 25 09:52:26 precise2 kernel: [ 71.396021] ipmi_si: SMBIOS: mem 0x0 regsize 1 spacing 1 irq 0
Jun 25 09:52:26 precise2 kernel: [ 71.396022] ipmi_si: Adding SMBIOS-specified kcs state machine
Jun 25 09:52:26 precise2 kernel: [ 71.396026] ipmi_si: probing via SPMI
Jun 25 09:52:26 precise2 kernel: [ 71.396028] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jun 25 09:52:26 precise2 kernel: [ 71.396028] ipmi_si: Adding SPMI-specified kcs state machine
Jun 25 09:52:26 precise2 kernel: [ 71.396031] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0010000, slave address 0x0, irq 0
Jun 25 09:52:26 precise2 kernel: [ 71.523906] ipmi_si: Invalid return from get global enables command, cannot enable the event buffer.
Jun 25 09:52:26 precise2 kernel: [ 71.524531] ipmi_si 0000:02:00.6: Error clearing flags: ff
Jun 25 09:52:26 precise2 kernel: [ 71.529347] ipmi_si 0000:02:00.6: Found new BMC (man_id: 0x001...

[Stefan Bader (smb)]

Ah ok, so it seems the basic support was already in for quite some time. I am not remembering which kernel version was used in the failing case but there seems to have been a change upstream about v3.7-rc2 which allows detecting a different regspacing and the working output seems to have detected a spacing of 4 while the old code only used 1. The relevant change there was:

commit a6c16c2803089f032f86fe15e952176c0713d6e3
Author: Corey Minyard <email address hidden>
Date: Tue Oct 16 15:53:40 2012 -0500

    IPMI: Detect register spacing on PCI interfaces

[Stefan Bader (smb)]

Probably should have stated that more explicit in previous comment. Is there need for a backport into pre-3.7 kernels? Raring/13.04 should be ok as it is 3.8.

[David Duffey (dduffey)]

As long as it lands in the 12.04.3 LTS point release (August?), that is okay, no need to backport.

I have two questions though.

1. I don't think I've tested this on stock raring. Should I test on stock raring or on a daily 12.04.3 build to make sure this will land in 12.04.3?

2. Could you also look into a related tg3 driver bug (same platform, same NIC) I would like to have land in 12.04.3. It works in Saucy but not raring (3.8). https://bugs.launchpad.net/opencompute/+bug/1178899

Thanks,

David

[Stefan Bader (smb)]

1. Not necessarily for the sake of the ipmi support only. If it works with the raring kernel it will work when the raring kernel becomes the 12.04.3 kernel. But I guess it make sense to get back to that as part of an overall integration test. So when we have a fix for 2. and think that kernel has landed in the daily previews.

2. Yes, I try to contact Leann to make sure we are not duplicating work (next week) and have a look.

[David Duffey (dduffey)]

I've tested stock raring (3.8.0-19) and proposed (3.8.0-27-40) and the ipmi interface doesn't work as I expected it to. I would like to see this support included in 12.04.3 LTS.

Here is the relevant information from inserting the ipmi_si module:

Jul 12 17:04:45 ubuntu kernel: [ 16.947988] ipmi_si 0000:02:00.6: probing via PCI
Jul 12 17:04:45 ubuntu kernel: [ 16.948038] ipmi_si 0000:02:00.6: [mem 0xd0010000-0xd001ffff 64bit pref] regsize 1 spacing 4 irq 0
Jul 12 17:04:45 ubuntu kernel: [ 16.948040] ipmi_si: Adding PCI-specified kcs state machine
Jul 12 17:04:45 ubuntu kernel: [ 16.948082] ipmi_si: probing via SMBIOS
Jul 12 17:04:45 ubuntu kernel: [ 16.948084] ipmi_si: SMBIOS: mem 0x0 regsize 1 spacing 1 irq 0
Jul 12 17:04:45 ubuntu kernel: [ 16.948085] ipmi_si: Adding SMBIOS-specified kcs state machine
Jul 12 17:04:45 ubuntu kernel: [ 16.948087] ipmi_si: probing via SPMI
Jul 12 17:04:45 ubuntu kernel: [ 16.948089] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 12 17:04:45 ubuntu kernel: [ 16.948090] ipmi_si: Adding SPMI-specified kcs state machine
Jul 12 17:04:45 ubuntu kernel: [ 16.948092] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0010000, slave address 0x0, irq 0
Jul 12 17:04:45 ubuntu kernel: [ 17.073723] ipmi_si: Invalid return from get global enables command, cannot enable the event buffer.
Jul 12 17:04:45 ubuntu kernel: [ 17.074433] ipmi_si 0000:02:00.6: Error clearing flags: ff
Jul 12 17:04:45 ubuntu kernel: [ 17.079455] ipmi_si 0000:02:00.6: Found new BMC (man_id: 0x00113d, prod_id: 0x165d, dev_id: 0x01)
Jul 12 17:04:45 ubuntu kernel: [ 17.079462] ipmi_si 0000:02:00.6: IPMI kcs interface initialized

[David Duffey (dduffey)]

If I use the script to manually load the ipmi driver (from comment #1) the ipmi device works.

[Stefan Bader (smb)]

Comment #15 would mean to me that it _was_ discovered. The regspacing and address of the pci discovery looks identical to the working case and the last line says the module was initialized.

[David Duffey (dduffey)]

I would tend to agree as well, but the ipmi devices are not created if
I simply boot or reload the module and things like "ipmitool lan
print" do not work (until I run the script to initialize).

I can do some more poking around if you give ideas.

David

[Stefan Bader (smb)]

If you could make sure which part of dmesg info related to the ipmi modules is
there before manual probing (well essentially right after boot as this should be
automatic). And maybe you could check which ipmi modules are loaded then.
And maybe compare whether there is any difference after manual probing.
With ipmi devices, you mean /dev/ipmi0?

[David Duffey (dduffey)]

I tried the precise daily build (08-Aug-2013) which had the kernel 3.8.0-27-generic #40 for the installer... then after I rebooted 3.8.0-28-generic #41 was installed.

uname -a suggests the installer kernel was built/compiled on Fri Jul 19th?

Anyway, the BMC did not work (ipmitool lan print). I used the script above to manually load it... and then, quite annoyingly, when I rebooted to capture logs and output, it just worked.....

I'm not sure if the problem is intermittent or not... so will do some additional desting

[David Duffey (dduffey)]

So after some testing what I found was that after installing ipmitool a reboot was required, after the reboot the ipmi_devintf module was loaded.

When doing a first boot, only ipmi_si and ipmi_msghandler is loaded... installing ipmitool complains that /dev/ipmi* doesn't exist. After rebooting the ipmi_devintf module is loaded fine and ipmitool works.

Changed this to Fix Committed.

Thanks Stefan! (now on to MAAS testing!)

[Stefan Bader (smb)]

Setting this to fix released but I do not know for sure. Sounds like it was and this was back in Trusty, so I assume there would have been updates if this did not get out.