Operating System - HP-UX
1846991 Members
3857 Online
110257 Solutions
New Discussion

Re: Fail to process new kernel

 
Lance Leung
Advisor

Fail to process new kernel

Hi, I am working on an HP 11.00 system and am in the process of testing a patch. After I used SAM to add the Subsystems and then tried to process the new kernel, I got a SAM internal error message. Inside the samlog, it says something like: "The current pointer undefined but is needed for this operation. Location: da_list_gets():305Error Code:1302

Any clue on what could be wrong here? And if there is any fix, workaround available? Thanks.

Lance
5 REPLIES 5
S.K. Chan
Honored Contributor

Re: Fail to process new kernel

What was the last patch/patches that you installed before the error occur ?
Lance Leung
Advisor

Re: Fail to process new kernel

Hi S.K.,
The machine is on loan so I don't know which patch was the last one applied. Any particular patch that I should look for? I saw some similar error message related to PHCO_21187 but then I was trying to edit the NIS table.

Lance
S.K. Chan
Honored Contributor

Re: Fail to process new kernel

It's quite hard to pin point what's the root cause. Have you looked at /var/sam/log/samlog file to see if you can spot any other error before or after the "da_list_gets" error ? Sometimes SAM misbehaves if you got some "funky" driver in the kernel, etc. I've seen a few times with networking related kernel (but can't rememember which driver). I would install the latest SAM cumulative patch (ie PHCO_23876), this patch actually superseed earlier patches (21187 and 21267) and it has no other dependencies plus it doesn't reboot upon installation. Why don't you give that a try.
Sanjay_6
Honored Contributor

Re: Fail to process new kernel

Lance Leung
Advisor

Re: Fail to process new kernel

Hi I think I know what the problem is right now. I tried to rebuild the kernel with the mk_kernel command and this time, I got a bunch of unsatisfied symbols messages. Tracking down these symbols showed me that their patches PHKL_22126 and PHKL_20349 might have been superceded by something else.

Thanks.

Lance