NetBSD Problem Report #53254

From www@NetBSD.org  Thu May  3 03:31:19 2018
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 48C287A159
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  3 May 2018 03:31:19 +0000 (UTC)
Message-Id: <20180503033117.DBCCD7A1F4@mollari.NetBSD.org>
Date: Thu,  3 May 2018 03:31:17 +0000 (UTC)
From: coypu@sdf.org
Reply-To: coypu@sdf.org
To: gnats-bugs@NetBSD.org
Subject: kernel panic in scsibus_discover_thread
X-Send-Pr-Version: www-1.0

>Number:         53254
>Category:       kern
>Synopsis:       kernel panic in scsibus_discover_thread
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 03 03:35:00 +0000 2018
>Last-Modified:  Thu May 03 17:00:00 +0000 2018
>Originator:     coypu
>Release:        NetBSD 8.99.14
>Organization:
>Environment:
NetBSD planets 8.99.14 NetBSD 8.99.14 (GENERIC) #11: Mon Apr 30 08:21:50 IDT 2018  fly@planets:/home/fly/obj/sys/arch/amd64/compile/GENERIC amd64

>Description:
My old phone, when attached via usb, will repeatedly disconnect / re-appear, as if it's trying to stress test systems :-)

[ 11313.2909026] umass1: detached
[ 11313.2909026] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11314.2413033] uhub3: device problem, disabling port 3
[ 11315.1917044] uhub3: device problem, disabling port 3
[ 11316.1621141] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11316.1621141] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11316.1621141] umass1: using SCSI over Bulk-Only
[ 11316.1621141] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11316.1621141] sd1 at scsibus1 target 0 lun 0: <Samsung, File-CD Gadget, 0000> disk removable
[ 11316.1621141] sd1: drive offline
[ 11316.1721175] sd2 at scsibus1 target 0 lun 1: <Samsung, File-CD Gadget, 0000> disk removable
[ 11316.1721175] sd2: drive offline
[ 11316.3621981] sd1: detached
[ 11316.3621981] sd2: detached
[ 11316.3621981] scsibus1: detached
[ 11316.3621981] umass1: detached
[ 11316.3621981] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11319.6335779] uhub3: device problem, disabling port 3
[ 11320.5839787] uhub3: device problem, disabling port 3
[ 11322.6948698] uhub3: device problem, disabling port 3
[ 11323.6652785] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11323.6652785] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11323.6652785] umass1: using SCSI over Bulk-Only
[ 11323.6652785] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11323.6652785] sd1 at scsibus1 target 0 lun 0: <Samsung, File-CD Gadget, 0000> disk removable
[ 11323.6652785] sd1: drive offline
[ 11323.6752829] sd2 at scsibus1 target 0 lun 1: <Samsung, File-CD Gadget, 0000> disk removable
[ 11323.6752829] sd2: drive offline
[ 11323.7853292] sd1: detached
[ 11323.7853292] sd2: detached
[ 11323.7853292] scsibus1: detached
[ 11323.7853292] umass1: detached
[ 11323.7853292] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11324.7557384] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11324.7557384] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11324.7557384] umass1: using SCSI over Bulk-Only
[ 11324.7557384] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11324.7557384] sd1 at scsibus1 target 0 lun 0: <Samsung, File-CD Gadget, 0000> disk removable
[ 11324.7557384] sd1: drive offline
[ 11324.7657457] sd2 at scsibus1 target 0 lun 1: <Samsung, File-CD Gadget, 0000> disk removable
[ 11324.7657457] sd2: drive offline
[ 11325.1959242] sd1: detached
[ 11325.1959242] sd2: detached
[ 11325.1959242] scsibus1: detached
[ 11325.1959242] umass1: detached
[ 11325.1959242] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11326.1463256] uhub3: device problem, disabling port 3
[ 11329.4177050] uhub3: device problem, disabling port 3
[ 11331.5285960] uhub3: device problem, disabling port 3
[ 11332.1588617] uhub3: port 3, device not enabled
[ 11332.7891270] uhub3: port 3, device not enabled
[ 11336.0805154] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11336.0805154] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11336.0805154] umass1: using SCSI over Bulk-Only
[ 11336.0805154] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11336.0805154] scsibus1: detached
[ 11336.0805154] umass1: detached
[ 11336.0805154] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11338.2114148] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11338.2114148] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11338.2114148] umass1: using SCSI over Bulk-Only
[ 11338.2114148] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11338.2114148] scsibus1: detached
[ 11338.2114148] umass1: detached
[ 11338.2114148] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11339.1818235] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11339.1818235] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11339.1818235] umass1: using SCSI over Bulk-Only
[ 11339.1818235] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11339.1818235] sd1 at scsibus1 target 0 lun 0: <Samsung, File-CD Gadget, 0000> disk removable
[ 11339.1818235] sd1: drive offline
[ 11339.1918279] sd2 at scsibus1 target 0 lun 1: <Samsung, File-CD Gadget, 0000> disk removable
[ 11339.1918279] sd2: drive offline
[ 11415.1638736] sd1: detached
[ 11415.1638736] sd2: detached
[ 11415.1638736] scsibus1: detached
[ 11415.1638736] umass1: detached
[ 11415.1638736] umass1: at uhub3 port 3 (addr 5) disconnected
[ 11416.1342830] umass1 at uhub3 port 3 configuration 1 interface 0
[ 11416.1342830] umass1: Android (0x4e8) Android (0x685b), rev 2.00/2.26, addr 5
[ 11416.1342830] umass1: using SCSI over Bulk-Only
[ 11416.1342830] scsibus1 at umass1: 2 targets, 2 luns per target
[ 11416.1342830] sd1 at scsibus1 target 0 lun 0: <Samsung, File-CD Gadget, 0000> disk removable
[ 11416.1342830] sd1: drive offline
[ 11416.1442881] sd2 at scsibus1 target 0 lun 1: <Samsung, File-CD Gadget, 0000> disk removable
[ 11416.1442881] sd2: drive offline
[ 11416.1442881] uvm_fault(0xffffffff815b0180, 0x0, 1) -> e
[ 11416.1442881] fatal page fault in supervisor mode
[ 11416.1442881] trap type 6 code 0 rip 0xffffffff80266ddb cs 0x8 rflags 0x10246 cr2 0xa9 ilevel 0 rsp 0xffff800067553ea0
[ 11416.1442881] curlwp 0xffffe4012cd02a00 pid 0.165 lowest kstack 0xffff8000675502c0
[ 11416.1442881] panic: trap
[ 11416.1442881] cpu0: Begin traceback...
[ 11416.1442881] vpanic() at netbsd:vpanic+0x16f
[ 11416.1442881] snprintf() at netbsd:snprintf
[ 11416.1542911] startlwp() at netbsd:startlwp
[ 11416.1542911] alltraps() at netbsd:alltraps+0xc8
[ 11416.1542911] scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x7f
[ 11416.1542911] cpu0: End traceback...

