Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I was trying to shutdown my laptop when suspend failed. I used "halt -p" command as root to force shutdown but shutdown freeze on NFS.
Whole situation was: I was connected via VPN, had some NFS mounts. I closed the VPN connection but NFS mounts were still there. Shutdown didn't success thus I use "halt -p" command as root to shutdown my laptop. Laptop did SOMETHING for a two hours and then died because of battery.
It is very unpleasant that root can't switch the system dirrectly and must renew vpn connection then unmout all NFS, close VPN connection and at last he/she is able to switch the system off.
Version-Release number of selected component (if applicable):
kernel: 2.6.32-167.el6.x86_64
upstart-0.6.5-10.el6.x86_64
Laptop: Lenovo T61
How reproducible:
Almost always.
Steps to Reproduce:
1. create VPN connection
2. create some RH NFS mounts in your computer
2. close the vpn connection
3. halt -p
Actual results:
I belive it's the similar / same problem as: https://bugzilla.redhat.com/show_bug.cgi?id=702630 but strange is that "halt" can't force the shutdown.
Expected results:
Additional info:
Comment 1RHEL Program Management
2011-10-07 15:41:14 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
That is odd, especially the part where halt -p didn't work. It's probably worth testing with the patches for bug 702630. If those don't fix it, then what I'd probably need is a core or sysrq-t dump of the tasks when the machine is in this state. In particular, it would be interesting to see what the stack of the
halt -p process looks like.
Jeff, I remeber the "freeze" but I am not able to reproduce it right now because I'm on RHEL-6.2.
I promised to test also "suspend" issue but I'm a little bit busy now I also need to get additional laptop to do so...
Ok, so it was fixed in 6.2? Should we then just close this since it's not a
problem in the current release? Or did I misunderstand what you were saying?
Comment 6RHEL Program Management
2012-02-28 14:05:07 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.