NetBSD Problem Report #43569

From www@NetBSD.org  Sun Jul  4 13:26:29 2010
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id B189A63BA81
	for <gnats-bugs@gnats.NetBSD.org>; Sun,  4 Jul 2010 13:26:29 +0000 (UTC)
Message-Id: <20100704132629.33BD263BA6F@www.NetBSD.org>
Date: Sun,  4 Jul 2010 13:26:29 +0000 (UTC)
From: daniel.meynen@homily-service.net
Reply-To: daniel.meynen@homily-service.net
To: gnats-bugs@NetBSD.org
Subject: sata cdrom drive downgraded to u-dma 1
X-Send-Pr-Version: www-1.0

>Number:         43569
>Category:       kern
>Synopsis:       sata cdrom drive downgraded to u-dma 1
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 04 13:30:00 +0000 2010
>Closed-Date:    Mon Aug 15 15:01:42 +0000 2016
>Last-Modified:  Mon Aug 15 15:01:42 +0000 2016
>Originator:     Daniel Meynen
>Release:        5.0.2 amd64
>Organization:
SCV
>Environment:
NetBSD comete.homily-service.net 5.0.2 NetBSD 5.0.2 (COMETE01) #0: Wed Jun  2 23:22:17 CEST 2010  daniel@comete.homily-service.net:/usr/src/sys/arch/amd64/compile/COMETE amd64

>Description:
The system is running on a motherboard asus m2n-sli deluxe with chipset nvidia nforce 570 sli mcp

The problem below seems to be linked to the one I have just posted in the PR 43565

The problem happens when I try to mount a cdrom put in a sata cdrom drive linked to this mb:

if I boot the system without acpi, I have to wait 30 seconds after I have sent the 'mount' command;  this means that mounting all the files of a cdrom takes at least 30 seconds;  during this time, /var/log/messages shows:

Jul  4 09:44:09 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:44:09 comete /netbsd: type: atapi tc_bcount: 8 tc_skip: 0
Jul  4 09:44:09 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:44:40 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:44:40 comete /netbsd: type: atapi tc_bcount: 4096 tc_skip: 0
Jul  4 09:44:40 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:45:10 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:45:10 comete /netbsd: type: atapi tc_bcount: 4096 tc_skip: 0
Jul  4 09:45:10 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:45:42 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:45:42 comete /netbsd: type: atapi tc_bcount: 2048 tc_skip: 0
Jul  4 09:45:42 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:45:42 comete /netbsd: cd0: transfer error, downgrading to Ultra-DMA mode 1
Jul  4 09:45:42 comete /netbsd: cd0(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA)
Jul  4 09:48:28 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:48:28 comete /netbsd: type: atapi tc_bcount: 2048 tc_skip: 0
Jul  4 09:48:28 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:48:28 comete /netbsd: cd0: transfer error, downgrading to PIO mode 4
Jul  4 09:48:28 comete /netbsd: cd0(viaide1:1:0): using PIO mode 4

but if I boot the system with acpi, I have to wait 90 seconds after I have sent the 'mount' command;  this means that mounting all the files of a cdrom takes at least 90 seconds;  during this time, /var/log/messages shows:

Jul  4 09:23:15 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:23:15 comete /netbsd: type: atapi tc_bcount: 4096 tc_skip: 0
Jul  4 09:23:15 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:23:45 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:23:45 comete /netbsd: type: atapi tc_bcount: 4096 tc_skip: 0
Jul  4 09:23:45 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:24:18 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:24:18 comete /netbsd: type: atapi tc_bcount: 2048 tc_skip: 0
Jul  4 09:24:18 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:24:48 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:24:48 comete /netbsd: type: atapi tc_bcount: 2048 tc_skip: 0
Jul  4 09:24:48 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:24:48 comete /netbsd: cd0: transfer error, downgrading to Ultra-DMA mode 1
Jul  4 09:24:48 comete /netbsd: cd0(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA)
Jul  4 09:25:18 comete /netbsd: viaide1:1:0: lost interrupt
Jul  4 09:25:18 comete /netbsd: type: atapi tc_bcount: 2048 tc_skip: 0
Jul  4 09:25:18 comete /netbsd: viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
Jul  4 09:25:18 comete /netbsd: cd0: transfer error, downgrading to PIO mode 4
Jul  4 09:25:18 comete /netbsd: cd0(viaide1:1:0): using PIO mode 4


Finally, all the files of the cdrom were mounted, but this took a long time...

Any help please...

Thanks!







>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:
From: Antti Kantee <pooka@cs.hut.fi>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/43569
Date: Mon, 5 Jul 2010 11:49:50 +0300

 When I've been in similar situations and have been unable to figure
 out what's wrong with DMA, I've compiled the kernel so that DMA is
 disabled for the cd.  The cd of course uses a lot more CPU that way,
 but at least you don't have to wait a long time for the initial access.
 You can do this by changing the cd line in the kernel config to the
 following:

 	cd*     at atapibus? drive ? flags 0x0ffc

 Disclaimer: I didn't verify it works, so there might be a typo there.
 See comments in GENERIC for more info.

 I don't know what the normal user way of doing that is supposed to be,
 but since you appear to have your own kernel, you might as well give
 that a go as a workaround.

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/43569: sata cdrom drive downgraded to u-dma 1
Date: Mon, 5 Jul 2010 21:15:54 +0000

 On Sun, Jul 04, 2010 at 01:30:00PM +0000, daniel.meynen@homily-service.net wrote:
  > The system is running on a motherboard asus m2n-sli deluxe with
  > chipset nvidia nforce 570 sli mcp
  > [...]
  > Jul  4 09:44:09 comete /netbsd: viaide1:1:0: lost interrupt

 Can you try 5.1 or -current? There were a bunch of fixes for nvidia
 viaide and I don't think they all made 5.0 (although I don't remember
 for sure...)

 Failing that, could you paste the dmesg bits for the viaide
 controller?

 Some of the nvidia sata controllers that attach as viaide ought to be
 getting handled as ahcisata instead, and I'm pretty sure we haven't
 found them all yet.

 -- 
 David A. Holland
 dholland@netbsd.org

From: Antti Kantee <pooka@cs.hut.fi>
To: daniel.meynen@homily-service.net
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/43569
Date: Tue, 6 Jul 2010 12:47:16 +0300

 On Tue Jul 06 2010 at 10:33:20 +0200, daniel.meynen@homily-service.net wrote:
 > Antti, 
 > 
 > 
 > 
 > Thank you very much for your help! 
 > 
 > It is a good solution.  I can now mount a cd or a dvd without waiting for a 
 > long time...  Any cd is mounted immediately, but with dma and u-dma disabled
 > for any cd. 
 > 
 > Nevertheless, David Holland has just sent me a message saying that the dvd 
 > drive I have should correctly work with the ahcisata driver...  Maybe 
 > another solution? 

 Yes, I recommend you try that and report back.  It might get DMA working
 for you and NetBSD would also be happy to know if the DMA problems with
 your hardware have been fixed in newer drivers.

From: daniel.meynen@homily-service.net
To: gnats-bugs@NetBSD.org
Cc: pooka@cs.hut.fi
Subject: Re: kern/43569
Date: Tue, 06 Jul 2010 10:33:20 +0200

 Antti, 



 Thank you very much for your help! 

 It is a good solution.  I can now mount a cd or a dvd without waiting for a 
 long time...  Any cd is mounted immediately, but with dma and u-dma disabled
 for any cd. 

 Nevertheless, David Holland has just sent me a message saying that the dvd 
 drive I have should correctly work with the ahcisata driver...  Maybe 
 another solution? 

 Daniel 







 Antti Kantee writes: 

 > The following reply was made to PR kern/43569; it has been noted by GNATS. 
 > 
 > From: Antti Kantee <pooka@cs.hut.fi>
 > To: gnats-bugs@netbsd.org
 > Cc: 
 > Subject: Re: kern/43569
 > Date: Mon, 5 Jul 2010 11:49:50 +0300 
 > 
 >  When I've been in similar situations and have been unable to figure
 >  out what's wrong with DMA, I've compiled the kernel so that DMA is
 >  disabled for the cd.  The cd of course uses a lot more CPU that way,
 >  but at least you don't have to wait a long time for the initial access.
 >  You can do this by changing the cd line in the kernel config to the
 >  following:
 >  
 >  	cd*     at atapibus? drive ? flags 0x0ffc
 >  
 >  Disclaimer: I didn't verify it works, so there might be a typo there.
 >  See comments in GENERIC for more info.
 >  
 >  I don't know what the normal user way of doing that is supposed to be,
 >  but since you appear to have your own kernel, you might as well give
 >  that a go as a workaround.
 >  

From: daniel.meynen@homily-service.net
To: gnats-bugs@netbsd.org
Cc: dholland-bugs@netbsd.org
Subject: Re: kern/43569: sata cdrom drive downgraded to u-dma 1
Date: Tue, 06 Jul 2010 15:54:59 +0200

 David, 



 I have just tried 5.1-RC3, but the result is the same. 

 I have not installed 5.1-RC3, for I have no hard drive free, but I began the 
 installation with the four diskets.  After that, I switched to /bin/sh and I 
 tried to mount a cd. 

 Here is the dmesg from the kernel of the four diskets of 5.1-RC3: 

 NetBSD 5.1_RC3 (INSTALL) #0: Sat Jun 12 20:26:05 UTC 2010
 	builds@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RC3/amd64/201006130031Z-obj 
 /home/builds/ab/netbsd-5-1-RC3/src/sys/arch/amd64/compile/INSTALL
 total memory =
  4094 MB
 avail memory = 3950 MB
 timecounter: Timecounters tick every 10.000 msec
 timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
 SMBIOS rev. 2.3 @ 0xf0000 (79 entries)
 System manufacturer System Product Name (System Version)
 mainbus0 (root)
 cpu0 at mainbus0 apid 0: AMD 686-class, 2210MHz, id 0x40fb2
 cpu0: AMD PowerNow! Technology 2200 MHz
 cpu0: available frequencies (Mhz): 1000 1800 2000 2200
 cpu1 at mainbus0 apid 1: AMD 686-class, 2210MHz, id 0x40fb2
 ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 11, 24 pins
 acpi0 at mainbus0: Intel ACPICA 20080321
 acpi0: X/RSDT: OemId <Nvidia,AWRDACPI,42302e31>, AslId <AWRD,00000000>
 acpi0: SCI interrupting at int 9
 acpi0: fixed-feature power button present
 timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
 ACPI-Fast 24-bit timer
 acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
 aiboost0 at acpi0 (ASOC, ATK0110-16843024)
 aiboost0: ASUS AI Boost Hardware monitor
 attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
 pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
 midi0 at pcppi1: PC speaker (CPU-intensive output)
 sysbeep0 at pcppi1
 FDC0 (PNP0700) at acpi0 not configured
 UAR1 (PNP0501) at acpi0 not configured
 LPT1 (PNP0400) at acpi0 not configured
 pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1
 FAN (PNP0C0B) at acpi0 not configured
 acpitz0 at acpi0 (THRM): active cooling level 0: 73.0C critical 75.0C 
 passive 40.0C
 attimer1: attached to pcppi1
 pckbd0 at pckbc1 (kbd slot)
 pckbc1: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard
 pci0 at mainbus0 bus 0: configuration mode 1
 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 vendor 0x10de product 0x0369 (RAM memory, revision 0xa1) at pci0 dev 0 
 function 0 not configured
 pcib0 at pci0 dev 1 function 0
 pcib0: vendor 0x10de product 0x0360 (rev. 0xa2)
 nfsmbc0 at pci0 dev 1 function 1: vendor 0x10de product 0x0368 (rev. 0xa2)
 nfsmb0 at nfsmbc0 SMBus 1
 iic0 at nfsmb0: I2C bus
 nfsmb1 at nfsmbc0 SMBus 2
 iic1 at nfsmb1: I2C bus
 vendor 0x10de product 0x036a (RAM memory, revision 0xa2) at pci0 dev 1 
 function 2 not configured
 ohci0 at pci0 dev 2 function 0: vendor 0x10de product 0x036c (rev. 0xa1)
 APCF: Picked IRQ 20 with weight 0
 ohci0: interrupting at ioapic0 pin 20
 ohci0: OHCI version 1.0, legacy support
 usb0 at ohci0: USB revision 1.0
 ehci0 at pci0 dev 2 function 1: vendor 0x10de product 0x036d (rev. 0xa2)
 APCL: Picked IRQ 21 with weight 0
 ehci0: interrupting at ioapic0 pin 21
 ehci0: EHCI version 1.0
 ehci0: companion controller, 10 ports each: ohci0
 usb1 at ehci0: USB revision 2.0
 viaide0 at pci0 dev 4 function 0
 viaide0: NVIDIA MCP55 IDE Controller (rev. 0xa1)
 viaide0: bus-master DMA support present
 viaide0: primary channel configured to compatibility mode
 viaide0: primary channel interrupting at ioapic0 pin 14
 atabus0 at viaide0 channel 0
 viaide0: secondary channel configured to compatibility mode
 viaide0: secondary channel ignored (disabled)
 viaide1 at pci0 dev 5 function 0
 viaide1: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)
 viaide1: bus-master DMA support present
 viaide1: primary channel wired to native-PCI mode
 APSI: Picked IRQ 22 with weight 0
 viaide1: using ioapic0 pin 22 for native-PCI interrupt
 atabus1 at viaide1 channel 0
 viaide1: secondary channel wired to native-PCI mode
 atabus2 at viaide1 channel 1
 viaide2 at pci0 dev 5 function 1
 viaide2: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)
 viaide2: bus-master DMA support present
 viaide2: primary channel wired to native-PCI mode
 APSJ: Picked IRQ 23 with weight 0
 viaide2: using ioapic0 pin 23 for native-PCI interrupt
 atabus3 at viaide2 channel 0
 viaide2: secondary channel wired to native-PCI mode
 atabus4 at viaide2 channel 1
 viaide3 at pci0 dev 5 function 2
 viaide3: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)
 viaide3: bus-master DMA support present
 viaide3: primary channel wired to native-PCI mode
 ASA2: Picked IRQ 20 with weight 1
 viaide3: using ioapic0 pin 20 for native-PCI interrupt
 atabus5 at viaide3 channel 0
 viaide3: secondary channel wired to native-PCI mode
 atabus6 at viaide3 channel 1
 ppb0 at pci0 dev 6 function 0: vendor 0x10de product 0x0370 (rev. 0xa2)
 pci1 at ppb0 bus 1
 pci1: i/o space, memory space enabled
 emuxki0 at pci1 dev 6 function 0: vendor 0x1102 product 0x0002 (audio 
 multimedia, revision 0x0a)
 APC1: Picked IRQ 16 with weight 0
 emuxki0: interrupting at ioapic0 pin 16
 emuxki0: ac97: SigmaTel STAC9708 codec; 18 bit DAC, 18 bit ADC, SigmaTel 3D
 emuxki0: ac97: ext id 80<SDAC>
 audio0 at emuxki0: full duplex, playback, capture, mmap, independent
 vendor 0x1102 product 0x7002 (miscellaneous input, revision 0x0a) at pci1 
 dev 6 function 1 not configured
 nfe0 at pci0 dev 8 function 0: vendor 0x10de product 0x0373 (rev. 0xa2)
 APCH: Picked IRQ 21 with weight 1
 nfe0: interrupting at ioapic0 pin 21
 nfe0: Ethernet address 00:18:f3:8b:8a:09
 makphy0 at nfe0 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1
 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 nfe1 at pci0 dev 9 function 0: vendor 0x10de product 0x0373 (rev. 0xa2)
 AMC1: Picked IRQ 22 with weight 1
 nfe1: interrupting at ioapic0 pin 22
 nfe1: Ethernet address 00:18:f3:8b:96:35
 makphy1 at nfe1 phy 1: Marvell 88E1116 Gigabit PHY, rev. 1
 makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 ppb1 at pci0 dev 10 function 0: vendor 0x10de product 0x0376 (rev. 0xa2)
 pci2 at ppb1 bus 2
 pci2: no spaces enabled!
 ppb2 at pci0 dev 11 function 0: vendor 0x10de product 0x0374 (rev. 0xa2)
 pci3 at ppb2 bus 3
 pci3: no spaces enabled!
 ppb3 at pci0 dev 12 function 0: vendor 0x10de product 0x0374 (rev. 0xa2)
 pci4 at ppb3 bus 4
 pci4: no spaces enabled!
 ppb4 at pci0 dev 13 function 0: vendor 0x10de product 0x0378 (rev. 0xa2)
 pci5 at ppb4 bus 5
 pci5: no spaces enabled!
 ppb5 at pci0 dev 14 function 0: vendor 0x10de product 0x0375 (rev. 0xa2)
 pci6 at ppb5 bus 6
 pci6: i/o space, memory space enabled, rd/line, wr/inv ok
 ppb6 at pci0 dev 15 function 0: vendor 0x10de product 0x0377 (rev. 0xa2)
 pci7 at ppb6 bus 7
 pci7: i/o space, memory space enabled, rd/line, wr/inv ok
 vga0 at pci7 dev 0 function 0: vendor 0x10de product 0x01df (rev. 0xa1)
 wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
 wsmux1: connecting to wsdisplay0
 drm at vga0 not configured
 pchb0 at pci0 dev 24 function 0
 pchb0: vendor 0x1022 product 0x1100 (rev. 0x00)
 pchb1 at pci0 dev 24 function 1
 pchb1: vendor 0x1022 product 0x1101 (rev. 0x00)
 pchb2 at pci0 dev 24 function 2
 pchb2: vendor 0x1022 product 0x1102 (rev. 0x00)
 amdtemp0 at pci0 dev 24 function 3
 amdtemp0: AMD CPU Temperature Sensors (K8: core rev BH-F2, socket AM2)
 isa0 at pcib0
 lpt0 at isa0 port 0x378-0x37b irq 7
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
 uhub0 at usb0: vendor 0x10de OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 10 ports with 10 removable, self powered
 uhub1 at usb1: vendor 0x10de EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
 uhub1: 10 ports with 10 removable, self powered
 viaide1 port 0: device present, speed: 1.5Gb/s
 wd0 at atabus0 drive 0viaide1 port 1: device present, speed: 1.5Gb/s
 : <Maxtor 6L080P0>
 wd0: drive supports 16-sector PIO transfers, LBA addressing
 wd0: 78167 MB, 158816 cyl, 16 head, 63 sec, 512 bytes/sect x 160086528 
 sectors
 wd0: 32-bit data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd1 at atabus0 drive 1: <HDT722520DLAT80>
 wd1: drive supports 16-sector PIO transfers, LBA48 addressing
 wd1: 186 GB, 387621 cyl, 16 head, 63 sec, 512 bytes/sect x 390721968 sectors
 wd1: 32-bit data port
 wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
 wd1(viaide0:0:1): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
 wd2 at atabus1 drive 0: <Kingston SSDNow V Series 64GB>
 wd2: drive supports 1-sector PIO transfers, LBA addressing
 wd2: 61057 MB, 124053 cyl, 16 head, 63 sec, 512 bytes/sect x 125045424 
 sectors
 wd2: 32-bit data port
 wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 wd2(viaide1:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA)
 atapibus0 at atabus2: 2 targets
 cd0 at atapibus0 drive 0: <TSSTcorpDVD-ROM SH-D163B, , SB01> cdrom removable
 cd0: 32-bit data port
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
 cd0(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA)
 Kernelized RAIDframe activated
 md0: internal 5000 KB image area
 pad0: outputs: 44100Hz, 16-bit, stereo
 audio1 at pad0: half duplex, playback, capture
 boot device: fd0
 root on md0a dumps on md0b
 root file system type: ffs
 WARNING: clock gained 23 days
 WARNING: CHECK AND RESET THE DATE!
 warning: no /dev/console
 uhidev0 at uhub0 port 6 configuration 1 interface 0
 uhidev0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 2, iclass 3/1
 ums0 at uhidev0: 3 buttons and Z dir
 wsmouse0 at ums0 mux 0
 viaide1:1:0: lost interrupt
 	type: atapi tc_bcount: 36 tc_skip: 0
 viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
 viaide1:1:0: lost interrupt
 	type: atapi tc_bcount: 32 tc_skip: 0
 viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
 viaide1:1:0: lost interrupt
 	type: atapi tc_bcount: 36 tc_skip: 0
 viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
 viaide1:1:0: lost interrupt
 	type: atapi tc_bcount: 36 tc_skip: 0
 viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
 cd0: transfer error, downgrading to Ultra-DMA mode 1
 cd0(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA)
 viaide1:1:0: lost interrupt
 	type: atapi tc_bcount: 4096 tc_skip: 0
 viaide1:1:0: bus-master DMA error: missing interrupt, status=0x21
 cd0: transfer
  error, downgrading to PIO mode 4
 cd0(viaide1:1:0): using PIO mode 4 


  --- 


 Do you need also the dmesg fro the kernel of 5.0.2? 

 Daniel 






 David Holland writes: 

 > The following reply was made to PR kern/43569; it has been noted by GNATS. 
 > 
 > From: David Holland <dholland-bugs@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/43569: sata cdrom drive downgraded to u-dma 1
 > Date: Mon, 5 Jul 2010 21:15:54 +0000 
 > 
 >  On Sun, Jul 04, 2010 at 01:30:00PM +0000, daniel.meynen@homily-service.net wrote:
 >   > The system is running on a motherboard asus m2n-sli deluxe with
 >   > chipset nvidia nforce 570 sli mcp
 >   > [...]
 >   > Jul  4 09:44:09 comete /netbsd: viaide1:1:0: lost interrupt
 >  
 >  Can you try 5.1 or -current? There were a bunch of fixes for nvidia
 >  viaide and I don't think they all made 5.0 (although I don't remember
 >  for sure...)
 >  
 >  Failing that, could you paste the dmesg bits for the viaide
 >  controller?
 >  
 >  Some of the nvidia sata controllers that attach as viaide ought to be
 >  getting handled as ahcisata instead, and I'm pretty sure we haven't
 >  found them all yet.
 >  
 >  -- 
 >  David A. Holland
 >  dholland@netbsd.org
 >  

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/43569: sata cdrom drive downgraded to u-dma 1
Date: Mon, 25 Oct 2010 02:33:28 +0000

 On Tue, Jul 06, 2010 at 02:00:07PM +0000, daniel.meynen@homily-service.net wrote:
  >  Here is the dmesg from the kernel of the four diskets of 5.1-RC3: 
  >  
  > [...]
  >  viaide0: NVIDIA MCP55 IDE Controller (rev. 0xa1)
  > [...]
  >  viaide1: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)
  > [...]
  >  viaide2: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)
  > [...]
  >  viaide3: NVIDIA MCP55 Serial ATA Controller (rev. 0xa2)

 That's the important bit. Unfortunately, as far as I know the MCP55
 controllers really are viaide (some or all MCP65 and MCP75 are really
 ahcisata) so what I suggested isn't going to help.

  >  Do you need also the dmesg fro the kernel of 5.0.2? 

 Nope, it won't be substantially different.

 If you feel brave you might try current (to see if it works, not so
 much for the dmesg) but probably it won't be any different.

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 31 Jul 2016 23:12:57 +0000
State-Changed-Why:
Are you still seeing this problem?


From: daniel.meynen@homily-service.net
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/43569 (sata cdrom drive downgraded to u-dma 1)
Date: Mon, 01 Aug 2016 07:33:13 +0200

 David, 



 I am still using NetBSD, but not with the same hardware.  Therefore, I 
 cannot answer your question.  Sorry... 

 Daniel 







 dholland@NetBSD.org writes: 

 > Synopsis: sata cdrom drive downgraded to u-dma 1 
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: dholland@NetBSD.org
 > State-Changed-When: Sun, 31 Jul 2016 23:12:57 +0000
 > State-Changed-Why:
 > Are you still seeing this problem? 
 > 
 >  
 > 

State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 15 Aug 2016 15:01:42 +0000
State-Changed-Why:
Hardware is gone, and it's unlikely this problem can be solved without
affected hardware :(


>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-2014 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.