From: "Carsten Grzemba via illumos-discuss" <discuss@lists.illumos.org>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: [discuss] BAD TRAP: type=7 (#nm Device not available) rp=fffffe0019e3d780 addr=0
Date: Tue, 11 Mar 2025 06:08:26 -0400 [thread overview]
Message-ID: <17416877060.A4eA.3424@composer.illumos.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]
Recently I see an crash dump with
NOTICE: SAM-QFS: samfs1: Initiated mount filesystem
panic[cpu3]/thread=fffffe0019e3dc20:
BAD TRAP: type=7 (#nm Device not available) rp=fffffe0019e3d780 addr=0
looking on the stack of the faulted thread
fffffe0019e3d690 unix:die+d3 ()
fffffe0019e3d770 unix:trap+855 ()
fffffe0019e3d780 unix:cmntrap+e9 ()
fffffe0019e3da10 samfs:sam_map_block+6f ()
fffffe0019e3dc00 samfs:sam_block_thread+1574 ()
fffffe0019e3dc10 unix:thread_start+b ()
and the the disassembled function sam_map_block
> sam_map_block::dis
sam_map_block: pushq %rbp
sam_map_block+1: movl %ecx,%eax
sam_map_block+3: shrl $0xc,%ecx
sam_map_block+6: andb $0xef,%ah
sam_map_block+9: andl $0x1,%ecx
sam_map_block+0xc: xorl $0x1,%ecx
sam_map_block+0xf: movq %rsp,%rbp
sam_map_block+0x12: pushq %r15
sam_map_block+0x14: pushq %r14
sam_map_block+0x16: movq %rsi,%r14
sam_map_block+0x19: pushq %r13
sam_map_block+0x1b: movq %r8,%r13
sam_map_block+0x1e: pushq %r12
sam_map_block+0x20: pushq %rbx
sam_map_block+0x21: subq $0x178,%rsp
sam_map_block+0x28: movl %eax,0xfffffffffffffecc(%rbp)
sam_map_block+0x2e: leaq (%rsi,%rdx),%rax
sam_map_block+0x32: movq 0x3e8(%rdi),%r12
sam_map_block+0x39: movq %rdx,0xfffffffffffffec0(%rbp)
sam_map_block+0x40: movq %r9,0xfffffffffffffea8(%rbp)
sam_map_block+0x47: movb %cl,0xfffffffffffffecb(%rbp)
sam_map_block+0x4d: movq %rax,0xfffffffffffffe98(%rbp)
sam_map_block+0x54: movq %r12,0xfffffffffffffe70(%rbp)
sam_map_block+0x5b: movq %rdi,%r12
sam_map_block+0x5e: nop
sam_map_block+0x60: testq %r13,%r13
sam_map_block+0x63: je +0x18 <sam_map_block+0x7d>
sam_map_block+0x65: xorl %esi,%esi
sam_map_block+0x67: movq $0x0,0x30(%r13)
sam_map_block+0x6f: pxor %xmm0,%xmm0
I build this kernel module with GCC14.
I have no clear understanding what "Bad trap: type=7 (#nm Device not available) " means. Looking on the assembler instruction "pxor %xmm0,%xmm0" seems that here special multimedia registers are used.
Is it possible the show the contents of this registers in mdb?
What does "Bad trap: type=7" means?
------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/Te2d5885af4d3b9f6-M732651bbffbab2e45832feb0
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
[-- Attachment #2: Type: text/html, Size: 3637 bytes --]
next reply other threads:[~2025-03-11 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 10:08 Carsten Grzemba via illumos-discuss [this message]
2025-03-11 10:54 ` Andy Fiddaman
2025-03-11 10:56 ` Toomas Soome via illumos-discuss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17416877060.A4eA.3424@composer.illumos.topicbox.com \
--to=discuss@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).