[ 11416.1542911] dumping to dev 0,1 (offset=1896, size=1013425):
[ 11416.1542911] dump


>How-To-Repeat:

>Fix:

>Audit-Trail:
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/53254: kernel panic in scsibus_discover_thread
Date: Thu, 3 May 2018 11:44:29 -0000 (UTC)

 coypu@sdf.org writes:

 >My old phone, when attached via usb, will repeatedly disconnect / re-appear, as if it's trying to stress test systems :-)

 >[ 11416.1442881] uvm_fault(0xffffffff815b0180, 0x0, 1) -> e
 >[ 11416.1442881] fatal page fault in supervisor mode
 >[ 11416.1442881] trap type 6 code 0 rip 0xffffffff80266ddb cs 0x8 rflags 0x10246 cr2 0xa9 ilevel 0 rsp 0xffff800067553ea0
 >[ 11416.1442881] curlwp 0xffffe4012cd02a00 pid 0.165 lowest kstack 0xffff8000675502c0
 >[ 11416.1442881] panic: trap
 >[ 11416.1442881] cpu0: Begin traceback...
 >[ 11416.1442881] vpanic() at netbsd:vpanic+0x16f
 >[ 11416.1442881] snprintf() at netbsd:snprintf
 >[ 11416.1542911] startlwp() at netbsd:startlwp
 >[ 11416.1542911] alltraps() at netbsd:alltraps+0xc8
 >[ 11416.1542911] scsibus_discover_thread() at netbsd:scsibus_discover_thread+0x7f
 >[ 11416.1542911] cpu0: End traceback...

 >[ 11416.1542911] dumping to dev 0,1 (offset=1896, size=1013425):
 >[ 11416.1542911] dump

 Can you identify the faulting instruction and source line ?

 A fault address of 0xa9 looks strange.

 -- 
 -- 
                                 Michael van Elst
 Internet: mlelstv@serpens.de
                                 "A potential Snark may lurk in every tree."

