Reboot After Panic.!

[Ivan_86]

Hi to all !!

We have, N40005 11.00 the system crash, but in the log's no exist register of the problem.

The sysmtem generated one directory crash and in the /etc/shutdownlog apper this entri

01:39 Fri Oct 28 2005. Reboot after panic: An invalid dirty buffer!

Sombody have idea of the problem

Thanks to all!

[Hanwant Verma_1]

What was the last change you did on your system. Did you reboot the server after that change?

[A. Clay Stephenson · Accepted solution]

PHKL_28105 addresses your problem.

[Geoff Wild]

Possibly could be vxfs patches - make sure you are up to date in your patches...

Rgds...Geoff

[Ivan_86]

Hi, thanks for yours response,

No the system no have changes more less 3 0 4 months

[Granite]

Hi Ivan,

For a panic reboot, you can better scrutinize the crash logs generated. It will be inside /var/adm/crash directory.The latest one will be crash.0.
Also, refer the /var/tombstones/ts* files. Tombstones can screen you if hardware issues.
Unless if the servers goes down gracefully /etc/shutdownlog cant address you exactly who and why it has happened.

regds,Granite

[Alex Glennie]

No points please !

but your question has already been answered correctly from the patch documention :

Symptoms:
PHKL_28105:
( SR:8606274037 CR:JAGae38116 )
A panic occurs when accessing an invalid dirty buffer in the
buffer cache. This can result in a couple of different
panics. Two types of panics seen so far are "panic: An
invalid dirty buffer!" and a Data Page Fault in bwrite().
A sample stack trace is given below.

panic: An invalid dirty buffer!

[Bharat Katkar]

Hi Evan

The cause of panic is breifly given in your shutdownlog file.
01:39 Fri Oct 28 2005. Reboot after panic: An invalid dirty buffer!

An invalid dirty buffer caused your system to reboot. As already mentioned try applying the patch and monitor your system.

Regards,

[Ivan_86]

thanks for all..!!

We are work in the plan for install this patches..!!!


Rgds.!