package linux-restricted-modules 2.6.24.19.21 failed to install/upgrade: dependency problems - leaving unconfigured

Bug #238568 reported by joel west
6
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

install of a all new kernel images fails via synaptic or apt:root@media:/home/joel# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
13 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up linux-image-2.6.24-19-generic (2.6.24-19.33) ...
Running depmod.
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/9p/9p.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/adfs/adfs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/coda/coda.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/ecryptfs/ecryptfs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/efs/efs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/exportfs/exportfs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/fuse/fuse.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/gfs2/gfs2.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/gfs2/locking/dlm/lock_dlm.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/gfs2/locking/nolock/lock_nolock.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/hfs/hfs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/hfsplus/hfsplus.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/lockd/lockd.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/mbcache.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/minix/minix.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/msdos/msdos.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/nfs/nfs.ko: Invalid argument
WARNING: Can't read module /lib/modules/2.6.24-19-generic/kernel/fs/nfs_common/nfs_acl.ko: Invalid argument

ProblemType: Package
Architecture: i386
Date: Mon Jun 9 09:40:53 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: dependency problems - leaving unconfigured
Package: linux-restricted-modules 2.6.24.19.21
PackageArchitecture: i386
SourcePackage: linux-meta
Title: package linux-restricted-modules 2.6.24.19.21 failed to install/upgrade: dependency problems - leaving unconfigured
Uname: Linux 2.6.24-19-server i686

Revision history for this message
joel west (joel-joelwest) wrote :
Revision history for this message
joel west (joel-joelwest) wrote :

Further to the above i noticed a core in /

root@media:/# gdb -c core
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(no debugging symbols found)
Core was generated by `depmod -a -F /boot//System.map-2.6.24-19-generic 2.6.24-19-generic'.
Program terminated with signal 11, Segmentation fault.
[New process 30200]
#0 0xb7ed5d28 in ?? ()
(gdb) quit

I am not at home or I would have attached the core itself.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 99547, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Changed in linux-meta:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.