lxc & hpsa driver

[Andy Igoshin]

every time lxc-start runs such hpsa messages appear in the host kern.log:

Feb 10 21:16:52 relay1 kernel: [682098.149398] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]

the same appears in container's dmesg and kern.log (attached).

hardware: HP DL380G6

----------------------------------------------------------------------------
root@relay1:~# lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

root@relay1:~# apt-cache policy lxc
lxc:
  Installed: 0.7.5-0ubuntu8.3
  Candidate: 0.7.5-0ubuntu8.3
  Version table:
 *** 0.7.5-0ubuntu8.3 0
        500 http://ru.archive.ubuntu.com/ubuntu/ oneiric-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     0.7.5-0ubuntu8 0
        500 http://ru.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 2012-02-11 20:04 seq
 crw-rw---- 1 root audio 116, 33 2012-02-11 20:04 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=5b931e9c-1d8f-4520-a560-a3f9aa49ab47
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MachineType: HP ProLiant DL380 G6
Package: linux-image-3.0.0-15-server 3.0.0-15.26
PackageArchitecture: amd64
PciMultimedia:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-server root=UUID=424677f3-ece9-4e8d-b730-e36d44042313 ro
ProcVersionSignature: Ubuntu 3.0.0-15.26-server 3.0.13
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-15-server N/A
 linux-backports-modules-3.0.0-15-server N/A
 linux-firmware 1.60
RfKill: Error: [Errno 2] No such file or directory
Tags: oneiric
Uname: Linux 3.0.0-15-server x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

dmi.bios.date: 05/05/2011
dmi.bios.vendor: HP
dmi.bios.version: P62
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP62:bd05/05/2011:svnHP:pnProLiantDL380G6:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL380 G6
dmi.sys.vendor: HP
---
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
Package: lxc 0.7.5-0ubuntu8.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.0.0-15.26-server 3.0.13
Tags: oneiric
Uname: Linux 3.0.0-15-server x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Serge Hallyn (serge-hallyn)]

Thanks for taking the time to report this bug.

Could you see whether adding the following line to your /var/lib/lxc/<container-name>/config:

lxc.cap.drop = sys_module mac_admin

stops the message?

Could you also tell us the exact command line you used to create the container?

[Andy Igoshin (andy-igoshin)]

no, messages still appear (attached).

lxc-create -n sbc -t ubuntu

[Andy Igoshin (andy-igoshin)]

host:

Feb 10 22:50:10 relay1 kernel: 429.615 pa00:40.:c ff806020hschc odto:ukontp:Sne x,AC x0 SQ x,Rtrigrsl:02 m=8 80 00 00 00 00 00 0c0]<4>[687685.535651] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00]
Feb 10 22:50:10 relay1 kernel: [687685.547674] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]
Feb 10 22:50:10 relay1 kernel: [687685.561166] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00]
Feb 10 22:50:10 relay1 kernel: [687685.571939] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]

[Andy Igoshin (andy-igoshin)]

sorry

lxc-create -n sbc -t oneiric

[Serge Hallyn (serge-hallyn)]

Thanks, Andy. In precise, that would have worked. However, in oneiric that created a container with no networking. The reason you have the two minute wait, then, is that the container's NIC is not getting an address, and the container doesn't enter runlevel 2 until the failsafe job kicks in after two minutes. The console starts on runlevel 2.

In oneiric, I usually create a container by doing:

apt-get install libvirt-bin # this is to use the virbr0 bridge it creates
cat < /etc/lxc.conf << EOF
lxc.network.type=veth
lxc.network.link=virbr0
lxc.network.flags=up
EOF

lxc-create -t ubuntu -n sbc -f /etc/lxc.conf

Note that when you created the container with just:

 lxc-create -t ubuntu -n sbd

you should have gotten a warning like this:

================================================================
root@server-4738:~# lxc-create -t ubuntu -n o1

Warning:
-------
Usually the template option is called with a configuration
file option too, mostly to configure the network.
eg. lxc-create -n foo -f lxc.conf -t debian
The configuration file is often:

lxc.network.type=macvlan
lxc.network.link=eth0
lxc.network.flags=up

or alternatively:

lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up

For more information look at lxc.conf (5)

At this point, I assume you know what you do.
Press <enter> to continue ...

================================================================

[Serge Hallyn (serge-hallyn)]

Please try creating a new container as shown above.

I assume that you'll have the same errors when you create the container as above, but it's worth a try. Since I don't have that hardware to reproduce on, once you confirm that you still get the error I'll set this to confirmed.

I may then set the bug as also affecting the kernel and ask you to do an apport-collect, to get some information on the driver.

[Andy Igoshin (andy-igoshin)]

host:

Feb 11 10:36:44 relay1 kernel: [729997.419244] hpsa 0000:04:00.0: cp ffff880036d00a00 has check condition: unknown type:
 Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]

[Andy Igoshin (andy-igoshin)]

i still get this error. see attached files.

[Andy Igoshin (andy-igoshin)]

i still get this error in the new container. see attached files.

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Andy Igoshin (andy-igoshin)]

apport information

[Serge Hallyn (serge-hallyn)]

The hpsa error messages start showing up 10 seconds after boot, so I don't think this is related to lxc.

[Serge Hallyn (serge-hallyn)]

