NetBSD Problem Report #12114

Received: (qmail 4715 invoked from network); 2 Feb 2001 15:44:05 -0000
Message-Id: <200102021543.f12Fhdd03927@lager.beer.org>
Date: Fri, 2 Feb 2001 08:43:39 -0700 (MST)
From: Herb Peyerl <hpeyerl@beer.org>
Reply-To: hpeyerl@beer.org
To: gnats-bugs@gnats.netbsd.org
Subject: adw driver in 1.5 and -current broken.
X-Send-Pr-Version: 3.95

>Number:         12114
>Category:       kern
>Synopsis:       adw driver in 1.5 and -current broken.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 02 15:45:00 +0000 2001
>Closed-Date:    Sun Feb 11 23:46:05 +0000 2001
>Last-Modified:  Sun Feb 11 23:46:05 +0000 2001
>Originator:     Herb Peyerl
>Release:        current
>Organization:
>Environment:
NetBSD grok 1.5Q NetBSD 1.5Q (GENERIC) #0: Thu Feb  1 18:36:52 MST 2001     hpey
erl@stout.beer.org:/data1/current-010123/syssrc/sys/arch/i386/compile/GENERIC i3
86
>Description:

I have a PIII/500 with an Advansys 3940 scsi controller.  This machine has
been happily running 1.4K as a production webserver with 200+ day uptimes. I
tried to upgrade to 1.5 and subsequently -current, by booting a kernel and
then untarring base.tgz over top of my 1.4K binaries.  Here's what happens:


	grok# foreach I (*.tgz)
	? gzcat $I | (cd / ; tar xpf - )
	? end
	adw0: DMA Error. Reseting bus
	^@^C^C^C^C^Cadw0: DMA Error. Reseting bus
	^C^C^C^C
	^C
	^C
	^C
	z
	^Z^Cadw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus:37:04 grok /netbsd: adw0: DMA Error. Reseting bus

	adw0: DMA Error. Reseting bus

....at which point my filesystem is hosed.

Here's a dmesg:

NetBSD 1.5Q (GENERIC) #0: Thu Feb  1 18:36:52 MST 2001
    hpeyerl@stout.beer.org:/data1/current-010123/syssrc/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III (Katmai) (686-class), 501.16 MHz
cpu0: I-cache 16K 32b/line 4-way, D-cache 16K 32b/line 2/4-way
cpu0: L2 cache 512K 32b/line 4-way
cpu0: features 383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
cpu0: features 383f9ff<PGE,MCA,CMOV,FGPAT,PSE36,MMX,FXSR,XMM>
total memory = 255 MB
avail memory = 231 MB
using 3297 buffers containing 13188 KB of memory
BIOS32 rev. 0 found at 0xf06b0
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82443BX Host Bridge/Controller (rev. 0x03)
ppb0 at pci0 dev 1 function 0: Intel 82443BX AGP Interface (rev. 0x03)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
pcib0 at pci0 dev 4 function 0
pcib0: Intel 82371AB PCI-to-ISA Bridge (PIIX4) (rev. 0x02)
pciide0 at pci0 dev 4 function 1: Intel 82371AB IDE controller (PIIX4) (rev. 0x01)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
pciide0: disabling primary channel (no drives)
pciide0: secondary channel wired to compatibility mode
pciide0: disabling secondary channel (no drives)
uhci0 at pci0 dev 4 function 2: Intel 82371AB USB Host Controller (PIIX4) (rev. 0x01)
uhci0: interrupting at irq 12
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Intel 82371AB Power Management Controller (PIIX4) (miscellaneous bridge, revision 0x02) at
 pci0 dev 4 function 3 not configured
fxp0 at pci0 dev 9 function 0: Intel i82557 Ethernet, rev 8
fxp0: interrupting at irq 12
fxp0: Ethernet address 00:90:27:93:d5:a2, 10/100 Mb/s
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1 at pci0 dev 10 function 0: Intel i82557 Ethernet, rev 8
fxp1: interrupting at irq 10
fxp1: Ethernet address 00:90:27:93:dd:87, 10/100 Mb/s
inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
adw0 at pci0 dev 11 function 0: AdvanSys ASB-3940UW-00 SCSI adapter
adw0: interrupting at irq 11
scsibus0 at adw0: 16 targets, 8 luns per target
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
lpt0 at isa0 port 0x378-0x37b irq 7
pcdisplay0 at isa0 port 0x3b0-0x3bf iomem 0xb0000-0xb7fff
wsdisplay0 at pcdisplay0: console (80x25, vt100 emulation), using wskbd0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
isapnp0: no ISA Plug 'n Play devices found
biomask fb65 netmask ff65 ttymask ffe7
scsibus0: waiting 2 seconds for devices to settle...
adw0: target 8 using 16-bits wide, 20.8 MHz synchronous transfers
sd0 at scsibus0 target 8 lun 0: <SEAGATE, ST318275LW, 0001> SCSI2 0/direct fixed
sd0: 17366 MB, 11721 cyl, 10 head, 303 sec, 512 bytes/sect x 35566480 sectors
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs
IP Filter: v3.4.9 initialized.  Default = pass all, Logging = enabled
adw0: DMA Error. Reseting bus
adw0: DMA Error. Reseting bus
adw0: DMA Error. Reseting bus
adw0: DMA Error. Reseting bus
adw0: DMA Error. Reseting bus



>How-To-Repeat:
install current on an Advansys 3940 bearing machine and untar base.tgz.
>Fix:
not known
>Release-Note:
>Audit-Trail:

