kernel panic in 2.0.27 while installing RedHat 4.1 (LONG)

kernel panic in 2.0.27 while installing RedHat 4.1 (LONG)

Post by Andrew V. Kle » Fri, 18 Apr 1997 04:00:00



I haven't seen anything in DejaNews that matches this problem,
and the articles in comp.os.linux.hardware from March 26th to
April 16th don't provide any clues, so here goes:

Installation of Red Hat 4.1 is failing with various kernel panics (see
the extracts from /var/log/messages attached at the end of this
posting).  The system is a Pentium on an ASUS P55TP4XE motherboard
with SCSI controller ASUS SC-200 and 48M RAM.  The old drive is a
Conner 2.1G SCSI with both DOS and a 1.2.13 Slackware running just fine
(along with a SCSI CD-ROM).

The new drive is a Western Digital 3.1G EIDE, connected to the
on-board IDE controller, which was supposed to be reasonably cheap and
effective.  Yes, I did have to download a newer BIOS from ASUS to get
LBA address translation to work correctly (Award BIOS v4.51PG,
#401A0-0202, 05/23/96-82430FX-PI-5XTP4C-00).  But it does work, for
DOS and Windows 3.11.  And it will boot up my 1.2.13 (which lives
on the SCSI drive).  But when I've tried to install Red Hat 4.1 off
the CD-ROM I get only so far; generally, the kernel falls down during
package installation.

I've tried fancy partitions and simple ones.  I've tried it using the
existing swap partition on the SCSI, or only using the swap on the IDE.
I've even tried running with PIO mode turned down to 2.  Full installs
all crashed.

By sneaking up on it (installing just a few packages) I was able to
get 2.0.27 & co. up and running; I then came on in and used rpm to
pull in the other selected packages I wanted.  It looked like the
system had become stable, so I left it running a bunch of X utilities
overnight... and the next morning found it had crashed.

Maybe the next thing I'll try is a full copy of the existing 1.2.13
system onto a new partition, and then letting it run overnight.  Or I
could try newer kernels... but first I'd like to ask for any insights
or suggestions you folks might have.

============================================================
Here are the extracts from /var/log/messages:

Example 1:

. . .
Apr  7 22:02:47 localhost login: ROOT LOGIN ON tty1
Apr  7 22:10:12 localhost kernel: ISO9660 Extensions: RRIP_1991A
Apr  7 22:22:41 localhost init: Switching to runlevel: 6
Apr  7 22:22:41 localhost kernel: general protection: 0000
Apr  7 22:22:41 localhost kernel: CPU:    0
Apr  7 22:22:41 localhost kernel: EIP:    0010:[insert_vm_struct+72/744]
Apr  7 22:22:41 localhost kernel: EFLAGS: 00010202
  eax: f000e739   ebx: 00000001   ecx: 02dfebd0   edx: 00000050
  esi: 00fd1658   edi: 00044000   ebp: 0808c000   esp: 02dfeba8
  ds: 0018   es: 0018   fs: 0018   gs: 002b   ss: 0018

  Process K15gpm (pid: 295, process nr: 9, stackpage=02dfe000)

  Stack:
  00fd1658 0000f875 00044000 00000000 bffe0000 02dfee6c bffffed5 00000000
  00086e64 00000050 00000000 02dfebd8 00000003 00fa4599 001597a9 001597db
  02e6a1f0 00159806 00000018 00000018 0000002b 00000000 02e6a6c8 00000080

  Call Trace:
     [ext2_lookup+129/364]
     [ext2_lookup+179/364]
     [ext2_lookup+222/364]
     [do_mmap+739/808]
     [load_elf_binary+1608/2680]
     [get__netinfo+669/704]
     [search_binary_handler+58/328]
     [do_load_script+471/492]
     [load_script+13/20]
     [search_binary_handler+58/328]
     [do_execve+318/428]
     [do_execve+354/428]
     [sys_execve+43/68]
     [system_call+85/124]

  Code: 39 68 08 76 0f 89 84 24 c8 00 00 00 8d 50 14 eb e3 8d 76 00

============================================================
Example 2:

. . .
Apr  8 09:51:54 localhost login: ROOT LOGIN ON tty1
Apr  8 09:52:48 localhost kernel: ISO9660 Extensions: RRIP_1991A
Apr  8 10:25:26 localhost kernel: general protection: 0000
Apr  8 10:25:26 localhost kernel: CPU:    0
Apr  8 10:25:26 localhost kernel: EIP:    0010:[refill_freelist+1001/1360]
Apr  8 10:25:26 localhost kernel: EFLAGS: 00010202
   eax: f000ef6f   ebx: 01dd7880   ecx: 00000001   edx: 01dd7770
   esi: 00000002   edi: 03800000   ebp: 01662d80   esp: 01662d3c
   ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018

   Process cpio (pid: 664, process nr: 23, stackpage=01662000)

   Stack:
   00000000 00000001 00000305 00000008 00010000 0000022d 00000000 0000370d
   00000000 00000000 00000000 01650044 00000000 01dd7770 00000000 00000000
   00000000 00000400 001234ea 00000400 00000375 001fab38 00000007 0004836f

   Call Trace:
     [getblk+442/1112]
     [ext2_new_block+1901/2176]
     [ext2_alloc_block+359/376]
     [block_getblk+347/608]
     [ext2_getblk+253/528]
     [ext2_file_write+387/1112]
     [schedule+560/648]
     [open_namei+176/996]
     [pipe_read+339/420]
     [sys_write+313/372]
     [system_call+85/124]

   Code: 89 58 18 8b 04 8d ec 70 1d 00 89 58 3c 8b 5b 20 29 5d cc 8b

============================================================
Example 3:

. . .
Apr  8 12:13:12 localhost kernel: ISO9660 Extensions: RRIP_1991A

Apr  8 13:05:57 localhost kernel:
 EXT2-fs error (device 03:05): ext2_find_entry: bad entry in directory #18289:
  inode out of bounds - offset=436, inode=121927, rec_len=20, name_len=10
 EXT2-fs error (device 03:05): ext2_find_entry: bad entry in directory #18289:
  inode out of bounds - offset=436, inode=121927, rec_len=20, name_len=10

Apr  8 13:06:47 localhost login: ROOT LOGIN ON tty2

Apr  8 13:09:55 localhost kernel:
 EXT2-fs error (device 03:05): ext2_find_entry: bad entry in directory #18289:
  inode out of bounds - offset=436, inode=121927, rec_len=20, name_len=10
Apr  8 13:09:55 localhost last message repeated 5 times

Apr  8 13:09:55 localhost kernel: VFS: Wrong blocksize on device 03:05
Apr  8 13:09:55 localhost kernel:
 EXT2-fs warning (device 03:05):
 ext2_free_inode: bit already cleared for inode 69147
 ext2_free_inode: bit already cleared for inode 69148
 ext2_free_inode: bit already cleared for inode 69149
 ext2_free_inode: bit already cleared for inode 69150
 ext2_free_inode: bit already cleared for inode 69151
 ext2_free_inode: bit already cleared for inode 69152

Apr  8 13:15:00 localhost kernel:
 Unable to handle kernel paging request at virtual address c8030803
Apr  8 13:15:00 localhost kernel: current->tss.cr3 = 00101000, <r3 = 00101000
Apr  8 13:15:00 localhost kernel: *pde = 00000000
Apr  8 13:15:00 localhost kernel: Oops: 0000
Apr  8 13:15:00 localhost kernel: CPU:    0
Apr  8 13:15:00 localhost kernel: EIP:    0010:[wake_up+44/224]
Apr  8 13:15:00 localhost kernel: EFLAGS: 00010216

 eax: 01ddf000   ebx: 08030803   ecx: 001d7108   edx: 01ddf044
 esi: 01ddf088   edi: 001d7104   ebp: 00088f64   esp: 00088f58
 ds: 0018   es: 0018   fs: 0018   gs: 0018   ss: 0018

 Process kswapd (pid: 3, process nr: 3, stackpage=00088000)

 Stack:
 00000000 01ddf088 01ddf0cc 00088fb4 00123ef0 001d7108 00124916 01ddf044
 00281e74 0000017f 00000bfe 00003000 03800000 00000001 01dd1000 0011aa79
 01ddf0cc 00088fb4 00000006 00000006 00000003 00000000 00000000 01ddf088

 Call Trace:
     [put_unused_buffer_head+28/32]
     [try_to_free_buffer+618/712]
     [53c7,8xx:ncr53c700_setup+-135224/24]
     [shrink_mmap+381/468]
     [try_to_free_page+63/156]
     [kswapd+327/344]
     [init+63/856]
     [kswapd+0/344]

 Code: 8b 13 8b 5b 04 85 d2 74 6d 8b 02 83 f8 02 74 07 8b 02 83 f8
============================================================
--

Andrew V. Klein
Motorola, Inc., IL75-3N12, 1475 W. Shure Drive, Arlington Heights, IL 60004

fax.: 847-435-9017

 
 
 

1. ICMP Difficulties with RedHat 4.1 and 2.0.27 and.30 Kernels

I've recently installed Red Hat Linux 4.1 on an HP XU/90 PC. The wierd
thing is that when I try to use ping or traceroute I get the error
messages saying "ping: unknown procotol icmp" and "icmp: procotol
unknown".  

I get the error when using the stock 2.0.27 from the Red Hat
distribution and using my usual customize kernels. I have use
NetKit-B-0.08-13.i386.rpm and NetKit-B-0.09-13.i386.rpm packages. I have
even recompile the NetKit 0.09 sources, and I still get the error. I
have some network mangement software that I use and all of it's icmp
functionality works with no problems.

I have installed Red Hat 4.1 on other computers systems without any
problems. I'm just about to wits end on this one.  Does anyone have any
ideas or suggestions?

Stephen L. Johnson

2. How Old Is Linus?

3. RedHat Linux 4.1 Kernel 2.0.27

4. Date format convertion

5. RedHat Linux 4.1 kernel 2.0.27.....

6. how to populate auto_direct with NIS+ ?

7. RedHat 4.1 Kernel 2.0.27, Log problems........

8. Sparc Motif Windows Manager

9. RedHat Linux 4.1 Kernel 2.0.27 Log Problems Pleaes Help!

10. Netscape 3.01 hang on RedHat 4.1 with kernel 2.0.27 at fvwm95 [HELP]

11. Kernel build freeze RH 4.1, kernel 2.0.27, AMD k5100

12. Terrible behaviour of NS 4.0b3 under RedHat 4.1 (2.0.27)

13. Redhat 4.1 (2.0.27) IP -> Name Auth Failure