Bug 57354 - kernel-2.4.16-0.6 fails to boot
Summary: kernel-2.4.16-0.6 fails to boot
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 1.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-10 19:18 UTC by Need Real Name
Modified: 2015-01-04 22:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-26 04:36:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2001-12-10 19:18:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011113

Description of problem:
When booting the newly compiled kernel it hangs at:
(scsi0) Downloading sequencer code...

Version-Release number of selected component (if applicable):
see above

How reproducible:

Steps to Reproduce:
1. Boot the new kernel

Actual Results:  (scsi0) Downloading sequencer code...

Expected Results:  (scsi0) Downloading sequencer code... 436 instructions
downloaded (or whatever the number of instructions to download for
kernel-2.4.16-0.6, 436 is from kernel-2.4.9-13)

Additional info:

#>rpm -q modutils binutils gcc sh-utils bash patch gnupg
binutils- (fails to build with

lspci -v
00:0a.0 SCSI storage controller: Adaptec AIC-7881U (rev 01)
        Subsystem: Adaptec AHA-2940UW SCSI Host Adapter
        Flags: bus master, medium devsel, latency 64, IRQ 9
        I/O ports at e800 [size=256]
        Memory at ec001000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at ea000000 [disabled] [size=64K]

alias scsi_hostadapter aic7xxx
(all previous kernels have booted without problems. Does this kernel enable
the new driver from adaptec as default? Previous kernels, up to 2.4.9??
used the old driver. Had speed problems on another box with this driver,
compared to the old driver, but no boot problems)

Comment 1 Arjan van de Ven 2001-12-13 09:04:56 UTC
Still the same driver.
Do you have any idea what the last kernel was that did boot ?
(makes searching for the breaking change simpler ;)

Comment 2 Need Real Name 2001-12-17 22:06:24 UTC
Had no success with kernels-2.4.16 at all. Kernels built from source are
2.4.16-0.6, 0.11, 0.13, see below. The unresolved symbols should not affect the
boot, is only for information. The first two kernels were built with 
binutils-, the last one with binutils- All are built
with gcc-3.1-0.10, glibc-2.2.4-20, modutils-2.4.12-3 installed.
Kernels between 2.4.9 and 2.4.16 have not been built from source due to either
space problems or failures when compiling.

depmod:*** Unresolved symbols in
depmod:         iiEllisCleanup

depmod: *** Unresolved symbols in
depmod:         sis_malloc_Ra3329ed5
depmod:         sis_free_Rced25333

depmod: *** Unresolved symbols in
depmod:         sis_malloc_Ra3329ed5
depmod:         sis_free_Rced25333

Comment 3 Need Real Name 2001-12-18 18:49:58 UTC
Now also kernel-2.4.9-18 is in the unbootable kernel collection. Hangs at the
same place as kernels-2.4.16-0.x. The latest kernel booting is 2.4.9-13.
However, it is downloaded, not natively compiled. The latest natively compiled
kernel is 2.4.9-0.5. The following modules are loaded in the current running
kernel (2.4.9-13):
aic7xxx               114624   7
sd_mod                 11676   7
scsi_mod               98424   2 [aic7xxx sd_mod]

Comment 4 Arjan van de Ven 2001-12-18 20:14:04 UTC
gcc-3.1 is unfortionatly not yet suitable for compiling kernels.....

Comment 5 Need Real Name 2001-12-18 22:51:18 UTC
Are you sure it's the compiler, the kernel is pure c-code? Maybe the kernel is
at fault... Also, when compiling with gcc-3.1 _numerous_ warnings are issued,
one for example is inline assembly for calculating checksums, which fails, etc...

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