By  "stuck in DIAG 308 land", I mean a reboot loop.

I should subscribe to the Herc list.


What happens is this:  the kernel loads, console traffic begins, but
before /sbin/init can get launched something triggers DIAG 308.  (In
fact, I think this is before the root gets mounted.)  If I boot from
disk, it loops rebooting.  If I boot from the
reader, it stops.  (empty hopper - duh!)


I guess the DIAG 308 code in Hercules is working because when booting
from disk it keeps going and going ... [insert Energizer Bunny humor
here]   So I don't know what trips the reboot:  there's no panic, just
signalling the processor(s) to stop, then 308.


-- R;   <><





On Sun, Dec 14, 2008 at 7:53 AM, Harold Grovesteen
<[email protected]> wrote:
> Rick, what does "stuck in DIAG 308 reboot land" mean?  Is the rebooting
> not working or is it rebooting when it should not be?  Hercules has code
> to support DIAG 308.  If there is a problem with DIAG 308 itself, that
> should be posted on the Hercules list.
>
> However, it sounds more like there is something causing the reboot to
> occur.  The Hercules list might be able to assist you in figuring that
> out.  The ultimate fix might need to come from the folks here once the
> root cause of the problem is understood.
>
> What build logic were you re-inserting and why?
>
> If you are not subscribed to the Hercules email list try
>
> http:/groups.yahoo.com/group/hercules-390
>
> Harold Grovesteen
>
> Rick Troth wrote:
>
>> folks --
>>
>>
>> Maybe someone can give me a tip
>> and advise me what I'm doing wrong.
>> Have tried off and on for quite a while now to re-visit
>> Linux on Hercules and consistently get stuck in DIAG 308 reboot land.
>> I have tried both home-grown kernels and distributed kernels.
>> Have used INITRD and statically compiled-in disk drivers.
>> The result is the same: before /sbin/init runs, reboot gets called.
>>
>>
>> One of our colleagues on this list suggested that I take a CVS
>> snap-shot of the current Herc tree.  Did that.  No joy.  (Some amount
>> of twiddling to re-insert the build logic, but am confident that is
>> correct.)  I've gone back and tried older Hercules builds.  No joy.
>>
>>
>> I have tried both 64-bit and 31-bit kernels.  Same thing.
>>
>>
>> Thoughts?
>>
>>
>> -- R;   <><
>>
>> ----------------------------------------------------------------------
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>
>>
>>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to