Bug 151500
Summary: | Starting cupd locks up entire system forcing reboot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joshua Ginsberg <joshg> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | james, pfrields |
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: | 2006-05-04 13:23: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
Joshua Ginsberg
2005-03-18 18:06:05 UTC
I think this is a kernel problem, but I want to make sure. Please try this, as root: chmod -x /usr/lib/cups/backend/* chmod +x /usr/lib/cups/backend/ipp Does this work around the problem? (You won't be able to print correctly until the 'x' permission is added back to all of the backends.) You are correct. It did not lock up the system when I changed the above permissions. -jag Okay, now please try enabling each backend, one by one, like this: chmod +x /usr/lib/cups/backend/parallel Each time, reboot and see if it works. I'd like to narrow down the problem to a particular backend. Then we can see what it does to provoke the kernel problem. So far, we know that the ipp backend does not provoke the problem, and that one of the others does. I have had similar behaviour on an HP Pavillion 6630. kernel-2.6.10-1.770_FC3 (i686) cups-1.1.22-0.rc1.8.5 I followed the above instructions (i.e., only enable the IPP backend) and booting was fine. I then enabled the parallel backend and the lockup came back. So it would appear to be a problem with the parallel port support for newer kernels. The lockup does not occur with kernel-2.6.9-1.667. Okay, definitely a kernel issue then. Thanks for testing. I know that FC4 is out, but the HP Pavillion 6630 machine that experiences this problem has not been upgraded yet. So, just for another data point, the problem still persists for kernel-2.6.11-1.35_FC3 (i686). An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. I have now tried the new kernel-2.6.12-1.1372_FC3 and the lockup during boot persists. I just upgraded the HP Pavillion to kernel-2.6.12-1.1378_FC3 and cups-1.1.22-0.rc1.8.7 and the lockup still occurs. This is a mass-update to all currently open Fedora Core 3 kernel bugs. Fedora Core 3 support has transitioned to the Fedora Legacy project. Due to the limited resources of this project, typically only updates for new security issues are released. As this bug isn't security related, it has been migrated to a Fedora Core 4 bug. Please upgrade to this newer release, and test if this bug is still present there. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. Thank you. Unfortunately the HP Pavillion has been put to pasture and is unlikely to get to the track again so I will not be able to verify if this bug exists in the FC4 kernels. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. |