Bug 191539 - LTC23833-some initcalls return with error during netboot and in dmesg
Summary: LTC23833-some initcalls return with error during netboot and in dmesg
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-12 19:35 UTC by IBM Bug Proxy
Modified: 2015-01-04 22:27 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2006-11-24 23:21:30 UTC

Attachments (Terms of Use)
netboot_output.txt (8.44 KB, text/plain)
2006-05-12 19:41 UTC, IBM Bug Proxy
no flags Details
var-log-messages.txt (59.81 KB, text/plain)
2006-05-12 19:41 UTC, IBM Bug Proxy
no flags Details

Description IBM Bug Proxy 2006-05-12 19:35:16 UTC
LTC Owner is: ameet@us.ibm.com
LTC Originator is: shenlinf@cn.ibm.com

Problem description:
I was testing "fedora-development tree (aka rawhide), snapshot May1" on junolp1.
I found some initcall errors during netboot. These errors were also showed in
dmesg after the installation finished and system rebooted.
initcall at 0xc000000000545378: .scanlog_init+0x0/0xf0(): returned with error
code -5
initcall at 0xc00000000055d220: .hvc_rtas_init+0x0/0xcc(): returned with error
code -5
initcall at 0xc00000000055d280: .hvc_fss_init+0x0/0x80(): returned with error
code -1
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
initcall at 0xc000000000565490: .i8042_init+0x0/0x114(): returned with error
code -16

Is this reproducible?
    If so, how long does it (did it) take to reproduce it?
    Describe the steps:
    1. config IPL in SMS
    2. netboot by bootp (find these errors)
    3. install ... and wait till it finishes and reboots
    4. dmesg (find these errors again)

    If not, describe how the bug was encountered:

Additional information:
1. We also found similiar errors on other systems:
Squadron ML8+
Squadron B60++
Squadron HV4
Squadron H

Comment 1 IBM Bug Proxy 2006-05-12 19:41:14 UTC
Created attachment 128959 [details]

Comment 2 IBM Bug Proxy 2006-05-12 19:41:54 UTC
Created attachment 128960 [details]

Comment 3 IBM Bug Proxy 2006-05-14 08:43:06 UTC
----- Additional Comments From antonb@au1.ibm.com(prefers email via anton@au.ibm.com)  2006-05-14 04:46 EDT -------
Some of these are fixed in mainline 

Comment 4 IBM Bug Proxy 2006-05-30 05:02:14 UTC
----- Additional Comments From shenlinf@cn.ibm.com  2006-05-30 01:06 EDT -------
It seems that these initcall failures don't appear in May 26 version. 

Comment 5 IBM Bug Proxy 2006-06-06 07:18:27 UTC

           What    |Removed                     |Added
            Version|FC5                         |devel

------- Additional Comments From shenlinf@cn.ibm.com  2006-06-06 03:20 EDT -------
I am changing the version to 'devel' to properly reflect that this recreates on

Comment 6 Dave Jones 2006-10-17 00:57:53 UTC
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 7 Dave Jones 2006-11-24 23:21:30 UTC
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug after installing all the
current updates, please reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

Thank you.

Comment 8 IBM Bug Proxy 2006-11-29 17:41:39 UTC

           What    |Removed                     |Added
             Status|ASSIGNED                    |REJECTED
         Resolution|                            |UNREPRODUCIBLE

------- Additional Comments From ameet@us.ibm.com (prefers email at ameet@austin.ibm.com)  2006-11-29 12:38 EDT -------
Yes, comment #9 is perfect.  I just missed it.

Since we don't know what changed to fix this problem, closing this as

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