Hi Greg
Thanks for the response.
On 2/11/2022 3:09 AM, Greg KH wrote:
On Tue, Feb 08, 2022 at 11:44:32AM -0800, Abhinav Kumar wrote:
There are cases where depending on the size of the devcoredump and the speed
at which the usermode reads the dump, it can take longer than the current 5 mins
timeout.
This can lead to incomplete dumps as the device is deleted once the timeout expires.
One example is below where it took 6 mins for the devcoredump to be completely read.
04:22:24.668 23916 23994 I HWDeviceDRM::DumpDebugData: Opening /sys/class/devcoredump/devcd6/data
04:28:35.377 23916 23994 W HWDeviceDRM::DumpDebugData: Freeing devcoredump node
What makes this so slow? Reading from the kernel shouldn't be the
limit, is it where the data is being sent to?
We are still checking this. We are seeing better read times when we bump
up the thread priority of the thread which was reading this.
We are also trying to check if bumping up CPU speed is helping.
But, results have not been consistently good enough. So we thought we
should also increase the timeout to be safe.
Increase the timeout to 10 mins to accommodate system delays and large coredump
sizes.
Nit, please wrap your changelog texts at 72 columns.
Yes, i will fix this when I re-post.
And what is "large"?
We are seeing devcoredumps in the range of 2.5MB-3MB. I can also mention
this in the commit text in the next post.
Thanks
Abhinav
thanks,
greg k-h
