NetBSD Problem Report #9178

Received: (qmail 27051 invoked from network); 12 Jan 2000 18:52:19 -0000
Message-Id: <200001121852.TAA00476@luxemburg.swox.se>
Date: Wed, 12 Jan 2000 19:52:00 +0100 (CET)
From: Torbjorn Granlund <tege@luxemburg.swox.se>
Reply-To: tege@swox.se
To: gnats-bugs@gnats.netbsd.org
Subject: DMA error reading fsbn NNNN
X-Send-Pr-Version: 3.95

>Number:         9178
>Category:       kern
>Synopsis:       DMA error reading fsbn NNNN
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bouyer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 12 10:54:00 +0000 2000
>Closed-Date:    Sat Sep 20 10:37:02 +0000 2003
>Last-Modified:  Sat Sep 20 10:37:02 +0000 2003
>Originator:     Torbjorn Granlund
>Release:        1.4.1
>Organization:
Swox AB
>Environment:

System: NetBSD luxemburg 1.4.1 NetBSD 1.4.1 (GENERIC) #1: Tue Aug 10 00:03:09 MEST 1999 fvdl@struis:/usr/src/sys/arch/i386/compile/GENERIC i386

motherboard ASUS P5A rev 1.06 (Ali chipset)
processor Amd K6-III/400MHz
64MB SDRAM Samsung GH
disk IDE IBM 7200rpm 9GB
cdrom IDE NEC 16x

>Description:

The machine is unbelievably slow.  `tail /var/log/messages' or `ls /etc'
take 10 seconds or more.  A hint about the cause is in /var/log/messages:

Jan 12 19:34:56 luxemburg /netbsd: wd0e: DMA error reading fsbn 180816 of 180816-180847 (wd0 bn 3072768; cn 3048 tn 6 sn 6), retrying
Jan 12 19:34:56 luxemburg /netbsd: wd0: soft error (corrected)
Jan 12 19:34:56 luxemburg /netbsd: wd0e: DMA error reading fsbn 180848 of 180848-180895 (wd0 bn 3072800; cn 3048 tn 6 sn 38), retrying
Jan 12 19:34:57 luxemburg /netbsd: wd0: soft error (corrected)
Jan 12 19:34:59 luxemburg /netbsd: wd0e: DMA error reading fsbn 764224 of 764224-764239 (wd0 bn 3656176; cn 3627 tn 2 sn 34), retrying
Jan 12 19:35:00 luxemburg /netbsd: wd0: soft error (corrected)
Jan 12 19:35:00 luxemburg /netbsd: wd0e: DMA error readinrrected)

>How-To-Repeat:

Just install NetBSD 1.4.1 on similar hardware.  You'll see the problem
already during the install, or when slowly booting the installed
machine.

