Bug 157390 - System doesn't reboot on SMP machine after diskdump finished
System doesn't reboot on SMP machine after diskdump finished
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Akira Imamura
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-11 01:47 EDT by Hirotaka Sasaki
Modified: 2007-11-30 17:07 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-17 18:17:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Hirotaka Sasaki 2005-05-11 01:47:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
Normally, if /proc/sys/kernel/panic is > 0, system reboots after disudmp finished. But on SMP machine, system doesn't reboot after diskdump (or netdump) finished.

When CPU#0 executed diskdump, system reboots. But When other CPU executed diskdump, system doesn't reboot.


Version-Release number of selected component (if applicable):
kernel-smp-2.6.9-5.0.5.EL

How reproducible:
Sometimes

Steps to Reproduce:
1.Configure diskdump (or netdump).
2.echo 1 > /proc/sys/kernel/sysrq
3.echo 5 > /proc/sys/kernel/panic
4.echo c > /proc/sysrq-trigger

Diskdump completed, but system stopped at following:

 CPU frozen: #0#1#3
 CPU#2 is executing diskdump.
 start dumping
 check dump partition...
 dumping memory.
 <6>disk_dump: diskdump succeeded
 <0>Rebooting in 5 seconds..
  

Actual Results:  System doesn't reboot after diskdump finished.

Expected Results:  If /proc/sys/kernel/panic is > 0, system reboot after diskdump finished.

Additional info:
Comment 2 Akira Imamura 2005-08-12 18:14:55 EDT
Sasaki-san,

Could you first check on whether Update1 kernel has the same problem as the
kernel that you used?

Best regards,
Akira Imamura

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