On Friday 14 May 2010 11:42:44 am Matthew Fleming wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular,
On Friday 14 May 2010 7:59:40 am Terry Kennedy wrote:
The crash was a page fault while in kernel mode with the current process
being the interrupt service routine for the bce0 GigE. Things progressed
reasonably until partway through the dump, when the system locked up with
a
Terry Kennedy wrote:
I'm reposting this over here at the suggestion of the Forums moderator.
The original post is at http://forums.freebsd.org/showthread.php?t=14163
Got an interesting crash just now (well, as interesting as a crash on a
soon-to-be production system can be).
This is
The crash was a page fault while in kernel mode with the current process
being the interrupt service routine for the bce0 GigE. Things progressed
reasonably until partway through the dump, when the system locked up with a
Sleeping thread (tid 100028, pid 12) owns a non-sleepable lock. That's
The crash was a page fault while in kernel mode with the current process
being the interrupt service routine for the bce0 GigE. Things progressed
reasonably until partway through the dump, when the system locked up with a
Sleeping thread (tid 100028, pid 12) owns a non-sleepable lock.
Hmm. You could try changing the code to not do a nested panic in that
case. You would update subr_turnstile.c to just return if panicstr is
not NULL rather than calling panic. However, there is still a good
chance you will end up deadlocking in that case. I have another patch I
can
On Fri, May 14, 2010 at 09:56:47AM -0400, Terry Kennedy wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular,
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular, the shutdown makes a bunch of the behind the scenes man-
Matthew Fleming wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after the system has been halted - press any key to reboot -
in particular, the shutdown makes a bunch of the
Oops, youre right that other CPUs are running.
The stop_cpus() call is only made if kdb is entered. doadump() is called
out of boot() which comes later. At Isilon weve been running with a patch
that does stop_cpus() pretty close to the front of panic(9).
This is interesting, and
I'm reposting this over here at the suggestion of the Forums moderator.
The original post is at http://forums.freebsd.org/showthread.php?t=14163
Got an interesting crash just now (well, as interesting as a crash on a
soon-to-be production system can be).
This is 8-STABLE/amd64, last cvsup'd
11 matches
Mail list logo
