Re: kern/45748: esiop fails with DEBUG kernels

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR kern/45748; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost
Subject: Re: kern/45748: esiop fails with DEBUG kernels
Date: Wed, 4 Jan 2012 16:31:18 +0100

 On Tue, Dec 27, 2011 at 07:20:00PM +0000, martin%NetBSD.org@localhost wrote:
 > probe(esiop1:0:11:0): command with tag id -1 reset
 > esiop1: DMA IRQ: bus fault DMA fifo empty, DSP=0x3c0 DSA=0xfe09e790:  
 > current T/L/Q invalid
 > esiop1: scsi bus reset
 > probe(esiop1:0:12:0): command with tag id -1 reset
 > esiop1: DMA IRQ: bus fault DMA fifo empty, DSP=0x3c0 DSA=0xfe09e840:  
 > current T/L/Q invalid
 > esiop1: scsi bus reset
 > probe(esiop1:0:13:0): command with tag id -1 reset
 > esiop1: DMA IRQ: bus fault DMA fifo empty, DSP=0x3c0 DSA=0xfe09e8f0:  
 > current T/L/Q invalid
 > esiop1: scsi bus reset
 > probe(esiop1:0:14:0): command with tag id -1 reset
 > esiop1: DMA IRQ: bus fault DMA fifo empty, DSP=0x3c0 DSA=0xfe09e9a0:  
 > current T/L/Q invalid
 > esiop1: scsi bus reset
 > probe(esiop1:0:15:0): command with tag id -1 reset
 > 
 > and then no devices are found.
 > 
 > A kernel from same sources but without DEBUG works fine.
 
 That's strange: options DEBUG should not change the compiler output for
 esiop sources. Could DEBUG cause a bug in sparc64's bus_space or bus_dma
 functions ?
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --