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
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
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
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
the same i see on differrent host with HP DL380G7 hardware.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug go to:
** Tags added: bios-outdated needs-upstream-testing
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about
Most likely smartctl is polling a disk on the hpsa controller. My case
it was munin cron via hddtemp_smartctl
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa
precise:
Apr 29 14:04:10 relay1 kernel: [ 12.193083] hpsa :04:00.0: cp
880036d0 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: [
(marking invalid in lxc as I don't believe lxc has anything to do with
it)
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug go to:
The hpsa error messages start showing up 10 seconds after boot, so I
don't think this is related to lxc.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug go
apport information
** Tags added: apport-collected oneiric
** Description changed:
every time lxc-start runs such hpsa messages appear in the host
kern.log:
Feb 10 21:16:52 relay1 kernel: [682098.149398] hpsa :04:00.0: cp
880036d0 has check condition: unknown type: Sense:
i still get this error in the new container. see attached files.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2729936/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2729937/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
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?
** Changed in: lxc
no, messages still appear (attached).
lxc-create -n sbc -t ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug
** Attachment added: dmesg.new1
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2730052/+files/dmesg.new1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
** Attachment added: kern.log.new1
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2730053/+files/kern.log.new1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
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
:04:00.0: cp 880036d0 has check condition: unknown type: Sense:
0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2, cmd=[85
sorry
lxc-create -n sbc -t oneiric
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug go to:
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
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
** Attachment added: test-dmesg
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2731012/+files/test-dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
** Attachment added: test-kern.log
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2731013/+files/test-kern.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Attachment added: test-syslog
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930285/+attachment/2731014/+files/test-syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
i still get this error. see attached files.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930285
Title:
lxc hpsa driver
To manage notifications about this bug go to:
host:
Feb 11 10:36:44 relay1 kernel: [729997.419244] hpsa :04:00.0: cp
880036d00a00 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]
--
You received this bug notification because you are
28 matches
Mail list logo