kernel/mkinitrd udpate broken? [Was: Missing in action...] (fwd)

John Ellson ellson at research.att.com
Wed Sep 1 16:07:29 UTC 2004


Satish Balay wrote:

><using forward to start a new thread>
>
>On Wed, 1 Sep 2004, Satish Balay wrote:
>
>  
>
>>BTW: I notice the following error in today's update:
>>
>>--
>>hal-cups-utils 100 % done 18/120
>>Stopping cups: [  OK  ]
>>Starting cups: [  OK  ]
>>mkinitrd 100 % done 19/120
>>/var/tmp/rpm-tmp.23804: line 1:  5655 Segmentation fault      /sbin/modprobe loop 2>/dev/null >/dev/null
>>kernel 100 % done 20/120
>>--
>>    
>>
>
>Ok - something causes the newly installed kernel (538) not to boot. I
>get:
>
>---
>Red Hat nash version 4.1.9 starting
>insmod: error inserting '/lib/ext3.ko': -1 Unknown symbol in module
>ERROR /bin/insmod exited abnormally!
>mount: error 19 mounting ext3
>mount: error 2 mounting none
>switchroot: mount failed: 22
>umount /initrd/dev failed: 2
>Kernel panic - not syncing: Attempted to kill init!
>---
>
>And I get similar error wth kerne-535 installed which was installed
>nash-2.1.8..
>
>I'm able to boot to kernel-533 (which was working fine before the
>updates/reboot) - but now I get a bunch of ext3 errors.
>
>And 'lsmod' shows only module loaded are 'ext3' and 'jbd' (no
>networking - so I can't cut/paste)
>
>Something is seriously broken..
>
>Satish
>  
>

In addition to backing down to kernel-533, I also backed out to
initscripts-7.73-1 and module-init-tools-3.0-2
(not sure that both are broken, but one of them cleared up the module issues.)

I did not back out mkinitrd.

I had to back out to xorg-x11-6.7.0-7.2 because of the i810 graphics issue.

And I backed out to metacity-2.8.4-1 because my desktop was still funky.  (not 100% sure
about this last being a real problem.)

Basically, there are multiple breakages in the latest updates.

Don't lose your old rpms.

John





More information about the test mailing list