>Fix:
Unknown
>Release-Note:
>Audit-Trail:

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: gnats-bugs@gnats.netbsd.org
Cc:  Subject: Re: kern/9178: DMA error reading fsbn NNNN
Date: Thu, 13 Jan 2000 09:48:20 +0100

 [ Bcc:'d to port-i386 ]

 On Wed, Jan 12, 2000 at 07:52:00PM +0100, Torbjorn Granlund wrote:
 > motherboard ASUS P5A rev 1.06 (Ali chipset)
 > processor Amd K6-III/400MHz
 > 64MB SDRAM Samsung GH
 > disk IDE IBM 7200rpm 9GB
 > cdrom IDE NEC 16x
 > 
 > >Description:
 > 
 > The machine is unbelievably slow.  `tail /var/log/messages' or `ls /etc'
 > take 10 seconds or more.  A hint about the cause is in /var/log/messages:
 > 
 > Jan 12 19:34:56 luxemburg /netbsd: wd0e: DMA error reading fsbn 180816 of 180816-180847 (wd0 bn 3072768; cn 3048 tn 6 sn 6), retrying

 I'd like to collect more infos about this problem.
 Could everyone with a Ali based motherboard send back to me and
 gnats-bugs@gnats.netbsd.org, with
 Subject: Re: kern/9178: DMA error reading fsbn NNNN
 (so that gnats records it):
 - type of motherboard
 - dmesg
 - whenever you had the "DMA error" problem or not with a GENERIC kernel
   (or custom kernel, but with pciide and wd without flags)
 - if you had the problem, whenever using flags to force Ultra-DMA mode 1 helped

 thanks !


 --
 Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
 --

From: orione <orione@fol.it>
To: gnats-bugs@gnats.netbsd.org
Cc:  Subject: Re: kern/9178: DMA error reading fsbn NNNN
Date: Sat, 15 Jan 2000 09:10:12 +0100

 - Motherboard:	ASUS P5A

 - dmesg [note: i could only get this on a forced running configuration,
 since in the other case the msgbuf is completely filled by the DMA
 errors messages]:

 NetBSD 1.4.1 (MILLENNIUM) #6: Tue Dec 28 22:16:16 PST 1999 
 root@DeepRed:/usr/src/sys/arch/i386/compile/MILLENNIUM
 cpu0: family 5 model 8 step c
 cpu0: AMD K6-2 (586-class)
 real mem  = 66699264
 avail mem = 59387904
 using 839 buffers containing 3436544 bytes of memory
 mainbus0 (root)
 pci0 at mainbus0 bus 0: configuration mode 1
 pci0: i/o enabled, memory enabled
 pchb0 at pci0 dev 0 function 0
 pchb0: Acer Labs M1541 Host-PCI Bridge (rev. 0x04)
 ppb0 at pci0 dev 1 function 0: Acer Labs product 0x5243 (rev. 0x04)
 pci1 at ppb0 bus 1
 pci1: i/o enabled, memory enabled
 vga1 at pci1 dev 0 function 0: STB Systems (2nd PCI Vendor ID)
 Velocity128 (AGP) (rev. 0x22)
 wsdisplay0 at vga1: console (80x25, vt100 emulation)
 ohci0 at pci0 dev 2 function 0: Acer Labs M5237 USB Host Controller
 (rev. 0x03)
 ohci0: interrupting at irq 12
 ohci0: OHCI version 1.0, legacy support
 usb0 at ohci0
 uhub0 at usb0
 uhub0: Acer Labs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 Acer Labs M7101 Power Management Controller (miscellaneous bridge) at
 pci0 dev 3 function 0 not configured
 pcib0 at pci0 dev 7 function 0
 pcib0: Acer Labs M1543 PCI-ISA Bridge (rev. 0xc3)
 ex0 at pci0 dev 11 function 0: 3Com 3c905B-TX 10/100 Ethernet
 ex0: interrupting at irq 10
 ex0: MAC address 00:50:04:f8:02:5e
 pciide0 at pci0 dev 15 function 0: Acer Labs M5229 UDMA IDE Controller
 pciide0: bus-master DMA support present
 pciide0: primary channel configured to compatibility mode
 wd0 at pciide0 channel 0 drive 0: <IBM-DJNA-371350>
 wd0: drive supports 16-sector pio transfers, lba addressing
 wd0: 12949MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 26520480
 sectors
 wd0: 32-bits data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4, Ultra-DMA
 mode 3, Ultra-DMA mode 2
 pciide0: primary channel interrupting at irq 14
 pciide0: secondary channel configured to compatibility mode
 atapibus0 at pciide0 channel 1
 cd0 at atapibus0 drive 0: <ASUS CD-S400/A, , V3.2H> type 5 cdrom
 removable
 cd0: 32-bits data port
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
 wd1 at pciide0 channel 1 drive 1: <IBM-DJNA-371350>
 wd1: drive supports 16-sector pio transfers, lba addressing
 wd1: 12949MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 26520480
 sectors
 wd1: 32-bits data port
 wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4, Ultra-DMA
 mode 3, Ultra-DMA mode 2
 pciide0: secondary channel interrupting at irq 15
 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
 transfers)
 cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
 transfers)
 wd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
 transfers)
 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
 lpt0 at isa0 port 0x378-0x37b irq 7
 lpt1 at isa0 port 0x278-0x27b irq 5
 pckbc0 at isa0 port 0x60-0x64
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard
 opmsprobe: command error
 pcppi0 at isa0 port 0x61
 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
 fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
 isapnp0: no ISA Plug 'n Play devices found
 biomask d040 netmask d440 ttymask d4e2
 Kernelized RAIDframe activated
 wscons: wskbd0 glued to wsdisplay0 (console)
 boot device: wd0
 root on wd0a dumps on wd0b
 root file system type: ffs
 RAIDFRAME: protectedSectors is 64
 raid0: Component /dev/wd0e being configured at row: 0 col: 0
          Row: 0 Column: 0 Num Rows: 1 Num Columns: 2
          Version: 1 Serial Number: 666 Mod Counter: 190
          Clean: 1 Status: 0
 raid0: Component /dev/wd1e being configured at row: 0 col: 1
          Row: 0 Column: 1 Num Rows: 1 Num Columns: 2
          Version: 1 Serial Number: 666 Mod Counter: 190
          Clean: 1 Status: 0
 RAIDFRAME: Configure (RAID Level 1): total number of sectors is 24946912
 (12181MB)
 RAIDFRAME(RAID Level 1): Using 6 floating recon bufs with no head sep
 limit
 wsdisplay0: screen 1 added (80x50, vt100 emulation)
 wsdisplay0: screen 2 added (80x50, vt100 emulation)
 wsdisplay0: screen 3 added (80x50, vt100 emulation)
 wsdisplay0: screen 4 added (80x50, vt100 emulation)

 - With the default configuration [AMD K6-2-400 with FSB 100Mhz, 8ns
 Dimm] I can't get a working system with UDMA-2 or UDMA-3. I got a real
 bunch of DMA errors... retrying|corrected, but usually the system ends
 up in... db>
 I can get a running system with UDMA-2 if I overclock to 450MHz, that,
 according to the motherboard manual, means: FSB 110MHz AGP 73MHz PCI
 36.6MHz. Can't get any UDMA-3 to work properly.

 - With a forced UDMA-1 I got a working system, even in 400MHz mode.

 Hope this help somehow.

 Marco.

