NetBSD Problem Report #45748

From martin@duskware.de  Tue Dec 27 19:17:28 2011
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id BF77E63DD4A
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 27 Dec 2011 19:17:27 +0000 (UTC)
Message-Id: <20111227191727.BF77E63DD4A@www.NetBSD.org>
Date: Tue, 27 Dec 2011 19:17:27 +0000 (UTC)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: esiop fails with DEBUG kernels
X-Send-Pr-Version: 3.95

>Number:         45748
>Category:       kern
>Synopsis:       esiop fails with DEBUG kernels
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 27 19:20:00 +0000 2011
>Last-Modified:  Wed Jan 04 15:35:01 +0000 2012
>Originator:     Martin Husemann
>Release:        NetBSD 5.99.59
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD sunny-weather.duskware.de 5.99.59 NetBSD 5.99.59 (SUNNY.MP) #59: Sat Dec 17 21:41:38 CET 2011 martin@night-porter.duskware.de:/usr/src-soc/sys/arch/sparc64/compile/SUNNY.MP sparc64
Architecture: sparc64
Machine: sparc64
>Description:

A -current kernel with DEBUG option enabled does not boot on my sparc64
machine:

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.

>How-To-Repeat:
Boot a GENERIC.DEBUG kernel on an U60 machine ;-)

>Fix:
n/a

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
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 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>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

Home	PR Database Search