Date: Sun, 15 Nov 1998 21:39:25 -0800 From: Eric Hodel <hodeleri@seattleu.edu> To: "Kenneth D. Merry" <ken@plutotech.com> Cc: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Re: Adaptec SCSI messages Message-ID: <364FBA8D.DE31C778@seattleu.edu> References: <199811160525.WAA25664@panzer.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kenneth D. Merry" wrote: <snip> > > changing root device to da0s1a > > da0 at ahc0 bus 0 target 6 lun 0 > > da0: <QUANTUM VIKING II 4.5WLS 3506> Fixed Direct Access SCSI2 device > > da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled > > da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) > > Do you have this disk plugged into the Ultra2 port on the motherboard? If > it is an Ultra 2 device, it should probbe at 40MHz. (assuming you don't > have any non-Ultra2 peripherals on the Ultra 2 port) You probably do have the HDD plugged into the SE instead of the LVD connection, I have the same controller/drive setup and it reports 80.0MB/s <snip> > > It doens't seem to matter how long the scsi timeout is set in the kernel. > > The Quantum disk is an UltraWide2 type, and so is the onboard scsi controller > > (Asus P2BS mainboard.) > > > > Can I alter scsi driver or kernel parameters to get rid of this timeout delay? > Maybe it has something to do with the hd firmware like with some other Quantum disks. > > It may well be a firmware bug. I don't think tuning any kernel parameters > will fix it. You can set your kernel to have a shorter timeout delay. I can't recall the exact option, check the LINT kernel. On the boot floppy kernel its 15 seconds, and on the generic its 8 (I think) I adjusted it down to 4, and haven't had a problem. <snip> Eric Hodel hodeleri@seattleu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?364FBA8D.DE31C778>