(marking invalid in lxc as I don't believe lxc has anything to do with it)

[Andy Igoshin (andy-igoshin)]

precise:

Apr 29 14:04:10 relay1 kernel: [ 12.193083] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sens
e: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00]
Apr 29 14:04:10 relay1 kernel: [ 12.203846] hpsa 0000:04:00.0: cp ffff880036d00f00 has check condition: unknown type: Sens
e: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00]
Apr 29 14:04:10 relay1 kernel: [ 12.214628] hpsa 0000:04:00.0: cp ffff880036d00000 has check condition: unknown type: Sens
e: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]
Apr 29 14:04:10 relay1 kernel: [ 12.225400] hpsa 0000:04:00.0: cp ffff880036d00280 has check condition: unknown type: Sens
e: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00]

[Grant Slater (firefishy)]

Most likely smartctl is polling a disk on the hpsa controller. My case it was munin cron via hddtemp_smartctl

[Andy Igoshin (andy-igoshin)]

bios updated.
system updated. Linux relay1 3.2.0-52-generic #78-Ubuntu SMP Fri Jul 26 16:21:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Aug 20 21:34:26 relay1 kernel: [ 0.981694] SCSI subsystem initialized
Aug 20 21:34:26 relay1 kernel: [ 1.062233] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Aug 20 21:34:26 relay1 kernel: [ 1.328958] HP HPSA Driver (v 2.0.2-1)
Aug 20 21:34:26 relay1 kernel: [ 1.328989] hpsa 0000:04:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
Aug 20 21:34:26 relay1 kernel: [ 1.329003] hpsa 0000:04:00.0: MSIX
Aug 20 21:34:26 relay1 kernel: [ 1.329047] hpsa 0000:04:00.0: irq 67 for MSI/MSI-X
Aug 20 21:34:26 relay1 kernel: [ 1.329054] hpsa 0000:04:00.0: irq 68 for MSI/MSI-X
Aug 20 21:34:26 relay1 kernel: [ 1.329060] hpsa 0000:04:00.0: irq 69 for MSI/MSI-X
Aug 20 21:34:26 relay1 kernel: [ 1.329065] hpsa 0000:04:00.0: irq 70 for MSI/MSI-X
Aug 20 21:34:26 relay1 kernel: [ 1.348351] hpsa 0000:04:00.0: hpsa0: <0x323a> at IRQ 67 using DAC
Aug 20 21:34:26 relay1 kernel: [ 1.368980] scsi0 : hpsa
Aug 20 21:34:26 relay1 kernel: [ 1.372154] hpsa 0000:04:00.0: RAID device c0b0t0l0 added.
Aug 20 21:34:26 relay1 kernel: [ 1.372159] hpsa 0000:04:00.0: Direct-Access device c0b0t0l1 added.
Aug 20 21:34:26 relay1 kernel: [ 1.372162] hpsa 0000:04:00.0: Direct-Access device c0b0t0l2 added.
Aug 20 21:34:26 relay1 kernel: [ 1.372733] scsi 0:0:0:0: RAID HP P410i 6.00 PQ: 0 ANSI: 5
Aug 20 21:34:26 relay1 kernel: [ 1.372927] scsi 0:0:0:1: Direct-Access HP LOGICAL VOLUME 6.00 PQ: 0 ANSI: 5
Aug 20 21:34:26 relay1 kernel: [ 1.373113] scsi 0:0:0:2: Direct-Access HP LOGICAL VOLUME 6.00 PQ: 0 ANSI: 5
Aug 20 21:34:26 relay1 kernel: [ 1.373329] scsi 0:0:0:0: Attached scsi generic sg0 type 12
Aug 20 21:34:26 relay1 kernel: [ 1.373707] sd 0:0:0:1: Attached scsi generic sg1 type 0
Aug 20 21:34:26 relay1 kernel: [ 1.373787] sd 0:0:0:1: [sda] 585871964 512-byte logical blocks: (299 GB/279 GiB)
Aug 20 21:34:26 relay1 kernel: [ 1.374156] sd 0:0:0:1: [sda] Write Protect is off
Aug 20 21:34:26 relay1 kernel: [ 1.374160] sd 0:0:0:1: [sda] Mode Sense: 6b 00 00 08
Aug 20 21:34:26 relay1 kernel: [ 1.374182] sd 0:0:0:2: Attached scsi generic sg2 type 0
Aug 20 21:34:26 relay1 kernel: [ 1.374217] sd 0:0:0:2: [sdb] 7030462556 512-byte logical blocks: (3.59 TB/3.27 TiB)
Aug 20 21:34:26 relay1 kernel: [ 1.374391] sd 0:0:0:1: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Aug 20 21:34:26 relay1 kernel: [ 1.374551] sd 0:0:0:2: [sdb] Write Protect is off
Aug 20 21:34:26 relay1 kernel: [ 1.374555] sd 0:0:0:2: [sdb] Mode Sense: 6b 00 00 08
Aug 20 21:34:26 relay1 kernel: [ 1.374747] sd 0:0:0:2: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Aug 20 21:34:26 relay1 kernel: [ 1.384545] sda: sda1 sda2 < sda5 >
Aug 20 21:34:26 relay1 kernel: [ 1.386065] sd 0:0:0:1: [sda] Attached SCSI disk
Aug 20 21:34:26 relay1 kernel: [ 1.443872] sdb: sdb1
Aug 20 21:34:26 relay1 kernel: [ ...

[Andy Igoshin (andy-igoshin)]

the same i see on differrent host with HP DL380G7 hardware.

[Andy Igoshin (andy-igoshin)]

fixed on precise with kernel 3.8.0.
Linux relay1 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Andy Igoshin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930285/comments/38 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.