Bug 29092
| Summary: | module_upgrade crashes in kernel post-install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Habig, Alec <ahabig> | ||||
| Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.1 | CC: | notting | ||||
| 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: | 2001-02-23 22:08:19 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: | |||||||
| Attachments: |
|
||||||
|
Description
Habig, Alec
2001-02-23 17:08:39 UTC
Neat. If you run kudzu from the command line, does it also lock the system? We (Red Hat) should really try to resolve this before next release. All kudzu does that could cause this is load any (already configured): - usb controller - SCSI - parallel port modules. None of these should hang the system. What does your /etc/sysconifg/hwconf look like? Created attachment 10880 [details]
/etc/sysconfig/hwconf
Also, what does your /etc/modules.conf look like? What happens if you load: a) the aic7xxx module b) the uhci module c) the usb-uhci module ? In answer to the questions - (thanks for being so fast guys!) a) Running module_upgrade now does not crash the system. This is with the new kernel all happily chugging away. b) This system is scsi based, and does have usb and parallel ports (but nothing running on the latter two). I have attached the /etc/sysconfig/hwconf That said, I bet I know the answer - if module_upgrade was loading modules at install time, and if it were trying to load the scsi driver from the old kernel (aic7xxx from kernel-smp-2.4.0-0.99.23), then that module was known to lock up the system at boot time at least - see bug #27993. I had worked around this crash-on-boot bug by putting a working aic7xxx_old.o driver into the initial ramdisk. But, module_upgrade would have know way of knowing about that workaround. If it _doesn't_ try to force a reload ofthe old modules when installing the new kernel, then this answer is for not. In that case, let me know and I'll try to back the system into the bug and play with things. No, it was loading the previous aic7xxx module, so that would explain the lockup. I'm going to mark this as closed, since that kernel issue is fixed with the current kernel. Also, there's really no reason for module_upgrade to be probing anything other than the PCI bus at the moment, so we'll fix that in kudzu as well. |