kernel crash with NVMe stack at resume |
||
Issue descriptionDoing a suspend/resume test with trim, we observed several crashes. See https://www.google.com/chromeos/partner/console/a/2/storageQualDetails?storageQualAttemptId=24 https://pantheon.corp.google.com/storage/browser/chromeos-moblab-peng-staging/results/0WGGTFQS1826801C/150e50c6c6a111e899e0e57200ec5a4c/99-moblab/192.168.231.101/crashinfo.192.168.231.101/pstore/pstore The crash happens at resume in the RQ processing part.
,
Oct 31
I ran StorageQualTrim.test on the Samsung 950 nvme on fizz with kernel 4.4 (image R72-11214.0.0) and did not see a crash.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||
►
Sign in to add a comment |
||
Comment 1 by gwendal@chromium.org
, Oct 24