[Bug 213371] panic: spin lock held too long

bugzilla...@freebsd.org

unread,

Oct 11, 2016, 5:54:54 AM10/11/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

Bug ID: 213371
Summary: panic: spin lock held too long
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebs...@FreeBSD.org
Reporter: wk...@cam.ac.uk
CC: freebs...@FreeBSD.org
CC: freebs...@FreeBSD.org

Created attachment 175614
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175614&action=edit
panic screenshot

Hello,
I'm trying to install FreeBSD 11.0-RELEASE on Dell R620 poweredge with Perc
H310mini raid controller. Controller is currently configured in jbod mode. I'm
getting panic consistently whenever installer tried to access hard drives. I
have tried zfs, ufs with raid, without raid. The problem doesn't exists when i
install freebsd 10.3. I have this machine for testing for a while so I can help
with debugging.
cheers
Wojciech

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebs...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs...@freebsd.org"

bugzilla...@freebsd.org

unread,

Oct 11, 2016, 7:54:47 AM10/11/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

Mark Linimon <lin...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression
CC|freebs...@FreeBSD.org |

bugzilla...@freebsd.org

unread,

Oct 12, 2016, 11:36:39 AM10/12/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #1 from Andriy Gapon <a...@FreeBSD.org> ---
Would it be possible for you to try a latest snapshot from here
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/ in a suitable
format?
A kernel in the snapshot should have more debugging facilities compiled in, so
that might help to get more information.

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 9:26:42 AM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #2 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175706
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175706&action=edit
panic with 12.0-CURRENT

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 9:28:41 AM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #3 from Wojciech Giel <wk...@cam.ac.uk> ---
I have tried install 12-CUREENT got the same kernel panic see attachment.
replaced H310 controller with H710 but behaviour is the same.

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 10:17:13 AM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #4 from Andriy Gapon <a...@FreeBSD.org> ---
(In reply to Wojciech Giel from comment #3)
Could you please reproduce this again? And once you are at the 'db>' prompt
please execute the following commands:
db> bt
db> tid 10186 [*]
db> bt
where '10186' is a place holder for the id reported in the "too long" message.
Please capture the output.
Thank you.

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 10:29:02 AM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #5 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175708
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175708&action=edit
bt tid 1

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 10:29:25 AM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #6 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175709
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175709&action=edit
bt tid 2

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 1:00:49 PM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #7 from Andriy Gapon <a...@FreeBSD.org> ---
Apologies for my conventions, but please do not enter '[*]', it should be just
'tid <number>'. I used '[*]' only to draw your attention to a fact that
'10186' should not be entered verbatim. Sorry.
Could you please get the stack traces again?

bugzilla...@freebsd.org

unread,

Oct 13, 2016, 1:02:59 PM10/13/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #8 from Andriy Gapon <a...@FreeBSD.org> ---
Also, it's not 'bt tid xxxx' on one line. Those are 3 separate commands: 'bt',
'tid xxxx', 'bt'. You hit enter after typing each.

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 5:23:22 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #9 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175735
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175735&action=edit
bt tid 3

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 5:24:43 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #10 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175736
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175736&action=edit
bt tid 4

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 5:26:17 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #11 from Wojciech Giel <wk...@cam.ac.uk> ---
tid 100245 returns No such command?

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 8:22:06 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #12 from Andriy Gapon <a...@FreeBSD.org> ---
(In reply to Wojciech Giel from comment #11)
I apologise again, I confused a kgdb command with a ddb command.
So, instead of 'tid' it should be 'thread'.
Could you please obtain the outputs again?

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 8:46:38 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #13 from Wojciech Giel <wk...@cam.ac.uk> ---
Created attachment 175739
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175739&action=edit
bt thread

no much there

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 9:10:27 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #14 from Andriy Gapon <a...@FreeBSD.org> ---
(In reply to Wojciech Giel from comment #13)
I am a little bit confused.
Could you please do the following?
<get the panic>
<take a picture>
bt
<take a picture>
thread xxxx
bt
<take a paicture>

So, I want to get 3 pictures of the same panic.
Thank you.

bugzilla...@freebsd.org

unread,

Oct 14, 2016, 9:11:19 AM10/14/16

to freebs...@freebsd.org

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

Andriy Gapon <a...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #175706|0 |1
is obsolete| |