Re: more problems with 5.3 and TIMEOUT - WRITE_DMA [SOLOTION]
On Mar 27, 2005 11:47 PM, Mike Daemon [EMAIL PROTECTED] wrote: On Sun, 27 Mar 2005 13:32:43 -0800, Thomas Foster [EMAIL PROTECTED] wrote: I had this same issue I´ll have seen some more posts on the list with about the same problem therefore, I hope some bright one will take alook at the code.. and post something smart.. I´m very much stuck, hopeing any new snapshot will work.. on an older AMD Nforce board. 5.2.1 seemed to install and run.. but moving to 5.3 gave me issues. I tinkered with the DMA settings in the BIOS.. to no avail. The Geometry seemed to be off on the drive I noticed (IBM deskstar) when I newfs'd it.. so I changed out drives.. but never got it working.. I eventually just dropped Gentoo on it. What chipset, drive controller hard drive are you using on this system? http://www.freebsd.org/cgi/man.cgi?query=atasektion=4manpath=FreeBSD+5.3-RELEASE I´ll notised that my idecontroller IS supported by the ata-driver, witch makes it even stranger.. (I think I will check on my cabling once more, even if it´s a newly installed _rounded_ 32 pin cable..) My atacontroller: SiS 5513 My HDD: Seagate 200 GB T - Original Message - From: Mike Daemon [EMAIL PROTECTED] To: FreeBSD Questions freebsd-questions@freebsd.org Sent: Sunday, March 27, 2005 1:15 PM Subject: more problems with 5.3 and TIMEOUT - WRITE_DMA I got this annoying problem when upgradeing to 5.3, the miniinst iso blurps out TIMEOUT - WRITE_DMA when it starts writing base to my disk. And when I tried to first install 5.2.1 and upgrade (cvsup, make buildworld etc.. ) to 5.3 that way everything seems fine until I reboot to single-user-mode, as soon as Im starting to write anything to the disk it´s blurping out those errors.. I have diagnosticed my disk, checked my cabling and fixed my PSU (installed a brand new one). No difference. I noticed that my ide-controller was supported in 4.11, but not? in 5.3, is that realy true? seems very strange... Sence I duel boot with Wintendo/Lunix and don´t see this problem with those oses I´m very confused of what to do next.. I´ll tried some snapshots to but no luck... / Mike ps My dmesg goes in the attachment, in hope for a patch/solution to this problem. ds ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I (with a little help from a good friend ) figured out an solution to the problem, in switching my brand new ata133 ide-cable to an old school ata33 ide-cable FreeBSD sets my drives to UDMA3 and boots up alright.. key commands here: atacontrol list and atacontrol mode channel number ( my buddy had come across some message telling about how SiS had created an new SiS 5513 chipset with the same tag.. unfortunal he didn't remember where that message were. But it would make sense why FreeBSD tryies to use UDMA5 on my UDMA3 only atachipset.. ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
more problems with 5.3 and TIMEOUT - WRITE_DMA
I got this annoying problem when upgradeing to 5.3, the miniinst iso blurps out TIMEOUT - WRITE_DMA when it starts writing base to my disk. And when I tried to first install 5.2.1 and upgrade (cvsup, make buildworld etc.. ) to 5.3 that way everything seems fine until I reboot to single-user-mode, as soon as Im starting to write anything to the disk it´s blurping out those errors.. I have diagnosticed my disk, checked my cabling and fixed my PSU (installed a brand new one). No difference. I noticed that my ide-controller was supported in 4.11, but not? in 5.3, is that realy true? seems very strange... Sence I duel boot with Wintendo/Lunix and don´t see this problem with those oses I´m very confused of what to do next.. I´ll tried some snapshots to but no luck... / Mike ps My dmesg goes in the attachment, in hope for a patch/solution to this problem. ds Copyright (c) 1992-2004 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.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0e6d000. Preloaded mfs_root /boot/mfsroot at 0xc0e6d244. Preloaded elf module /boot/kernel/acpi.ko at 0xc0e6d288. ACPI APIC Table: ASUS P4S533 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.10-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 268419072 (255 MB) avail memory = 246906880 (235 MB) ioapic0 Version 0.0 irqs 0-23 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S533 on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00f1b10 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SIS Generic host to PCI bridge mem 0xe800-0xebff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 ohci0: SiS 5571 USB controller mem 0xe680-0xe6800fff irq 20 at device 2.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xe600-0xe6000fff irq 23 at device 2.3 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. atapci0: SiS 5513 UDMA33 controller port 0xd800-0xd80f at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: multimedia, audio at device 5.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xa400-0xa4ff mem 0xe500-0xe5ff irq 17 at device 9.0 on pci0 rl0: Ethernet address: 00:c1:26:0e:fe:f5 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 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/16 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: Option ROM at iomem 0xd-0xd3fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2400095416 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image
Re: more problems with 5.3 and TIMEOUT - WRITE_DMA
On Sun, 27 Mar 2005 13:32:43 -0800, Thomas Foster [EMAIL PROTECTED] wrote: I had this same issue I´ll have seen some more posts on the list with about the same problem therefore, I hope some bright one will take alook at the code.. and post something smart.. I´m very much stuck, hopeing any new snapshot will work.. on an older AMD Nforce board. 5.2.1 seemed to install and run.. but moving to 5.3 gave me issues. I tinkered with the DMA settings in the BIOS.. to no avail. The Geometry seemed to be off on the drive I noticed (IBM deskstar) when I newfs'd it.. so I changed out drives.. but never got it working.. I eventually just dropped Gentoo on it. What chipset, drive controller hard drive are you using on this system? http://www.freebsd.org/cgi/man.cgi?query=atasektion=4manpath=FreeBSD+5.3-RELEASE I´ll notised that my idecontroller IS supported by the ata-driver, witch makes it even stranger.. (I think I will check on my cabling once more, even if it´s a newly installed _rounded_ 32 pin cable..) My atacontroller: SiS 5513 My HDD: Seagate 200 GB T - Original Message - From: Mike Daemon [EMAIL PROTECTED] To: FreeBSD Questions freebsd-questions@freebsd.org Sent: Sunday, March 27, 2005 1:15 PM Subject: more problems with 5.3 and TIMEOUT - WRITE_DMA I got this annoying problem when upgradeing to 5.3, the miniinst iso blurps out TIMEOUT - WRITE_DMA when it starts writing base to my disk. And when I tried to first install 5.2.1 and upgrade (cvsup, make buildworld etc.. ) to 5.3 that way everything seems fine until I reboot to single-user-mode, as soon as Im starting to write anything to the disk it´s blurping out those errors.. I have diagnosticed my disk, checked my cabling and fixed my PSU (installed a brand new one). No difference. I noticed that my ide-controller was supported in 4.11, but not? in 5.3, is that realy true? seems very strange... Sence I duel boot with Wintendo/Lunix and don´t see this problem with those oses I´m very confused of what to do next.. I´ll tried some snapshots to but no luck... / Mike ps My dmesg goes in the attachment, in hope for a patch/solution to this problem. ds ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
