Re: ATA problems(unlean fs) on recent cvsup
Just a follow up. I've since been able to get my -CURRENT system running under the new build. However the booting process is still slow around those ata?: [MPSAFE] messages. Any ideas on getting a speed up? -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems(unlean fs) on recent cvsup
It seems Alastair G. Hogge wrote: Just a follow up. I've since been able to get my -CURRENT system running under the new build. However the booting process is still slow around those ata?: [MPSAFE] messages. Any ideas on getting a speed up? I'm working on it... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems(unlean fs) on recent cvsup
Hi... Sorry to do a me too, but I have a similar problem after a cvsup midday on the 13th September. The previous kernel was pre-ATAng. The machine panic'd after inserting a friends wireless PCMCIA card (but that's probably another unrelated issue), rebooted and left me in single user after failing to automatically run fsck. Prior to that it had booted fine when the disks were clean. Unfortunately, I wasn't able to copy down the exact error messages it printed in the failed fsck_ufs. But they were definitely of the form CANNOT WRITE BLK: and the fsck then died with a SIGABRT. A manual fsck of the disks has got me back up and running and the machine now boots multiuser without fsck terminating abnormally, but still seems unable to resolve the inconsistencies on-disk. http://www.silent.co.uk/freebsd/ ... contains a dmesg and messages log of the failing background fsck if they are of any help. I will try to investigate further but please get in touch if there is more information I can provide. Cheers, Si On Sun, Sep 14, 2003 at 03:52:33PM +1000, Alastair G. Hogge wrote: Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: 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-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,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,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. 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_cpu1: 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 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 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 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 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 2.7 (no driver attached) ohci0: SiS 5571 USB controller mem 0xde00-0xde000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy
Re: ATA problems(unlean fs) on recent cvsup
I've seen that too, although my problem was with my Alcatel Speedtouch 330 which routinely panics the system. I'djust retrieved usr from a backup to get round it, and put it down to the perils of -current, but if there is really a problem, I can investigate further here. Mark Simon Brown wrote: Hi... Sorry to do a me too, but I have a similar problem after a cvsup midday on the 13th September. The previous kernel was pre-ATAng. The machine panic'd after inserting a friends wireless PCMCIA card (but that's probably another unrelated issue), rebooted and left me in single user after failing to automatically run fsck. Prior to that it had booted fine when the disks were clean. Unfortunately, I wasn't able to copy down the exact error messages it printed in the failed fsck_ufs. But they were definitely of the form CANNOT WRITE BLK: and the fsck then died with a SIGABRT. A manual fsck of the disks has got me back up and running and the machine now boots multiuser without fsck terminating abnormally, but still seems unable to resolve the inconsistencies on-disk. http://www.silent.co.uk/freebsd/ ... contains a dmesg and messages log of the failing background fsck if they are of any help. I will try to investigate further but please get in touch if there is more information I can provide. Cheers, Si On Sun, Sep 14, 2003 at 03:52:33PM +1000, Alastair G. Hogge wrote: Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: 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-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,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,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. 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_cpu1: 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 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 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 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq
ATA problems(unlean fs) on recent cvsup
Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: 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-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,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,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. 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_cpu1: 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 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 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 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 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 2.7 (no driver attached) ohci0: SiS 5571 USB controller mem 0xde00-0xde000fff irq 9 at device 3.0 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: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/2.42, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. ohci1: SiS 5571 USB controller mem 0xdd80-0xdd800fff irq 9 at device 3.1 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: 2 ports with 2 removable, self powered ohci2: SiS 5571 USB controller mem 0xdd00-0xdd000fff irq 9 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: SiS 5571 USB controller on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 3.3 (no driver attached) pci0: multimedia, audio at device 9.0 (no driver attached) pci0: input device at device 9.1 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0x8800-0x88ff
ATA problems on Promise controller
With a -current kernel ( cvsupped today ) I can no longer boot. It hangs on the drives connected to the promis controller built into my MSI KT266 mobo. The messages are like ad2: READ command timeout tag=0 serv=0 - resetting Same for ad3. It tries falling back to pio mode but after that it hangs completely. I have tried putting hw.at.tags=0 in /boot/loader.conf as suggested in some older messages on this list but that dit not help. dmesg of a working kernel built 19-1-2003 is attached 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.0-CURRENT #1: Sun Jan 19 15:50:33 MET 2003 [EMAIL PROTECTED]:/raid/bsd/obj/raid/bsd/freebsd/src/sys/trantor Preloaded elf kernel /boot/kernel.ok/kernel at 0xc04b1000. Preloaded elf module /boot/kernel.ok/acpi.ko at 0xc04b10ac. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 1405012013 Hz CPU: AMD Athlon(tm) XP 1600+ (1405.01-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 516407296 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: flags 0x7 npx0: INT 16 interface acpi0: AMIINT on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 10 entries at 0xc00f7d80 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 0x808-0x80b 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 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci0: display, VGA at device 6.0 (no driver attached) pci0: network, ethernet at device 7.0 (no driver attached) sym0: 810a port 0xd800-0xd8ff mem 0xdbfeff00-0xdbfe irq 10 at device 8.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking atapci0: Promise ATA100 controller port 0xc400-0xc43f,0xc800-0xc803,0xcc00-0xcc07,0xd000-0xd003,0xd400-0xd407 mem 0xdbfc-0xdbfd irq 11 at device 12.0 on pci0 ata2: at 0xd400 on atapci0 ata3: at 0xcc00 on atapci0 isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 atapci1: VIA 8233 ATA100 controller port 0xff00-0xff0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 10 at device 17.2 on pci0 usb0: VIA 83C572 USB controller 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 uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhci1: VIA 83C572 USB controller port 0xbc00-0xbc1f irq 10 at device 17.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 ugen0: Genesys Logic USB Host To Host Bridge, rev 1.00/1.80, addr 2 uhci2: VIA 83C572 USB controller port 0xc000-0xc01f irq 10 at device 17.4 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 acpi_button1: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 fdc0: cmd 3 failed at out byte 1 of 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: 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/9 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven port fdc0: cmd 3 failed at out byte 1 of 3 orm0: Option ROMs at iomem 0xd1000-0xd3fff,0xc9000-0xd0fff,0xc8000-0xc8fff,0xc-0xc7fff on isa0 fdc0: cannot reserve I/O port range (6 ports) sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. acpi_cpu: CPU throttling available, 16 steps from 100% to 6.2% ad0: 28629MB ST330621A [58168/16/63] at ata0-master UDMA100 ad1: 29312MB Maxtor 33073H3 [59556/16/63] at ata0-slave UDMA100 acd0: CD-RW PLEXTOR CD-R PX-W8432T at ata1-master PIO4 ar0: 78533MB ATA RAID0 array [10011/255/63] status: READY subdisks: 0 READY ad2: 39266MB IC35L040AVER07-0 [79780/16/63] at
Re: ATA problems on Promise controller
try hw.ata.ata_dma=0 in /boot/loader.conf to disable DMA, it is currently broken but worked on On Sat, 5 Apr 2003, Paul van der Zwan wrote: With a -current kernel ( cvsupped today ) I can no longer boot. It hangs on the drives connected to the promis controller built into my MSI KT266 mobo. The messages are like ad2: READ command timeout tag=0 serv=0 - resetting Same for ad3. It tries falling back to pio mode but after that it hangs completely. I have tried putting hw.at.tags=0 in /boot/loader.conf as suggested in some older messages on this list but that dit not help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems
It seems Dag-Erling Smorgrav wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: No tags, like you said. Previously, with a tags-capable kernel, enabling tags would cause a continuous stream of timeouts and resets on both disks. Just for kicks, I removed the #if 0 in ata-disk.c and got exactly the same symptoms as before: ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests That why it is disabled, its not working for the time being. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
Scotty [EMAIL PROTECTED] writes: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L disks) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
It seems Dag-Erling Smorgrav wrote: Scotty [EMAIL PROTECTED] writes: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L disks) Tags are disabled in -current in ata-disk.c so if the sources are up to date that cannot be the problem. Please update and then at least provide a dmesg if it still fails. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
Soeren Schmidt [EMAIL PROTECTED] writes: Tags are disabled in -current in ata-disk.c so if the sources are up to date that cannot be the problem. Please update and then at least provide a dmesg if it still fails. top-of-tree: [EMAIL PROTECTED] /home/des# egrep '(ata|ad)[0-9]' /var/run/dmesg.boot ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 9641MB IBM-DTTA-371010 [19590/16/63] at ata0-master UDMA33 ad1: 39266MB IC35L040AVER07-0 [79780/16/63] at ata1-master UDMA33 acd0: CD-RW HL-DT-ST GCE-8400B at ata0-slave WDMA2 No tags, like you said. Previously, with a tags-capable kernel, enabling tags would cause a continuous stream of timeouts and resets on both disks. I saw your commit disabling tags on 2003-02-23, but I didn't see any related discussion that would explain why they were disabled. [EMAIL PROTECTED] /home/des# atacontrol cap 0 0 ATA channel 0, Master, device ad0: ATA/ATAPI revision4 device model IBM-DTTA-371010 serial number WN0WKFW1158 firmware revision T77OA73A cylinders 16383 heads 16 sectors/track 63 lba supported 19746720 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued yes yes 31/1F SMART yes no microcode download no no security yes no power management yes yes advanced power management no no 0/00 automatic acoustic management no no 0/000/00 [EMAIL PROTECTED] /home/des# atacontrol cap 1 0 ATA channel 1, Master, device ad1: ATA/ATAPI revision5 device model IC35L040AVER07-0 serial number SX0SXM75217 firmware revision ER4OA44A cylinders 16383 heads 16 sectors/track 63 lba supported 80418240 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued yes yes 31/1F SMART yes no microcode download no no security yes no power management yes yes advanced power management yes no 0/00 automatic acoustic management yes no 254/FE 128/80 DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: No tags, like you said. Previously, with a tags-capable kernel, enabling tags would cause a continuous stream of timeouts and resets on both disks. Just for kicks, I removed the #if 0 in ata-disk.c and got exactly the same symptoms as before: ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad0: 9641MB IBM-DTTA-371010 [19590/16/63] at ata0-master tagged UDMA33 ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad1: 39266MB IC35L040AVER07-0 [79780/16/63] at ata1-master tagged UDMA33 acd0: CD-RW HL-DT-ST GCE-8400B at ata0-slave WDMA2 ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ad0: trying fallback to PIO mode ata0: resetting devices .. ad0: invalidating queued requests done ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad1: no request for tag=0 ad1: invalidating queued requests ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ad1: trying fallback to PIO mode ata1: resetting devices .. ad1: invalidating queued requests done it never even got to mounting root, I grew tired of waiting and coldbooted it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
Soeren Schmidt [EMAIL PROTECTED] writes: It seems Dag-Erling Smorgrav wrote: ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests That why it is disabled, its not working for the time being. For me, the time being == since it was introduced in the tree. It has never worked for me, ever. That's the point I was trying to make. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
On Tue, Mar 04, 2003 at 04:59:33PM +0100, Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: Soeren Schmidt [EMAIL PROTECTED] writes: It seems Dag-Erling Smorgrav wrote: ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests That why it is disabled, its not working for the time being. For me, the time being == since it was introduced in the tree. It has never worked for me, ever. That's the point I was trying to make. It's probably dependent of your ATA controller. You have the infamous P5A board with ALi chipset, it has timekeeping problems also if I remember. I've used DTLA and DPTA disk behind PIIX4 controller and have had zero problems after the initial development did settle. -- Vallo Kallaste To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
I am getting the same ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. error messages, and disk io pauses when it resets the devices for around 3 seconds (estimated from mpg123 pause in play), a brief description of my system until i reboot and submit a verbose dmesg later tonight: Abit BP6 with 2 processors, Highpoint366 in dma mode, Western digital 80 gig running -current from mid february sources I am very willing to test patches to solve this problem - Scott MacPhee To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA problems
This morning I booted a kernel built last night, and it panicked when trying to mount the root filesystem after this: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ad0: removed from configuration done cvsup'd, built a new kernel, and now instead of a panic I get (with some extra stuff): atapci0: AcerLabs Aladdin UDMA66 controller port 0xeff0-0xefff at device 4.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed ad0: 28615MB TOSHIBA MK3017GAP [58140/16/63] at ata0-master UDMA66 acd0: CD-RW UJDA720 DVD/CDRW at ata1-master PIO4 ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done Mounting root from ufs:/dev/ad0s2a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot ufs:ad0s2a Mounting root from ufs:ad0s2a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 :( -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA problems
It seems Wesley Morgan wrote: This morning I booted a kernel built last night, and it panicked when trying to mount the root filesystem after this: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ad0: removed from configuration done cvsup'd, built a new kernel, and now instead of a panic I get (with some extra stuff): Disable DMA for now, I'm working on a fix for this problem.. Are you willing to test patches to solve this problem ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
still ATA problems with promise tx2
hello, i couldnt decide from reading the list if there should or shouldnt be problems with promise ata/100 controller with current. anyway, i have problems with it. i've tried several current versions from the devel snapshot to apr 22nd and all of those fail after installation. in the floppy boot all looks ok, and it installs fine, but when i boot up after the installation it panics every time, looks like at the time the machine is probing for the controller. any ideas? i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) this is a single disk on that controller. no errors during the installation. [this is an attempt to make a fresh installation, all my other current machines are too old to be helpfull] mickey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: still ATA problems with promise tx2
It seems mika ruohotie wrote: hello, i couldnt decide from reading the list if there should or shouldnt be problems with promise ata/100 controller with current. I dont think so... anyway, i have problems with it. i've tried several current versions from the devel snapshot to apr 22nd and all of those fail after installation. in the floppy boot all looks ok, and it installs fine, but when i boot up after the installation it panics every time, looks like at the time the machine is probing for the controller. any ideas? i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) That would be most helpfull, where does it panic, what is the panic message ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: still ATA problems with promise tx2
On Wed, Apr 24, 2002 at 02:17:27PM +0200, Søren Schmidt wrote: It seems mika ruohotie wrote: i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) That would be most helpfull, where does it panic, what is the panic message ? panic: bad ivar read request (4) Debugger(panic) Stopped at Debugger+0x40: xorl%eax,%eax db trace Debugger(c03c241c) at Debugger+0x40 panic(c057a399,4,d7bdf070,ce4e0c00,d7c2ce00) at panic+0x70 acpi_read_ivar(ce4e0c00,d7c2bc80,4,c05aebb8) at acpi_read_ivar+0x9b ata_pci_match(d7c2ce00) at ata_pci_match+0x918 ata_pci_probe(d7c2ce00,d7c2ce00,d7c2e780,d7c2ce00,0) at ata_pci_probe+0xd device_probe_child(d7c2e780,d7c2ce00,d7c2ce00,d7c2bc80,d7c2e780) at device_probe_child+0xca device_probe_and_attach(d7c2ce00) at device_peobe_and_attach+0x41 bus_generic_attach(d7c2e780,d7c2e780,d6928280,ce4e0c00,1) at bus_generic_attach+0x16 device_probe_and_attach(d7c2e780) at device_probe_and_attach+0x9a bus_generic_attach(d7c2bc80,d7bd5090,ce4e0c00,d7c2bc80,c05aec90) at bus_generic_attach+0x16 acpi_pcib_attach(d7c2bc80,d7c2bc80,ce4e0c00,ce4e0c00,0) at acpi_pcib_attach+0x1d7 device_probe_and_attach(d7c2bc80) at device_probe_and_attach+0x9a bus_generic_attach(ce4e0c00,ce4e0ba0,ce4e0b80,ce4b23e0,c05aecf8) at bus_generic_attach+0x16 i hope that's enough, had to type that by hand... =) -Søren mickey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ata problems (was: Re: ld-elf.so.1 broken with world from yesterday)
On 8 Apr, David O'Brien wrote: yesterday I've made a new world. After booting it, ld-elf-so.1 complains about every library (libc, libutil, ...). My -current is not usable anymore because of this. Defined complains. freebsd-current readers should know to spend EXACT error messages. Something about a missing or wrong ELF header. I thought it was a general problem so everyone would see it, but it turned out to be a problem in the ata driver. After turning off tagged queuing everything was fine. I'm not the only one with problems with tagged queuing. Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel too, but a Apr 6-8 kernel spills alot of tag related errors (I think you already have those errors from someone else, no need to repeat them here) and goes into PIO mode after some time. Turning of tagged queuing works. Bye, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ata problems (was: Re: ld-elf.so.1 broken with world from yesterday)
It seems Alexander Leidinger wrote: Something about a missing or wrong ELF header. I thought it was a general problem so everyone would see it, but it turned out to be a problem in the ata driver. After turning off tagged queuing everything was fine. I'm not the only one with problems with tagged queuing. Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel too, but a Apr 6-8 kernel spills alot of tag related errors (I think you already have those errors from someone else, no need to repeat them here) and goes into PIO mode after some time. Turning of tagged queuing works. Yes, I'm aware of some having problems with tags, but I cant seem to reproduce the problem here no matter what I try... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ata problems (was: Re: ld-elf.so.1 broken with world from yesterday)
On 9 Apr, Søren Schmidt wrote: Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel too, but a Apr 6-8 kernel spills alot of tag related errors (I think you already have those errors from someone else, no need to repeat them here) and goes into PIO mode after some time. Turning of tagged queuing works. Yes, I'm aware of some having problems with tags, but I cant seem to reproduce the problem here no matter what I try... I first had problems to reproduce it too, but yesterday I got hit by it. Do you want my complete system configuration (kernel config, dmesg) to perhaps try to reproduce it with a specific -current (cvs ... -D 200204080900) in your lab? Bye, Alexander. -- Intel: where Quality is job number 0.9998782345! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ata problems (was: Re: ld-elf.so.1 broken with world from yesterday)
It seems Alexander Leidinger wrote: On 9 Apr, Søren Schmidt wrote: Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel too, but a Apr 6-8 kernel spills alot of tag related errors (I think you already have those errors from someone else, no need to repeat them here) and goes into PIO mode after some time. Turning of tagged queuing works. Yes, I'm aware of some having problems with tags, but I cant seem to reproduce the problem here no matter what I try... I first had problems to reproduce it too, but yesterday I got hit by it. Do you want my complete system configuration (kernel config, dmesg) to perhaps try to reproduce it with a specific -current (cvs ... -D 200204080900) in your lab? Sure, anything that can get me to get my hands on the problem.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ata problems, nevermind
Wierd, I turned the computer off and turned it back on again and the problem is solved... sorry bout that. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
Maybe this is a silly suggestion, but could someone with a card like that boot it in a Windows environment and tell us what that hardware manager tells us about hardware requirements the card would have if it is configured for the '0x160' address (whatever that configuration is on the card I don't know)? Nick A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in the HSCX or ISAC: the ASIC on the card has 'folded' the address space so that the fifo appears at an address 3 bytes after the last register (0x3e with the current scheme - see tels0163_read_fifo()). Oh yes, you are right! I was (and am still a bit) confused. So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX and at least three bytes at its base address, right ? This makes sense. Now the real question left is are this the only locations where the card is driving the bus ? hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. This is a bug in the isic driver. I'm sure it doesn't use every port in that range so it needs to split the range in to two or more pieces and only allocate ports which it actually needs. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
Jose Gabriel Marcelino wrote: This obviously conflicts with the secondary IDE controller which lies at 0x170, however this has not been a problem till this day and no driver complained about this. Now, with the newer kernel I get this: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. This type of error with the 2nd IDE controller was reported also by other people, mostly the reports were "working sometimes". First of all, Teles refuses to give out any docs about their hardware, so it might be that not all addresses are used but this is 100% speculation. What you are recognizing is the real nice thing about newbus: you can't allocate a resource twice. I admit, this might be a bit cumbersome in the single case but it saves us from the "working sometimes" and "working sometimes not" and "sometimes, very seldom and unreproducible" error reports in the general case. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
Doug Rabson wrote: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. This is a bug in the isic driver. I'm sure it doesn't use every port in that range so it needs to split the range in to two or more pieces and only allocate ports which it actually needs. How do you come to that conclusion ? A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. The card in question allocates 3 portranges for this uses with each 0x40 bytes in length. In case there is is already an IDE controller allocated at 0x170 and a Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. So where is the bug ? This all looks perfectly reasonable to me with the exception that we could start argueing about whether it would be reasonable to split the allocation ranges for the ISAC and to save (if at all possible, there are some more registers at the end of the HSCX on the card) some bytes in the HSCX case. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: Doug Rabson wrote: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. This is a bug in the isic driver. I'm sure it doesn't use every port in that range so it needs to split the range in to two or more pieces and only allocate ports which it actually needs. How do you come to that conclusion ? A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. The card in question allocates 3 portranges for this uses with each 0x40 bytes in length. In case there is is already an IDE controller allocated at 0x170 and a Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. So where is the bug ? This all looks perfectly reasonable to me with the exception that we could start argueing about whether it would be reasonable to split the allocation ranges for the ISAC and to save (if at all possible, there are some more registers at the end of the HSCX on the card) some bytes in the HSCX case. So you are saying that what we really have here is a simple i/o conflict and possibly the ISDN card can be reconfigured to use a non-conflicting address? If so, then everything is working correctly and the resource manager has pointed a possible hardware problem :-). -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
From the keyboard of Martin Husemann: In case there is is already an IDE controller allocated at 0x170 and a Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. This is a PnP card, right? No. hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote: Jose, the problem seems to be resolved by rebuilding the boot loader. Or bypass the loader altogether. cd /usr/src/sys/boot make obj make all install and you'll be able to boot the kernel with the latest ata stuff. Do you use KLMs? When I load the kernel alone, it detects the ATA devices normally. When I let the loader load a module in addition to the kernel (I tried it with each of vinum, netgraph, linux, splash_bmp and joy), it fails with these messages: ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed (The primary slave is a CDROM.) This was with linux.ko; with joy.ko, the line "WARNING:..." wasn't printed. (BTW, with kernel+umap.ko, the ATA detection succeeded.) Every access to an ATA device then fails like this: # fdisk ad0 fdisk: cannot open disk /dev/rad0: Device not configured # ls -l *ad0 crw-r- 1 root operator 116, 0x00010002 Feb 19 17:03 ad0 crw-r- 1 root operator 116, 0x00010002 Feb 19 17:03 rad0 This is with an updated /boot/loader and the "lun=2" patch applied. Bye, Philipp P.S.: Here's a diff between a successful and an unsuccessful verbose boot: ~%diff -1000 -u /var/tmp/dmesgv_ok /var/tmp/dmesgv_fail --- /var/tmp/dmesgv_ok Sat Feb 19 18:55:55 2000 +++ /var/tmp/dmesgv_failSat Feb 19 19:51:41 2000 @@ -1,247 +1,205 @@ Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #145: Sat Feb 19 18:13:37 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/I609 -Calibrating clock(s) ... TSC clock: 233862696 Hz, i8254 clock: 1193178 Hz +Calibrating clock(s) ... TSC clock: 233862171 Hz, i8254 clock: 1193176 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method -Timecounter "TSC" frequency 233864747 Hz -CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) +Timecounter "TSC" frequency 233865033 Hz +CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 96M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 100663296 (98304K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) -0x0033f000 - 0x05ff5fff, 97218560 bytes (23735 pages) -avail memory = 94158848 (91952K bytes) +0x00353000 - 0x05ff5fff, 97136640 bytes (23715 pages) +avail memory = 94076928 (91872K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f9a20 bios32: Entry = 0xf04e0 (c00f04e0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x510 pnpbios: Found PnP BIOS data at 0xc00fcf10 pnpbios: Entry = f:cf40 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: -Preloaded elf kernel "kernel" at 0xc0326000. +Preloaded elf kernel "kernel" at 0xc033a000. +Preloaded elf module "linux.ko" at 0xc033a09c. module_register_init: MOD_LOAD (vesa, c0240a78, 0) error 6 md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71008086) npx0: math processor on motherboard npx0: INT 16 interface -i586_bzero() bandwidth = 43677658 bytes/sec -bzero() bandwidth = 46259888 bytes/sec +i586_bzero() bandwidth = 43664308 bytes/sec +bzero() bandwidth = 46249190 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71008086) pcib0: Host to PCI bridge on motherboard found-vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found-vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base e000, size 4 found-vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=255 map[20]: type 1, range 32, base d800, size 5 found-vendor=0x8086, dev=0x7113,
Re: Big ATA problems
It seems Bryan Liesner wrote: On Sat, 19 Feb 2000, Soren Schmidt wrote: Have you rebuild your modules lately ?? -Søren Yes. My world is current as of a few hours ago. I did a make world right after finding out about the loader problem to rule that possibility out. The disk probes still fail when loading today's modules with the loader. Wierd, I'll try to investigate that here... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
Hi again, After remaking the loader (unnecessary since it's still broken), I've removed my KLDs from loader.conf (I was loading a splash screen) and it now boots as Bryan noticed. However it seems another problem showed up, and I'm not sure where the problem is. I have a Teles ISDN card on this machine which was working very well before this change using it's factory default IO configuration which places it at 0xd80. It's driver however due to some hardware "features" unknown to me says the following: ata-pci0: VIA 82C586 ATA-33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... isic0 at port 0xd80,0x960-0x99f,0x160-0x19f,0x560-0x59f irq 10 flags 0x3 on isa0 isic0: Teles S0/16.3 This obviously conflicts with the secondary IDE controller which lies at 0x170, however this has not been a problem till this day and no driver complained about this. Now, with the newer kernel I get this: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. Thanks again. Regards, Gabriel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, 19 Feb 2000, Philipp Mergenthaler wrote: On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote: Jose, the problem seems to be resolved by rebuilding the boot loader. Or bypass the loader altogether. cd /usr/src/sys/boot make obj make all install and you'll be able to boot the kernel with the latest ata stuff. Do you use KLMs? Yes, I do! I was loading a screen saver with the boot loader. And now I see I am wrong about rebuilding the loader! When I had success loading the kernel directly, I moved loading the screensaver into rc.conf instead. Then I thought that something may be wrong with the loader, rebuilt it, and booted successfully. I broke the rule - never change more than one thing at a time :) I put the screen saver back in loader.conf and the boot failed again, so it is a loader/kernel issue, but I didn't have to rebuild loader. -Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
It seems Bryan Liesner wrote: Do you use KLMs? Yes, I do! I was loading a screen saver with the boot loader. And now I see I am wrong about rebuilding the loader! When I had success loading the kernel directly, I moved loading the screensaver into rc.conf instead. Then I thought that something may be wrong with the loader, rebuilt it, and booted successfully. I broke the rule - never change more than one thing at a time :) I put the screen saver back in loader.conf and the boot failed again, so it is a loader/kernel issue, but I didn't have to rebuild loader. Have you rebuild your modules lately ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, 19 Feb 2000, Soren Schmidt wrote: Have you rebuild your modules lately ?? -Søren Yes. My world is current as of a few hours ago. I did a make world right after finding out about the loader problem to rule that possibility out. The disk probes still fail when loading today's modules with the loader. -Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, 19 Feb 2000, Soren Schmidt wrote: It seems Bryan Liesner wrote: The latest ata commits left my system completely unbootable. No disks were probed. He, you always seem to be lucky when I change something :) I always hold my breath when I cvsup and see changes to ata*:) Hmm, yes you have one of those motherboards that screw the order of the controllers, it is an ASUS aliddin right ?? It's a PCChips motherboard... You could try to not use the ATA_STATIC_ID option, that way your disks should be numbered 0 and 1 and at least make it boot... Never used that option before. -Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
It seems Bryan Liesner wrote: On Sat, 19 Feb 2000, Soren Schmidt wrote: It seems Bryan Liesner wrote: The latest ata commits left my system completely unbootable. No disks were probed. He, you always seem to be lucky when I change something :) I always hold my breath when I cvsup and see changes to ata*:) Hmm, yes you have one of those motherboards that screw the order of the controllers, it is an ASUS aliddin right ?? For those that has this problem, this patch should do the trick: Index: ata-all.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.48 diff -u -r1.48 ata-all.c --- ata-all.c 2000/02/18 20:57:27 1.48 +++ ata-all.c 2000/02/19 13:58:58 @@ -336,7 +336,7 @@ if (pci_get_progif(dev) PCIP_STORAGE_IDE_MASTERDEV) lun = unit; else - lun = -1; + lun = 2; if (!(child = device_add_child(dev, "ata", lun))) return ENOMEM; -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
hi Soren, The latest ata commits left me unbootable too, the patch you provided below didn't help this too. I have a very different configuration from Bryan's (much simpler too): - DFI K6XV3+ mb with VIA MVP3 chipset ata-pci0: VIA 82C586 ATA-33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: 14664MB IBM-DJNA-351520 [31781/15/63] at ata0-master using UDMA33 ad1: 4103MB ST34321A [8894/15/63] at ata0-slave using UDMA33 acd0: DVD-ROM TOSHIBA DVD-ROM SD-M1212 at ata1-master using UDMA33 afd0: 96MB IOMEGA ZIP 100 ATAPI [96/64/32] at ata1-slave using PIO0 With the latest kernel I get this relevant messages: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed nodevsw (majdev=0 bootdev=0xa020) Mouting root from ufs:/dev/wd0s1a no such device 'wd' Thinking that the wd device was gone I tried using /dev/ad0s1a, but it was the same: no such device 'ad' Thanks, Gabriel The latest ata commits left my system completely unbootable. No disks were probed. Index: ata-all.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.48 diff -u -r1.48 ata-all.c --- ata-all.c 2000/02/18 20:57:27 1.48 +++ ata-all.c 2000/02/19 13:58:58 @@ -336,7 +336,7 @@ if (pci_get_progif(dev) PCIP_STORAGE_IDE_MASTERDEV) lun = unit; else - lun = -1; + lun = 2; if (!(child = device_add_child(dev, "ata", lun))) return ENOMEM; -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
It seems Jose Gabriel Marcelino wrote: Well, rebuild the loader, that helped Bryan, apparently it has nothing to do with the ata driver The latest ata commits left me unbootable too, the patch you provided below didn't help this too. I have a very different configuration from Bryan's (much simpler too): - DFI K6XV3+ mb with VIA MVP3 chipset ata-pci0: VIA 82C586 ATA-33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: 14664MB IBM-DJNA-351520 [31781/15/63] at ata0-master using UDMA33 ad1: 4103MB ST34321A [8894/15/63] at ata0-slave using UDMA33 acd0: DVD-ROM TOSHIBA DVD-ROM SD-M1212 at ata1-master using UDMA33 afd0: 96MB IOMEGA ZIP 100 ATAPI [96/64/32] at ata1-slave using PIO0 -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Big ATA problems
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote: hi Soren, The latest ata commits left me unbootable too, the patch you provided below didn't help this too. I have a very different configuration from Bryan's (much simpler too): Jose, the problem seems to be resolved by rebuilding the boot loader. Or bypass the loader altogether. cd /usr/src/sys/boot make obj make all install and you'll be able to boot the kernel with the latest ata stuff. Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Big ATA problems
The latest ata commits left my system completely unbootable. No disks were probed. I have on the motherboard's Alladin controller: HP 4x4x24 CD burner as master primary channel 40x CD as slave primary channel HP Colorado 8 Gig ATAPI tape as master secondary channel On a Promise Ultra66: WDC AC29100D WDC AC32500H each on thier own channel. Here are the boot messages (I had to write them down) ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: timeout waiting for intr ata0-slave: identify failed these were repeated once and when attempting to mount / no devsw(msgdev=0 bootdev=0xa20) no such device 'ad' Prior the the commit, the motherboard ide controllers were numbered ata0,1 and the Promise was ata2,3. After the commit it is switched around. Now the controllers probe as Promise ata0,1 and the motherboard as ata2,3. Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Still ATA problems
I am still having problems with the ATA driver. I am seeing the same error messages as has been reported on the lists during the last few weeks, both on i386 and alpha platforms. On the i386, the problem is just an irritating itch, but it seems to be far more serious on the alpha, where the system reboots instantly when the problems occur. On reboot, the system stops at the probing of disks, reporting a timeout. Then, the system reboots again, probing and rebooting in an endless loop. I have the latest sources, as cvsupped today, October 6th. I can provide more information on the system configuration if needed, but I have no access to it right now. ===++=== Erik H. Bakke || To be or not to be... Senior Consultant/Developer|[EMAIL PROTECTED]|Is simply a question of Habatech AS|| binary logic ===++== To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Still ATA problems
It seems Erik H. Bakke wrote: I am still having problems with the ATA driver. I am seeing the same error messages as has been reported on the lists during the last few weeks, both on i386 and alpha platforms. On the i386, the problem is just an irritating itch, but it seems to be far more serious on the alpha, where the system reboots instantly when the problems occur. On reboot, the system stops at the probing of disks, reporting a timeout. Then, the system reboots again, probing and rebooting in an endless loop. I have the latest sources, as cvsupped today, October 6th. I can provide more information on the system configuration if needed, but I have no access to it right now. I have a new version almost ready that should fix this problem, including the panic on the alpha. It just a bit more testing then I'll commit it... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
