It looks like your system has: 1. Kernel crash dump configured. 2. Something is causing crash while you issue a reboot, may be some module unload path has a bug. 3. Crash is triggering kernel dump to take dump of memory (I guess you have plenty of RAM to justify 45 minutes) in /var/core directory. Although dump image is highly compressible but compression is the last step. 4. If there is no space in /var/core, kdump gives up and you see faster reboot. -Rajat On Fri, May 30, 2014 at 12:39 PM, <Valdis.Kletnieks@vt.edu> wrote:
On Fri, 30 May 2014 12:32:32 -0700, Vipul Jain said:
On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Is this reproducible?
Do you have any clue at all where in the reboot process it's sitting for the 45 minutes?
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies