From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 8 19:22:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CEF737B401 for ; Tue, 8 Jul 2003 19:22:08 -0700 (PDT) Received: from STYX.ORG (mail.styx.org [204.138.67.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DAC43FA3 for ; Tue, 8 Jul 2003 19:22:06 -0700 (PDT) (envelope-from ww@STYX.ORG) Received: by STYX.ORG (Postfix, from userid 1001) id 8246A4F44; Tue, 8 Jul 2003 22:22:05 -0400 (EDT) Date: Tue, 8 Jul 2003 22:22:05 -0400 From: news+freebsd_hackers@news.styx.org To: abkonstantinov@earthlink.net Message-ID: <20030709022205.GK12955@styx.org> References: <20030709014153.GA5165@andruxa.sytes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030709014153.GA5165@andruxa.sytes.net> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org Subject: DMA issues (Was Re: lpt0 - device busy) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: news+freebsd_hackers@news.styx.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 02:22:08 -0000 FWIW, I have similar symptoms with 5.1. Worse in fact. Nothing that does DMA (which includes the parallel port in ECP mode) functions correctly on this VIA C3 board. Disks running PIO4 -- it is necessary to turn off UDMA in the BIOS for 5.1 to boot (5.0 boots ok off the CD) Strangely, the disk shows up in the dmesg as supporting UDMA. Not sure which interface is being used in reality. The cdrom drive acting *really* weird -- skipping all over the place, then locking up -- if I try to access any audio data. For example, booting and logging in with an audio CD in the drive causes a very unpleasant reaction when the KDE desktop gunk tries to see what sort of disc is in the drive... I'm on a very slow network connection right now, so I haven't tried updating my source from CVS. I believe the DMA problems have been mentioned on the freebsd-hardware list recently, specifically relating to the IDE subsystem. I believe that someone was working on an improved IDE driver that didn't have this problem. I'm not sure if the fix is general enough make DMA work properly for the printer port also. As well, I believe the CPU should be running at 1GHz, but it looks like 666MHz from the dmesg (and feels like it too). Can anyone offer any elucidations about the status of FreeBSD on this sort of hardware? Dmesg follows. Cheers, -w Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #1: Fri Jul 4 22:15:26 GMT 2003 ww@parc.styx.org:/usr/obj/export/FreeBSD/src/sys/PARC Preloaded elf kernel "/boot/kernel/kernel" at 0xc070a000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc070a244. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 667815180 Hz CPU: VIA C3 Samuel 2 (667.82-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x672 Stepping = 2 Features=0x803035 real memory = 528416768 (503 MB) avail memory = 504606720 (481 MB) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdc70 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4 000-0x407f,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xd0000000-0xd3ffffff at device 0.0 o n pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x9000-0x900f at device 7.1 on pc i0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x9400-0x941f irq 11 at device 7.2 on pc i0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: at device 7.4 (no driver attached) pci0: at device 7.5 (no driver attached) cbb0: mem 0xd8404000-0xd8404fff irq 12 at device 8. 0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 dc0: port 0xbc00-0xbcff mem 0xd8403000-0xd84033ff ir q 10 at device 9.0 on pci0 dc0: Ethernet address: 00:50:bf:fe:68:d6 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 10.0 (no driver attached) rl0: port 0xc000-0xc0ff mem 0xd8406000-0xd84060ff ir q 11 at device 14.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:07:95:58:8b:75 miibus1: on rl0 rlphy0: on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: port 0x3f7,0x3f0-0 x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: