Bug 110890
Summary: | Nautilus locks whole machine | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Ian Laurie <nixuser> |
Component: | kernel | Assignee: | Ernie Petrides <petrides> |
Status: | CLOSED DUPLICATE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | alexl, petrides, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-06 01:30:45 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
Ian Laurie
2003-11-25 10:18:27 UTC
While it may be coincidence, knowing exactly what you did with preferences for zoom might still help reproduce it here. Can you give more details, or possibly manage to repeat the behavior with a better idea of what you did beforehand? Also - were there any extra programs running the two times you had it happen? The caps lock flashing sounds like a kernel oops. Here is how I have just done it this morning: 1. Boot system, login as root, launch Nautilus. 2. Initially Nautilus is in icon view at 75% zoom. 3. Click on /root in tree view, then /proc, then /opt. 4. Click in reverse, ie click on /proc then /root. 5. Select from preferences icon zoom of 100%. 6. Click back up, /proc then /opt. 7. Select icon zoom back to 75%. 8. Click back down. When /proc is selected the system goes over. 9. Leds flash on the keyboard, but system is totally stopped with all services dead. I was not able to work on this yesterday, but if you still can't duplicate the problem I'll have more time to devote later today. I can get it to happen within a few seconds of trying, so it is quite repeatable. The system is WS 3.0 on a DELL PowerEdge 600SC with apache, samba, telnet, vsftpd (compiled from source cd) running. I'll give you a "ps ax" output if you need it. I'm not running with the motherboard video, I have a Matrox G450 in the bottom PCI slot. The system appears to be solid in other respects, so I doubt there is a h/w issue. Hopefully within 24-48 hours I'll have another DELL system to play with, I can see if the problem exists on it. If you want me to do a specific test, let me know. This really sounds like a kernel bug, since the kernel crashes. So i'm reassigning. However, reading various files in /proc has side effects, so reading /proc as root isn't all that safe. Would it be crazy to modufy Nautilus to not iterate the /proc directory, that is, treat /proc differently and not go in there? I ask because I presume this would be a potential issue with any version and distribution of Linux. With kernel-2.4.21-15.0.3.EL and nautilus-2.2.4-4.E I am no longer able to reproduce this bug at will. Previously I could get a kernel crash in 10 seconds or less, I've just tried for 10 minutes and I can't crash it. I'll consider this fixed then. This is an issue again. Under kernel-2.4.21-27.0.1.EL the symptom I've experienced is the system freezes solid. The screen is unchanged, no obvious signs of a kernel OOPS as such (no flashing keyboard lights), but you can't ssh or telnet into the box, she's completely dead. The real problem was in the kernel's handling of access to /proc/kcore. Related bugs are 132838, 133905, 134988, 136317, 145563, and 151934. The fix for this was committed to the RHEL3 U5 patch pool on 28-Jan-2005 (in kernel version 2.4.21-27.10.EL). The U5 advisory message was as follows: "An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-294.html" But please upgrade to U6 now (RHSA-2005:663). *** This bug has been marked as a duplicate of 133905 *** |