NetBSD Problem Report #49861

From www@NetBSD.org  Mon Apr 27 03:23:20 2015
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id A8235A654F
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 27 Apr 2015 03:23:20 +0000 (UTC)
Message-Id: <20150427032319.33517A6554@mollari.NetBSD.org>
Date: Mon, 27 Apr 2015 03:23:19 +0000 (UTC)
From: jdbaker@mylinuxisp.com
Reply-To: jdbaker@consolidated.net
To: gnats-bugs@NetBSD.org
Subject: 7.99.12 panic probing ieee1394 perphierals
X-Send-Pr-Version: www-1.0

>Number:         49861
>Notify-List:    jdbaker@consolidated.net
>Category:       kern
>Synopsis:       7.99.12 panic probing ieee1394 perphierals
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 27 03:25:00 +0000 2015
>Last-Modified:  Tue Jan 29 06:31:50 +0000 2019
>Originator:     John D. Baker
>Release:        NetBSD/i386-7.99.12
>Organization:
>Environment:
NetBSD slab.technoskunk.fur 7.99.12 NetBSD 7.99.12 (SLAB) #4: Sun Apr 26 14:18:49 CDT 2015  sysop@slab.technoskunk.fur:/d1/build/current/obj/i386/sys/arch/i386/compile/SLAB i386

>Description:
Booting a current kernel with ieee1394 disk and DVD-RW drive attached
(or plugging in after boot) causes a panic as follows (w/dmesg excerpts):

NetBSD 7.99.12 (SLAB) #4: Sun Apr 26 14:18:49 CDT 2015
	sysop@slab.technoskunk.fur:/d1/build/current/obj/i386/sys/arch/i386/compile/SLAB
[...]
fwohci0 at pci2 dev 0 function 2: Ricoh 5C552 PCI-CardBus Bridge/Firewire (rev. 0x00)
fwohci0: interrupting at irq 9
fwohci0: OHCI version 1.0 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:06:1b:00:10:00:72:5f
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
ieee1394if0 at fwohci0: IEEE1394 bus
fwip0 at ieee1394if0: IP over IEEE1394
fwohci0: Initiate bus reset
[...]
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc2, gen=1, CYCLEMASTER mode
ieee1394if0: 3 nodes, maxhop <= 2 cable IRM irm(2) (me)
ieee1394if0: bus manager 2
[...]
ieee1394if0: New S400 device ID:0050c502e0002799
ieee1394if0: New S400 device ID:0050c50250003475
sbp0 at ieee1394if0: SBP-2/SCSI over IEEE1394
scsibus0 at sbp0: 1 target, 0 luns per target
sbp1 at ieee1394if0: SBP-2/SCSI over IEEE1394
scsibus1 at sbp1: 1 target, 0 luns per target
sbp0: ordered:1 type:5 EUI:0050c50250003475 node:1 speed:2 maxrec:8
sbp0: sbp0:0:0 'ADS Technologies Inc.' 'DLX-185+ IDE Device 1' '000101'
sbp1: ordered:1 type:14 EUI:0050c502e0002799 node:0 speed:2 maxrec:8
sbp1: sbp1:0:0 'ADS Technologies Inc.' 'DLX-185+ IDE Device 1' '000101'
sd0 at scsibus1 target 0 lun 0: <ADS Tech, DLX-185+ IDE Dev, 1600> simplified direct fixed
cd0 at scsibus0 target 0 lun 0: <DVDRW, IDE1108, B028> cdrom removable
panic: kernel diagnostic assertion "cold || KERNEL_LOCKED_P()" failed: file "/d1/nbsd/current/src/sys/dev/scsipi/scsipi_base.c", line 219 
fatal breakpoint trap in supervisor mode
trap type 1 code 0 eip c0251584 cs 8 eflags 246 cr2 0 ilevel 0 esp db456f0c
curlwp 0xc35eb540 pid 0 lid 48 lowest kstack 0xdb4542c0
Stopped in pid 0.48 (system) at netbsd:breakpoint+0x4:  popl    %ebp
db{0}> bt
breakpoint(c09d3079,c0b76500,c0964a04,db456f28,0,0,c0964bb5,db456f1c,c08990c3,c0
964a04) at netbsd:breakpoint+0x4
vpanic(c0964a04,db456f28,db456f54,c06975b1,c0964a04,c0964bb5,c09c770e,c09c79b4,d
b,20202020) at netbsd:vpanic+0x127
kern_assert(c0964a04,c0964bb5,c09c770e,c09c79b4,db,20202020,20202020,20202020,a1
719a98,0) at netbsd:kern_assert+0x23
scsipi_lookup_periph(c2f8c588,0,0,c35bc0b8,c2f8c588,0,c2f8c548,c2f8c6c4,c2f8c6c0
,c2f8c628) at netbsd:scsipi_lookup_periph+0x111
sbp_scsipi_scan_target(c2f8c628,cad000,cb6000,0,c0100304,0,0,0,0,0) at netbsd:sb
p_scsipi_scan_target+0x102
db{0}>

The system is an IBM ThinkPad A31p.  A curious thing is that in the
above dmesg excerpt it attaches the ieee1394 DVD-RW drive as "cd0".

When running netbsd-7, the machine probes and attaches the ieee1394
peripherals without a problem and the internal ATAPI DVD-ROM/CDRW
drive is attached as "cd0" and the ieee1394 DVD-RW drive is "cd1".
>How-To-Repeat:
Boot -current (7.99.12, and some earlier) kernel with ieee1394 peripheral
attached and powered up.  Alternatively, plug in ieee1394 perhipheral at
a later time.
>Fix:

>Release-Note:

>Audit-Trail:

>Unformatted:

Home	PR Database Search