I'm interested in hearing HOW you capture the register information from
processors "(executing a tight loop, interrupts disabled)" Care to let me
"Monty Vanderbilt" <mvb@xxxxxxxxxx>@oss.sgi.com on 10/25/2001 12:38:25 PM
Sent by: owner-lkcd@xxxxxxxxxxx
To: bharata@xxxxxxxxxxxxx, <lkcd@xxxxxxxxxxx>
Subject: RE: capturing cpu states on SMP
Why is it necessary to capture the stacks? Those pages should already be in
the memory dump. With the registers you should be able to seed the
for any cpu.
From: owner-lkcd@xxxxxxxxxxx [mailto:owner-lkcd@xxxxxxxxxxx]On Behalf Of
Bharata B Rao
Sent: Thursday, October 25, 2001 3:29 AM
Subject: capturing cpu states on SMP
This note is just a heads up to avoid duplicating our efforts. We are
on capturing the registers and stack on all the cpus at the time of
This has been found to be crucial to debug problems where some of the cpus
on an SMP are hung (executing a tight loop, interrupts disabled).
We have this working in the kernel side. We have also added a command to
the saved registers in the lcrash. We need to add some bits to lcrash
so that it can look at the right (saved) stack when back tracing.
Crash Dump Team,
IBM Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: 91-80-5262355 Ex: 3962