I see that rather frequently vm_page_dump bitmap gets changed during minidumpsys
execution. Sometimes this results in number of pages to dump growing larger
than
space we already reserved on disk, and thus in aborting dump near the end with
"Attempt to write outside dump device boundaries" error
You can do it this way, but IMO, the best thing to do is to when
you're panicing stop all other CPUs.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hack
on 03/09/2010 19:10 Matthew Jacob said the following:
> You can do it this way, but IMO, the best thing to do is to when you're
> panicing
> stop all other CPUs.
Entirely agree, that's the way it should be handled.
Unfortunately, all I could come up with was the patch that I posted.
--
Andriy
On 9/3/2010 9:17 AM, Andriy Gapon wrote:
on 03/09/2010 19:10 Matthew Jacob said the following:
You can do it this way, but IMO, the best thing to do is to when you're
panicing
stop all other CPUs.
Entirely agree, that's the way it should be handled.
Unfortunately, all I could come up with w
Matthew Jacob wrote:
> ... IMO, the best thing to do is to when
> you're panicing stop all other CPUs.
which is fine _if_ the system is healthy enough to do it.
If it's unhealthy enough to be panicing, it may not be
healthy enough to be doing IPC operations.
5 matches
Mail list logo
