"Kamal R. Prasad" <kamalp@acm.org> wrote in message
news:1125993654.044815.297800@g14g2000cwa.googlegr oups.com...
>
> Tim Clarke wrote:
> > Hi Kamal...
> >
> > "Kamal R. Prasad" <kamalp@acm.org> wrote in message
> > news:1125915088.450348.15510@g49g2000cwa.googlegro ups.com...
> > > Hello,
> > >
> > > Im getting a spurious crash fixed by IBM as stated below -involving
> > > hd_terminate(). It happens on systems that have jf2 as filesystem type
> > > on aix 5.3 (running mp kernel). Can someone confirm if they get this
> > > crash and/or whether it is an IBM bug or something that can be
> > > triggered by bad ke code?
> > > ------------------------------
> > >
> > > APAR: IY21904 COMPID: 5765C3403 REL: 430
> > > ABSTRACT: HD_TERMINATE(STRIPE)
> > >
> > > PROBLEM DESCRIPTION:
> > > A system experiencing this problem would crash at the
> > > assert in hd_terminate, and analysis of the dump would
> > > indicate that the logical buffer being terminated is
> > > actually a striped physical buffer.
> > >
> > > PROBLEM SUMMARY:
> > > System asserts in hd_terminate
> > >
> > > PROBLEM CONCLUSION:
> > > Fix internal logic for striped and mirrored LVs
> > > ------------------------------
> >
> > The above abstract shows that IBM has an "Open" APAR against the AIX 5.3
> > code for the symptom described. I.E. they recognise there is a problem
in
> > their code that will, eventually be fixed and thus "Close" the APAR, in
due
> > course.
>
> Tim ,
>
> Thanks for the info. I happened to interpret it as -problem has been
> determined and the patch IY21904 should fix the problem. There is
> something in my kext that is causing this problem to show up every
> minute. Does someone know the trigger pt for this crash i.e. what
> inside a kext could trigger it to happen frequently? Also, is there a
> patch in the works that could fix this problem on AIX 5.3?

Not quite true, the APAR documents the "problem" and it's ongoing
status/resolution and, eventually, the PTF that "fixes" the problem for a
specific Version+Release and/or any Correlated PTFs for "other"
Version+Release levels. This APARs "environment" is AIX V4.3 not AIX V5.3,
so there's a notional APAR open against all higher levels than AIX V4.3. If
you have a support option then re-report the problem quoting the APAR hit
against AIX V4.3, this will "kick" the priority of the development of the
V5.3 Correlated fix up a notch.
--
Regards,
Tim Clarke (a.k.a. WBST)