From: coypu@sdf.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/53254: kernel panic in scsibus_discover_thread
Date: Thu, 3 May 2018 16:58:08 +0000

 On Thu, May 03, 2018 at 12:15:01PM +0000, Michael van Elst wrote:
 >  Can you identify the faulting instruction and source line ?
 >  
 >  A fault address of 0xa9 looks strange.

    0xffffffff80267583 <+92>:	mov    (%r14),%rbx
    0xffffffff80267586 <+95>:	cmp    (%rbx),%r12
    0xffffffff80267589 <+98>:	jne    0xffffffff80267574 <scsibus_discover_thread+77>
    0xffffffff8026758b <+100>:	mov    $0xffffffff81517eb8,%rdi
    0xffffffff80267592 <+107>:	callq  0xffffffff80226860 <mutex_exit>
    0xffffffff80267597 <+112>:	mov    $0xffffffff,%edx
    0xffffffff8026759c <+117>:	mov    %edx,%esi
    0xffffffff8026759e <+119>:	mov    %r15,%rdi
    0xffffffff802675a1 <+122>:	callq  0xffffffff80266d54 <scsi_probe_bus>
 => 0xffffffff802675a6 <+127>:	mov    $0xffffffff81517eb8,%rdi
    0xffffffff802675ad <+134>:	callq  0xffffffff80226840 <mutex_enter>
    0xffffffff802675b2 <+139>:	mov    0x8(%rbx),%rax
    0xffffffff802675b6 <+143>:	test   %rax,%rax
    0xffffffff802675b9 <+146>:	je     0xffffffff8026763f <scsibus_discover_thread+280>
    0xffffffff802675bf <+152>:	mov    0x10(%rbx),%rdx
    0xffffffff802675c3 <+156>:	mov    %rdx,0x10(%rax)
    0xffffffff802675c7 <+160>:	mov    0x10(%rbx),%rax
    0xffffffff802675cb <+164>:	mov    0x8(%rbx),%rdx
    0xffffffff802675cf <+168>:	mov    %rdx,(%rax)
    0xffffffff802675d2 <+171>:	mov    $0xffffffff81517ea0,%rdi
    0xffffffff802675d9 <+178>:	callq  0xffffffff80992243 <cv_broadcast>
    0xffffffff802675de <+183>:	mov    $0xffffffff81517eb8,%rdi
    0xffffffff802675e5 <+190>:	callq  0xffffffff80226860 <mutex_exit>
    0xffffffff802675b9 <+146>:	je     0xffffffff8026763f <scsibus_discover_thread+280>
    0xffffffff802675bf <+152>:	mov    0x10(%rbx),%rdx
    0xffffffff802675c3 <+156>:	mov    %rdx,0x10(%rax)
    0xffffffff802675c7 <+160>:	mov    0x10(%rbx),%rax
    0xffffffff802675cb <+164>:	mov    0x8(%rbx),%rdx
    0xffffffff802675cf <+168>:	mov    %rdx,(%rax)
    0xffffffff802675d2 <+171>:	mov    $0xffffffff81517ea0,%rdi
    0xffffffff802675d9 <+178>:	callq  0xffffffff80992243 <cv_broadcast>
    0xffffffff802675de <+183>:	mov    $0xffffffff81517eb8,%rdi
    0xffffffff802675e5 <+190>:	callq  0xffffffff80226860 <mutex_exit>

 No matching netbsd.gdb.

Home	PR Database Search