Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Jan 2005 04:58:31 +0000
From:      Jason Henson <jason@ec.rr.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: 5.3 interrupt storm (atapicam) and I/O error
Message-ID:  <1107061111l.6754l.0l@BARTON>
In-Reply-To: <41FA4046.40003@daniel.stefan.haischt.name> (from me@stefan.haischt.name on Fri Jan 28 08:38:14 2005)
References:  <20050128061002.2C2EC12D2D@mprdmxin.myway.com> <200501281005.30884.olivier.certner@free.fr> <41FA4011.7070301@daniel.stefan.haischt.name> <41FA4046.40003@daniel.stefan.haischt.name>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/28/05 08:38:14, Daniel S. Haischt wrote:
> oops, did forget the tixt file ...
>=20
> Daniel S. Haischt schrieb:
>> I don't know whether this is related to your issue,
>> but on one of my boxes I am also getting an interrupt
>> storm with atapicam enabled.
>>=20
>> On FreeBSD 5.2.1 I did not experience any interrupt
>> storm issues, even if using the same hardware configuration.
>>=20
>> Have a look at the attached text file for a detailed
>> description ...
>>=20
>> Olivier Certner schrieb:
>>=20
>>>  Hi,
>>>=20
>>>  Could you give a look at my post dated 04/01/2005 entitled "Freeze =20
>>> with CAM (using KsCD)"? Maybe we have fallen on the same kind of =20
>>> bug concerning atapicam.
>>>=20
>>>  If you have KDE, maybe you should try to reproduce the problem I =20
>>> had. I've no time to test your scenario (the one with the EIDE =20
>>> drive, I don't have SCSI) now, but I'll try to reproduce it at the =20
>>> beginning of next week, in order to see if the freeze happens also =20
>>> on my computer.
>>>=20
>>>  Hope this will help us to progress on our issues.
>>>=20
>>>  Regards,
>>>=20
>>>   Olivier
>>> _______________________________________________
>>> freebsd-questions@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to "freebsd-questions-=20
>>> unsubscribe@freebsd.org"
>>=20
>>
>=20
>--=20
> Mit freundlichen Gruessen / With kind regards
> DAn.I.El S. Haischt
>=20
> Want a complete signature??? Type at a shell prompt:
> $ > finger -l haischt@daniel.stefan.haischt.name
>

> Hello,
>=20
> recently I updated one of my FreeBSD boxes to
> v 5.3. This box got a builtin Promise PDC20269
> UDMA133 controller. Actually it's a controller
> with two IDE channels.
>=20
> So far if using the GENERIC kernel that comes
> with FreeBSD, I do not experience any problems.
>=20
> If using my own customized kernel I am getting
> the following error message while booting the
> system:
>=20
> ----8<--------8<--------8<-------8<-----8<-----
> Interrupt storm detected on "irq10: atapci1";
> throtteling interrupt source:
> ---->8-------->8-------->8------->8----->8-----
>=20
> After some trail-and-error based investigations,
> I did figure out that if I don't plugin any device
> into IDE channel two, the just described error
> does not occur.
>=20
> So it has something to do with IDE channel two.
>=20
> As an additional note - The controller works
> under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD
> 5.2.1 (custom kernel).
>=20
> Any hints on how to solve this issue would be
> greatly appreciated.


How about a copy of your custom changes to the kernel?  Also did you =20
get a response from S=F8ren Schmidt <sos@DeepCore.dk>, he wrote and =20
maintains the ata stuff iirc.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1107061111l.6754l.0l>