Bug 77851
| Summary: | RPM allows multiple copies of kernel to be installed | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Jeremy Sanders <jss> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-11-15 11:11:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jeremy Sanders
2002-11-14 13:00:46 UTC
try 'rpm -e --allmatches kernel-2.4.18-17.7.x' ... or some variation thereof Thanks - that command got rid of the kernel. Should rpm have allowed an install of more than one of the same kernel? I also ran into another rpm kernel problem, where rpm got stuck installing that same kernel rpm, trying to unmount a temporary loopback initrd image (the umount process was stuck at 100% cpu and couldn't be killed, even with kill -9). I can't reproduce it (but I saw it on two machines), so I haven't filed another bug. As regards the second comment, the stack trace of the stuck umount and the loop
device are:
Nov 15 11:08:06 xpc3 kernel: loop1 S DBFCBF24 0 22868 1
13058 (L-TLB)
Nov 15 11:08:06 xpc3 kernel: Call Trace: [<c0107d21>] __down_interruptible
[kernel] 0x71 (0xf4177f84))
Nov 15 11:08:06 xpc3 kernel: [<c0107dcf>] __down_failed_interruptible [kernel]
0x7 (0xf4177fac))
Nov 15 11:08:07 xpc3 kernel: [<fa449100>] .text.lock.loop [loop] 0x55 (0xf4177fb8))
Nov 15 11:08:07 xpc3 kernel: [<fa447bf0>] loop_thread [loop] 0x0 (0xf4177fc8))
Nov 15 11:08:07 xpc3 kernel: [<c010744e>] kernel_thread [kernel] 0x2e (0xf4177ff0))
Nov 15 11:08:07 xpc3 kernel: [<fa447bf0>] loop_thread [loop] 0x0 (0xf4177ff8))
Nov 15 11:08:07 xpc3 kernel:
Nov 15 11:08:07 xpc3 kernel: umount R current 8 22914 22694
(NOTLB)
Nov 15 11:08:07 xpc3 kernel: Call Trace: [<c0140d3e>] invalidate_bdev [kernel]
0x5e (0xdbfcbf04))
Nov 15 11:08:07 xpc3 kernel: [<c014560b>] kill_bdev [kernel] 0x1b (0xdbfcbf38))
Nov 15 11:08:07 xpc3 kernel: [<c014648d>] blkdev_put [kernel] 0xad (0xdbfcbf4c))
Nov 15 11:08:07 xpc3 kernel: [<c014455a>] remove_super [kernel] 0x6a (0xdbfcbf68))
Nov 15 11:08:07 xpc3 kernel: [<c015742f>] sys_umount [kernel] 0x3f (0xdbfcbf80))
Nov 15 11:08:07 xpc3 kernel: [<c01574a7>] sys_oldumount [kernel] 0x17 (0xdbfcbfb4))
Nov 15 11:08:07 xpc3 kernel: [<c01090ff>] system_call [kernel] 0x33 (0xdbfcbfc0))
Nov 15 11:08:06 xpc3 kernel: new-kernel-pk S BFFFF3A0 8 22691 22675 22694
(NOTLB)
Nov 15 11:08:06 xpc3 kernel: Call Trace: [<c0125b50>] sys_rt_sigaction [kernel]
0xa0 (0xefd21f64))
Nov 15 11:08:06 xpc3 kernel: [<c011e260>] sys_wait4 [kernel] 0x100 (0xefd21f80))
Nov 15 11:08:06 xpc3 kernel: [<c01090ff>] system_call [kernel] 0x33 (0xefd21fc0))
Nov 15 11:08:06 xpc3 kernel:
Nov 15 11:08:06 xpc3 kernel: mkinitrd S BFFFF7A0 8 22694 22691 22914
(NOTLB)
Nov 15 11:08:06 xpc3 kernel: Call Trace: [<c0125b50>] sys_rt_sigaction [kernel]
0xa0 (0xeed0ff64))
Nov 15 11:08:06 xpc3 kernel: [<c011e260>] sys_wait4 [kernel] 0x100 (0xeed0ff80))
Nov 15 11:08:06 xpc3 kernel: [<c01090ff>] system_call [kernel] 0x33 (0xeed0ffc0))
(sorry for pasting round the wrong way...)
rpm has always permitted multiple, even identical, instances of packages to be installed, that's not going to change. open a bug against the kernel package for the umount problem (if necessary). |