Re: 5.3 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
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. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
oops, did forget the tixt file ... 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. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, 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. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- 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. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, My problem might be slightly different than yours. My system hangs during the boot process whenever I boot a kernel with atapicam enabled. A can't do anything but reboot the box at that point. Maybe this is a good time to learn to use the kernel debugger. When I get home this evening I'll try a few more things. This problem didn't happen in 5.2.1. Thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner < [EMAIL PROTECTED] > wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, Not sure what to think about this yet but it definitely has something to do with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel will boot with atapicam enabled. I don't seem to be able to use my motherboard's embedded EIDE controller with the Promise adapter installed. I don't see any obvious I/O or interrupt conflicts, but I also don't have too much control over it with this old SuperMicro mainboard. Seems odd to me though, since this all worked on 5.2.1. Open for suggestions, but for now I'm going to try to track down the SCSI I/O error problem so I can get some CD burning done (critical system backups) and then I'll see if I can try to figure out if this is an EIDE driver issue or a atapicam issue. If anyone comes up with anything in the meantime... please YELL! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:37:21 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error I don't know whether this is related to your issue,but on one of my boxes I am also getting an interruptstorm with atapicam enabled.On FreeBSD 5.2.1 I did not experience any interruptstorm issues, even if using the same hardware configuration.Have a look at the attached text file for a detaileddescription ...Olivier Certner schrieb:> Hi,> > Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM > (using KsCD)"? Maybe we have fallen on the same kind of bug concerning > atapicam.> > If you have KDE, maybe you should try to reproduce the problem I had. I've no > time to test your scenario (the one with the EIDE drive, I don't have SCSI) > now, but I'll try to reproduce it at the beginning of next week, in order to > see if the freeze happens also on my computer.> > Hope this will help us to progress on our issues.> > Regards,> > Olivier> ___ > freebsd-questions@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to "[EMAIL PROTECTED]"-- Mit freundlichen Gruessen / With kind regardsDAn.I.El S. HaischtWant a complete signature??? Type at a shell prompt:$ > finger -l [EMAIL PROTECTED]___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... 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. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, 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. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- 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. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). 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 get a response from Søren Schmidt <[EMAIL PROTECTED]>, he wrote and maintains the ata stuff iirc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
evices. @@ -242,6 +260,9 @@ device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) +#device disc# discard device (ds0, ds1 etc) + + # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter @@ -251,22 +272,22 @@ device ohci# OHCI PCI->USB interface device usb # USB Bus (required) #deviceudbp# USB Double Bulk Pipe devices -device ugen# Generic -device uhid# "Human Interface Devices" -device ukbd# Keyboard -device ulpt# Printer -device umass # Disks/Mass storage - Requires scbus and da -device ums # Mouse -device urio# Diamond Rio 500 MP3 player -device uscanner# Scanners +#deviceugen# Generic +#deviceuhid# "Human Interface Devices" +#deviceukbd# Keyboard +#deviceulpt# Printer +#deviceumass # Disks/Mass storage - Requires scbus and da +#deviceums # Mouse +#deviceurio# Diamond Rio 500 MP3 player +#deviceuscanner# Scanners # USB Ethernet, requires mii -device aue # ADMtek USB Ethernet -device axe # ASIX Electronics USB Ethernet -device cue # CATC USB Ethernet -device kue # Kawasaki LSI USB Ethernet -device rue # RealTek RTL8150 USB Ethernet +#deviceaue # ADMtek USB Ethernet +#deviceaxe # ASIX Electronics USB Ethernet +#devicecue # CATC USB Ethernet +#devicekue # Kawasaki LSI USB Ethernet +#devicerue # RealTek RTL8150 USB Ethernet # FireWire support -device firewire# FireWire bus code -device sbp # SCSI over FireWire (Requires scbus and da) -device fwe # Ethernet over FireWire (non-standard!) +#devicefirewire# FireWire bus code +#devicesbp # SCSI over FireWire (Requires scbus and da) +#devicefwe # Ethernet over FireWire (non-standard!) -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Sat 01/29, Jason Henson < [EMAIL PROTECTED] > wrote: From: Jason Henson [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Sun, 30 Jan 2005 04:58:31 + Subject: Re: 5.3 interrupt storm (atapicam) and I/O error On 01/28/05 08:38:14, Daniel S. Haischt wrote:> oops, did forget the tixt file ...> > 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.>> >> On FreeBSD 5.2.1 I did not experience any interrupt>> storm issues, even if using the same hardware configuration.>> >> Have a look at the attached text file for a detailed>> description ...>> >> Olivier Certner schrieb:>> >>> Hi,>>> >>> Could you give a look at my post dated 04/01/2005 entitled "Freeze >>> with CAM (using KsCD)"? Maybe we have fallen on the same kind of >>> bug concerning atapicam.>>> >>> If you have KDE, maybe you should try to reproduce the problem I >>> had. I've no time to test your scenario (the one with the EIDE >>> drive, I don't have SCSI) now, but I'll try to reproduce it at the >>> beginn ing of next week, in order to see if the freeze happens also >>> on my computer.>>> >>> Hope this will help us to progress on our issues.>>> >>> Regards,>>> >>> Olivier>>> ___>>> freebsd-questions@freebsd.org mailing list>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>>> To unsubscribe, send any mail to "freebsd-questions- >>> [EMAIL PROTECTED]">> >>> >-- > Mit freundlichen Gruessen / With kind regards> DAn.I.El S. Haischt> > Want a complete signature??? Type at a shell prompt:> $ > finger -l [EMAIL PROTECTED]>> Hello,> > 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.
Re: 5.3 interrupt storm (atapicam) and I/O error
On Saturday 29 January 2005 05:30, ad5gb wrote: > Greetings, > > Not sure what to think about this yet but it definitely has something to do > with having my ATAPI CD connected to the 2nd channel of my Promise Ultra > 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the > kernel will boot with atapicam enabled. I don't seem to be able to use my > motherboard's embedded EIDE controller with the Promise adapter installed. > I don't see any obvious I/O or interrupt conflicts, but I also don't have > too much control over it with this old SuperMicro mainboard. > > Seems odd to me though, since this all worked on 5.2.1. Open for > suggestions, but for now I'm going to try to track down the SCSI I/O error > problem so I can get some CD burning done (critical system backups) and > then I'll see if I can try to figure out if this is an EIDE driver issue or > a atapicam issue. > > If anyone comes up with anything in the meantime... please YELL! > > > Kind regards > > -- > Randall D. DuCharme (Radio AD5GB) > > Powered by FreeBSD! > The Power to Serve > > > > --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: freebsd-questions@freebsd.org > Date: Fri, 28 Jan 2005 14:37:21 +0100 > Subject: Re: 5.3 interrupt storm (atapicam) and I/O error > > I don't know whether this is related to your issue,but on one of my > boxes I am also getting an interruptstorm with atapicam > enabled.On FreeBSD 5.2.1 I did not experience any > interruptstorm issues, even if using the same hardware > configuration.Have a look at the attached text file for a > detaileddescription ...Olivier Certner schrieb:> Hi,> > > Could you give a look at my post dated 04/01/2005 entitled "Freeze > with CAM > (using KsCD)"? Maybe we have fallen on the same kind of bug > concerning > atapicam.> > If you have KDE, maybe you should > try to reproduce the problem I had. I've no > time to test your > scenario (the one with the EIDE drive, I don't have SCSI) > now, but > I'll try to reproduce it at the beginning of next week, in order to > > see if the freeze happens also on my computer.> > Hope this will > help us to progress on our issues.> > Regards,> > > Olivier> ___ > I am also having a shitload of problems on my newly installed 5.3 box (which was a happy camper under 4.x. I have a promise tx2 100 board. there are a pair of disks with a geom stripe over them, Under heavy i/o the system either freezes or crashes. I will have some time later next week to investigate but I am really inclined to use the time to revert to 4.11. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Hello, attached you will find a copy of my custom kernel config which did work without any issue under FreeBSD 5.2.1. As outlined earlier if using this config on FreeBSD 5.3-RELEASE I am getting an interrupt storm while booting the system. The following hardware configuration *won't* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: * harddrive attached to IDE channel #1 * no device attached to channel #2 The following hardware configuration *will* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: Config #1: * harddrive attached to IDE channel #1 * CDROM or CDRW attached to channel #2 Config #2: * CDROM or CDRW attached to channel #1 * harddrive attached to IDE channel #2 Jason Henson schrieb: On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... 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. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, 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. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- 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. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). 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 get a response from Søren Schmidt <[EMAIL PROTECTED]>, he wrote and maintains the ata stuff iirc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.369.2.2 2002/12/31 05:35:45 scottl Exp $ machine i386 #cpuI486_CPU cpu I586_CPU #cpuI686_CPU ident ABYSSONE maxusers512 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options NETATALK
Re: 5.3 interrupt storm (atapicam) and I/O error
Daniel I wonder if you can mount a CD with a GENERIC kernel? I also wonder if you can avoid the "interrupt storm" with your custom kernel but by disabling atapi dma? (hw.ata.atapi_dma="0" in /boot/loader.conf) If this kernel boots, can you mount a CD? If you get some free time and feel like messing around with it, I'd be curious what you find. Regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:38:14 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error oops, did forget the tixt file ...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.> > On FreeBSD 5.2.1 I did not experience any interrupt> storm issues, even if using the same hardware configuration.> > Have a look at the attached text file for a detailed> description ...> > Olivier Certner schrieb:> >> Hi,>>>> Could you give a look at my post dated 04/01/2005 entitled "Freeze >> with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug >> concerning atapicam.>>>> If you have KDE, maybe you should try to reproduce the problem I had. >> I've no time to test your scenario (the one with the EIDE drive, I >> don't have SCSI) now, but I'll try to reproduce it at the beginning of >> next week, in order to see if the freeze happens also on my computer.>>>> Hope this will help us to progress on our issues.>>>> >>> Regards,>>>> Olivier>> >>> ___>> >>> freebsd-questions@freebsd.org mailing list>> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>> To >>> unsubscribe, send any mail to >> "[EMAIL PROTECTED]"> > >>> -- Mit freundlichen Gruessen / With kind regardsDAn.I.El >>> S. HaischtWant a complete signature??? Type at a shell >>> prompt:$ > finger -l [EMAIL PROTECTED]Hello,recently I >>> updated one of my FreeBSD boxes tov 5.3. This box got a builtin >>> Promise PDC20269UDMA133 controller. Actually it's a controllerwith >>> two IDE channels.So far if using the GENERIC kernel that >>> comeswith FreeBSD, I do not experience any problems.If using >>> my own customized kernel I am gettingthe following error message while >>> booting thesystem:8< 8<8<---8<-8<-Interrupt storm detected on "irq10: atapci1";throtteling interrupt source:>8>8>8--->8->8-After some trail-and-error based investigations,I did figure out that if I don't plugin any deviceinto IDE channel two, the just described errordoes not occur.So it has something to do with IDE channel two.As an additional note - The controller worksunder Linux, FreeBSD 5.3 (GENERIC) and FreeBSD5.2.1 (custom kernel).Any hints on how to solve this issue would begreatly appreciated. ___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