From: Rick Cockerham <cockerham@flame.org>
To: gnats-bugs@gnats.netbsd.org
Cc: cockerham@flame.org
Subject: Re: kern/9178: DMA error reading fsbn NNNN
Date: 5 Feb 2002 00:48:43 -0000

 I have fried three hard drives now.  I have:
  A Quantum, Western Digital, and MDT hard drive.
  All UDMA, 2GB, and two 10GB's


  The first Quantum died in a case with plenty of power,
  and a VIA P5BV3+ motherboard.  Sorry no dmesg.


  The second two died in a case with more power, and
  a FIC VA-503+ motherboard (new).  I would have to copy
  the dmesg by hand to get this one.


  I get a variety of error messages:


  wd1a: aborted command reading fsbn 64 of 64-79(wd0 bn 4197376, cn 4164, tn 1, sn 1) retrying
  pciide0:1:0: recal error(4)
  pciide channel 1: reset failed for drive 0
  pciide 0:1:0: not ready, st=0xd0, err=0x00


  pciide 0:0:0 lost interrupt
     type: ata tc_bcount: 8192 tc_skip:0


  Will rebuilding a kernel with UDMA off help me?  I'm asking because I would rather not.


  What about these hard drives?  Are they all paper weights?  One is new, so I can get another one.


  Thanks,
 	Richard Cockerham
 	cockerham@flame.org

Responsible-Changed-From-To: kern-bug-people->bouyer 
Responsible-Changed-By: bouyer 
Responsible-Changed-When: Mon Apr 7 09:09:50 PDT 2003 
Responsible-Changed-Why:  
I handle pciide problems 
State-Changed-From-To: open->feedback 
State-Changed-By: bouyer 
State-Changed-When: Mon Apr 7 09:10:17 PDT 2003 
State-Changed-Why:  
Hi, 
this is old. Do you know if this is still a problem with recent NetBSD releases ? 

From: Torbjorn Granlund <tege@swox.com>
To: gnats-bugs@netbsd.org, postmaster@netbsd.org
Cc:  
Subject: Re: kern/9178: DMA error reading fsbn NNNN
Date: 20 Sep 2003 12:20:29 +0200

 Please stop sending me mail after mail about some 3 year old bug
 report.  You have ignored the bug report for three years, and
 certainly you cannot expect me to worry too much about netbsd on
 this platform now.

 I used to be a happy netbsd user around '95-'98.  I ran it on all
 sorts of hardware.  But after that period, releases usually
 didn't install, or crashed in the first boot, or worked horribly
 poorly after they booted.  From having had almost no problems
 with netbsd, I had nothing but problems with it.  Bug reports
 where silently ignored.

 This made me migrate away from netbsd to other bsd'es.  But I
 made infrequent attempts to install netbsd again.  The last one
 was in 2000, and that failure resulted in the bug report from me
 that is now generating unwanted mail.

 You are welcome to keep all bug reports from me open, or delete
 them.  But please don't put them in feedback state as long as
 your system then starts firing away mail after mail to my
 mailbox.  It gets enough junk mail already.

 -- 
 Torbjörn
State-Changed-From-To: feedback->closed 
State-Changed-By: bouyer 
State-Changed-When: Sat Sep 20 06:35:08 EDT 2003 
State-Changed-Why:  
Sender doesn't want to look at this any more. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.