Re: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!]

1999-12-12 Thread Vallo Kallaste

On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White [EMAIL PROTECTED] wrote:

  I'm getting the "lost disk contact" messages every now and then, but
  only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
  an PPro machine with Intel mobo. Can it be related to newer IBM disks?
 
 Depends on what 'now and then' is.  The Deskstar series of drives was not
 intended to run 24/7, and therefore shut themselves down every week to
 clean the heads.  

Mhm, now I remember the discussion in -current list some time ago. It
can be, yes, but I need to follow the logs to say for sure. About month
ago the messages appeared several times per day, not per week.
Thank you refreshing my memory :-)
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!]

1999-12-12 Thread Soren Schmidt

It seems Vallo Kallaste wrote:
 On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White [EMAIL PROTECTED] 
wrote:
 
   I'm getting the "lost disk contact" messages every now and then, but
   only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
   an PPro machine with Intel mobo. Can it be related to newer IBM disks?
  
  Depends on what 'now and then' is.  The Deskstar series of drives was not
  intended to run 24/7, and therefore shut themselves down every week to
  clean the heads.  
 
 Mhm, now I remember the discussion in -current list some time ago. It
 can be, yes, but I need to follow the logs to say for sure. About month
 ago the messages appeared several times per day, not per week.
 Thank you refreshing my memory :-)

Well, I use alot of IBM's and I've newer seen them do this...
Have you tried upping the timeout in ata-disk.c about line 426 to 
say 10s and see if it changes behavior ??

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!]

1999-12-11 Thread Vallo Kallaste

On Fri, Dec 10, 1999 at 09:31:57PM +0100, Soren Schmidt [EMAIL PROTECTED] wrote:

  I've connected the disk back to the UDM33 controller and it works
  fine. Now I get the message twice a day:
  
  ata0-master: ad_timeout: lost disk contact - resetting
  ata0: resetting devices .. done
  
  I've applied the patches until 4133 and will try to reconnect 
  the disk to the UDMA66 controller.
  
  Am I missing something about UDMA33/UDMA66 or specifically about
  the HighPoint controller ?
 
 Hmm, I have one in my development machine, so it takes a fair bit
 of beating, I haven't seen any of these problems. Could you mail
 me a dmesg, preferably from a verbose boot.

I'm getting the "lost disk contact" messages every now and then, but
only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
an PPro machine with Intel mobo. Can it be related to newer IBM disks?


Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Thu Nov 25 13:23:02 EET 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/Muzz
Timecounter "i8254"  frequency 1193200 Hz
Timecounter "TSC"  frequency 166195509 Hz
CPU: Pentium Pro (166.20-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x612  Stepping = 2
  Features=0xf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV
real memory  = 33554432 (32768K bytes)
avail memory = 29683712 (28988K bytes)
Preloaded elf kernel "kernel" at 0xc02bf000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02bf09c.
module_register_init: MOD_LOAD (vesa, c02194a4, 0) error 6
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX3 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
xl0: 3Com 3c905-TX Fast Etherlink XL irq 10 at device 11.0 on pci0
xl0: Ethernet address: 00:60:08:05:58:14
miibus0: MII bus on xl0
nsphy0: DP83840 10/100 media interface on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vga-pci0: ATI model 4755 graphics accelerator at device 17.0 on pci0
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 8 virtual consoles, flags=0x200
fdc0: direction bit not set
fdc0: cmd 3 failed at out byte 1 of 3
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0 at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0: PLIP network interface on ppbus 0
lpt0: generic printer on ppbus 0
lpt0: Interrupt-driven port
ppi0: generic parallel i/o on ppbus 0
gusc0: Gravis UltraSound Plug  Play PCM at port 0x220-0x22f,0x320-0x327,0x32c-0x32f 
irq 11 drq 5,7 on isa0
pcm0: GUS CS4231 on gusc0
unknown0: Disabled Device on isa0
unknown1: Disabled Device on isa0
unknown2: Disabled Device on isa0
unknown3: Disabled Device on isa0
ad0: IBM-DPTA-353750/P51OA30A ATA-4 disk at ata0 as master
ad0: 35772MB (73261440 sectors), 7144 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 31 depth queue, DMA
acd0: 685A/8.4D CDROM drive at ata1 as master
acd0: read 1171KB/s (1171KB/s), 120KB buffer, PIO
acd0: supported read types:
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
Mounting root from ufs:/dev/wd0s1a
WARNING: / was not properly dismounted
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 120 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 180 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 240 bytes
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 300 bytes
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message