[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#644362: linux-image-2.6.39-bpo.2-686-pae: hpacucli hangs when creating disks on cciss



On Thu, 2011-10-06 at 08:03 -0500, scameron@beardog.cce.hp.com wrote:
> On Thu, Oct 06, 2011 at 01:55:37AM -0500, Jonathan Nieder wrote:
> > leo weppelman wrote[1]:
> > 
> > > I tried to reproduce the problem with 3.1.0-rc7-686-pae from
> > > experimental as you requested, but I failed. The problem is that
> > > hpacucli does not find any controllers with this kernel :-( I used the
> > > latest available hpacucli version (8.75-12.0). This version definitely
> > > works with 2.6.39. I tried strace-ing hpacucli but that didn't give me
> > > any clues. It was looking for /dev/cciss/c0d0/cciss, which is weird
> > > and might indicate that the 3.1 environment makes the hpacucli device
> > > search fail....
> > 
> > Weird.  Stephen et al: any ideas?
> 
> Yeah I suspect I know what's going on.  There was some code
> in hpaaculi which was asking the question "Is this a 2.4 kernel?
> Or is this a 2.6 kernel?" It didn't consider the possibility of
> a 3.x kernel, and in the face of a 3.x kernel, it just kind of
> gave up.
> 
> Pretty sure this bug is fixed in a released version of hpacucli
> because rhel6.1 uses a 3.x kernel, and I know we support that.
> 
> Bill Kilcoyne might know the specifics.

RHEL 6 will be sticking with what is nominally version 2.6.32, although
RH continues to backport large changes from later versions.  The first
stable distribution with a 3.x kernel will presumably be Ubuntu 11.10
'oneiric'.

Stable update 3.0.4 added a process personality flag that causes the
kernel to report version numbers beginning '2.6.', and the 'setarch'
command in util-linux has been updated to allow setting this flag.
However. neither Debian nor Ubuntu has this new version of util-linux
yet.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: