atom feed20 messages in org.freebsd.freebsd-stableRe: Continuing ahc problems - also ca...
FromSent OnAttachments
Martin KraemerJul 20, 2001 1:50 am 
Matt DillonJul 25, 2001 10:11 am 
Martin KraemerJul 27, 2001 9:51 am 
Brandon D. ValentineJul 27, 2001 10:24 am 
Justin T. GibbsJul 27, 2001 11:58 am 
Martin KraemerJul 30, 2001 1:27 am 
Martin KraemerJul 30, 2001 5:30 am 
Justin T. GibbsJul 30, 2001 7:21 am 
Martin KraemerJul 30, 2001 8:33 am.dmesg, .pciconf, .messages
Martin KraemerJul 30, 2001 8:52 am 
Matt DillonJul 30, 2001 9:46 am 
Chad R. LarsonJul 30, 2001 9:59 am 
Cy Schubert - ITSD Open Systems GroupJul 30, 2001 11:10 am 
Martin KraemerJul 30, 2001 1:28 pm 
Mike HardingJul 30, 2001 9:14 pm 
Martin KraemerJul 30, 2001 11:44 pm 
Michael Sperber [Mr. Preprocessor]Jul 31, 2001 5:00 am.dmesg
Arno J. KlaassenJul 31, 2001 9:48 am 
Justin T. GibbsJul 31, 2001 1:00 pm 
Michael Sperber [Mr. Preprocessor]Aug 2, 2001 9:57 am 
Subject:Re: Continuing ahc problems - also cause fxp failure
From:Martin Kraemer (Mart@Fujitsu-Siemens.com)
Date:Jul 27, 2001 9:51:43 am
List:org.freebsd.freebsd-stable

On Wed, Jul 25, 2001 at 10:12:12AM -0700, Matt Dillon wrote:

Hmm. Well, that last conversation seemed to come to a concensus that a known thermal problem with a chip on my DELL motherboard related to heavy use of the on-board adaptec and on-board ethernet might have been the cause. I replaced the motherboard and moved away from the on-board ethernet (threw in another PCI card), and the problem went away.

I don't know if your problem below is the same problem or a different problem. It sounds like it may be a different problem.

IMO it is quite different, as I changed the following parameters:

* opened the PC to allow free air circulation (*iff* that does anything)

* replaced the on-board 7880UW controller by a PCI AHA-2940UW card. While both offer the same functionality, and are made by the same manufacturer, they also share the same timeout problems.

In my first mail I said I had seen 4.2-STABLE work and 4.3-STABLE fail, but that was not true: the old system was 4.2-RELEASE, and I noticed the error for the first time with 4.3-RELEASE).

So I upgraded to 4.3-STABLE afterwards, no change. So I got the cvs source tree of dev/aic7xxx/ to see the differences between 4.2-RELEASE and 4.3-RELEASE. But the gratest change seems to be in the sequencer code, about which I don't understand very much... In the source file aic7xxx_freebsd.c (that's where the ahc_timeout() prints the messages) I see that only little changed since 4.2-RELEASE: a detach routine was added, but IMO it is only invoked then the device is released completely. In aic7xxx.c, a LOT has changed.

Can the changes in the sequencer code be the reason for the still re-occurring "lost interrupts" on higher load -- or what else can be causing the timeout?

Or can the presence of a second (non-wide) 2940 which is used for my DAT cause any problems of this kind?

Puzzled,

Martin

On-board 7880: ahc0: <Adaptec aic7880 Ultra SCSI adapter> port 0xf800-0xf8ff mem
0xfedfb000-0xf edfbfff irq 9 at device 6.0 on pci0 ahc0: Using left over BIOS settings aic7880: Wide Channel A, SCSI Id=15, 16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: <IBM DDYS-T18350N S92A> Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 64H 32S/T 17501C) Mounting root from ufs:/dev/da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: <WDIGTL WDE9100 1.30> Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da1: 8683MB (17783204 512 byte sectors: 64H 32S/T 8683C)

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message