Bug 83327 - kernel-2.4.20-2.28 doesnt shut down properly
Summary: kernel-2.4.20-2.28 doesnt shut down properly
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-02 18:06 UTC by Need Real Name
Modified: 2007-04-18 16:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-02 20:09:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Need Real Name 2003-02-02 18:06:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
installed onto 8.0.  During shutdown, hangs b4 turning of power,
in all 3 attempts so far.  reboots also fail, cuz shutdown hangs.
Hard reset is needed to clear the lockup.

3 slightly different manifestations:

1. sending all processes the TERM message.
2. stopping all RAID devices (md...)
3.

heres one of the log/messages chunks:

Feb  2 03:06:57 groucho dd: 1+0 records in
Feb  2 03:06:57 groucho dd: 1+0 records out
Feb  2 03:06:57 groucho random: Saving random seed:  succeeded
Feb  2 03:06:57 groucho rpc.statd[876]: Caught signal 15, un-registering and
exiting.
Feb  2 03:06:58 groucho nfslock: rpc.statd shutdown succeeded
Feb  2 03:06:59 groucho portmap: portmap shutdown succeeded
Feb  2 03:06:59 groucho kernel: Kernel logging (proc) stopped.
Feb  2 03:06:59 groucho kernel: Kernel log daemon terminating.
Feb  2 03:07:00 groucho syslog: klogd shutdown succeeded
Feb  2 03:07:00 groucho exiting on signal 15
Feb  1 20:18:40 groucho syslogd 1.4.1: restart.
Feb  1 20:18:40 groucho syslog: syslogd startup succeeded

Im not seeing evidence here, other than an ntp setup issue..

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. reboot or shutdown
    

Additional info:

Comment 1 Need Real Name 2003-02-02 20:09:16 UTC
superceded by -2.30

btw -2.30 appears to have some network-scripts related probs, at least on Enigma.
boot hangs at startup of cipe-1.4.5-6 tunnels (repeated 3 times), when I changed
them to dont-start-on-boot, the rest of eth* failed - only lo was done.




Note You need to log in before you can comment on or make changes to this bug.