Bug 231380 - 12-ALPHA5 Deadlock panic
Summary: 12-ALPHA5 Deadlock panic
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash, regression
Depends on:
Blocks:
 
Reported: 2018-09-15 10:47 UTC by Jeremy Faulkner
Modified: 2022-10-12 00:49 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Faulkner 2018-09-15 10:47:16 UTC 
12-ALPHA5 GENERIC kernel amd64

https://flic.kr/p/28kmbBC
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2018-10-09 15:49:20 UTC 
Is this a regression from an earlier install, or is this a new install?
Comment 2 Jeremy Faulkner 2018-10-09 20:57:11 UTC 
This system was upgraded from 11.2-RELENG branch to 12-ALPHA by cloning the boot environment, and then building from source. I forget exactly which ALPHA 4, or 5 but it's currently at 8.

And I have a core to upload for the deadlock panic. It's 1.8GB compressed, so it will take some time to upload.
Comment 3 Jeremy Faulkner 2018-10-09 22:40:28 UTC 
tar zcvf core-dump-deadlock.tar.gz /boot/kernel /var/crash/*6

https://drive.google.com/open?id=1NPm4DqrnJ5pigKAaN0hEDwuQb7CNG66b
Comment 4 Mark Johnston freebsd_committer freebsd_triage 2018-10-09 22:55:21 UTC 
(In reply to Jeremy Faulkner from comment #3)
You'll need to include /usr/lib/debug/boot/kernel for the core to be useful.
Comment 5 Jeremy Faulkner 2018-10-09 23:27:25 UTC 
tar.gz of  /usr/lib/debug/boot/kernel

https://drive.google.com/open?id=1lq1cdyTuWyxL7wLKyMuO6bbttCXPslRr
Comment 6 Mark Johnston freebsd_committer freebsd_triage 2020-12-23 19:53:23 UTC 
Sorry that this didn't get more attention.  There were several bugs in 12.0 that have since been fixed that could have caused kernel deadlocks.  Are you able to reproduce any problems on later releases, i.e. 12.1 or 12.2?
Comment 7 Jeremy Faulkner 2020-12-26 05:55:07 UTC 
As I don't think this particular panic occurred again and the server has tracked 12-STABLE to 12.2-STABLE #3 r368696M without this deadlock panic happening again.
Comment 8 Mark Johnston freebsd_committer freebsd_triage 2020-12-27 03:31:49 UTC 
(In reply to Jeremy Faulkner from comment #7)
Ok, thanks for the update.  I'll close for now, please re-open if the panic occurs again and we'll try to investigate more promptly.