From: Greg Oster <oster@cs.usask.ca>
To: hpeyerl@beer.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/12114: adw driver in 1.5 and -current broken. 
Date: Fri, 02 Feb 2001 10:02:18 -0600

 Herb Peyerl writes:
 > I have a PIII/500 with an Advansys 3940 scsi controller.  This machine has
 > been happily running 1.4K as a production webserver with 200+ day uptimes. I
 > tried to upgrade to 1.5 and subsequently -current, by booting a kernel and
 > then untarring base.tgz over top of my 1.4K binaries.  Here's what happens:

 Did you power-cycle the machine between the 1.4K and the 1.5 kernels?
 I *think* that there is slightly newer microcode in 1.5 and -current
 (as compared to 1.4K), and perhaps the microcode on the card isn't getting 
 flushed properly?

 (My main box has a 3940, and has been up 55 days, and I havn't seen that 
 error... I've seen stuff like:

 Nov 19 14:33:56 merlin /netbsd: adw0: Carrier Ready failure!
 Nov 19 14:33:56 merlin last message repeated 415 times

 with pre 1.5 proper kernels, but i havn't had a single problem with 1.5+adw)

 OOOHH!!!!!! 
 > adw0: target 8 using 16-bits wide, 20.8 MHz synchronous transfers

 That is *NOT* U2W... which means your SCSI cable length had better be short...

 If it's really doing U2W, you should see something like:
 adw0: target 1 using 16-bits wide, 40.0 MHz synchronous transfers

 Later...

 Greg Oster



From: Herb Peyerl <hpeyerl@beer.org>
To: Greg Oster <oster@cs.usask.ca>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/12114: adw driver in 1.5 and -current broken. 
Date: Fri, 02 Feb 2001 09:15:08 -0700

 Greg Oster <oster@cs.usask.ca>  wrote:
  > Did you power-cycle the machine between the 1.4K and the 1.5 kernels?
  > I *think* that there is slightly newer microcode in 1.5 and -current
  > (as compared to 1.4K), and perhaps the microcode on the card isn't getting 
  > flushed properly?

 ugh. no, I didn't power cycle, though I did hit reset (with my weasel). The
 machine is in a colo facility in sweden so it would cost me money to send
 someone out to power-cycle it.

  > (My main box has a 3940, and has been up 55 days, and I havn't seen that 
  > error... I've seen stuff like:
  > 
  > Nov 19 14:33:56 merlin /netbsd: adw0: Carrier Ready failure!
  > Nov 19 14:33:56 merlin last message repeated 415 times
  > 
  > with pre 1.5 proper kernels, but i havn't had a single problem with 1.5+adw)

 I've never seen that with my 1.4k kernel. strange.

  > OOOHH!!!!!! 
  > > adw0: target 8 using 16-bits wide, 20.8 MHz synchronous transfers
  > 
  > That is *NOT* U2W... which means your SCSI cable length had better be short...
  > 
  > If it's really doing U2W, you should see something like:
  > adw0: target 1 using 16-bits wide, 40.0 MHz synchronous transfers

 I don't understand what you're getting at there.  and it's an internal disk
 with the standard kinda 18 inch scsi cable.  no external devices.  I don't
 think it's a U2W controller. I think it's UW only.



From: Greg Oster <oster@cs.usask.ca>
To: Herb Peyerl <hpeyerl@beer.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/12114: adw driver in 1.5 and -current broken. 
Date: Fri, 02 Feb 2001 11:47:38 -0600

 Herb Peyerl writes:
 > Greg Oster <oster@cs.usask.ca>  wrote:
 >  > Did you power-cycle the machine between the 1.4K and the 1.5 kernels?
 >  > I *think* that there is slightly newer microcode in 1.5 and -current
 >  > (as compared to 1.4K), and perhaps the microcode on the card isn't getting
 >  
 >  > flushed properly?
 > 
 > ugh. no, I didn't power cycle, though I did hit reset (with my weasel). The
 > machine is in a colo facility in sweden so it would cost me money to send
 > someone out to power-cycle it.
 > 
 >  > (My main box has a 3940, and has been up 55 days, and I havn't seen that 
 >  > error... I've seen stuff like:
 >  > 
 >  > Nov 19 14:33:56 merlin /netbsd: adw0: Carrier Ready failure!
 >  > Nov 19 14:33:56 merlin last message repeated 415 times
 >  > 
 >  > with pre 1.5 proper kernels, but i havn't had a single problem with 1.5+ad
 > w)
 > 
 > I've never seen that with my 1.4k kernel. strange.
 > 
 >  > OOOHH!!!!!! 
 >  > > adw0: target 8 using 16-bits wide, 20.8 MHz synchronous transfers
 >  > 
 >  > That is *NOT* U2W... which means your SCSI cable length had better be shor
 > t...
 >  > 
 >  > If it's really doing U2W, you should see something like:
 >  > adw0: target 1 using 16-bits wide, 40.0 MHz synchronous transfers
 > 
 > I don't understand what you're getting at there.  and it's an internal disk
 > with the standard kinda 18 inch scsi cable.  no external devices.  I don't
 > think it's a U2W controller. I think it's UW only.

 Oh!  You're right... the 3940 you have is only UW.  Hmmmmmm.

 Later...

 Greg Oster


State-Changed-From-To: open->closed 
State-Changed-By: hpeyerl 
State-Changed-When: Sun Feb 11 15:43:01 PST 2001 
State-Changed-Why:  
Fixed in /sys/dev/ic/adw.c: 1.27. 
>Unformatted:
 Sun Feb 11 15:44:36 PST 2001

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.