Bug 128012 - IPF OS_INIT handler does not print any information
Summary: IPF OS_INIT handler does not print any information
Keywords:
Status: CLOSED DUPLICATE of bug 130800
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anil S Keshavamurthy
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-16 12:28 UTC by Jun'ichi NOMURA
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-09 20:40:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jun'ichi NOMURA 2004-07-16 12:28:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.6)
Gecko/20040528 Debian/1.6-7

Description of problem:
   IPF OS_INIT handler (which is implemented in arch/ia64/kernel/mca.c)
   is called when INIT interrupt is issued.

   The handler in RHEL3 prints the processor's register information
   to the console.

   It works on 2.4.21-15.EL, but it does not work on 2.4.21-17.EL.
   I also tried 2.6.7 and it works.


Version-Release number of selected component (if applicable):
kernel-2.4.21-17.EL

How reproducible:
Always

Steps to Reproduce:
1. Boot up OS
2. Issue INIT interrupt
3.
    

Actual Results:  Nothing displayed on console

Expected Results:  The message "Entered OS INIT handler." appears on
console,
then register information and some other information will follow.


Additional info:

I tried 'dmesg -n 8' to display all messages to console,
but it doesn't work either.

With 2.4.21-15.EL kernel, the expected messages appear on console.

Comment 1 Anil S Keshavamurthy 2006-05-08 23:42:29 UTC
Do you still see this bug in the latest RHEL3 update kernel?

Comment 2 Jun'ichi NOMURA 2006-05-09 12:24:22 UTC
I don't have an access to the machine currently
and cannot answer promptly. I'll check if I can
find a way to test.

Is it just a confirmation?

Or are there any related fix in the recent kernel
which might affect this bug?
If so, should I try any specific version?



Comment 3 Anil S Keshavamurthy 2006-05-09 17:12:14 UTC
I just started to look at this bug and will be helpful if you can see if the
problem still exist on the latest RHEL3 U8 kernel.

Comment 4 Jun'ichi NOMURA 2006-05-09 19:30:43 UTC
OK, thanks for looking.

I tried 2.4.21-42.EL on currently available machine
and saw no problem.

Please close this bug.



Comment 5 Ernie Petrides 2006-05-09 20:40:11 UTC
This problem was fixed in RHEL3 U4.

*** This bug has been marked as a duplicate of 130800 ***


Note You need to log in before you can comment on or make changes to this bug.